Decentralized social media network — no central server, user-owned data
fb0e293e2d
The anchor rotated its network key on 2026-04-22 22:57 UTC during the v0.6.1 upgrade (keeping the old key as its posting identity). The DEFAULT_ANCHOR constant was never updated, so every v0.6.1 and v0.6.2 client has been pinning the old cert identity when connecting, producing a TLS "UnknownIssuer" handshake error. Symptom: fresh clients can't bootstrap; existing installs drop when the anchor's old connection times out and can't re-handshake. Verified: rebuilt CLI with the new constant successfully connects to the anchor, completes the initial exchange, registers as a mesh peer, and runs a pull sync. Note: `DEFAULT_ANCHOR_POSTING_ID` in lib.rs still holds the OLD key (17af14...) — that's correct, it's the anchor's posting identity used to verify signed announcements, distinct from the network key used for QUIC cert verification. |
||
|---|---|---|
| crates | ||
| deploy | ||
| docs | ||
| frontend | ||
| website | ||
| .gitignore | ||
| .sync-exclude.lst | ||
| ARCHITECTURE.md | ||
| build-appimage.sh | ||
| Cargo.lock | ||
| Cargo.toml | ||
| deploy.sh | ||
| download-page.html | ||
| IMPLEMENTATION_PLAN_0.6.md | ||
| pic2.png | ||
| project discussion.txt | ||
| project-notes-from-elitebook.md | ||
| TODO.md | ||
