Back to browse
GitHub Repository

Project Falcon Sovereign real-time communication infrastructure built on the AT Protocol and a Decentralized AI Inference Mesh

21 starsTypeScript

Falcon – Chat-first communities built on Bluesky AT Protocol

by JohannaWeb·Feb 24, 2026·5 points·4 comments

AI Analysis

MidShip ItBold Bet

AT Protocol + Discord UX hybrid, but messaging isn't live yet—WebSocket TBD.

Strengths
  • Genuine architectural ambition: bridges decentralized identity (AT Protocol) with community chat, solving a real gap in Bluesky ecosystem.
  • Honest early-stage transparency: author explicitly asks about scaling decisions (WebSocket, pub/sub) rather than overselling readiness.
  • Functional core: Bluesky feed, server management, and HTTP-based messaging work today; clear path to real-time layer.
Weaknesses
  • Incomplete product: no WebSocket messaging means channels feel like REST polling—core feature is planned, not shipped.
  • Solo builder monolith risk: Spring Boot + H2 in-memory DB; author's own question reveals uncertainty about production scaling.
  • Crowded space with structural gap: Discord exists, Bluesky federated chat exists (Bluemoji, etc.); unclear why Electron desktop hybrid is the answer.
Target Audience

Bluesky users, decentralized social platform enthusiasts, developers exploring AT Protocol

Similar To

Discord · Bluesky app · Bluemoji (Bluesky chat)

Post Description

I’m building a chat-first community app that uses Bluesky’s AT Protocol for identity.

Current architecture: - Electron client - Spring Boot backend (monolith) - REST for servers/channels - Planning WebSocket-based messaging

As a solo builder, I’m trying to balance simplicity with future scalability.

At what point would you introduce: - a separate WebSocket gateway - pub/sub (Redis, etc.) - or keep everything in one Spring app until it breaks?

Curious how others approached real-time chat systems early on.

Project for context: https://github.com/JohannaWeb/ProjectFalcon

Similar Projects