OverviewFilesCommitsIssuesDocsReleasesPeers

pearbrowser-desktop commits / 7ec6c93

Record v0.7.1 Pear publications
7ec6c9333881ad0c1cc7c891b195318d6f23efd1
by Local LLM <localllm@local> · 2026-07-16T13:44:49.000Z

Changed files (2) +12 -4

README.md +1 -1
……@@ -4,7 +4,7 @@ A local-first peer-to-peer browser, app store, search engine, naming layer, Nost
44
55**No accounts. No DNS. No manual app updates.** Sites and apps are addressed by stable Pear/Hyperdrive keys and pinned 24/7 on the [HiveRelay](https://github.com/bigdestiny2/P2P-Hiverelay) backbone. The publisher's laptop being offline doesn't matter — the relays carry the bytes, and users launch the current release from the catalogue without hunting for a download or applying an updater.
66
7**Current release candidate:** `v0.7.1`. This corrective release makes the renderer/backend RPC transport survive reload and live-update handoffs: pending calls fail immediately on disconnect, the per-launch authenticated socket reconnects during a bounded grace window, and the shell visibly resumes instead of reporting unrelated 30-second command timeouts. It retains all `v0.7.0` Content Shield, Pear Plugins, and P2P catalogue features. See [docs/RELEASE_v0.7.1_OPERATOR.md](./docs/RELEASE_v0.7.1_OPERATOR.md) for the coordinated publish record.
7**Current release:** `v0.7.1`. This corrective release makes the renderer/backend RPC transport survive reload and live-update handoffs: pending calls fail immediately on disconnect, the per-launch authenticated socket reconnects during a bounded grace window, and the shell visibly resumes instead of reporting unrelated 30-second command timeouts. It retains all `v0.7.0` Content Shield, Pear Plugins, and P2P catalogue features. The stable Pear link is live at length `92835`, and catalogue version `9` advertises the release. See [docs/RELEASE_v0.7.1_OPERATOR.md](./docs/RELEASE_v0.7.1_OPERATOR.md) for the coordinated publish record.
88
99**Current architecture:** start with [docs/ARCHITECTURE_AND_CAPABILITIES.md](./docs/ARCHITECTURE_AND_CAPABILITIES.md). The deeper catalogue/search/naming/Nostr audit is in [docs/DEEP_AUDIT_CATALOG_SEARCH_NAMING_NOSTR_2026-06-21.md](./docs/DEEP_AUDIT_CATALOG_SEARCH_NAMING_NOSTR_2026-06-21.md).
1010
docs/RELEASE_v0.7.1_OPERATOR.md +11 -3
……@@ -45,9 +45,17 @@ Hyperdrive mirror all advertise `v0.7.1` and pass their fresh-reader checks.
4545
4646## Final record
4747
48- Source merge/tag: pending
49- Stable Pear length: pending (from `78006`)
50- Live catalogue length/version: pending (from length `307`, version `8`)
48- Source merge: PR [#65](https://github.com/bigdestiny2/pearbrowser-desktop/pull/65),
49 merge commit `3afe35c0337daa4f3ebce7270842b563f066bd55`.
50- Stable Pear length: `92835` (from `78006`); five relays accepted the seed
51 request. A fresh peer found seven peers, reached the exact length, and read
52 `/index.html` (451 bytes). A signed HiveRelay storage proof was unavailable
53 because the relay returned `ROUTE_NOT_FOUND: storage-proof.prove`; the direct
54 fresh-peer content check passed.
55- Live catalogue length/version: `324`, version `9` (from length `307`, version
56 `8`); five relays accepted the seed request. A fresh reader found five peers,
57 verified the signed metadata, all 14 application rows, PearBrowser `0.7.1`,
58 and the expected Peercord, peerit, and HiveWorm entries.
5159- GitHub release/workflow: pending
5260- Website deploy: pending
5361- Website Hyperdrive length: pending (from `126`)