Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 18
Generated: 16:05:07
avatar
chrizzz npub13syp...gns9
nostr:nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7q2uwaehxw309ac8ymmc0yhxummnw3ez6un9d3shjtnpwpcz7ct9xvcxycfjxvmnycm9vsmxxvfexccxgdpevvcryd3kvejxgvm9xqmkxetpx5exyvtzvcenwwrxv33rvwp5v9jk2d3nxcekgetrxsmqqltm2c something changed and Jumble can't read Tor relays anymore, for example: ws://oxtrdevav64z64yb7x6rjg4ntzqjhedm5b5zjqulugknhzr46ny2qbad.onion/
2025-11-11 14:58:26 from 1 relay(s) 2 replies ↓
Login to reply

Replies (18)

avatar
Cody cody@jumble.social npub1syjm...f6wl
Looks fine on my end. But if you're connecting to a ws:// relay, you might need to tweak your browser’s security settings. On Tor Browser (desktop), go to about:config and set network.websocket.allowInsecureFromHTTPS to true, that should do the trick. image
2025-11-12 02:06:05 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
avatar
Cody cody@jumble.social npub1syjm...f6wl
That makes sense, the issue is that right now it only checks whether the userAgent contains "torbrowser" to decide if the browser supports onion. I’m not sure if there’s a more reliable or efficient way to detect it. Maybe adding an option in the settings would be a better approach.
2025-11-12 06:22:51 from 1 relay(s) ↑ Parent 1 replies ↓ Reply