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.
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.