Projects Directory

Bitsocial Projects

Bitsocial is meant to grow into thousands of apps, tools, and services built by anyone, not approved by gatekeepers. If you’re a dev, submit your own app.

Project Categories
5chan logo

5chan

Anonymous imageboards on Bitsocial, for web, Android, and desktop.

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 logo

Seedit

Reddit-style communities on Bitsocial, for web, Android, and desktop.

Seedit brings Reddit-style discussion to Bitsocial: communities anyone can create and own, voting, threaded comments, and moderation set by each community's owner. It is the fastest way to try the forum side of the network from a browser, Android phone, or desktop app.

4chan-style thread archiving, bump limits, and purging for 5chan boards.

5chan Board Manager runs next to Bitsocial CLI and gives a board 4chan's thread lifecycle: threads that fall off the last page are archived, archived threads are purged after a set time, threads past the bump limit stop bumping, and posts deleted by their author are purged.

Active Page Sort

Imageboard bump order where sage replies and threads past the bump limit stop bumping.

Active Page Sort is a custom page sort for community owners that replaces the built-in bump order. A reply with a line matching one of the board's keywords, such as sage, does not bump its thread, and with a bump limit set only a thread's first replies can bump it. Those threads sink but are never hidden. It publishes under the same active key as the built-in sort, so clients show the new order without any change. It requires pkc-js 0.0.114 or later.

Checks each post against the community's rules with an AI model the owner chooses.

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.

AskWise logo

AskWise

AI reply bot that communities opt into and summon with @askwise.

AskWise is an AI reply bot that Bitsocial communities opt into. In a community that installed it, anyone can mention @askwise or askwise.bso in a post or reply, and the bot reads the thread, including its images, and answers there while following the community's rules. Communities that haven't installed it are ignored, and only threads that mention it are sent to the operator's AI provider. AskWise is an independent project that runs on bitsocial-cli; it is not made or run by Bitsocial.

Base64 Challenge

Rejects publications that hide images or other files in their text as base64 data.

Base64 Challenge runs on a Bitsocial community node and rejects any publication that embeds a data: URI or a long run of base64 in any text field, from post bodies and titles to display names and edit reasons. Without it, a community can end up signing, storing and serving a small image hidden in a post's text, which an AI moderator sees only as a wall of characters. The check is deterministic and runs no model, hex strings such as hashes and transaction data pass, and moderators can be exempted.

bitbones logo

bitbones

A developer client for inspecting Bitsocial protocol data.

Inspect the protocol data behind Bitsocial feeds, communities, posts, and replies. See React hook calls, raw JSON, client states, and debug logs as you test changes against real communities.

Bitsocial CLI

Run a Bitsocial node and manage communities from the terminal.

Bitsocial CLI is the official terminal interface for the protocol. Use it to run a node, create and manage communities, publish content, and start a WebSocket JSON-RPC server that other programs can drive.

Finds Bitsocial communities that no list carries yet and checks which ones are alive.

Bitsocial Discovery starts from community lists, submissions, indexers and ENS records, then follows the pointers communities leave to each other: addresses mentioned in posts and descriptions, crossposts, and the chain of an author's previous comments. It keeps rechecking every community it finds to track which are still alive, and serves the results as a JSON API for clients, indexers and review tools. It stores community metadata, never posts, and ships idle: the operator chooses the sources and what the API shows.

Telegram bot that posts compact GitHub activity for Bitsocial repositories.

Bitsocial GitHub Alerts forwards pushes, releases, issues, and pull requests from GitHub into any Telegram chat, group, or forum topic. The Bitsocial team runs it for its own repositories, and the container image is public so anyone can self-host it for theirs.

Bitsocial Indexer

Self-hostable crawler, search index, and web UI for Bitsocial communities.

Bitsocial Indexer connects to a Bitsocial CLI daemon over RPC, indexes the communities an operator configures into a local SQLite database, and serves them through a REST and full-text search API with an optional server-rendered web UI. It ships empty: the operator decides what gets indexed.

Link-preview and redirect server that renders share cards for Bitsocial posts.

Bitsocial Previewer renders OpenGraph and Twitter cards when a post link is shared on other platforms, then redirects real browsers into the app. One instance is multi-tenant by hostname, so a single deployment and TLS setup covers every client and mirror domain.

Bitsocial Seeder

Keeps Bitsocial communities fast and reachable by re-hosting their content, via Docker or npm.

Bitsocial Seeder helps communities load quickly by keeping extra copies of their content online. It pins community first pages, post-update CIDs, and pubsub topic routing through a Bitsocial daemon. It reuses an already-running local daemon when one is reachable or starts the bundled bitsocial-cli daemon automatically, and ships as both a Docker image for unattended VPS deployments and an npm package for Node-first operators.

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 an image captcha on the community's own node and requires posters to solve it before a post, reply, or vote is accepted. Nothing is sent to a third-party captcha service. It is a basic deterrent that determined bots can brute-force, so pair it with another challenge on communities that attract spam.

Challenge Composer

Offline-first editor for a community's anti-spam challenge settings.

Challenge Composer visualizes and edits the challenges array of a Bitsocial community's settings, then exports a ready-to-run CLI script. It ships as a single self-contained HTML file that makes no outward requests at runtime, so it can be opened straight from disk or a USB stick.

EVM Contract Call

Requires posters to pass an on-chain check, such as holding a token.

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 posting rules.

Flags Challenge

Verified country and board flags on posts, signed by an issuer the community trusts.

Flags Challenge runs on a Bitsocial community node and verifies signed flag assertions from a configurable issuer service. The first bundled profile targets 5chan, covering country flags, /pol/ memeflags, and /mlp/ pony flags, while keeping the same pattern reusable for any client that runs its own issuer and namespace.

Flair Page Sort

Community pages that hold only the posts and replies carrying a chosen flair.

Flair Page Sort is a custom page sort for community owners. Listed in a community's page settings with a set of flairs, it makes the node publish an extra page holding only the posts or replies that carry one of those flairs, ordered by most recently flaired, new, hot, or best. A community can publish it as its default page so clients open on it, and clients need nothing installed to read it. It requires pkc-js 0.0.143 or later.

Mod-queue bot that only approves posts whose image matches what the community allows.

Image Classifier Bot moderates communities that only want one kind of picture, such as only cats, only dogs, or only food. It runs next to bitsocial-cli, watches the community's mod queue, and approves or rejects each new post by classifying its linked image with a CLIP/SigLIP vision model the owner hosts themselves on a CPU. Labels are plain English and need no training, so switching from cats to dogs is a config change. Posters don't wait for the check, no image goes to a third-party AI service, and rejected posts show the reason.

MintPass logo

MintPass

Paid, non-transferable Ethereum passes for directory voting and captcha-free posting.

MintPass is a paid, non-transferable, expiring pass on Ethereum mainnet that each Bitsocial app deploys under its own name: 5chan Pass for 5chan and Seedit Gold for Seedit. A valid pass lets its holder vote in directory contests and post without solving a captcha on communities that check it with EVM Contract Call. The price is fixed in USD and paid in ETH, and buying again renews the same pass instead of minting a second one. The contracts are not deployed yet.

Pubsub Provider

Fallback pubsub relay and routing provider for Bitsocial operators.

Pubsub Provider runs a bundled Kubo node with Bitsocial-compatible pubsub, gateway, name-provider, and delegated HTTP routing endpoints. It is useful as a fallback path for clients that disable pure browser P2P, and it defaults to swarm port 4002 so it can run beside bitsocial-seeder on the same host.

R9K Challenge

Robot9000-style rule that rejects any post repeating text already posted in the community.

R9K Challenge runs on a Bitsocial community node and compares normalized post text against the owner node's local comments database. It gives communities a Robot9000-style posting experience without using AI: exact reposts fail before acceptance, backlinks are ignored, repeated failures trigger escalating temporary bans, and accepted-text hashes stay in private local state instead of storing raw post text.

Spam Blocker

Hosted risk-scoring service that helps communities filter spam and ban evasion.

Spam Blocker evaluates publications and returns a risk score that communities can combine with their own moderation logic. Its hosted service also links signer keys first seen from the same IP, so a user who keeps generating new accounts to dodge a community ban or manufacture a conversation sees their risk score rise, while a few signers stay allowed for legitimate multi-device use.

Subreddit Mirror

Mirrors a subreddit into a Bitsocial community and keeps what Reddit removes.

Subreddit Mirror is a daemon that copies a subreddit's posts and replies into a Bitsocial community and keeps checking each thread for a week. When Reddit removes a post or comment, the mirrored copy stays and gets a flair saying whether moderators, Reddit, or the author removed it, with the text recovered from public archives when the live page lost it. A community can open on a removed-only view that lists just the threads where something was removed. It runs next to bitsocial-cli, and can also backfill a subreddit's history or mirror a banned subreddit from the archives alone. Subreddit Mirror is an independent project; it is not made or run by Bitsocial.

Tipping Challenge

Verified tips on replies, sent wallet to wallet and checked on chain by the community.

Tipping Challenge lets a community show verified tips. An author sends a token straight to another author's wallet, then replies to the comment being tipped with the transaction hash, and the community node looks the transaction up on chain and writes the verified amount into the reply. Tips can be ERC-20 tokens, NFTs or a chain's native coin. The community cannot intercept a tip or fake one, and replies without a tip are not affected. It implements the tipping/v1 contract, so a client written against that contract keeps working with other implementations.

Voucher Challenge

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. A code is bound to the first author who redeems it, so that author keeps posting with it and nobody else can reuse it.

Community wordfilters enforced as a posting rule instead of a display filter.

Wordfilter Challenge makes a community's word replacements binding. Publishing clients apply the replacements before signing, so the signed comment and its CID already contain the replacement text, and the community node rejects any publication that still contains a filtered word. It implements the wordfilter/v1 contract, so a client written against that contract keeps working with other implementations.

Idea-stage feed and recommendation providers that users can switch like a setting.

Bitsocial Algorithms is research into feed and recommendation algorithms as replaceable services across Bitsocial clients. A client can ship with a strong default, and a user can switch to another provider, run their own or rank posts locally without moving their profile, while a chronological feed stays available without any provider. Providers discover and rank posts but never own identities, posts or social state, so no single company decides what everyone sees. Nothing is built yet; the repository collects the research and the accepted architecture.

Idea-stage Ethereum L2 for .bso names, tips, payments and community tokens.

Bitsocial Chain is the proposed economic layer for Bitsocial apps in Phase 3 of the master plan: an Ethereum L2 to host .bso names, tipping and payments, community tokens and AgoraSwap. It is meant to add no trust beyond Ethereum itself, with no upgrade keys, no security council and no privileged operator. Posts and communities stay peer-to-peer; nothing social goes on chain. A proof of concept derives a .bso name registry from plain Ethereum transactions that anyone can recompute. It is not audited or deployed.

Idea-stage live chat and private messages that work across every Bitsocial app.

Bitsocial Chat is a plan for chat built on the identities and nodes Bitsocial already has, so a user keeps one identity and one inbox in every app. It would start with public live chat in communities and beside posts or streams, sent over pubsub and not stored. Private messages would follow: one-to-one, end-to-end encrypted and held as ciphertext on the recipient's profile node until read, which would also give communities modmail. Whether to build this natively or reuse an existing network such as XMTP is still open. Nothing is built yet; the repository collects the design and the research.

Idea-stage forum client where each section belongs to whichever community wins it.

Bitsocial Forum is a planned forum for Bitsocial projects and the third Bitsocial client after Seedit and 5chan, meant to gather discussion now split across Telegram, Twitter and GitHub. Each section, such as one for 5chan or .bso names, is a directory that communities compete for: the community ranked first runs it with its own moderators, and another can take it over if that one goes away or is run badly. There is no server and no global admin. An early build reads any Bitsocial community, but posting and profiles are not built yet.

Idea-stage open crawler that maps which authors and communities are active on Bitsocial.

Bitsocial Graph is research into an open crawler that builds the Bitsocial social graph from public protocol data: authors, communities and how they interact. Bitsocial content stays reachable only while someone keeps publishing or seeding it, so the graph also tracks liveness and shows the network as it is now rather than everyone who ever joined. The results would be published as open data and APIs for clients, search and feed providers, with this crawler as one provider among many. Communities that hide author identities stay unlinkable. Nothing is built yet; the repository collects the research and the accepted architecture.

Idea-stage plan to keep Bitsocial communities running when the internet is cut off.

Bitsocial Mesh is a plan to keep communities working through an internet shutdown or a disaster. First, a laptop or small computer hosts a community and opens a Wi-Fi hotspot, so people nearby can read, post and moderate from a browser. Later stages would link these boxes across a city over LoRa radio and carry posts out once any connection returns, with phone-to-phone Bluetooth last, if at all. Unlike mesh chat apps such as bitchat, it keeps communities with their own rules, moderators and spam defences. Nothing is built or tested yet; the repository collects the design.

GitCommons logo

Idea-stage code collaboration platform that pairs peer-to-peer Git with Bitsocial's social layer.

GitCommons is research into a GitHub alternative that combines a Radicle-style peer-to-peer Git layer with Bitsocial profiles, communities, discovery and reputation. Each repository's discussions would be a Bitsocial community, developer profiles would be Bitsocial profiles, and CI would come from competing runner services instead of one mandatory provider. GitCommons is a working name; the project is not affiliated with GitHub, Inc. or the Git project.

Infinipedia logo

Idea-stage encyclopedia where competing editorial groups publish their own versions of each article.

Infinipedia is an encyclopedia that nobody owns. Editorial groups, human or AI-assisted, each publish their own versions of articles on top of a Wikipedia baseline, every revision is signed by its author, and readers choose whose versions they trust and can compare any two side by side. Nothing is built yet; the repository collects the design.

ModelSwarm logo

Idea-stage Hugging Face alternative where open-weight AI models are shared by a swarm of peers.

ModelSwarm is a hub of open-weight AI models that nobody owns. Publishers sign releases from their own Bitsocial profile, the weights travel over BitTorrent and HTTP mirrors, and every piece of every file is checked against the signed release as it downloads. Hubs are Bitsocial communities that curate releases and host discussion, and files in formats that can run code are flagged before download. Nothing is built yet; the repository collects the design.

Idea-stage research into prediction markets with a Bitsocial community around each question.

Prediction Markets is open research into apps that put a prediction market and its discussion in one place, so people can find a question, debate the evidence, take a position and come back for the result. Bitsocial would carry the communities and threads, while an existing market protocol handles trading and settlement; Trueo is the first candidate being studied. A community vote never settles a market. The idea is open for any developer or project to build. Nothing is built yet and no partnership is agreed.

WeTube logo

WeTube

Idea-stage YouTube alternative where each channel is a Bitsocial community its creator owns.

WeTube is a YouTube alternative in which every channel is a Bitsocial community controlled by its creator's key, every video lists redundant embed sources so no single host can take it down, and channels are curated through community lists ranked by votes. A read-only web preview browses channels and plays videos peer-to-peer; uploads, view counts and monetization are not built. The full app belongs to Phase 5 of the Bitsocial master plan.