From the perspective of writing and running a client, most of the relays are bitchy and it drives me nuts trying to manage and work with all these different bitchy relays with different rules and behaviors.

From the perspective of running a relay, a lot of clients are aggressive as fuck and it drives me nuts trying to keep my tiny relay from running out of resources without denying service to the nice people.

Nostr is a battlefield. And we're using hastily written software barely glued together from bits of string and chewing gum.

Reply to this note

Please Login to reply.

Discussion

I see so many relay errors when I post. Makes me wonder what kind of slowness my relays introduce when reading.

Is this something a new NOSTR standard can solve?

No. This can only be solved by writing more robust relays that can handle DDoS situations, and smarter clients that can handle all kinds of relay situations better. No matter what you do to a protocol, someone out there wont follow it and if what they do breaks your software, your software needs to harden up. I'm as guilty as anyone. We have work to do.

Only if there were multimedia nostr:npub1h0rnetjp2qka44ayzyjcdh90gs3gzrtq4f94033heng6w34s0pzq2yfv0g relay that could support a variety of use-cases… so people don’t have to reinvent a new relay for every new media/app type. 🤷‍♂️ nostr:note15xlnk7ycq9a9msscn5nvf5ad2rkx6f5u5u2096zmx2426qhpehnqhajkee