docs(tracker): add B22 (peer download/audio errors), B23 (group chat), B3 PASSED-http
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
602b9cd3df
commit
6c92eacba0
@ -114,6 +114,14 @@ Tag whether the peer connection is Tor or FIPS and surface it as a small pill on
|
|||||||
### B22 — Peer cloud download/audio errors (.228→.198) — TODO (pairs with B3)
|
### B22 — Peer cloud download/audio errors (.228→.198) — TODO (pairs with B3)
|
||||||
Observed 2026-06-15 browsing .228's cloud from .198: (a) downloading a peer cloud file → "Operation failed. Check server logs for details." (b) playing a peer AUDIO file → "Could not play audio. File Browser may not be running." (misleading — it's a peer file, not File Browser; that's the OLD base64/blob path B3 replaces). ACTION: (a) check content.download-peer backend error on .198 logs while downloading (likely the same Range/transport/timeout path as B3, or a peer-side 4xx); (b) verify B3 streaming fixes peer audio once deployed, and fix the misleading audioPlayer error string. Get server logs: ssh .198, journalctl -u archipelago | grep -i 'content\|peer\|download'.
|
Observed 2026-06-15 browsing .228's cloud from .198: (a) downloading a peer cloud file → "Operation failed. Check server logs for details." (b) playing a peer AUDIO file → "Could not play audio. File Browser may not be running." (misleading — it's a peer file, not File Browser; that's the OLD base64/blob path B3 replaces). ACTION: (a) check content.download-peer backend error on .198 logs while downloading (likely the same Range/transport/timeout path as B3, or a peer-side 4xx); (b) verify B3 streaming fixes peer audio once deployed, and fix the misleading audioPlayer error string. Get server logs: ssh .198, journalctl -u archipelago | grep -i 'content\|peer\|download'.
|
||||||
|
|
||||||
|
### B23 — Archipelago group chat (all nodes) broken/slow over Tor — TODO (PRIORITY, mesh)
|
||||||
|
The all-nodes "Archipelago group" chat (over Tor) doesn't seem to work. Facets:
|
||||||
|
- (a) Group delivery unreliable / "doesn't work" over Tor.
|
||||||
|
- (b) Messages may just be VERY SLOW (latency — likely Tor-only path; should use FIPS+Tor per the new transport method like B14, preferring FIPS).
|
||||||
|
- (c) Add the SENDER CONTACT NAME to each message so you can differentiate who sent what (group messages lack attribution).
|
||||||
|
- (d) Messages sometimes DUPLICATED (dedup by message id / sender_seq — cf mesh.ts:73 cross-transport identity (sender_pubkey, sender_seq); duplicate likely from receiving same msg over both transports or re-broadcast).
|
||||||
|
Code: core/archipelago/src/mesh (typed_messages, listener), frontend Mesh.vue/stores/mesh.ts. Relates to B2 (identity), B14/B14b (transport). Test on .116/.198 (+ a Tor-only peer like .228).
|
||||||
|
|
||||||
### B8 — netbird app doesn't work — TODO (LOW / much later)
|
### B8 — netbird app doesn't work — TODO (LOW / much later)
|
||||||
|
|
||||||
(RETRACTED: CryptPad placeholder-icon — user says cryptpad is fine.)
|
(RETRACTED: CryptPad placeholder-icon — user says cryptpad is fine.)
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user