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

Lemmy.world Support

3293 readers
207 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
 

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
[–] MrKaplan 7 points 1 day ago (3 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.

[–] [email protected] 4 points 1 day ago (1 children)

Hmm... I don't know what would be causing this particular issue on the Cloudflare side, but the fact that lemmy.world shows @[email protected] instead of usernames when viewed with JS disabled suggests that you should review your Cloudflare configuration... At a minimum you have their email filter enabled when it shouldn't be; there could be other issues too.

[–] MrKaplan 1 points 18 hours ago (1 children)

why shouldn't the email filter be enabled?

I have to admit that it doesn't do much for us, as the support emails we have in sidebars and posts are unfortunately federated to other instances where they're not getting obfuscated and will be crawled there, but we do have contact emails on the website. I'm currently not aware of any issues caused by that.

[–] [email protected] 2 points 16 hours ago

It breaks readability of your site without JS. That's particularly bad for the "old" (mlmym) UI which would otherwise be usable for basic interaction without JS entirely, but I find it annoying every time I end up loading a page from lemmy.world directly -- e.g. to check federation.

That's one of the reasons why I'm on reddthat instead of lemmy.world: old.reddthat.com works without JS.

[–] [email protected] 2 points 1 day ago (1 children)

I have seen this on lemm.ee for the past year. It’s rare but happens

[–] MrKaplan 1 points 19 hours ago (2 children)

glad to at least have confirmation that this isn't just us, thanks!

do you remember whether this has still been happening while lemm.ee was on lemmy 0.19.5 or 0.19.8?

[–] [email protected] 2 points 10 hours ago

I have not seen it for a while. I have not seen it for about 6 months. You may want to reach out to Sunaurus over at Lemm.ee to see if he has any info about it.

[–] [email protected] 1 points 18 hours ago

We could maybe open a thread somewhere to try to get additional evidence.

I was thinking about [email protected] , but that would probably get removed as a support question.

Maybe [email protected] ?

[–] PugJesus 1 points 22 hours ago

I've been seeing this for as long as I've been using Lemmy, I assumed it was just some known bug in the code.