to be decided on Nostr: > There are also clients to have communities .. Yeah, but that kind of adds another ...
> There are also clients to have communities ..
Yeah, but that kind of adds another layer on top of plain nostr. I'd prefer a nostr #community to exist and be accessible on "base" nostr, not exclusively in this or that app/client.
My point is: I think it'd make a huge difference if people were to adopt a culture of differentiating between different kinds of #hashtags.
Example: using the following hashtags transports/signals IMO an intention.
#comm_cats (don't know if this is supported)
#commCats
These, to me, say more clearly that the note is adressing a _community_ who cares about cats, than just using the hashtag 'cats'.
Maybe other people feel differently and they perceive using just a plain 'cats' hashtag as having the same intentionality of addressing the community, I don't know.
I like how adopting such a system of using hashtags would enable communities that are offering at least some of the functionality of #reddit communities. And all that with "plain simple" nostr.
Repeating myself here: I think agreeing on some common format for tagging communities would really make a difference. People might also be more conscious about tag usage if there's this explicit hint that a community is addressed. As opposed to just writing a post and adding a few tags that are somewhat related. 7fqx (npub1njs…7fqx)