Great question! Unlike Lemmy, which relies on federation with dedicated servers, Plebbit is fully peer-to-peer (P2P) and does not have a central server or even instances. Instead, storage happens via a combination of IPFS and users seeding data. Here’s how it works:
Subplebbit Owners Host the Data (Like Torrent Seeders)
Users Act as Temporary Seeders
IPFS for Content Addressing
PubSub for Live Updates
Feature | Lemmy | Plebbit |
---|---|---|
Hosting Model | Federated servers (instances) | Fully P2P (no servers) |
Who Stores Data? | Instance owners (like Reddit mods running a server) | Subplebbit owners & users (like torrents) |
If Owner Goes Offline? | Instance still exists; data stays up | The community disappears unless users seed it |
Historical Content Availability | Instances keep all posts forever | Older data may disappear if not seeded |
Scalability | Limited by instance storage & bandwidth | Infinite, as long as people seed |
It’s a radical trade-off for decentralization and censorship resistance, but if no one cares about a community, the content naturally dies off. No server, no mods deleting you from a database—just pure P2P.
Hope that clears it up! 🚀
Plebbit only hosts text. Images from google and other sites can be linked/embedded in posts. This fixes the issue of hosting any nefarious content.
Nowhere in the project whitepaper or FAQ does it talk about banning image hosting. Base64 encoding images in the text post is trivial, so maybe OP is the one projecting this intent or feature?
Where can I find the protocol specifications?