My time away gave me some perspective on :Nostr: Nostr things. The #communikeys spec being one of them.
So I made it better (I think 😉):
Or
nostr:naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyghwumn8ghj7mn0wd68ytnhd9hx2tcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqqumnfwqkkxmmdd46ku6ttv4us8t5702
The right to publish content types is now 100% :badge: Badge based (no more fees or other complexity).
For this, Badges just need a one tag update that lets people request the badge from the author with a Form they fill in, which I think is useful for Badges in general.
nostr:naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyghwumn8ghj7mn0wd68ytnhd9hx2tcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqqjmnfwqkkyctyvajsxu8naa
Business, Brands and Apps that want to embrace Nostr already have:
- a pubkey by default
- very often some kind of members or subscriptions categories for their users/customers
So I believe this spec maps onto that really well. Little complexity (relative to other community specs) and tons of flexibility, all while keeping transparency to the users.