From the world of The Boys comes Gen V. Young, aspiring heroes have their physical and moral boundaries put to the test while competing for Godolkin Universi…
From the world of The Boys comes Gen V. Young, aspiring heroes have their physical and moral boundaries put to the test while competing for Godolkin Universi…
Hi realcaseyrollins, please can you ask your server admins to look into their time settings?
Your posts always come from the future (“in 2 hours”) so they stick around at the top of everyone’s feeds until the times agree.
To illustrate
The issue
It doesn’t look like the linked github issue will get resolved any time soon, so it might be easier if Project Segfault fixes it from their end.
Thanks.
It’s an issue with kbin and Lemmy communications. Nothing the user can do about it, but I’ve seen talk about fixing it in other threads.
I was hoping he could message his instance admins to change the time of their server.
I realise it doesn’t fix the underlying issue of Lemmy not checking if the timestamp is sane, but it would work as a short-term fix to stop his posts living at the top of a New feed for 2 hours, above everything else that’s genuinely newer.
Posts from kbin.social don’t have the problem (compare this kbin post with this lemmy post (same timestamp), so a workaround is available.
The other thing he could do in the meantime is post from a Lemmy instance, of course. His posts are all seem to be Lemmy communities anyway.
OPs post was 30 minutes ago…
I doubt your comment had anything to do with it, but maybe it’s fixed now
It’s all relative. This post says it was posted 44 minutes ago, but has comments from 2 hours ago. Because it was posted 2 hours ago: see here