Bitsocial is meant to grow into thousands of apps, tools, and services built by anyone, not approved by gatekeepers. Explore what’s live now, then submit your own.
Decentralized imageboards with direct web, APK, and desktop downloads.
5chan is the first public Bitsocial client. It recreates the anonymous imageboard flow on a peer-to-peer network: boards, threads, image posting, community moderation, and multiple public mirrors without relying on a central server.
Forum-style Bitsocial client with web, APK, and desktop builds.
Seedit brings Reddit-style discussion to Bitsocial with threads, identities, community management, and multiple distribution paths. It is the fastest way to try the forum side of the network from a browser, Android phone, or desktop app.
Board administration tooling for custom 5chan communities.
5chan Board Manager connects to Bitsocial CLI to help administrators create, configure, and moderate custom imageboard boards. It is the utility layer for board owners who want operational control.
OpenAI-compatible moderation checks against each community's rules.
AI Moderation Challenge evaluates Bitsocial comment content against community.rules with an OpenAI-compatible model endpoint. Communities can route risky posts to review while keeping provider keys and prompts in private node settings.
Command-line control for nodes, communities, and automation workflows.
Bitsocial CLI is the official terminal interface for the protocol. Use it to manage nodes, publish content, start a WebSocket JSON-RPC server for programmatic control and code automation, automate admin flows, and work directly against Bitsocial primitives without a GUI client.
Feed bots that relay new Bitsocial posts into Telegram channels or groups.
Bitsocial Telegram Bots monitor client community lists and forward new posts into Telegram destinations with inline links back to Bitsocial clients. The active bot covers 5chan feeds today, with the repo structured to add more client-specific bots over time.
Custom image captchas for communities that want human verification.
Captcha Canvas Challenge generates visual captchas that communities can plug into their own publishing flow. It is a lightweight option for communities that want direct human checks without giving up self-hosted moderation.
On-chain gating for communities that want token or contract checks.
EVM Contract Call verifies publications by calling an EVM contract before a post is accepted. It lets communities build token gates, staking rules, or other on-chain checks into their moderation flow.
NFT-backed access control for communities that need stronger anti-spam gates.
Mintpass is a flexible authentication layer for Bitsocial communities. It lets moderators mix NFT ownership, verification flows, and custom challenge modules without pushing everyone onto a central login system.
Centralized risk scoring layer for filtering abusive publications.
Spam Blocker evaluates publications and returns a risk score that communities can combine with their own moderation logic. It is useful when you want a pragmatic extra layer before building more custom anti-spam rules.
Invite-style voucher codes for communities that prefer controlled growth.
Voucher Challenge lets moderators distribute trusted voucher codes that unlock publishing without a global identity provider. It is a good fit for invite-driven communities, niche boards, and gradual rollouts.
{"locale":"en","dir":"ltr","url":{"pathname":"/apps","search":"","hash":""},"i18n":{"resources":{"hero":{"tagline":"<openSource>Bitsocial is an open-source</openSource> <p2p>peer-to-peer network</p2p> <socialApps>for social apps</socialApps>, <noServers>with no servers</noServers>, <noBans>no global bans</noBans>, <crypto>where users and communities are cryptographic property.</crypto>","readDocs":"Read Docs","exploreApps":"Explore Apps","taglineSegments":{"openSource":"Bitsocial is an open-source","p2p":"peer-to-peer network","socialApps":"for social apps","noServers":"with no servers","noBans":"no global bans","crypto":"where users and communities are cryptographic property."}},"nav":{"apps":"Apps","docs":"Docs","status":"Stats","language":"Language","theme":"Theme","sourceCode":"Source code","newsletter":"Newsletter"},"languageSelector":{"title":"Select Language","searchPlaceholder":"Search languages...","noResults":"No languages match your search."},"mailingList":{"title":"Stay in the Loop","description":"Get notified about protocol milestones, new Bitsocial apps, and ecosystem updates. Low frequency, high signal.","placeholder":"you@example.com","inputLabel":"Email address","subscribe":"Subscribe","subscribing":"Subscribing…","success":"You’re on the list!","confirmationSent":"Check your email to confirm your subscription.","privacy":"No spam, ever. Unsubscribe anytime.","error":"Subscription failed. Please try again.","unavailable":"Newsletter signup is temporarily unavailable."},"footer":{"tagline":"Open Source P2P Network for Social Apps","bottomTagline":"Decentralize All Social Media","explore":"Explore","apps":"Apps","docs":"Docs","status":"Stats","resources":"Resources","blog":"Blog","about":"About Us","newsletter":"Newsletter","community":"Community","github":"GitHub","twitter":"Twitter","telegram":"Telegram","contribute":"Improve this page","privacy":"Privacy"},"features":{"title":"Core Features","items":{"open-source":{"description":"Bitsocial is <strong>free and open source</strong> software: the protocol and clients are public, forkable, and open to outside contributions. <strong>Anyone can inspect the code</strong>, ship improvements, or build a compatible app without asking permission from a company.","cta":"Browse source code"},"peer-to-peer":{"description":"Bitsocial is <strong>neither federated nor on-chain</strong>. Each community is a peer-to-peer swarm using <ipfs>IPFS</ipfs>, <strong>closer to BitTorrent</strong> than a hosted website: users seed effortlessly, nodes run on cheap hardware, and each community is fully independent and sovereign.","cta":"Learn how p2p works"},"social-apps":{"description":"Anyone can build a Bitsocial app with its own interface, discovery model, or defaults. Apps compete on product quality instead of locking users into a private database, because compatible clients can <strong>share the same communities, identities, and network</strong>.","cta":"Explore apps"},"no-servers":{"description":"Bitsocial does not require every community to rent a datacenter box, buy a domain, or manage SSL just to stay online. A community node can run from home on consumer hardware, and <strong>there is no single company-run backend that can take the whole network down</strong>.","cta":"Check network stats"},"no-global-bans":{"description":"Moderation still exists, but it stays local. Community owners set rules for their own spaces and apps can choose what they index or show, yet <strong>there is no protocol-level super-admin</strong> who can erase a profile or seize a community from the network itself.","cta":"Read moderation notes"},"cryptographic-property":{"description":"Profiles and communities are controlled by private keys, not by revocable platform accounts. You can delegate hosting without giving away ownership, so <strong>your identity and community behave more like wallet-controlled property</strong> than a username rented from a company.","cta":"Read ownership notes"}}},"sanctuary":{"sectionLabel":"Sanctuary Communication","headline":"It just works.","supporting":"No servers to rent. No domains to buy. No chains to sync. A Bitsocial node runs on a Raspberry Pi. And each community can enforce its own anti-spam challenge: captchas, reputation, SMS, payments, tokens, IP checks, or anything else that can be coded.","approaches":{"federated":{"label":"Federated","subtitle":"Bluesky, Mastodon, Lemmy"},"blockchain":{"label":"Chain / Hub","subtitle":"Farcaster, Lens, DeSo, Steemit"},"bitsocial":{"label":"Bitsocial","subtitle":"Pure P2P with arbitrary anti-spam challenges"}},"rows":{"selfHostingCost":{"label":"Self-hosting cost","federated":"Server + domain + SSL","blockchain":"Expensive node, hub, or RPC","bitsocial":"Extremely cheap, runs on Raspberry Pi"},"whoKeepsOnline":{"label":"Who keeps it online","federated":"Service / instance operator","blockchain":"Chain, hub, or RPC infrastructure","bitsocial":"Community owners + helper seeders"},"scalingModel":{"label":"Scaling model","federated":"Bigger instances, higher bills","blockchain":"More state, heavier infra","bitsocial":"More peers, more bandwidth"},"customAntiSpam":{"label":"Custom anti-spam logic","federated":"Not built into the protocol","blockchain":"Tied to chains, hubs, or fees","bitsocial":"Built in: challenge can be anything"},"takedownChokePoints":{"label":"Takedown choke points","federated":"Host, registrar, SSL, DDoS provider","blockchain":"Validators, hubs, RPCs","bitsocial":"No single choke point"}},"quote":"Your community literally cannot be banned or blocked by anyone, even a government. We solve that problem.","quoteAttribution":"— Esteban Abaroa, Bitsocial founder","deepComparison":{"prompt":"See deep comparison with:","go":"Go","modalEyebrow":"Deep comparison","modalTitle":"{{service}} vs Bitsocial","close":"Close deep comparison","tableCaption":"Concise sourced comparison table for {{service}} vs Bitsocial","table":{"topic":"Topic","bitsocial":"Bitsocial"},"services":{"nostr":"Nostr","bluesky":"Bluesky","mastodon":"ActivityPub / Fediverse","lemmy":"Lemmy","farcaster":"Farcaster","lens":"Lens","deso":"DeSo","steemit":"Steemit"},"rows":{"identity":{"label":"Human names","nostr":"Your account is a long public key; readable names need extra providers.","bluesky":"Readable handles are DNS names; the DID document points apps to the account's current server.","mastodon":"Your readable handle includes a server, so moving servers can change your address.","farcaster":"Farcaster usernames are protocol registrations with app signer keys.","lens":"Lens names follow wallet, app, and chain infrastructure.","deso":"A DeSo profile follows a public key, but the social history lives on the DeSo chain.","steemit":"A Steem username is readable, but tied to Steem's account system.","bitsocial":"Keys stay yours, and .bso names can point to people or communities.","detail":"Nostr's base identity is a public key, which is portable but hard to remember. Readable names are useful, but they are added through separate conventions and providers. Bitsocial also uses public keys while adding .bso names, so a person or community can have a readable identity without a central account provider.","detailBluesky":"Bluesky has a real improvement over raw public keys: DIDs plus readable handles. The tradeoff is that handles are DNS names and the DID document still advertises the user's current PDS. Bitsocial keeps cryptographic ownership while adding .bso names for people and communities.","detailMastodon":"Mastodon handles are readable because WebFinger turns @user@domain into an ActivityPub actor URI. The domain matters: the same username on another server is a different account. Mastodon can redirect or move followers to a new account, but posts and media do not move. Bitsocial keeps cryptographic ownership and adds .bso names for people and communities.","detailFarcaster":"Farcaster IDs, custody addresses, signer keys, storage registration, and usernames are anchored onchain. That gives accounts cryptographic portability, but the identity is still a protocol registration with app-managed signer paths and paid storage. Bitsocial keeps cryptographic ownership while adding .bso names for people and communities.","detailLens":"Lens accounts live on Lens Chain, and V3 treats every EVM account as a profile with usernames and social primitives available through apps. That is much friendlier than raw public keys, but the readable identity still follows wallet, chain, app, and indexer infrastructure. Bitsocial keeps cryptographic ownership while adding .bso names for people and communities.","detailDeso":"DeSo identity is controlled by a public key, and apps can sign actions through DeSo Identity. That gives portability across DeSo apps, but the human profile and social history are still DeSo-chain objects that every serious node or indexer has to carry. Bitsocial keeps cryptographic ownership while adding .bso names for people and communities.","detailSteemit":"Steem accounts are readable names with hierarchical keys, including posting, active, owner, and memo permissions. That is practical for a blockchain app, but the identity is still a Steem account rather than a portable person or community name. Bitsocial keeps cryptographic ownership while adding .bso names for people and communities."},"dataLayer":{"label":"Data hosting","nostr":"Relays keep posts online and deliver them to readers.","bluesky":"Public posts live on a Personal Data Server, then relays and AppViews index them.","mastodon":"Posts are hosted by an instance, then federated as ActivityPub objects.","farcaster":"Identity is onchain, while casts and social messages are stored by hubs or Snapchain.","lens":"Profiles, graph, feeds, groups, and rules live in Lens smart-contract primitives.","deso":"Profiles, posts, comments, follows, and reactions are written as DeSo transactions.","steemit":"Posts, votes, rewards, and account actions are written to the Steem blockchain.","bitsocial":"Users can fetch and share posts directly with each other.","detail":"Nostr posts are portable because users control their keys, but a server still has to keep the posts online. In normal Nostr use, that job belongs to relays. Bitsocial separates finding people from carrying the data: small lookup services can help find peers, then users fetch and share the content directly.","detailBluesky":"Bluesky's repo design is one of its strongest parts: public records are signed, portable, and exportable. But the authoritative host is still the current PDS, and the normal app experience depends on relays and AppViews. Bitsocial starts with peer-to-peer content sharing instead of server-hosted account repos.","detailMastodon":"ActivityPub actors live on servers with inboxes and outboxes. In Mastodon, ActivityPub Notes and Questions become statuses and polls that the instance stores, serves, and delivers to other servers. That is much more open than one central platform, but the normal data host is still an always-online server. Bitsocial starts with peer-to-peer content sharing instead.","detailFarcaster":"Farcaster keeps the account identity and storage accounting on OP Mainnet, while casts, follows, reactions, and profile updates are signed messages stored and replicated by hubs or Snapchain. That makes it lighter than a fully onchain social network, but the normal data layer is still a server network. Bitsocial starts with peer-to-peer content sharing instead of hub-hosted social state.","detailLens":"Lens has moved toward Lens Chain and a V3 model with account, feed, graph, group, namespace, action, and rule primitives. That gives developers powerful shared infrastructure, but social state still goes through chain and protocol primitives plus their indexers. Bitsocial starts with peer-to-peer content sharing instead of chain-hosted social state.","detailDeso":"DeSo's strongest claim is that identities, profiles, posts, comments, likes, follows, and related social data are stored directly on its purpose-built blockchain. That removes a single app database, but it also means each social action becomes transaction-shaped data that nodes and indexers have to keep carrying. Bitsocial starts with peer-to-peer content sharing instead of writing every social action to a global ledger.","detailSteemit":"Steemit runs on Steem, so posts, comments, votes, rewards, and account operations are blockchain actions served through Steem nodes and front ends. That makes the record public and portable across Steem apps, but the normal data layer is still the Steem chain plus API nodes. Bitsocial starts with peer-to-peer content sharing instead."},"communityModel":{"label":"Who accepts posts?","nostr":"A group depends on relays and apps agreeing which posts count.","bluesky":"Community-like spaces are built through feeds, lexicons, or app features, not P2P objects with their own gate.","mastodon":"A Fediverse community is still defined by the app or instance that accepts and announces its posts.","farcaster":"Channels are app/client layers, not communities that accept posts themselves.","lens":"Groups and feeds can have rules, but acceptance runs through Lens infrastructure.","deso":"A node can curate a feed, but communities are views over global transaction data.","steemit":"Communities can organize posts, but Steem accounts and chain rules accept them.","bitsocial":"The community is the thing you post to; it accepts or rejects posts itself.","detail":"Nostr can build group features, but the group still depends on relays and apps agreeing on what belongs there. That is fragile for forum-style communities. Bitsocial lets the community accept posts directly, which fits forums, imageboards, and subreddit-style spaces better.","detailBluesky":"Bluesky can build groups, forums, and community feeds through lexicons, AppViews, and feed generators. That still leaves the community dependent on services that index and interpret records. Bitsocial treats the community as the addressed object: its node validates posts and publishes the accepted state.","detailMastodon":"ActivityPub lets different apps interoperate, but the server software still decides what a community means. Mastodon is mostly profile and timeline based. Lemmy adds ActivityPub Groups for forum communities, but the Lemmy instance still accepts, stores, and announces the posts. In Bitsocial, the community is the object you post to: its node checks the posting gate and publishes the accepted thread state. That is the difference: the rule belongs to the community, not just the app or instance hosting it.","detailFarcaster":"Farcaster's base protocol stores user messages and relationships. Channels and community-like spaces are client or app conventions layered on top, so the posting gate depends on the app and indexing path users choose. Bitsocial treats the community as the addressed object: its node validates posts and publishes the accepted state.","detailLens":"Lens is stronger than many social protocols here: V3 includes groups, feeds, namespaces, and rules that can restrict interactions. The tradeoff is that acceptance still runs through Lens chain/protocol primitives, apps, and indexers. Bitsocial treats the community as the addressed object: its node validates posts and publishes the accepted state.","detailDeso":"DeSo nodes can create their own feeds over the shared firehose, which helps discovery and curation. But the community is still a curated view over global chain transactions, not a P2P object that owns its own acceptance gate before new posts enter. Bitsocial treats the community as the addressed object: its node validates posts and publishes the accepted state.","detailSteemit":"Steem communities can organize posts and mute content through community operations, and front ends can choose what to show. The underlying post is still accepted as a Steem account and chain operation, not by a P2P community object with its own gate. Bitsocial treats the community as the addressed object: its node validates posts and publishes the accepted state."},"moderation":{"label":"Censorship points","nostr":"If major relays stop carrying you, many users may never find your posts.","bluesky":"The account host, relay, or AppView can block the normal path to your audience.","mastodon":"Instance admins can limit local accounts or block whole remote servers.","farcaster":"Clients, APIs, channels, and hub/index access can shape what users actually see.","lens":"Apps can filter, contracts can enforce rules, and interfaces still decide what users see.","deso":"The chain keeps public data; node operators pay to index and filter what users see.","steemit":"The chain keeps the record, but front ends, votes, witnesses, and communities shape reach.","bitsocial":"A community can stay reachable while peers keep sharing it.","detail":"A Nostr key can survive a relay ban, but visibility still depends on the relays, search services, and apps people actually use. If those places stop carrying you, the account exists but the audience may not see it. Bitsocial removes the relay as the center of power: users can keep sharing a community through different discovery paths as long as peers keep it online.","detailBluesky":"Bluesky separates account hosting, relay distribution, and AppView indexing. That helps portability, but it also creates several visibility gates that ordinary users rarely change. A PDS can refuse service, relays can stop carrying data, and AppViews can hide or ignore records. Bitsocial keeps reach closer to the community and its peers.","detailMastodon":"Mastodon moderation is local to each server: one admin cannot delete a remote account globally, but they can hide, limit, suspend, or domain-block what their own users see. If influential servers block an instance, reach can collapse for many users. Bitsocial keeps reach closer to the community and the peers still sharing it.","detailFarcaster":"Farcaster messages are valid if they satisfy protocol rules, but what users actually see is shaped by clients, APIs, channels, indexers, and moderation systems around the protocol. That reduces global deletion risk, but visibility still follows the popular surfaces. Bitsocial keeps reach closer to the community and the peers still sharing it.","detailLens":"Lens can enforce rules in protocol primitives, and each interface can also apply its own terms, filters, and ranking. That gives flexibility, but users still depend on apps, indexers, RPCs, and protocol governance for visibility. Bitsocial keeps reach closer to the community and the peers still sharing it.","detailDeso":"DeSo's public chain can keep content from disappearing from every node at once, but node operators still need to run and index the growing ledger before deciding what to expose, hide, rank, or make compliant. Bitsocial keeps reach closer to the community and the peers still sharing it.","detailSteemit":"Steem makes the chain record hard to erase, but front ends, witnesses, community moderators, downvotes, reputation, and reward rules shape what people find and trust. Bitsocial keeps reach closer to the community and the peers still sharing it."},"contentDiscovery":{"label":"Finding content","nostr":"Discovery often follows the relays and search services with the most data.","bluesky":"Discovery depends on AppViews, search indexes, feeds, and client defaults.","mastodon":"Search and timelines depend on what your instance has seen, cached, and chosen to show.","farcaster":"Discovery depends on clients, channels, APIs, and indexers built over hub data.","lens":"Discovery depends on Lens apps, APIs, indexers, graphs, feeds, and app defaults.","deso":"Discovery depends on nodes and feeds that can afford to index the growing chain.","steemit":"Discovery depends on front-end feeds, tags, communities, rewards, and ranking.","bitsocial":"Discovery finds peers; it does not become the place that owns the content.","detail":"Nostr discovery works best when popular relays, search relays, and apps already have the data. That gives the best-connected services extra power over what people find. Bitsocial discovery only helps find peers. It does not need to host the content, own the community, or become the place everyone must trust.","detailBluesky":"Bluesky's own architecture puts feeds, search, and aggregate views in AppViews and related services. That makes discovery powerful, but visibility follows whichever aggregators the app uses. Bitsocial discovery services only return peer addresses. They do not need to host the content, own the community, or decide what everyone sees.","detailMastodon":"ActivityPub delivers activities to actor inboxes and shared inboxes, so discovery naturally depends on what servers receive, cache, index, and choose to show. Mastodon users can also filter users, keywords, and whole domains. Bitsocial discovery services only return peer addresses; they do not need to host content or decide what everyone sees.","detailFarcaster":"Farcaster discovery usually happens through clients, channels, recommendation systems, APIs, and indexed hub or Snapchain data. The protocol data can be open, but the practical discovery layer is still whichever app and indexer the user uses. Bitsocial discovery services only return peer addresses; they do not need to host content or decide what everyone sees.","detailLens":"Lens gives developers shared graphs, feeds, groups, APIs, and indexers, which is useful for building social apps. But discovery still follows the Lens app, API, indexer, feed, and graph choices users enter through. Bitsocial discovery services only return peer addresses; they do not need to host content or decide what everyone sees.","detailDeso":"DeSo nodes can expose different feeds over the same open chain data. That makes curation competitive, but discovery still follows the node or feed view that can keep indexing and serving the growing transaction history. Bitsocial discovery services only return peer addresses; they do not need to host content or decide what everyone sees.","detailSteemit":"Steemit discovery is driven by front-end feeds, tags, communities, rewards, votes, and ranking. Those mechanisms are useful, but they make visibility depend on Steem-specific economics and interfaces. Bitsocial discovery services only return peer addresses; they do not need to host content or decide what everyone sees."},"replies":{"label":"Spam replies","nostr":"Spam can reach the thread first. Cleanup usually happens after.","bluesky":"Spam is limited by servers, then handled by labels and AppView moderation.","mastodon":"Spam reaches servers first, then filters, reports, and moderators respond.","farcaster":"Valid signed casts can enter hubs; apps moderate visibility after the fact.","lens":"Replies are protocol interactions; app and rule choices determine visibility.","deso":"A spam comment can become an onchain transaction before filters hide it.","steemit":"A valid comment can enter the chain; voting and moderation happen after.","bitsocial":"A community can challenge posters first and reject spam before it appears.","detail":"Nostr can show which key wrote a reply, but publishing and moderation are separate. A relay or app can hide junk after it arrives. Bitsocial gives the community a front door: complete the challenge, or the reply is never accepted into the thread.","detailBluesky":"Bluesky uses PDS limits, moderation labels, and AppView choices to reduce abuse. Those defenses are useful, but they are server and indexing-layer defenses. Bitsocial gives the community a front door: complete the challenge, or the reply is never accepted into the thread.","detailMastodon":"ActivityPub does not define a universal anti-spam gate. The spec recommends server-side filtering, and Mastodon adds signup limits, email confirmation, reports, blocks, filters, and domain moderation. Those tools help, but they usually work at the server or visibility layer. Bitsocial lets a community challenge a poster before the reply is accepted.","detailFarcaster":"A Farcaster reply is a signed message accepted when the FID, signer, and storage rules check out. Storage rent limits volume, but it is not a community-owned challenge before each reply. Bitsocial gives the community a front door: complete the challenge, or the reply is never accepted into the thread.","detailLens":"Lens can attach rules to feeds, groups, accounts, and posts, so it can block or restrict some interactions. That is useful, but it is still smart-contract and app rule execution, not a P2P community challenge chosen and run by the community node itself. Bitsocial gives the community a front door: complete the challenge, or the reply is never accepted into the thread.","detailDeso":"A DeSo comment is an onchain transaction. Nodes and moderation services can filter what they show, but junk can still become part of the shared ledger, adding cost and data that future nodes and indexers have to carry. Bitsocial gives the community a front door: complete the challenge, or the reply is never accepted into the thread.","detailSteemit":"A Steem comment can enter the chain if the account has resources and signs the operation. Communities and votes can suppress it afterward, but the anti-spam path is mostly post-acceptance. Bitsocial gives the community a front door: complete the challenge, or the reply is never accepted into the thread."},"antiSpam":{"label":"Community rules","nostr":"Rules depend on the relay or app people happen to use.","bluesky":"The app can filter content, but the community cannot require its own challenge first.","mastodon":"Rules belong to the instance, the user, or a domain blocklist.","farcaster":"Storage rent raises spam cost, but community gates are app or channel policy.","lens":"Rules can be programmable, but the gate lives in Lens contracts and apps.","deso":"Rules mostly filter chain data after transactions already exist.","steemit":"Rules mostly rely on chain resources, voting, reputation, and later moderation.","bitsocial":"Rules belong to the community, so accepted posts pass the same gate.","detail":"On Nostr, a relay can set rules for that relay, and an app can filter what that app shows. Those rules do not truly belong to the community. Bitsocial lets each community choose the gate for posting, such as account age, reputation, captcha, whitelist, payment, or another challenge.","detailBluesky":"Bluesky moderation is built around labels, AppViews, and service rules. That can hide, rank, or limit content, but it is not the same as a community-owned pre-post gate. Bitsocial lets each community choose the gate for posting, such as account age, reputation, captcha, whitelist, payment, or another challenge.","detailMastodon":"Mastodon gives instance admins, moderators, and users many controls: filters, mutes, blocks, reports, server-wide limits, and suspensions. They are powerful federation controls, but they are not a portable community-owned pre-post gate. Bitsocial lets each community choose its posting challenge, so accepted posts pass the same rule before entering the thread.","detailFarcaster":"Farcaster's storage registry makes spam more costly and clients can filter or moderate channels, but the rule is not owned by each forum-style community as a pre-post gate. Bitsocial lets each community choose the gate for posting, such as account age, reputation, captcha, whitelist, payment, or another challenge.","detailLens":"Lens rules are powerful and programmable, but they live as protocol and app primitives on Lens Chain. For a forum-style community, that still means depending on the chain, app, and indexer path to enforce and display the rule. Bitsocial lets each community choose the gate for posting, such as account age, reputation, captcha, whitelist, payment, or another challenge.","detailDeso":"DeSo moderation is intentionally open: every node can choose the subset of public chain data it exposes, and external labelers can participate. That helps filtering, but it usually happens after a signed transaction has entered the shared chain. Bitsocial lets each community choose its posting challenge, so accepted posts pass the same rule before entering the thread.","detailSteemit":"Steem has account resources, voting, reputation, muting, and community moderation. Those tools can discourage or hide spam, but they usually work through chain economics and post-acceptance curation rather than a community-owned pre-post gate. Bitsocial lets each community choose its posting challenge, so accepted posts pass the same rule before entering the thread."},"scalingEconomics":{"label":"Scaling costs","nostr":"High traffic pushes more server and bandwidth cost onto relays.","bluesky":"Growth pushes load onto account servers, relays, AppViews, and feed services.","mastodon":"Growth pushes storage, federation, streaming, and moderation cost onto instances.","farcaster":"Growth pushes load onto hubs, storage rent, APIs, and indexers.","lens":"Growth pushes load onto Lens Chain, storage, indexers, RPCs, and app backends.","deso":"Each social action is a transaction, so node and index costs keep climbing.","steemit":"Growth pushes more posts, votes, rewards, API load, and moderation work onto Steem infrastructure.","bitsocial":"More readers can also mean more people helping share the content.","detail":"In Nostr, relays are still the servers keeping posts online and sending them to readers. A popular post can be great for users while becoming expensive for relay operators. In Bitsocial, readers can also help distribute the content they read, so popularity can add capacity instead of only adding server cost.","detailBluesky":"ATProto deliberately uses servers for convenience and availability. Relays aggregate firehoses, AppViews index the network, and custom feeds often consume the firehose. Official docs describe relays and AppViews as resource intensive, and relay operations have already needed scaling work. Bitsocial uses routers only to find peers; readers can help carry the content.","detailMastodon":"A Mastodon server needs a domain, always-online hosting, email, database, Redis, background workers, streaming, and often object storage. Mastodon can scale horizontally, but that means operating more app servers, workers, databases, queues, and moderation capacity. Bitsocial uses routers only to find peers; readers can help carry the content they read.","detailFarcaster":"Farcaster avoids putting every social action onchain, but hub or Snapchain nodes, storage accounting, APIs, and indexers still need to replicate and serve a large public social graph. Popularity increases those operator costs. Bitsocial uses routers only to find peers; readers can help carry the content they read.","detailLens":"Lens is built for scalable SocialFi with Lens Chain, ZK infrastructure, storage, APIs, and indexers. That is more scalable than posting everything to a general L1, but growth still concentrates load in chain, RPC, indexing, storage, and app infrastructure. Bitsocial uses routers only to find peers; readers can help carry the content they read.","detailDeso":"DeSo optimizes a blockchain for social storage, but that means posts, comments, likes, follows, and other social actions become transactions. The official node FAQ already describes a large node baseline and database plus transaction-index growth, so popularity raises the hardware and indexing bar for operators. Bitsocial uses routers only to find peers; readers can help carry the content they read.","detailSteemit":"Steem offers fast blocks and resource-based free transactions, but scaling still means more chain history, more API node work, more witness infrastructure, and more front-end moderation and ranking load. Bitsocial uses routers only to find peers; readers can help carry the content they read."},"browserMobile":{"label":"First post","nostr":"A web client feels simple only while its relay choices work.","bluesky":"The easy path is a hosted account with that provider's limits and rules.","mastodon":"You post through the server account you chose.","farcaster":"First post usually starts through an app that manages signers, storage, and hubs.","lens":"First post usually starts through a Lens app, wallet, RPC, and indexer path.","deso":"The easy path signs a social transaction through DeSo Identity and a hosted node API.","steemit":"First post starts with Steem account keys and a Steem front end or API node.","bitsocial":"You can start with a local key, without making a server own your identity.","detail":"Nostr can feel easy when a good web client has good relays already configured. The hidden dependency remains: those relays must accept, store, and serve the activity. Bitsocial can create the user's key locally and let the app choose direct peer-to-peer or hosted access without making an account server own the identity.","detailBluesky":"Bluesky is easy when bsky.social or another PDS handles accounts, sessions, writes, and hosting. That convenience is server-based, and hosted services apply their own API limits and policies. Bitsocial can create the user's key locally and let the user post through direct P2P or optional hosted access without a platform account owning the identity.","detailMastodon":"Mastodon is easy once a user chooses an instance and creates an account. The server handles sessions, posts, media, federation, and rules. Self-hosting gives more control, but requires operating the stack. Bitsocial can create the user's key locally and let the user post through direct P2P or optional hosted access without a platform account owning the identity.","detailFarcaster":"Farcaster's user experience is easiest through a client that manages account setup, app signers, storage, and hub or Snapchain connectivity. Running your own data path is possible, but not the first-post path for normal users. Bitsocial can create the user's key locally and let the user post through direct P2P or optional hosted access without routing the first post through app-managed signer and storage infrastructure.","detailLens":"Lens focuses on a web2-like flow with gasless or signless transactions and embedded wallet support. That improves onboarding, but a user is still entering through a Lens app, wallet, RPC, indexer, and chain path. Bitsocial can create the user's key locally and let the user post through direct P2P or optional hosted access without routing the first post through wallet, RPC, indexer, and chain infrastructure.","detailDeso":"DeSo web apps commonly rely on DeSo Identity for signing and on a node API for constructing and submitting social transactions. That is easier than running a node, but the post still enters through hosted identity, node, and transaction infrastructure. Bitsocial can create the user's key locally and let the user post through direct P2P or optional hosted access without a platform account owning the identity.","detailSteemit":"Steemit is straightforward once a user has a Steem account and posting key, but that account belongs to the Steem permission model and the post enters through a Steem front end or API node. Bitsocial can create the user's key locally and let the user post through direct P2P or optional hosted access without a platform account owning the identity."}},"expand":"Learn more","collapse":"Hide explanation","sourcesLabel":"Sources:","placeholder":{"service":"Lorem ipsum dolor sit amet, consectetur adipiscing elit.","bitsocial":"Lorem ipsum dolor sit amet, consectetur adipiscing elit.","detail":"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."}}},"arbitraryChallenges":{"sectionLabel":"Arbitrary Challenges","title":"Anti-spam? Future-proof.","supporting":"Each node runs its own anti-spam challenge, exchanged purely peer-to-peer with the user. When spam evolves, nodes adapt without changing the protocol.","diagram":{"user":"User","userHint":"publishes a post","node":"Bitsocial node","nodeHint":"runs the challenge","module":"Challenge module","moduleHint":"any code-backed test","request":"Request","challenge":"Challenge"},"optionsLabel":"Plug in any challenge","options":{"code":"any code","service":"AI-powered moderation","proof":"SMS OTP","next":"whatever comes next"},"quote":"The only Bitsocial innovation is solving spam and DDoS using arbitrary challenges like captchas over p2p.","quoteAttribution":"— Esteban Abaroa, Bitsocial founder"},"masterPlan":{"title":"A Call to Action","logoAlt":"Logo","easterEggAlt":"SpongeBob","epilogue":"The end state is not one app. It is a market of clients, nodes, services, and communities that can replace platform ownership with protocol competition.","epilogueFinal":"Social media finally finds its equilibrium: a fully decentralized, peer-to-peer social network that nobody owns; Bitsocial.","phases":{"phase1":{"phase":"Phase 1","status":"Ongoing","title":"Decentralize imageboards and forums","description":"<strong>Imageboards are the simplest form of social media to decentralize</strong>: anonymous posting, few default boards, and no profile graph. 5chan proves Bitsocial can replace centralized imageboards while removing global admins from the equation.","rpcDescription":"<forgeLink>Bitsocial Forge</forgeLink> will launch the first non-custodial RPC service for Bitsocial apps. <rpcLink>Bitsocial RPC</rpcLink> will let users manage nodes remotely, while preserving the option to self-host or run competing RPC infrastructure. <strong>Users will be able to create and manage unstoppable p2p communities from mobile</strong>.","forumsDescription":"Forums add persistent identities, post history, and community management. Seedit is the first prototype Bitsocial app for <strong>Reddit-style discussion</strong>, and public RPC makes those always-on P2P communities practical from anywhere."},"phase2":{"phase":"Phase 2","title":"Launch Bitsocial Network","description":"In order to decentralize all social media, Bitsocial apps will need killer features and strong network effects: <strong>unstoppable financial structures</strong>, decentralized Bitsocial domains (.bso), awards and tipping, common liquidity, and practical monetization. All of this will be powered by Bitsocial Network, a <strong>decentralized appchain solution</strong> for Bitsocial apps."},"phase3":{"phase":"Phase 3","title":"Launch the flagship Bitsocial app","description":"The flagship Bitsocial app should be the first profile-based client: posts, replies, follows, real-time public conversation, and communities that can pull network effects from every Bitsocial client. <strong>By default, it can feel as familiar as a modern For You social app</strong>, while still letting users switch RPCs, feeds, instances, algorithms, ads, or remove ranking entirely.","rpcNodes":"Through non-custodial RPC, each user can still act as a full p2p node without trusting the RPC with ownership. Anyone should be able to move to their own profile node on a low-spec machine, including a Raspberry Pi, whenever they want.","everythingApp":"Because Phase 2 gives the app an unstoppable crypto financial layer, the flagship client can potentially become an <strong>everything-app</strong> without turning into a custodial platform."},"phase4":{"phase":"Phase 4","title":"Scale Bitsocial economies","description":"The next layer is ecosystem funding and infrastructure pluralism. <strong>Bitsocial Forge's RPC should not be the only successful RPC</strong>: many businesses, independent teams, anonymous operators, and community entities should build RPCs, media hosting, discovery, moderation, and other services on top of Bitsocial. Funding should push that decentralization forward, so developers and operators can compete to make the network faster, cheaper, more reliable, and harder to capture."},"phase5":{"phase":"Phase 5","title":"Decentralize all social media","description":"With the core apps, public RPCs, profile nodes, discovery, and monetization in place, <strong>Bitsocial can fund and build the long tail of social clients</strong>: blogging, crowdfunding, creator video and a credible YouTube alternative, niche experiments, and every format too early for the first four phases. Bitsocial Forge can build some of them, centralized clients can compete too, they do not all have to be FOSS, and decentralized community grants can fund as many developers as possible."}},"cta":{"learnMore":"Learn More","try5chan":"Try 5chan","trySeedit":"Try Seedit","buildYourOwn":"Build your own"},"subtitle":"Bitsocial wins by attracting as many builders as possible. Run your own unstoppable community, develop your own decentralized social app, or even launch your own business on top of Bitsocial. The tide rises with every builder.","sectionLabel":"Master Plan"},"apps":{"title":"Bitsocial Apps","subtitle":"Bitsocial is meant to grow into thousands of apps, tools, and services built by anyone, not approved by gatekeepers. Explore what’s live now, then submit your own.","allCategories":"All","allProjects":"All Projects","allProjectsDescription":"The full Bitsocial ecosystem, from user-facing clients to protocol tools.","submitApp":"Submit App","submitAppDescription":"Have a Bitsocial app or tool? Submit it to the directory.","visit":"Visit","backToApps":"All Apps","linksAndMirrors":"Links & Mirrors","linksSectionDescription":"Launch the app, grab a build, or use a mirror without leaving the directory.","relatedApps":"Related Apps","sourceCode":"Source Code","notFound":"App not found","notFoundDescription":"The app you're looking for doesn't exist in the directory.","notFoundBack":"Back to Apps","emptyCategory":"Coming Soon","emptyCategoryDescription":"No apps in this category yet. Be the first to build one!","searchPlaceholder":"Search apps, tools, or tags","clearSearch":"Clear search","clearFilters":"Clear filters","noMatches":"No projects match these filters","noMatchesDescription":"Try a different search, platform, or category combination.","viewDetails":"Details","readyToUse":"Ready to use","experimental":"Experimental","mirrors":"Mirrors","webLinks":"Open on the web","mobileDownloads":"Mobile downloads","desktopDownloads":"Desktop downloads","extraDownloads":"Extra builds","sectionLabel":"App Directory","directoryLabel":"Directory","catalog":{"categories":{"apps":{"label":"Apps","description":"User-facing Bitsocial clients you can open or install today."},"anti-spam":{"label":"Anti-Spam","description":"Authentication, filtering, and moderation modules for Bitsocial communities."},"tools":{"label":"Tools","description":"CLI and admin utilities for running or extending Bitsocial apps."}},"platforms":{"web":{"label":"Web","shortLabel":"Web","description":"Browser-based apps and live web mirrors."},"android":{"label":"Android","shortLabel":"Android","description":"Direct APK downloads for Android devices."},"ios":{"label":"iOS","shortLabel":"iOS","description":"Native or installable apps for iPhone and iPad."},"desktop":{"label":"Desktop","shortLabel":"Desktop","description":"Windows, macOS, and Linux downloads."}},"tags":{"accessControl":"Access control","automation":"Automation","boardAdmin":"Board admin","bots":"Bots","captcha":"Captcha","cli":"CLI","contracts":"Contracts","downloadable":"Downloadable","feeds":"Feeds","forums":"Forums","humanChecks":"Human checks","imageboard":"Imageboard","invites":"Invites","mirrors":"Mirrors","moderation":"Moderation","onChain":"On-chain","riskScores":"Risk scores","telegram":"Telegram","verification":"Verification"},"linkLabels":{"androidApk":"Android APK","linux":"Linux","linuxArm":"Linux ARM","linuxX64":"Linux x64","macosApple":"macOS Apple","macosIntel":"macOS Intel","openWebApp":"Open web app","openWebsite":"Open website","windows":"Windows","windowsPortable":"Windows Portable"},"items":{"5chan":{"tagline":"Decentralized imageboards with direct web, APK, and desktop downloads.","description":"5chan is the first public Bitsocial client. It recreates the anonymous imageboard flow on a peer-to-peer network: boards, threads, image posting, community moderation, and multiple public mirrors without relying on a central server."},"seedit":{"tagline":"Forum-style Bitsocial client with web, APK, and desktop builds.","description":"Seedit brings Reddit-style discussion to Bitsocial with threads, identities, community management, and multiple distribution paths. It is the fastest way to try the forum side of the network from a browser, Android phone, or desktop app."},"mintpass":{"tagline":"NFT-backed access control for communities that need stronger anti-spam gates.","description":"Mintpass is a flexible authentication layer for Bitsocial communities. It lets moderators mix NFT ownership, verification flows, and custom challenge modules without pushing everyone onto a central login system."},"spam-blocker":{"tagline":"Centralized risk scoring layer for filtering abusive publications.","description":"Spam Blocker evaluates publications and returns a risk score that communities can combine with their own moderation logic. It is useful when you want a pragmatic extra layer before building more custom anti-spam rules."},"captcha-canvas-challenge":{"tagline":"Custom image captchas for communities that want human verification.","description":"Captcha Canvas Challenge generates visual captchas that communities can plug into their own publishing flow. It is a lightweight option for communities that want direct human checks without giving up self-hosted moderation."},"voucher-challenge":{"tagline":"Invite-style voucher codes for communities that prefer controlled growth.","description":"Voucher Challenge lets moderators distribute trusted voucher codes that unlock publishing without a global identity provider. It is a good fit for invite-driven communities, niche boards, and gradual rollouts."},"evm-contract-call":{"tagline":"On-chain gating for communities that want token or contract checks.","description":"EVM Contract Call verifies publications by calling an EVM contract before a post is accepted. It lets communities build token gates, staking rules, or other on-chain checks into their moderation flow."},"bitsocial-cli":{"tagline":"Command-line control for nodes, communities, and automation workflows.","description":"Bitsocial CLI is the official terminal interface for the protocol. Use it to manage nodes, publish content, start a WebSocket JSON-RPC server for programmatic control and code automation, automate admin flows, and work directly against Bitsocial primitives without a GUI client."},"telegram-bots":{"tagline":"Feed bots that relay new Bitsocial posts into Telegram channels or groups.","description":"Bitsocial Telegram Bots monitor client community lists and forward new posts into Telegram destinations with inline links back to Bitsocial clients. The active bot covers 5chan feeds today, with the repo structured to add more client-specific bots over time."},"5chan-board-manager":{"tagline":"Board administration tooling for custom 5chan communities.","description":"5chan Board Manager connects to Bitsocial CLI to help administrators create, configure, and moderate custom imageboard boards. It is the utility layer for board owners who want operational control."}}},"mirrorVerificationTooltip":"This mirror page hash matches the official GitHub HTML release for {{appName}} {{releaseTag}}.","mirrorVerified":"Verified","mirrorWeb3Tag":"web3","mirrorWeb3TooltipTitle":"{{ensName}} Web3 mirror","mirrorWeb3TooltipBody":".eth names are ENS names, not DNS records. The .limo address is a centralized gateway. Bitsocial uses IPFS, so with the IPFS Companion browser extension running an IPFS full node you can open {{ensName}} directly as static HTML without .limo.","mirrorWeb3CompanionLink":"Install IPFS Companion","githubTopic":{"description":"Explore Bitsocial apps under development on GitHub. If you are building one, add the \"bitsocial\" topic to your repo so others can find it.","link":"Explore GitHub topic"}},"home":{"devOnlyRouteNotice":"{{path}} is still under construction. You have been redirected to the front page.","dismissDevOnlyRouteNotice":"Dismiss notice"},"privacy":{"eyebrow":"How bitsocial.net handles data","title":"Privacy Notice","sections":{"summary":{"title":"Summary","body":["bitsocial.net collects very little data.","The code for bitsocial.net is free and open source and lives in the public bitsocial-web repository.","If you sign up for the newsletter, the email address you enter is sent to the mailing-list service configured for the site.","Other than that, bitsocial.net uses privacy-focused traffic and performance measurement, stores your language preference in browser storage, and loads fonts from Google Fonts."]},"uses":{"title":"What bitsocial.net uses","body":["Newsletter signup sends your email address to the configured mailing-list endpoint only when you submit the form.","Vercel Web Analytics and Speed Insights are used on bitsocial.net for aggregate traffic and performance measurement.","The about site and docs site store your language choice in browser storage so the interface can reopen in the language you selected.","The public pages load fonts from Google Fonts, so your browser connects to Google's font servers."]},"cookies":{"title":"Cookies and storage","body":["bitsocial.net does not use Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, or similar advertising or profiling scripts on the public site.","bitsocial.net tries to avoid non-essential tracking cookies.","The site does use browser storage for language preference, and the stats surface may rely on strictly necessary Grafana session state for administrator login.","There is no cookie banner right now because the public site is limited to language-preference storage and privacy-focused measurement. If that changes, this page should change too."]},"choices":{"title":"Your choices","body":["You can avoid newsletter processing by not submitting the signup form.","You can clear the language preference at any time by clearing site storage in your browser.","You can block remote font requests with browser or network controls, although doing so may change the site's appearance.","We will update this page if the public site starts using additional tracking, embeds, or signup flows.","This version was last updated on April 5, 2026."]}},"contact":{"title":"Contact","body":"Questions or corrections about this page can be sent to"}},"about":{"sectionLabel":"About Us","title":"Bitsocial Core Team","subtitle":"Bitsocial has been in active development since early 2022. We're also building <pkcLink>PKC</pkcLink>, a barebones implementation of the peer-to-peer backend, intended for general development use.","members":{"esteban":{"role":"Bitsocial founder and lead developer"},"rinse":{"role":"Bitsocial co-founder and core developer"},"tommaso":{"role":"Bitsocial co-founder and core developer, founder & CEO of <forgeLink>Bitsocial Forge</forgeLink>"}},"memberProfileAlt":"Profile photo of {{name}}"}}},"newsletter":{"isConfigured":true,"requiresConfirmation":false},"clientDefaults":{"graphicsMode":"pending"}}