Just link to the Community / Brand pubkeys.
They can build a #communikey, on it when they and the apps are ready for it.
Or have fun chasing community event IDs (or even relay addresses + slugs 🤦 ) of the other specs.
OK community folks, how do we best represent the 500 or so nostr:nprofile1qqsra2ey033mkdwl5w8q0jss9ak69zafh82xsuvhwsaauw3trkq2amgpz9mhxue69uhkummnw3ezuamfdejj7qgcwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tck28qzu communities natively on Nostr?
Right now we have an Area primative that is a geojson (multi)poly then a bunch of tags for name, logo, population etc. We use Areas for both Communities and Countries.
Feels like this is an Area kind that may reference existing community kinds of different flavours. Or a geographic addon to existing Community kind?
#asknostr
Discussion
#communigays
it sounds like a disease to me, communikeys
have you thought about the idea of not having the start of the word "communicable" in your naming schemes?
Yeah, existing specs are a bit of a mess.
All the socials and brand could be added to the Communikey? Then we just reference a generic Area from there if they want to hitch themselves to a geography?
Maybe just an optional property of a Community without the extra kind type?