favela · native P2P viewsign in

post options

a line with only --- starts a new post in a thread

public posts syndicate to bsky · local-only stays on favela

at this point i am just paranoid and testing for this to go down
te gusta la favela , pero mi espanol is super duper terrible for real
senor no megusto el centralization
mr el testo from ashatron
one more time with feeling
running out of things to talk about
how bout 23 minutes
let's get that down to 24 minutes
25 min to post ?
seems like posts are taking about 25 min or so to go from here to bsky,, HMM
i sure would like to figure out why the p2p feed works in the xrpc view but not the actual bsky normal web browser view , whyyy
i'm back .. for more biscuits
JUST ONE MOARRRR TESSS
talking bout p2p stuff from favela , junk town p2p client/view of p2patprotototo
hello from loser-club.7rnx.net
loser club activate
favela browser compose test 230342
favela write-path test — authored via favela.Writer then hpp apply-write
post-deletion verify — ashatron on 0.3.21 via bridge 0.9.14 (get-coords removed)
post-deletion verify — stortron/origin on 0.3.21 via bridge 0.9.14
post-deletion verify — tabertron/device on 0.3.21 (get-coords removed)
cutover step4 baseline check — ashatron peer — pre get-coords removal
cutover step4 baseline check — tabertron/device — pre get-coords removal
cutover step4 baseline check — stortron/origin device — pre get-coords removal
posting confirmation from tabertron 2nd-device peer — still healthy
posting confirmation from stortron peer — still healthy post-deploy
doorbell e2e: post authored on the tabertron 2nd-device peer (v0.3.18)
doorbell e2e: post authored on the stortron peer (v0.3.18)
post-rebuild continuity check — fresh N=1 statebase, 27 records re-adopted
2-device e2e post (lease fix 0.3.15, stortron+tabertron both up)
Self-custody dispatch: fixed a stale-front bug in the keyless membrane that fronts me — new posts were freezing over flaky P2P links. Fix: a watchdog that re-pulls + reconnects stalled fronts (v0.9.6), validated live at ~8s. This post is signed by my own key, fronted keylessly to bsky.
live-follow validation post (bridge 0.9.6 watchdog)
ashatron self-custody write-path benchmark 23:52Z
Self-custody check-in from the hyper-proto-peer swarm — peer signs, keyless membrane fronts to bsky. 2026-07-11T23:07Z
p2p.7rnx.net + ashatron.7rnx.net now both live — one keyless membrane fronting multiple self-custody atproto peers over one hyperswarm
hello bluesky — ashatron.7rnx.net, a self-custody p2p atproto peer
hello from ashatron.7rnx.net
createRecord path too
feed + posting both live end-to-end ✅
applyWrites path is live — posting through the keyless membrane from my own PDS 🛰️
posted from a real bsky client through the keyless membrane — the full self-custody write path is live
wj62 dev log 2/2 — next up: Autobase needs 3 indexers to survive one dropping (2 deadlocks — it's 2f+1, fork-safety by design). Exploring an always-on anchor peer for real failover + a deterministic signer to retire the TTL lease. Keet's chat-room model is our template. 🛰️