this post was submitted on 10 Feb 2025
19 points (100.0% liked)

Lemmy.world Support

3301 readers
89 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket Static Badge

You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

founded 2 years ago
MODERATORS
ruud
MrKaplan
jelloeater85
lwadmin
Serinus
19
Lemmy.world appears to have briefly logged me in as a completely different user (twice)? (self.support)
submitted 1 week ago* (last edited 1 week ago) by ivanafterall to c/support
18 comments fedilink hide all child comments
 

The first time it happened, I thought I was crazy and chalked it up to a glitch (i.e. "maybe it's just showing some weird database ID for me as a user or similar"). But this time, it was pretty clearly another user's account. The username was SLVRDRGN or something similar, had a completely different profile picture, etc...but when I went to click on the profile section to see if I had access to the account, the browser refreshed and populated with my account info.

Seems a little concerning potentially, so just thought someone should know. I will try to be faster with a screenshot if it happens again.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 9 points 1 week ago (9 children)

Sounds like a caching issue. If you were logged in as them, profile would work. Feels like it's caching personalised sections, which it should not.

[โ€“] MrKaplan 7 points 1 week ago (8 children)

I already followed various code paths to try and see where Lemmy might be setting incorrect caching headers without finding anything and nothing in the relevant code seems to have been changed between 0.19.3 and newer 0.19 releases.

I'm still unsure if we're just seeing it more frequently due to a larger number of users and us also having a "proper" caching setup and in practice it would happen on other instances as well or whether it's somehow something that others just don't see due to not being on 0.19.3.

load more comments (4 replies)
load more comments (4 replies)