Server side bug with lemmy.world and intermitent authentication.
Server side bug with lemmy.world and intermitent authentication.
I am currently getting signed out every minute from lemmy.world. This is not a client side cache issue. I tested making API calls from the command line (with curl) with no cache and the issue still occurs. One call I get the correct response, the next I get a 400 telling me im not signed in.
I'm primarily testing with the https://lemmy.world/api/v3/user/unread_count api endpoint. I'm not sure if this issue occurs with all endpoints.
Reproduction steps:
- Get a lemmy.world JWT token for your account using your desired method (eg. postman).
curl https://lemmy.world/api/v3/user/unread_count?auth={JWT_TOKEN_HERE}- Note the 400 error. If you do not get an error repeat step 2.
Edit
This issue only seems to affect lemmy.world so a temporary workaround is to use a different instance for the time being.
You're viewing a single thread.
Permanently Deleted
No. This issue goes a lot deeper than your login information.
Permanently Deleted
It's based on my understanding of how servers work and my tests. There is obviously always room for error, but I'm like 99% confident I'm right.
Also AFAIK lemmy doesn't kick you out because you signed in elsewhere.
Permanently Deleted
This is stupid. You might as well ask him to try wishing for it to stop and clicking his heels three times. 🙄
Permanently Deleted
No, no it doesn't. Like, at all. You clearly have no idea what you're talking about, which makes your pithy little 'opinion' comment further down make you look even more stupid.
Permanently Deleted
You're right, I don't need to be, just like you don't need to repeatedly try to talk about shit you clearly don't have a goddamn clue about, yet, here we are
Fwiw, the fix literally yesterday was to change your password in certain app/mobile configurations to force invalidate your old token that was signed by the old key.
Permanently Deleted
I'm done.
One can only hope.