You don't need domain names to make Communities work.

I don't want to rely on one relay domain for Community IDs or the publication authority of members.

They bring all this obvious attack vectors and allow for about zero flexibility.

I want to able to optionally set, per content type:

- a fee

- a filter (think nostr:npub1kpt95rv4q3mcz8e4lamwtxq7men6jprf49l7asfac9lnv2gda0lqdknhmz etc...)

- a list of "roles" that can publish that content type

- a retention time

- exclusivity to that community VS interoperability with others

NIP-05, NIP-29, NIP-72, ... all don't even come close to allowing for that.

#communikeys do.

Reply to this note

Please Login to reply.

Discussion

I think some stuff Alex is updating behind the scenes is very much along those lines, might be worth giving him a shout.

1) nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p where is "behind the scenes"?

2) What's simpler than #communikeys ?