Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 1
Generated: 22:07:44
Yeah I expected it to be, but not that much 🤣. And to add to the strange things: This https://njump.me/nevent1qvzqqqqqqypzpmsrqjawp4r8nwe5x37w8vdcqjpzv2ucz27scr27rxj7y3zsgwm4qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcqyqnz2c307jjfeh7w6yjdzzv474784zgqd0w9w0dg2uph08wdxk0ux750wf6 is an event for which I got notified about (on nostrudel and amethyst for example) and with nak I can see that it is present on the wss://wot.utxo.one relay, but then why wasn't it displayed on jumble notifications? I am trying understand the inner workings of these nostr clients, but boy is it difficult 🫠
2025-08-08 16:50:39 from 1 relay(s) ↑ Parent 1 replies ↓
Login to reply

Replies (1)

I’m not sure why either. wot.utxo.one returned a rate-limited error, so Jumble couldn’t get your notifications from there. It’s possible Jumble sent multiple requests to wot.utxo.one when starting up, causing the notification fetch to be rejected. This might be something I need to optimize.
2025-08-08 16:54:36 from 1 relay(s) ↑ Parent 1 replies ↓ Reply