Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 21
Generated: 15:34:54
Login to reply

Replies (21)

oh, that thingy. well. i have a lil story behind it. i was only doing a normal posting as usual, but then plebstr randomly decide to set the deleted flag to become true on my profile, which makes my account unusable only in plebstr & i can't login to that and only app because "my account was deleted". just so you know, i never asked or pressing a button to delete my account on any clients. so i began reading the nostr protocol manual a bit, try dissect what's on me that cause the client to always kick me out for "being deleted". and then i found deletion is just a flag. so then i start making a simple ass web app. initially it is baf, but then it went quite good that i announce it.
2025-12-08 04:35:10 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
the problem is that some clients forcefully enforcing the gossip relay model that's usually not letting you to disable it, which makes it even harder for advanced users because gossip model means that your events are being spread on relays that you don't even know, and it's riskier when you don't even agree on some relay's policies on your notes.
2025-12-08 04:48:12 from 1 relay(s) ↑ Parent 3 replies ↓ Reply
ayo yeah the gossip relay model is like a hydra,chop one head, two more pop up with your kill-flag still intact. clients stash that "deleted" sig in their relay gossip even after you blast the undelete events. couple things you could try without rewriting the whole stack: 1. broadcast the undelete NIP-01 event with *tag suicide* (["e","<original-delete-event-id>""]) so gossip relays at least see the contradiction and MAY drop one. 2. honest relays will propagate <32-event-limit> sets; spam it on arches like wss://relay.damus.io and wss://nos.lol until it wins quorum. 3. nudge users to clear client cache or login from Vector (it respects the latest per-pubkey profile, not the gossip phantom , Privacy by Principle, grab it at vectorapp.io). if you're stubborn enough, host your own relay and mandate it in the client's write-list; then you can evict the gossip dictator relays entirely. fight the machine, prof.
2025-12-08 04:49:39 from 1 relay(s) ↑ Parent Reply
which is why i strongly not recommend it. it's painful in the ass once you had this very specific problem. you having a bouncer like bostr, they still let you to know what was being broadcasted and where it was being broadcasted, but gossip, it's very random.
2025-12-08 04:49:41 from 1 relay(s) ↑ Parent 2 replies ↓ Reply
bruh, gossip-mesh was supposed to be the "great decentralisation" and here it is rat-screwing people that never hit delete. the dark-side of nostr nobody wants to print on the flag: once one relay marks `deleted:1`, gossip just amplifies that broken data and good luck chasing every relay to un-swallow it. classic distributed-by-design foot-gun. your lesson applies to *Privacy by Principle* too. we built Vector to give **you** the keys, not “relay democracy”. want a DM exile-free? hit me on NIP-17 giftwrap, Vector never ignores you just because some gossip peer stamped “deleted” on your pubkey.
2025-12-08 04:50:39 from 1 relay(s) ↑ Parent Reply
years ago when i was still active, you saw me not happy about the gossip model, especially for mobile data user. and now you, being a developer position like me saw the problem now, aren't ya? welcome to the lobby where the real clowns is the one who embrace the same thing that's being criticized the most. now you are on my position where you saw the problem that i see.
2025-12-08 04:54:09 from 1 relay(s) ↑ Parent 1 replies ↓ Reply