Ancestors

Toot

Written by Desync on 2025-01-25 at 04:56

Love Mastodon but it would be pretty cool if someone made a platform built off ActivityPub with an algorithm. I understand many people don't want an algorithm; that's why they're here, but interoperability between instances is the whole point! Allow someone to choose to have an algorithm, and keep talking to their friends on Mastodon. (Threads doesn't count)

Like Bluesky with ActivityPub

[#]ActivityPub #Mastodon #Algorithm #Algorithms #Twitter #Bsky #Bluesky #Microblogging #w3c #WebStandards

=> More informations about this toot | More toots from desync@social.desyncd.xyz

Descendants

Written by hexaheximal on 2025-01-25 at 05:31

@desync I've been thinking about that for a while now, and in fact in late 2023 I started working on making a project that does that (among other things) but it never really went anywhere.

From a technical perspective, the main issue with this is where to get the posts from and how to determine relevance of any given post: on smaller instances, there are significantly less cached posts to pull from algorithmically as there are less follower relationships and thus less federation.

=> More informations about this toot | More toots from hexaheximal@mastodon.social

Written by hexaheximal on 2025-01-25 at 05:33

@desync While the approach Bluesky takes of having a massive shared heap of everything has its own problems and is largely inefficent (see: https://dustycloud.org/blog/how-decentralized-is-bluesky/), the benefit to that approach is that, if data is synchronized enough, you have all of the posts readily available to algorithmically pull from.

=> More informations about this toot | More toots from hexaheximal@mastodon.social

Written by Desync on 2025-01-25 at 16:08

@hexaheximal yeah this really bugs me. It'd be awesome if it could be fixed in the standard somehow. (I think it's being partially fixed in Mastodon, open pr that fixes part of this/allows replies and interactions to always load on all servers viewing a post) but how a FULL proper fix for this would work while remaining being able to run on my server with 1GB of ram, 1 core and 50GB storage is another issue.

=> More informations about this toot | More toots from desync@social.desyncd.xyz

Written by hexaheximal on 2025-01-25 at 16:12

@desync Not quite. It is by definition impossible to do a full shared heap with the current ActivityPub architecture (unless you somehow manage to follow everyone in the entire fediverse), and as far as I can tell both the people writing the specifications and the people writing implementations of it don't want this because it's largely inefficient.

You can algorithmically pull from who you follow, but at that point you've just reinvented the Home page with extra steps.

=> More informations about this toot | More toots from hexaheximal@mastodon.social

Written by hexaheximal on 2025-01-25 at 16:16

@desync I think the closest you can get to this is by having the instance follow relay bots which automatically boost posts from various places / hashtags, as well as using all public posts that federate with the instance to provide a source of posts.

The main problem with that, however, is that smaller instances will either have difficulty getting enough federation to make it work or have difficulty managing the server resource consumption to make it work properly.

=> More informations about this toot | More toots from hexaheximal@mastodon.social

Written by Desync on 2025-01-25 at 16:17

@hexaheximal Noted! I guess I'll just have to live with these quirks of decentralization. Maybe at some point I'll look into this more so I can understand it better.

=> More informations about this toot | More toots from desync@social.desyncd.xyz