

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?
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?
that has nothing to do with this issue.
we’re not running any modifications that would impact caching and we don’t have any custom caching logic. we’re only caching what lemmy/lemmy-ui return as cacheable, which suggests that the issue is likely in one of those services, however, i couldn’t find it in either one.
it’s also rare enough that it’s extremely difficult to troubleshoot, as we see people report this maybe once or twice every few months but without any useful information that would allow us to look into this further than trying to find bugs in related code just from the general symptom of seemingly invalid cache.
additionally, the impact of this should be fairly low, as, unless this somehow impacts private messages as well, no data would be returned that isn’t already otherwise public. with this seemingly “just” being a caching issue, there is also no risk at impersonating other users.
nonetheless i agree that this should not be happening in the first place, even if it’s rare and the impact appears limited.
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.
we’re still unsure what might be causing this, but we’ll be updating to 0.19.9 soon. maybe that’ll fix this issue.
could be that it’s the same thing, in this case it’s the result of a user deleting their account.
you seem to be lost.
this community is about lemmy.world, not a general support community.
might still have been related, i guess we’ll never know.
the rule i changed did look like it had some false positives at least, so even if it wasn’t that it should fix issues that could have been experienced by others randomly.
there is a possibility that this was caused by a cloudflare rule that was not scoped narrowly enough to achieve what it’s intended for. does this issue still persist for you?
while it would likely be a good idea to limit this, i don’t see a limit in the code that would prevent from blocking more users. what’s the actual error message you’re seeing?
the existence of an automod bot in a moderator position does not indicate anything about the extent of human moderation.
the human moderators are still active on lemmy and content is being moderated.
are you referring to !nostupidquestions@lemmy.world?
that community is actively moderated and therefore not eligible for transfer, but you’re welcome to reach out to the mod team with your suggestions.
you can also consider creating a new community with a different name if you’re not in agreement with their moderation decisions and can’t/don’t want to discuss that with them.
if you’re referring to another community please link it to make it clear which one it is.
hello @6iiiiii@lemmy.world, are you still reading your notifications?
as far as I can tell you had previously been banned from the community, but it seems that the modlog entry for that had not been created due to a bug in lemmy.
i can see that a moderator has since removed the community ban and i believe you should be able to comment there now.
hi, welcome to your new moderator position :)
hi, welcome to your new moderator position :)
you’re probably looking for the !perchance@lemmy.world community
they’re generally not read. it’s just a bot account.
we need to update the text there to clarify that, it’s come up a few times already, including people reporting automod pms.
in most cases these pms are a result of community moderator actions, so it’s generally recommended to contact the community mods about this.
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.