If I understand the spec correctly, it shouldn't be that much hard. In a general big relay that is used by different clients, this check may break the function or performance of the relay. But in a Communikey specific relay it won't have any issues.
nostr:npub1h49w8en79xty6j2pwgnpm3znjhyf767jua6xgt3kvyn3w80ms86s2z9kay how easy would something like this be to implement on the (automated) relay side?
The idea is that you'd (for example) ONLY accept Articles from the profiles that have a "Member" Badge (awarded by the #communikey itself OR someone with one awarded by the #communikey, not deeper).
Discussion
I'm setting up the spec so I can do in-app verification and still have it work in nostr:npub18stt78efprta2el02tzgnez6ehghzgtt000v58967wvkgezjmprs0n7h7u for #communikeys that use general dumb relays.
It'll just be slower and (potentially) a bit spammier.
Nice, will read it once you published it.
It's coming together in these wikis:
Thanks a lot. I'll read it. 👀
Great! Good to know 😃