archy

218 Commits 57 Branches 23 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
archipelago	3347b8b8b9	fix(ui): https app launches and the nostr bridge follow the frame's real origin Three launcher/bridge defects combined to make HTTPS dashboards look broken while HTTP ones worked: 1. portAuth() looked the launch port up under the name the user clicks ('mempool-web', 'lnd', 'bitcoin-knots'…), but the signed catalog declares those ports under the manifest id that owns them (archy-mempool-web, lnd-ui, bitcoin-ui). The lookup missed, portIsGateFronted answered false, and an HTTPS dashboard handed app frames http:// URLs — blocked as mixed content: mempool and IndeeHub 'did not connect', bitcoin knots/core opened http:// in a new tab. Resolution now follows launch aliases, then a port-wide catalog scan that only answers when every declarer of that port agrees (a port any app publishes as plain HTTP is never upgraded to https). 2. The signed-catalog cache was only warmed by the Store/Discover views, so a user who went straight to My Apps launched apps with an empty cache. Warmed at dashboard mount now — fetchAppCatalog() already memoizes with a 1h TTL. 3. The NIP-07 bridge compared event.origin for strict equality with the recorded (http) app URL and replied to the recorded URL as the postMessage targetOrigin — both break the moment a frame is scheme- upgraded (cached HSTS did exactly that): every nostr request was silently dropped and replies to the stale origin threw. The bridge now matches host+port (scheme deliberately ignored) and always replies to event.origin — the frame's real origin. Unit tests cover alias resolution (incl. bitcoin-knots→8334→https), the conservative port-scan, and scheme-agnostic sender matching.	2026-09-01 10:29:05 -04:00
archipelagoandClaude Fable 5	2399eeac66	feat(ui): auto-tab fallback — embed-refusing apps become tab apps Demo images / Build & push demo images (push) Successful in 3m49s Details An app whose frame never loads while its backend reports Running (the embed-refusal signature: frame-busting JS, top-level-origin apps, SameSite=Strict logins — everything the gate's header stripping cannot fix) is remembered in localStorage; every later launch opens a tab straight from the click (user gesture, so no popup blocker), and opensInTab() gives it the tab-launch icon. A successful iframe load clears the memory and entries expire after 7 days, so nodes that gain embedding (gate improvements) get re-probed instead of being remembered broken forever. Dev guide updated; v1.8.2 changelog + What's New curated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-13 20:23:04 -04:00
Archipelago	b67e1527a2	Archipelago — open-source initial import	2026-08-12 10:55:50 +00:00

Author

SHA1

Message

Date

archipelago

3347b8b8b9

fix(ui): https app launches and the nostr bridge follow the frame's real origin

Three launcher/bridge defects combined to make HTTPS dashboards look
broken while HTTP ones worked:

1. portAuth() looked the launch port up under the name the user clicks
   ('mempool-web', 'lnd', 'bitcoin-knots'…), but the signed catalog
   declares those ports under the manifest id that owns them
   (archy-mempool-web, lnd-ui, bitcoin-ui). The lookup missed,
   portIsGateFronted answered false, and an HTTPS dashboard handed app
   frames http:// URLs — blocked as mixed content: mempool and IndeeHub
   'did not connect', bitcoin knots/core opened http:// in a new tab.
   Resolution now follows launch aliases, then a port-wide catalog scan
   that only answers when every declarer of that port agrees (a port
   any app publishes as plain HTTP is never upgraded to https).

2. The signed-catalog cache was only warmed by the Store/Discover
   views, so a user who went straight to My Apps launched apps with an
   empty cache. Warmed at dashboard mount now — fetchAppCatalog()
   already memoizes with a 1h TTL.

3. The NIP-07 bridge compared event.origin for strict equality with the
   recorded (http) app URL and replied to the recorded URL as the
   postMessage targetOrigin — both break the moment a frame is scheme-
   upgraded (cached HSTS did exactly that): every nostr request was
   silently dropped and replies to the stale origin threw. The bridge
   now matches host+port (scheme deliberately ignored) and always
   replies to event.origin — the frame's real origin.

Unit tests cover alias resolution (incl. bitcoin-knots→8334→https),
the conservative port-scan, and scheme-agnostic sender matching.

2026-09-01 10:29:05 -04:00

archipelagoandClaude Fable 5

2399eeac66

feat(ui): auto-tab fallback — embed-refusing apps become tab apps

Demo images / Build & push demo images (push) Successful in 3m49s

Details

An app whose frame never loads while its backend reports Running (the
embed-refusal signature: frame-busting JS, top-level-origin apps,
SameSite=Strict logins — everything the gate's header stripping cannot
fix) is remembered in localStorage; every later launch opens a tab
straight from the click (user gesture, so no popup blocker), and
opensInTab() gives it the tab-launch icon. A successful iframe load
clears the memory and entries expire after 7 days, so nodes that gain
embedding (gate improvements) get re-probed instead of being remembered
broken forever. Dev guide updated; v1.8.2 changelog + What's New curated.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-13 20:23:04 -04:00

Archipelago

b67e1527a2

Archipelago — open-source initial import

2026-08-12 10:55:50 +00:00