Conversation

Notices

1. Embed this notice
   Greg Slepak (taoeffect@crib.social)'s status on Monday, 05-Aug-2024 04:33:15 JST Greg Slepak
   I hate to say it, but stability concerns aside, one thing that's keeping users off of the #fediverse is the lack of a algorithmic feed.
   
   #BlueSky is trying to implement this, but their implementation sucks. It doesn't work (see attached).
   
   Most fediverse instances already have the concept of multiple timelines (following, global/federated, etc.). It wouldn't be that difficult to add additional ones that are algorithmically ranked based on engagement.
   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Monday, 05-Aug-2024 04:33:14 JST BeAware :fediverse:

     in reply to

     @taoeffect the bigger instances have the advantage here because it's already a thing on the "trending" page, but it's only calculated by likes originating from your instance.

     Though, I think it's that way because likes are only federated between the instance that the post originates from and the instance that the "like" comes from. So when you see a post with a number of likes, you know that they came from your instance or the post is from your instance.

   • Embed this notice
     Greg Slepak (taoeffect@crib.social)'s status on Monday, 05-Aug-2024 04:41:10 JST Greg Slepak

     in reply to

     • BeAware :fediverse:
     @BeAware Yeah, maybe the protocol could get upgraded where servers periodically send to relays a batch of "most liked posts" along with their like counts. That would reduce traffic while keeping it possible for small servers to generate such feeds.