What do you guys think about using Badges like this for relay access?

nostr:nevent1qvzqqqqqqypzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyt8wumn8ghj7mnfv4kzumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qpqtayhwf9x2jrq260tpqd26d07m2mr0v6vjj3ykuqj2vf248k8p0gqsfpp5r

Reply to this note

Please Login to reply.

Discussion

I prefer NIP-05, but that also works.

I can't do invites with NIP-05

yes you can. you can create a nip05 on someone's behalf, they dont need to have it in their kind0

Of course, but then I need an API so that people who already have a nip-05 can create (pending) nip-05s from within my apps.

Or if need an event for a Nip-05 invite or sth. But then the relay had to look at events as well and then the Badge solution wins.

Members need to able to invite others by directly handing them out write access. But only one level deep.

With nip-05 that gets complex fast

any source of access can be part of the Web Of Access (WOA). i am unsure about badges, i couldn't figure out from reading the spec if they were revokeable, but i assume you thought of this..

Deleting from the community relay = revoking already.

Good point tho, I didn't make that clear.

Second way of revoking is removing the badge from the profile label (or badge awarding event) of that profile.