Conversation
Notices
-
@shitpisscum @eris @Moon During the first reply the OP failed to fetch, then someone else interacted with it resulting in successful fetch and the OP appearing out of order.
-
@shitpisscum @Moon @eris Pleroma uses the fetch/delivery time to sort objects, since the timestamp in an object itself can be completely arbitrary and easily faked. This is a downside of that, but it isn't as bad as someone "pinning" the post by setting its date to some distant future, for example.
-
@shitpisscum @eris @Moon I've seen that happen with one of my VMs; due to some shenanigans it was running in local time (UTC+3), but thought it was UTC. Even after I fixed that, I had to wait three hours for the post to move from the very first position in timeline.
-
@mint @eris @Moon
>someone "pinning" the post by setting its date to some distant future
Didn't really think of that lol but yea makes sense
-
@mint @eris @shitpisscum i have seen a post faked to 400 years in the past and arguably all the gnu social posts on my server have faked dates since they predate converting to pleroma
-
@mint @eris @Moon I think I remembet that lol, it was like 5PM local time where I am and that post said 8PM right?