In this case how can you ever learn about new relays a user might have migrated to? From event hints?
Kind 6 is an antipattern.
Do you send the same query to all relays? i.e. if user A is most likely not publishing to relay Z but relay Z is selected to be connected to, do you still ask Z it for A's posts?
This is a must-watch: #[0]
What do you think about the Gossip model? https://mikedilger.com/gossip-relay-model.mp4
I don't know what a DMUD is, but sounds very interesting.
XSS is not a problem if you use good libraries or be careful in your code. Use native clients though, the web is a complete mess.
But real people are so boring!
Nunca tive esse problema no https://github.com/mikedilger/gossip
al-bee
We're well served of web clients I believe. We need more Nostr native desktop clients.
No, they can read from it anyway. They just can't publish unless they go to https://eden.nostr.land and pay.
https://astral.ninja/ is very good too, I hadn't tried it since a long time ago. After the very first initial setup (when it is probably loading a bunch of notes and saving on the local db) it gets pretty smooth.
Publishing this note to wss://eden.nostr.land/, where no spammers will enter.
#[1]
https://hamstr.to/ is good.
Would be nice if some relays automatically sent you a "curated" global feed if you sent a filter specifying nothing.
Curated could mean only posts from friends of friends, for example.
Anyone running the Elixir relay? The C++ relay? The Clojure relay?
NIP-01 is already clear about it being plaintext.