Derek Ross
· 1d
sure, which is why you can use multiple relays, just like regular nostr. this is why i've always disliked NIP-29. i don't like single points of failure.
Well, kindly pushing back on the "just like regular nostr" part. I've been reading through the spec and the Armada codebase, and that part doesn't really hold up. Concord relays need a specific configuration, as far as I can tell.
Concord reverses nip 59. A normal gift wrap has a random one-time author and the real recipient in the p-tag. Concord flips it: the author is a the stream key, and the p-tag is a random ephemeral key. Members read by the author, not by the p-tag. So it breaks on any relay doing the nip 59 "correct" thing, because nip 59 says relays SHOULD only serve kind 1059 to the marked recipient, and here nobody is the marked recipient. The spec admits it outright: "Communities must choose relays accordingly."
Also, if someone uses relays that prune or just nuke their db, that breaks the whole authority layer (roles, bans, channels all ride on 1059), and deletion gets messy because every wrap is authored by the same shared stream key that every member holds: on generic relays that honor author-based deletion, anyone can delete any message, or all of them, just by sending deletion requests, which from my POV is a huge hole.
In practice Armada runs on two default relays configured in the same way
