The world is waking up to the flaws of centralized social networks: surveillance, censorship, algorithmic manipulation, and data exploitation. People want to seek out alternatives that empower them instead of controlling them.

That's where OmniSocial ProtocolKit comes in.

Formerly known as OmniSocial Hub, this open-source project has completely transformed into a modular, federated social media starter kit. It's not just a platform — it's a toolkit, an engine, a foundation for building interoperable social apps that embrace decentralization, user sovereignty, and Protocol pluralism.

Let's dive into what's changed, why it matters, and what's now possible.

The renaming wasn't just cosmetic — it reflects a deeper shift in purpose and design.

OmniSocial Hub originally aimed to unify decentralized social interactions under one roof. While ambitious, the early vision was focused more on the end-user experience. As the project matured, a more flexible, developer-focused foundation became necessary.

Hence, OmniSocial ProtocolKit was born — shifting from an all-in-one hub to a developer-friendly Protocol framework that can be adapted, extended, and customized by anyone building the next wave of social apps.

This means:

• Composable protocol modules

• Unified architecture for ActivityPub, AT Protocol, Nostr, and more

• Interoperable posting, discovery, and identity

• Lightning-powered microtransactions

• Matrix integration for DMs and chat

• OpenPGP E2EE and BridgeID identity layer

• Self-sovereign user IDs like username@domain

Build with only what you need:

• ActivityPub for federation across Mastodon, Lemmy, PeerTube, etc.

• AT Protocol for rich client-server social graphs (Bluesky)

• Nostr for censorship resistance and relay-based messaging

• Webfinger + IndieWeb (Micropub, Webmention) for Indie-authored content

• DIDs + BridgeID for self-sovereign identity and cross-protocol linking

• RSS for open syndication

Each module is standalone but interoperable, allowing devs to mix and match protocols or run all of them simultaneously.

Microtransactions are baked in:

• Pay-to-comment, pay-to-DM, pay-to-view (creators set pricing)

• Free posts up to a limit (e.g., 5/hr), with Lightning payments beyond that

• Full invoice creation and verification

• An optional monetization layer without compromising decentralization

This helps fight spam, support creators, and build sustainable social economies — all in a censorship-resistant way.

• OpenPGP-based E2EE for content

• Matrix integration for real-time, federated messaging

• Optional paywall on DMs via Lightning

• Group chat support via Matrix rooms

• When users sign up, they get a cross-protocol identifier like:
  username@yourdomain.com

• This identity maps to:

  • ActivityPub @username@yourdomain

  • AT Protocol DID and handle

  • Nostr public key

  • BridgeID mapping for Protocol linking

You own your ID, your content, and your keys.

• Post once → seen everywhere.

• One post can be sent simultaneously to ActivityPub servers, AT Protocol feeds, and Nostr relays.

• RSS and IndieWeb feeds are automatically generated.

• Optional IPFS or Arweave pinning is available for immutability and offline access.

• Full GitHub repo with docs, CI/CD workflows, Docker deploy

• Ready-to-use API routes with Swagger/OpenAPI auto-docs

• .env templates for multi-instance federation setup

• Live demo deployment with branded UI

OmniSocial ProtocolKit doesn't reinvent the wheel — it assembles all the powerful parts into a working machine. It's not trying to be the next Twitter — it's empowering developers to build 100 Twitters, 50 Substacks, 20 Peertubes, and whatever else they dream up — all interoperable.

It's protocol-native by design.

It respects choice. You're not locked into a specific app, server, or ecosystem. You can fork, adapt, remix, host, or build on top.

That's the true spirit of the open web.

Imagine you want to create a niche social platform for local artists:

1. You deploy OmniSocial ProtocolKit on your domain.

2. Users register with @name@yourdomain.com.

3. They post artwork broadcast to Nostr relays and ATProto feeds and are federated with Mastodon/Pixelfed.

4. Users can sell premium content via Lightning paywalls.

5. Comments are pay-to-post to prevent spam.

6. DMs are routed via Matrix with optional tips.

7. All while maintaining self-hosted control.

With config tweaks and theme changes, you can create a decentralized, monetizable, censorship-resistant social network.

Here's what's coming soon:

• 🧠 Creator dashboards for Lightning earnings + analytics

• 🎨 Customizable post types (blogs, media, polls, etc.)

• 🛠 BridgeID UI for managing linked Protocol identities

• 🔍 Federated search across all protocols

• 🏗 Plugin system for adding more protocols or features

• 📲 Mobile-first responsive frontend UI

• 📚 GitHub Wiki and full developer onboarding docs

OmniSocial ProtocolKit is more than code — it's a statement.

It's a declaration that we can build social spaces that prioritize freedom, not friction, identity, not exploitation, and modularity, not monoculture.

We don't have to accept closed, siloed, ad-infested networks.

We can build better. Together.

Want to join the conversation, contribute, or fork your platform?

• GitHub Repository

• 🌐 Blog + Community Hub

• 💬 Join the discussion on Revolt

Let's make the future of social human, open, and truly ours.