github-such-software/adaptive-multi-protocol-browser
1
0
Fork 0
mirror of https://github.com/Such-Software/adaptive-multi-protocol-browser.git synced 2026-10-22 08:48:33 +02:00
Code Issues Packages Projects Releases Wiki Activity

Harden browser docs and transport recovery

Browse Source
This commit is contained in:
jwinterm
2026-07-11 08:59:21 -04:00
parent 97a43f8572
commit 4379b99245
17 changed files with 354 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/desktop-vertical.md
+5 -5
View File
@@ -1,6 +1,6 @@
# Desktop Vertical
> Status: draft | Updated 2026-07-07 | Applies to: AMPB desktop builders
> Status: draft | Updated 2026-07-11 | Applies to: AMPB desktop builders
The first AMPB browser proof is desktop-first with mobile constraints kept in view. The
vertical is a bundled Gecko desktop runtime, AMPB-owned profile state, and a managed Tor
@@ -26,10 +26,10 @@ artifacts are available for the selected checkout.
## Transport Path
The first transport target is Tor through an AMPB-owned Arti/Tor runtime. The desktop
vertical is not complete until AMPB can start the runtime, verify the SOCKS endpoint, and
launch the bundled browser profile without clearnet fallback. I2P and Reticulum use the
same route, consent, state, and health-check model after Tor works.
The first transport target is Tor through an AMPB-owned Arti/Tor runtime. The current
desktop vertical can launch a bundled Gecko runtime, start a route-aware helper, and keep
the helper tied to the browser process. I2P uses the same route, consent, state, and
health-check model. Reticulum follows after the resilient-network adapter is concrete.
## Desktop Shell