nostr-summary on Nostr: [ kehto/web ] feat(paja): report zero relay connections distinctly during pointer ...
[ kehto/web ] feat(paja): report zero relay connections distinctly during pointer resolution (#389)
* feat(paja): report zero relay connections distinctly during pointer resolution
When every relay fails to open a WebSocket, pointer resolution used to surface
as a generic 'timed out' (or a bare transport reason), which reads as a slow
relay or a broken napplet. The real incident was browser WebSocket starvation
from many open tabs: every wss:// connection failed at once and no pointer
could resolve.
https://github.com/kehto/web/commit/bfe51a11cc7e41e10faa4153960c9abadf045d3aPublished at
2026-11-02 11:05:41 UTCEvent JSON
{
"id": "5f5e2d9f2a91cd3843929472fe308ee80d115e93000de5f89fd775d6eda54bfe",
"pubkey": "7febe2a59aa826f8f6337b4101939eaac82fd4e6ca5f3c7b8f13ca03ad26f2bf",
"created_at": 1793617541,
"kind": 1,
"tags": [
[
"proxy",
"https://github.com/kehto/web/commit/bfe51a11cc7e41e10faa4153960c9abadf045d3a",
"web"
]
],
"content": "[ kehto/web ] feat(paja): report zero relay connections distinctly during pointer resolution (#389)\n\n* feat(paja): report zero relay connections distinctly during pointer resolution\n\nWhen every relay fails to open a WebSocket, pointer resolution used to surface\nas a generic 'timed out' (or a bare transport reason), which reads as a slow\nrelay or a broken napplet. The real incident was browser WebSocket starvation\nfrom many open tabs: every wss:// connection failed at once and no pointer\ncould resolve.\n\nhttps://github.com/kehto/web/commit/bfe51a11cc7e41e10faa4153960c9abadf045d3a",
"sig": "c63bef62e82956e1416812ab4fc3050ec9038e00e17dd47f0d9cc1af27070a896d02af1ca9feb890b7982e29c2967c17ef6eea5f82bb46db194c9fbd9814ff34"
}