Plaid_KaleidoscooeTime Travel? Or something funky with my backend?
cerevantI think Kbin has posts labeled with local time, while Lemmy uses UTC. So if the Kbin instance is east of your location, recent posts will appear to be from the future.
This probably won’t be fixed until spammers figure out how to exploit it.
For fedio.io, the issue is mentioned here
It also happens with posts from project.sefau.lt to movie&tv at lemmy.film
It’s not some minor thing btw: those posts will be stuck a the top of everyone’s New feed for however many hours it takes to time out, above any other post, irrespective of where and when posted.
Lemmy timestamps Fedia.io users' actions 2 hours in the future
When interactions by Fedia.io users federate onto Lemmy instances, Lemmy says they happen two hours in the future. This results in threads and posts that were posted "in 2 hours". It effectively pins Fedia.io users' threads at the top of Lemmy's "hot" and "new" sorts for two hours after they receive a single upvote from anywhere. There is an issue open for open on Lemmy: https://github.com/LemmyNet/lemmy/pull/3496 When discussing this in @[email protected], @[email protected], and @[email protected] , the consensus is that there are two problems: 1. Fedia.io is probably sending an incorrect time zone to Lemmy, like mistaking Germany's UTC+2 as UTC+0. 2. Lemmy doesn't notice when federated actions have invalid timestamps This is frustrating to some Lemmy users whose feeds become dominated by Fedia.io users' threads. Some are beginning to block the more active Fedia magazines over this bug.
Oh wow, ok. Thank you for the info. I wasn’t really sure what to search for since I don’t know how these things work. Just wanted to make sure that using the recent “old lemmy” thing wasn’t causing me issues.
Have a good day!