this post was submitted on 01 Sep 2025
611 points (97.5% liked)
Fediverse
36627 readers
201 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's doable on Mastodon but significantly more complicated.
You need crawlers to index posts across the Fediverse (and avoid getting them blocked), personalized recommendation models per user, and you need pre-emptive caching on the user's instance for anything recommended (ideally the crawler would make a cache on behalf of each of the opted-in users' instances, but without content addressing this is a security risk). You also need to poll for edits / deletions.
Doesn't Mastodon already receive the posts?
On Mastodon, your instance doesn't receive posts until somebody on your instance interacts with the account posting it (following the poster, browsing directly to the post, etc).
Feeds with recommendations requires fetching stuff in advance to not be slow and janky. Basically the feed service would need a bot account on your instance and retrieving all popular posts, given the current architecture. Having thousands of these bots across every instance do this would cause a significant performance hit on smaller Mastodon instances when one of their users posts something popular. So you need something different, like a server plugin where the bot fetches the content once and tells all participating Mastodon servers about their cached copy, so they don't all have to hit the hosting instance. But that's a security risk with the Mastodon design.