Mastodon announces new European non-profit, change of CEO

Algorithmic curation & feed experience

• Strong divide over algorithms: some see the purely chronological feed as Mastodon’s best feature (less manipulation, less doomscrolling, “it’s okay to miss things”); others see the lack of curation as the main barrier to adoption.
• Pain points without algorithms: prolific posters dominating feeds, time-zone bias, difficulty surfacing “quiet” but valued accounts, and weak discoverability compared to Bluesky/Threads.
• Workarounds: users rely on external tools, lists, filters, and separate feeds; some propose client-side or “bring your own algorithm” models, similar to Bluesky’s pluggable feeds.
• Opponents of algorithms stress that engagement-optimized ranking created ragebait, spam amplification, and addiction on legacy platforms; they prefer explicit user curation and see occasional friction (unfollows, list setup) as “healthy hygiene.”

Governance, nonprofit structure & leadership

• Mastodon is moving ownership to a new European nonprofit after losing charitable status in Germany; exact legal form of the new entity is still undecided.
• The previous structure concentrated control with the founder; the new association-style model is described as more democratic, though some note that even such entities can be tightly controlled in practice.
• The founder stepping down as CEO and moving trademarks/ownership out of personal hands is widely seen as a major, positive governance shift, especially in contrast to other social platforms perceived as “enshittified.”
• Some worry about “control by committee” but others argue it’s preferable to unilateral control by billionaires and better aligned with Mastodon’s federated ethos.

Architecture, federation & identity

• Critics argue Mastodon’s instance-based architecture ties identity and data too tightly to a single server, with only “soft migration” and no robust escape path if a server disappears or refuses cooperation.
• Others counter that federation and local “fiefdom” moderation are features: instances can set their own rules, and users can run viable single-user instances; reports of federation-wide blocking making them “nonviable” are disputed.
• Discoverability and search (handles, keywords) are seen as weak compared to Bluesky’s more modular, DNS-backed identity and protocol design.

UX, clients & technical direction

• Some praise noticeable UX improvements (options for a simpler web interface, system dark-mode support).
• Others criticize dropping the HTML-only interface and requiring JavaScript, citing slower loads, more round trips, and abandonment of progressive enhancement.
• Several point to third-party clients, RSS, and alternative frontends as mitigating factors, but there is concern that Mastodon’s technical direction favors JS-heavy, resource-intensive design.

Funding & ambition

• A planned 5M€ budget raises questions; defenders say it reflects a shift from volunteerism to staffed development, legal work, and trust & safety investment.
• Supporters argue significant funding is necessary if Mastodon is to mature and compete with corporate social media; skeptics want clearer breakdowns and fear overreach.