|
|
|
|
Show HN: Trust-gated developer communities with portable identity (AT Protocol)
(github.com)
|
|
2 points
by JohannaWeb
109 days ago
|
|
|
Hi HN — I've been working on Falcon, a developer collaboration platform built around portable identity instead of server ownership.
The core idea: communities shouldn't disappear when a platform, server, or admin does. Your identity and relationships should persist.
This latest iteration moves Falcon into a service-oriented architecture and introduces a trust-gated access model tied to AT Protocol identities.
What's new: Identity-first access: entry to communities based on verified identity + trust signals, not invite links
Trust service: prototype for reputation/relationship-based gating
Gateway: auth + routing boundary for identity-aware services
Real-time infra: JetStream-backed messaging layer in progress
Mono-repo with bounded services: gateway, trust, messaging (SIV), client, protocol lexicons The goal isn't "decentralization for its own sake." It's to test whether developer communities would coordinate differently if identity and membership weren't locked to a single platform like Discord or Slack.
Still early: prototype stage
infra evolving quickly
no production deployment yet I'm a solo founder with 10 years of backend experience, building this because my community needs it.
I'm especially looking for feedback from OSS maintainers, infra/protocol engineers, and teams running private dev communities.
Main question: Would identity-portable, trust-gated communities actually change how dev groups collaborate — or is platform gravity still too strong? repo: https://github.com/JohannaWeb/ProjectFalcon |
|
|