Centralized social platforms have failed us through data exploitation and algorithmic manipulation. At Circuitry Hub Insights Collective, we're addressing this through OmniSocial Hub – a modular framework enabling developers to build social networks where:

• Users control their identity via decentralized identifiers (DIDs)

• Content flows across protocols via ActivityPub/AT Protocol/Nostr bridges

• Communities set their moderation policies

We've engineered OmniSocial Hub as three interconnected layers:

Handles protocol-specific operations through TypeScript plugins:

• ActivityPub: Full ActivityStreams 2.0 implementation with Mastodon compatibility

• AT Protocol: Lexicon schema validator and DID:PLC resolver

• Nostr: NIP-05 identifier management and event encryption

• Webfinger+DIDs: @username@domain resolution to decentralized profiles

typescript// Cross-protocol post creation example  
const post = await omniSocial.createPost({  
  protocols: ['activitypub', 'nostr'],  
  content: {  
    text: 'Decentralized future starts now!',  
    media: ['ipfs://bafy...']  
  },  
  author: 'did:web:omnisocial.hub/user123'  
});  

Simplified API usage demonstrating multi-protocol posting1

Our Express.js-based gateway exposes standardized endpoints:

Built with PostgreSQL and Redis for:

• Cross-protocol social graph storage

• Event sourcing for auditability

• Content-addressable storage via IPFS integration

• Swagger UI Integration: Interactive API explorer at /api-docs

• Docker-Compose Setup: Preconfigured containers for dev/prod environments

• Modular Design: Add new protocols without core modifications

bash# Start development environment  
docker-compose -f docker-compose.dev.yml up --build  

Quickstart command from our documentation1

• Federation Templates: Prebuilt Mastodon/Bluesky/Nostr compatibility rules

• Governance Models: DAO templates for community moderation

• Monetization Plugins: Lightning Network tipping, NFT membership support

We automate testing and deployment through GitHub Actions:

textname: Production Deployment  
on:  
  workflow_dispatch:  
jobs:  
  deploy:  
    runs-on: ubuntu-latest  
    steps:  
      - uses: actions/checkout@v4  
      - name: Build Docker Image  
        run: |  
          docker build -t omnisocial-hub:${{ github.sha }} .  
          docker push ghcr.io/beitmenotyou-com/omnisocial-hub  
      - name: Render Deploy  
        run: ./render-deploy.sh  

Simplified deployment workflow from our GitHub repository1

• protocols/sync_schemas.ts: Auto-updates Protocol specs from Bluesky/Mastodon/Nostr

• generate_contributors.py: Maintains contributor list via GitHub API

• webfinger-generator: Dynamic Webfinger JSON generator

• Node.js 20.x

• PostgreSQL 14+ with pgvector extension

• Redis 7+ with JSON modules

bash# Clone repository  
git clone https://github.com/beitmenotyou-com/omnisocial-hub  
cd omnisocial-hub  

# Install dependencies  
pnpm install  

# Configure environment  
cp .env.example .env  
nano .env  # Update database credentials  

# Run migrations  
pnpm migrate:up  

# Start development server  
pnpm dev  

Visit http://localhost:3000/api-docs to explore API endpoints1.

Join 150+ contributors in building:

1. Protocol Bridges: Connect OmniSocial to new networks

2. Moderation Tools: Create AI-assisted content filters

3. UX Components: Build React/Vue frontend modules

Contribution Process:

bash# Create feature branch  
git checkout -b feat/new-feature  

# Commit with signed-off  
git commit -s -m "feat: add new protocol bridge"  

# Open PR against develop branch  

Explore the Project:
📂 GitHub Repository
📘 Documentation Portal
💬 Community Chat

Authored by Circuitry Hub Insights Collective – Updated 27 March 2025