How about a setting?
Have the user choose which one to use.
I know it could be more work to make... but.. i have infinite data on my phone.
Others may only have 2 gb
this post was submitted on 06 Aug 2023
4 points (70.0% liked)
Nemmy
141 readers
12 users here now
Nemmy: The Neat Lemmy App for the Web
This project is focused on building an App with the best possible User Experience.
founded 1 year ago
MODERATORS
Yeah true. That is probably the correct way to do it.
I vote Yes, but also preferably an opt out/settings to reduce data usage.
Wouldn't loading it twice make it slower, then just loading once?
No, actually. Sorry I should've explained more in the post.
The plan is to always send 2 requests, one with user details (to get upvotes, read posts, bookmarks etc) and the other without any personal data.
The one with a JWT attached to the requests can't be server-side cached, since that would be a security risk.
The one without any personal data can however be cached.
So when I first do a server render of any page, almost all content will be cached and served instantly. Then I do a client side fetch of the same data, filling in user data such as bookmarked posts for example.
Effectively, this will make the time until you see posts and stuff much faster.