Good idea! I'll incorporate something like this in my own Lemmy App.
I'm actually trying to solve this issue on my own Lemmy app. It automatically switches instances when the requested one is down. Works only in the Feed right now and, of course, accounts are still instance-bound - but I will fix that soon.
It also works in Nemmy.
Disclosure that I'm the main Nemmy dev :)
Yeah true. That is probably the correct way to do it.
Off-topic question, but where can you see the stats?
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.
It's in the Settings but the Settings page only works when logged in right now, which will change soon.
If it's not in the Settings just refreshing the page should update Nemmy.
Let me know if that fixes it.
Nice! Thanks for testing it out :).
Could you try loggin in to https://nemmy-git-big-update-cr4yfish-s-team.vercel.app/auth/login?
It's the preview branch of the new update.
Could you try to log in here: https://nemmy-git-big-update-cr4yfish-s-team.vercel.app/auth?
It's the preview website of the next update.
Hm, thanks a lot for telling me. I will take another look at the login code. Seems to have a couple issues.