0.0.35: the device publishes its own Bluesky repo
Carries the on-device bsky projector. The two networks were never symmetric: the fediverse
bridge HOLDS a registered name's feed and projects from it server-side, so this phone
federated nine posts with nothing running on it — while Bluesky's membrane is keyless and
re-serves only what the device SIGNED, so its atproto repo held exactly one record, hpp's
fresh-account `self.hello`, and no profile at all. Identity, handle, relay and consent were
all correct. Nothing had ever authored anything.
favela-bridge's projection pass is now transport-free, favela-host supplies hpp and
favela-peer as objects rather than sockets (SELinux gives an app no `sock_file`), and the
Bluesky card grows a fourth step that runs it — dry run beside send, because it publishes a
history and a post there cannot be recalled.
Bundle 41.00 MB → 41.93 MB. The projector's own closure is most of that; making
favela-bridge's hyper-svc import opaque kept a third copy of the transport out (915 files
back to 610), which plain deferral did not — bare-pack follows a static dynamic import.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
24bb374418d0871952dce5d6e8d0eb6fccd53eca
by plankatron <fleeky@gmail.com> · 2026-09-11T22:51:39.000Z