Conversation

Notices

1. Embed this notice
   BeAware :fediverse: (beaware@social.beaware.live)'s status on Tuesday, 21-May-2024 15:06:32 JST BeAware :fediverse:

   in reply to

   • #?.info :commodore:

   @poundquerydotinfo technically this is not correct. On the back end, there's "job queues" where a job is a sent or received post. Those other servers delayed the jobs for those posts so they'd send when it was online again. Your instance is just getting sent random jobs based on other instances queues. Hope this makes sense.

   • Embed this notice
     #?.info :commodore: (poundquerydotinfo@forum.virctuary.com)'s status on Tuesday, 21-May-2024 15:06:33 JST #?.info :commodore:

     So I have an answer to the question you probably didn't realize was important to begin with:

     Is #Mastodon's view really reverse-chronological? Or is it focusing on making sure I see everything posted by people I follow at least once?

     The answer is the second. My instance was offline for most of the last 48 hours, and as it's been catching up over the last few hours, the content isn't completely in-order. I see stuff I posted 4 hours ago coming lower down compared to content dated 5+ hours ago.

     Which is what you'd want. (Probably) nobody truly wants reverse-chronological: if a network glitch means one server sends its posts two days late to another, we don't want that to all be inserted in our feeds where all the other posts that are two days old are, as we'll miss it if we've already read everything (except those posts) from two days ago.

     It's good to know Mastodon does it the right way.