everything keeps going in circles:
hashtags, works on any relay -> gets spammed -> use different relays where hash tags are moderated -> which relays? -> goto 10.
the pieces that are missing:
invites to relays + nip66 enhancements. invites or recommended relays for a particular hashtag. relays being mod capable, easy to mod, via CLIENTS, in the first place.
Lol, post of the year right here.
i keep bringing up the hashtag association with a relay set could easily be a 'community' but clients are not interested. i think, because they werent architected to be able to do such a thing and would need a rewrite (kinda like outbox rollout).
i am hopeful that the outbox generation of clients will have more control over their sdks so as to make these experiments possible.
We could do #bitcoin@nostr1.com as a hashtag.
Or a #bitcoin@nprofile1.. as a hashtag. 🤔
In those cases, users could at least choose which definition they are going for. Spam is still an issue.
heres a simple case:
you create a team that cares about a hashtag. you create a relay, with them as mods. you publish your nip66 events with the hashtag.
clients offer up these nip66 relays, when following a hashtag, the relays go in the field for relay in the follow list.
mods that browse global of that relay casually can remove offtopic and etc, perform their regular mod duties as they see fit.
done!
I prefer associating #communikeys with hashtags, labels and wiki topics.
So that these communities can be found by browsing on either of these three.
Our #Zaplab clients will make that experiment, at least, very possible.
