Mozilla exits the Fediverse and will shutter its Mastodon server in December

Mozilla’s Mastodon Instance & Shutdown

• Instance reportedly had ~270 active users; many see that as tiny but normal for a federated service, where “small instance” is not inherently a problem.
• Others argue there was no financial upside and the project always looked like a weak “experiment” with poor promotion and long invite-only status.
• Mozilla’s public rationale is unclear in the thread; posters mostly infer internal politics and alignment with big platforms.
• Some note Mozilla has accounts on Threads that are not federated, questioning how this fits with its open‑web mission.

Fediverse UX, Migration, and Structural Issues

• Major criticism: Mastodon migration moves followers/following, but not old posts; archives are exportable but not re-importable as live content.
• Several users only discovered this after migrating, calling it a “fatal” UX flaw that prevents using Mastodon as a primary content store.
• Defenders say migrating historical content would be technically heavy, unreliable, and risky, and point out that other social networks also don’t offer full, portable histories.
• Additional pain points: confusing instance choice, broken or limited global search, lack of reliable trending, and failed/partial follower migrations.

Moderation, Censorship, and Federation Dynamics

• Some praise instance-level moderation and liken it to running a topic-focused message board; users who disagree can join or run another instance.
• Others see “a thousand little fiefdoms” and “tiny tyrants,” with defederation silently breaking relationships between users on different servers.
• There is disagreement on acceptable levels of content control and on whether moderation should be instance-level or primarily user-driven.

Alternatives and Architectural Debates

• ActivityPub/Mastodon criticized as leading to eventual centralization and poor portability; Nostr and Bluesky cited as architecturally better for decentralization and data mobility, though not without tradeoffs.
• Some advocate IndieWeb-like approaches: own a blog, then syndicate to social networks (POSSE).
• Self-hosting (running your own instance) is promoted by some, but others say it’s unrealistic for most users and raises scalability concerns.

Mozilla’s Broader Strategy and Finances

• Multiple comments argue Mozilla should stop pursuing side projects (like mozilla.social) and focus on Firefox, especially dev tools and a reusable engine.
• There is frustration that new initiatives often start and then get shuttered while Firefox loses share.
• Posters debate Mozilla’s reported ~$200M/year “software development” spend and staffing; some claim much of this does not reach Firefox, others call critical sources biased.
• Ideas floated include user-funded models for Firefox, but others doubt enough users would pay given free alternatives and payment friction.

Network Effects, Threads, and the Future of Social

• Network effects are repeatedly cited: Brazil’s Twitter ban example is used to show users flocking to Bluesky/Threads rather than Mastodon.
• Threads’ partial ActivityPub integration is seen by some as “embrace” in a classic “embrace, extend, extinguish” pattern; others dispute historical analogies (e.g., to XMPP).
• Many believe most users primarily care about UX (speed, media quality, notifications) rather than decentralization principles.
• Some expect future federated systems to emerge that learn from Mastodon’s and current fediverse shortcomings.