Why Org Social is the ethical Fediverse alternative

The Fediverse has 3 structural problems: concentration, human cost, and complexity. For example, Mastodon advertises itself as decentralized, but in practice almost 40% of Mastodon's registered accounts live on mastodon.social. Meanwhile, smaller instances depend on volunteers who can burn out or be forced to shut down for not receiving enough donations to keep the servers running. And if you decide to run your own instance, madness awaits. ActivityPub is a complex protocol with a dense specification. Very few people have the technical skills to set up and manage their own instance, and far fewer to incorporate the protocol into their own projects.

Before going any further, it is time to be transparent: I created Org Social, so this article is a partisan defense. That is why every criticism of the Fediverse is backed by sources (you will find them at the end) and Org Social's limitations are listed below, with none of them hidden.

Org Social boils down to a text file called social.org that looks like this:

#+TITLE: My journal
#+NICK: YourNick
#+DESCRIPTION: A brief description about yourself
#+AVATAR: https://example.com/avatar.jpg
#+LINK: https://my-awesome-website.com
#+FOLLOW: https://jane.com/social.org

* Posts
** 2025-04-28T12:00:00+0100
:PROPERTIES:
:LANG: en
:TAGS: emacs org-social
:MOOD: ❤️
:END:

This is my first post on Org Social.

** 2025-04-29T09:30:00+0100
:PROPERTIES:
:LANG: en
:TAGS: welcome decentralized
:MOOD: 🚀
:END:

Loving how my data stays in a plain text file that I fully own.

** 2025-04-29T18:15:00+0100
:PROPERTIES:
:REPLY_TO: https://jane.com/social.org#2025-04-29T17:00:00+0100
:LANG: en
:END:

Good point, Jane! A reply is just a post with a REPLY_TO property.

Your presence and your posts are one and the same file. The specification can be learned in minutes.

You can host it on GitHub Pages, Codeberg, a €5/month server, your own machine, or host.org-social.org, a free hosting service specific to Org Social that gives you a public URL in a minute (quick tutorial to get started on Org Social). You can read it with cat, back it up or migrate it to another server with cp, and edit it with any editor.

And how does a social network without a server work? You add the URL of other people's social.org files to your #+FOLLOW. It is a network of files interlinking with each other. You use a client, or you compose a rudimentary timeline by chaining Unix commands:

grep '^#+FOLLOW:' social.org | awk '{print $NF}' | xargs curl -s | grep '^\*\* ' | sort -r | head

For everything else, like finding out about mentions, replies, and threads from people you don't follow, there are Relays: volunteer nodes that index public feeds and notify your client. They are optional and interchangeable: if a Relay disappears, your file and your followers remain intact.

Why it is more ethical than the Fediverse

Org Social is more ethical than the Fediverse because it fixes the problems by design:

Simplicity: Org Social is a simple text file you can edit with Emacs, Vim, or any other editor you like. If not, there are also visual clients. Compare that with ActivityPub, where implementing the protocol means dealing with fragmented HTTP signatures, JSON-LD variants, and incompatibilities between platforms... In contrast, the complete Org Social specification fits in a README.
Accessibility: the feed can be read by humans and machines. No APIs, no JavaScript, no visibility limited by the instance.
Decentralization: you are a node in the network. The feed is hosted on any web server and anyone can access it; there is no central instance to depend on. In the Fediverse, decentralization is held up by volunteer admins who may burn out and shut down their servers (as happened with mastodon.technology, mozilla.social, and dozens more), taking their users' accounts with them. Here there is no instance that can close; each node costs whatever serving a static file costs.
Richer format: native Org Mode features are used to enrich the social experience, such as tables, code blocks, and links. On top of them, the specification builds threads, mentions, polls, and reactions. And with no character limit: a post can be a single sentence or an entire article.
Your information belongs to you: your social.org is yours in the most literal sense. Your posts, who you follow, and your interactions with the community are recorded in your file, under your control, not on an instance's server. There is no third-party database (your own file already is one). And migrating is not a process.
Real censorship resistance: nobody can deplatform you, except your hosting provider, and in that case it is enough to move the file to another server or provider. No instance, or third party, can defederate you or silence your content without your knowledge.
Human sustainability: no social network is free; in the Fediverse the bill is paid by volunteer admins and moderators who carry ratios of one moderator per thousands of users and well-documented burnout. Org Social does not need anyone to moderate or maintain infrastructure for you: you decide who to follow and everyone serves their own file. So who protects you from harassment and spam? The design itself: your timeline only contains people you chose to follow, and mentions from strangers only arrive if you request them from a Relay, where your client can filter or ignore them without asking anyone's permission.
Honesty about privacy: Mastodon offers DMs and "followers-only" posts that travel without end-to-end encryption and that the admins of both instances can read. Org Social does not promise a privacy it cannot deliver: everything is public by design and you know it from the very first moment.

But not everything is perfect, of course. Org Social does not have all the features of a modern social network:

External media: multimedia content must be hosted elsewhere; the file only links to it.
No private messages: there are no DMs.
Everything is public: by design there are no private posts or protected accounts.
Relay recommended: the user experience improves when connected to a Relay, but it is not mandatory.
Technical barrier: smaller than it looks, but it exists. Hosting the file yourself requires some knowledge, although host.org-social.org hosts it for free and the clients sync it for you (the iOS app is completely visual). Even so, getting started takes a bit more curiosity than creating an account on mastodon.social.

Conclusion

The Fediverse promised to give us back control and only spread it around. It swapped one big platform for thousands of small platforms, each with its own server, its own database, and its own admin to depend on. Mastodon and its derivatives prove that decentralization can be an illusion, because the three problems from the beginning, concentration, human cost, and complexity, are not bad luck, they are consequences of that architecture. Org Social dissolves them by reducing the social network to its minimal unit, a text file that belongs to you. You give up features, that is true; in exchange, your identity, your posts, and your social graph are no longer in the hands of third parties. Ethics here is not a promise of the project, it is a consequence of the design.

I recommend the quick tutorial to take your first steps on Org Social.

Sources

User concentration data: FediDB, mastodon.social and FediDB, Mastodon (checked on July 16, 2026: 3,341,720 registered accounts on mastodon.social out of a total of 8,681,159 on Mastodon, and 267,274 monthly active users out of 967,685).
Volunteer admin and moderator burnout: The Fediverse has a Mental Health Problem and mozilla.social shutting down (TechCrunch).
Mastodon account migration limitations (posts do not transfer, old server required, 30-day cooldown): official Mastodon documentation.
DMs without end-to-end encryption, readable by admins: The Markup, We Joined Mastodon.
Complexity of implementing ActivityPub: Why implementing ActivityPub is hard (Fedify).