OverviewFilesCommitsIssuesDocsReleasesPeers

favela-surface-android commits / 73462b4

0.0.36: images and banners reach both networks
Two independent defects, both found by the audit and both silent. ⛔ IMAGES NEVER REACHED BLUESKY. hpp returned `blobs: null` from a booted node unless the DID used the overlay backend — favela-host sets none, so that is every DID it mints — while the real store sat in scope already serving three other surfaces. Only an IN-PROCESS consumer reads that field, and the projector is the first one. Measured: 11 posts in the atproto repo, none with an image; the same posts on the fediverse with their jpegs attached, because that projection never asks for a blob store. ⛔ BANNERS NEVER REACHED ANYTHING. The banner shares the avatar's store on purpose and inherited its 512 KiB cap, which the source itself calls a thumbnail policy. A banner is a wide header and does not fit, so the upload threw — after the avatar in the same submission had already saved, which is why it read as "the avatar works". The live fediverse actor had `icon` set and `image` null, and the atproto profile had no banner. Every link in the chain was correct; only the cap was wrong. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
73462b4a4021829e1dfe83c0f9efbcd5962e815d
by plankatron <fleeky@gmail.com> · 2026-09-11T23:07:23.000Z

Changed files (1) +1 -1

package.json +1 -1
……@@ -1,6 +1,6 @@
11{
22 "name": "favela-surface-android",
3 "version": "0.0.35",
3 "version": "0.0.36",
44 "description": "favela-surface-android — a React Native shell over a bare-kit worklet running a full favela-peer node (markdown records, no atproto) with favela-surface rendering its pages in a WebView.",
55 "type": "module",
66 "private": true,