I think a big problem behind the reluctance of alternatives to the strictly chronical timeline on Mastodon is that people fear that too much power is taken out of their hands if they are introduced. But the fact is: it is already the case that we put a lot of trust in administrators to put the correct software in place. A strictly chronological timeline makes one thing less to worry about but basically, it only reduces the symptom of the problem. Instead, I think the real problem needs to be faced: take away the fear of users that their instances are not working as they are supposed to and give them the power to check themselves whether the instances they are on are actually doing what they subscribed to.

As the most important, I think of the following two:

  • Defederation Tool: shows from which other instances your own instance defederated (I think that already exists).
  • Timeline tool: is the timeline curated based on the algorithm the instance proposed.

If these are in place, you could check that you see the right posts by the right instances, which is already a nice thing to know to begin with and would at least me quite content for introducing custom timelines and thereby giving more power to the admins. And with the mentality of this being an important issue, there would always be someone trying to see if an instance is run as promised and most admins wouldn’t bother trying to do bad things.

Additionally, the algorithms would need to be determinstic and data collected by the instance about the user downloadable.

PS: Of course admins are doing a great job here, also given that most of them are volunteers. I’m not saying they are bad people, I’m just saying there need to be tools to control what they are doing if more powerful tools will be introduced to them in the future like custom timelines.

  • blue_berry@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Ignoring the fact that having a proper recommendation AI for every single user would be environmentally disastrous, it would also place much more burden on the ones hosting instances. Keep in mind that most instances are hosted by people who do not earn anything from them and that many bigger instances already had to rent bigger servers because of the influx of people. Adding computationally expansive algorithms in the mix would just increase the cost for the volunteers on top of signing the death of some smaller instances run on a tight budget.

    Ok, I didn’t think of that :(

    It would also be prone to recreating the SEO mess that we can see today on social medias like youtube where, if you want to grow your community, satisfying the algorithm becomes more important than the actual content of your posts.

    I think federation should solve that right? If an instance has to aggressive algorithms it gets defederated and people leave.

    However, I would have no issues with an algorithm that a user of an instance could run on their devices and tweak to their liking. This solution would probably be less convenient but would avoid most of the mess.

    That would be cool

    • waffle@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      It would also be prone to recreating the SEO mess that we can see today

      I think federation should solve that though?

      Ah, yeah you’re probably right my bad. Big data isn’t my speciality so I can’t say much about that :/