MrKaplan @ MrKaplan @lemmy.world

other accounts:

---

Read more

Posts

0

Comments

293

Joined

1 yr. ago

Moderating

---

I'll make sure this gets looked at this weekend if it's not picked up by then

the way federation works is typically, when everything works correctly, that the updates go out within the same minute.

iirc this will be resolved in our soon to come lemmy update

local server time is UTC.

time in UTC is included both in the title and the post itself.

incremental backups might also be something worth looking into

we've been observing that in a few cases over the last weeks, we're planning to investigate this in more detail after updating lemmy and our db to a newer version, as that should already improve performance in a few places.

the monitoring alerts aren't very accurate currently, we've been looking into improving them to better reflect reality, although that's still in progress

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.

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.

unfortunately it seems that people are trusting google search results to be accurate without following links.

as far as I can tell this is a combination of reddit returning the subreddit creation date as the timestamp that will show up in search results yet including images of recent posts, which google will then use as an indicator of "the image exists on this page". this will lead to a 7 year old subreddit with recent posts showing as the image being present on a 7 year old search result. if people actually follow the link they'll see it's just a link to the subreddit and not to an individual post.

are there actually this old posts?

this seems like google + reddit being a shitty combination. i'm seeing fewer results but the two results i get that are 7 years old are just links to the subreddit, not to posts, which is likely throwing off the date on there.

other reverse image searches like tineye don't show any prior images, so it's very likely that you're just fooled by misleading search results.

unless you can produce links or other evidence about actual 7 year old content please correct your comment.

I have already commented the same on the other post.

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?