s@ (Satproto) — On Our Radar

Status: 🟡 Under observation
Why we're talking about it: s@ is attempting to build a social network on static sites, a move that would make servers as redundant as a chocolate teapot if it actually scales (GitHub/HN).

What we know:
- Version 0.1.0 utilizes X25519 keypairs for identity and XChaCha20-Poly1305 for content encryption via libsodium/WASM (GitHub).
- Identity verification is handled via HTTPS/TLS through a /.well-known/satproto.json discovery file (satproto.org).
- Spam prevention is hardcoded via a mutual-follow mechanism where users only see replies from people they follow (satproto.org/protocol).
- Private keys are stored in browser localStorage, making them volatile and vulnerable to malicious extensions (HN).
- There is no account recovery mechanism; clearing browser data results in permanent identity loss (HN).

The unknowns:
- We don't know yet if there is any plan for long-term funding or a sustainable monetization model (UsedBy Dossier).
- There is no information regarding the availability of a mobile-native client as of March 2026 (UsedBy Dossier).

This article will be updated when we have more data. Until then, proceed with caution.

Ship clean code,
Marcus.