Earlier quoted context omitted.
> Partly because algorithmic curation is a big business, tied in pretzel knots with advertising, and is marketed by major companies as a huge "improvement" or "user need" (to sell more ads) You might have inadvertently fallen for the fallacy of composition. What to describe is only one type of algorithm; one meant to maximize engagement/revenue. Mastodon has the potential for a user-centric "Bring your own algorithm"…
Mastodon simply cannot be that user centric because the user can only control the subset of the Fediverse that your instance is able and allowed to see. Given that single user instances are largely nonviable due to the abundance of blocking in the 'verse in lieu of adequate spam controls, which ActivityPub fundamentally lacks, your choice of homeserver matters more than anything. And of course, there's no good way to…
Bring your own algorithm can tackle spam (like adblocks). ActivityPub is flexible enough for Mastodon to build up references to algo-providers.
I've been frustrated by Mastodons slow movement on this, I considered approaching the popular clients to implement this. After all, ad-blockers run entirely on the client. A basic standard can be drawn up that governs how to boost or penalize toots' visibility based on keywords, author or instance, based on an updated list is viable today amd can run entirely on the user's device. Web-based clients are more complex, and require patching the standard Masto server or running in a sidecar.