What do we do when we have one hashtag and two meanings for it?
Like, there is #Amethyst, for the Nostr client, and #Amethyst for crystallography research.
If the same hashtag is used by both groups in separate relays and users start merging those relays by rebroadcasting stuff, do both hashtags just cease to become interesting?
Do their communities disappear out of "I am not here for this" feelings of disappointment? Is this a Nostr battle for which community wins over the other by the sheer amount of posts? Do clients have a role in this? Do relays?
How do we solve it? Do we even need to solve it?
Replies (37)
I recall
@jack saying similar issues about hashtags like this with the old days at twitter
@jack what solutions have you guys tested over there? Tell us your secrets. :)
- Actual communities
- Using the wiki topic instead (as the topic I'd)
Hash collisions? π
Moderator-led communities are an easy answer. But I do wonder if there are alternative schemes, like what
@jb55 has been discussing.
Me too.
And it's the same topic-problem wikis have too. Hence my idea.
The beauty and the problem of #hashtags is that anyone can use it to either reference the actual topic, or to infiltrate its feed (like it happened with some porn making it to the #zapathon feed briefly).
If the ability to use any hashtag is taking away from users, discoverability on #nostr is hindered, but is there anyway this can be solved on a user level?
Do we need moderators to filter? People or Ai filters?
Language is Defined by The User.
Clients, Relays, and Users will adapt to this accordingly.
#Amethyst
I don't think you need to solve it. the lesser community will come up with their own hashtag to circumvent the larger community. it happens all the time.
No point bothering with hashtags, when AI can figure out the topics covered.
I just use them to make the word appear in a different #style.
Yeah I think it's kind of a "is what it is" problem
I feel like we had the same feeling with WoT a couple years ago, but WoT never came to save us.
This is a moot argument because people can use any hashtag they want for any topic or discussion. Hashtags are cool on paper, but in practice they just don't work. #foodstr
Well, you can still game a semantic search.
Best protection against that is moderating users and/or requiring payment.
So your 2 positions are:
* we already have all the tools we need to make hashtags work
* hashtags can never work except on paper
My position is still that hashtags can work when devs build the tools for them to work, which you fucking gaslit me and muted me over because it contradicted your position that we already had those tools, but now you say hashtags can only work on paper?
Why are you fucking allergic to the simple position of "we should build the tools hashtag users need?"
Why are you fucking allergic to the simple position of "we should build the tools hashtag users need?"
Why are you fucking allergic to the simple position of "we should build the tools hashtag users need?"
What the fuck is wrong with you and your supporters?
@7fqx please either call out this guy's bullshit or defend why you act like he's not so bad
Why when u post videos on Primal it wonβt show on Amethyst & tells u to go to Primal to download video @Vitor Pamplona ??? I thought u can view videos in any apps
Hashtags are retarded. Always have been.
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.
Well first -- it would be a great problem to have if there were actually enough users here to make a viable "crystallography" community.
But 2nd, I'm sure Twitter had to evolve through this kind of thing. As others have pointed out, AI-powered content discovery might solve this as well.
Lol, post of the year right here.
Don't these things eventually self-resolve if there is longer-term use/confusion.... ie. #AmethystApp #AmethystCrystals
They do, but those communities suffer a lot in between. Then the problem repeats a few years later when one of them goes back into using #Amethyst again because no one else is using it.
You wouldn't zap a hash crash π I'll see myself out
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.
As usual, we'll call it a nostr feature and we'll pat ourselves in the back (2Β’)π
Joking aside, this is a common issue, usually most popular group wins.
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.
We don't need to solve it, and eventually one use will win over the other and it will solve itself.
#AmethystApp
got the same problem with #matrix the movie
and #matrix the messaging application
I think it helps with discovery. plenty of words have more than one meaning, we'll manage. not a problem, a solution.
Vitor Pamplona
What do we do when we have one hashtag and two meanings for it?
Like, there is #Amethyst, for the Nostr client, and #Amethyst for crystallography research.
If the same hashtag is used by both groups in separate relays and users start merging those relays by rebroadcasting stuff, do both hashtags just cease to become interesting?
Do their communities disappear out of "I am not here for this" feelings of disappointment? Is this a Nostr battle for which community wins over the other by the sheer amount of posts? Do clients have a role in this? Do relays?
How do we solve it? Do we even need to solve it?
View quoted note →
Vitor Pamplona
What do we do when we have one hashtag and two meanings for it?
Like, there is #Amethyst, for the Nostr client, and #Amethyst for crystallography research.
If the same hashtag is used by both groups in separate relays and users start merging those relays by rebroadcasting stuff, do both hashtags just cease to become interesting?
Do their communities disappear out of "I am not here for this" feelings of disappointment? Is this a Nostr battle for which community wins over the other by the sheer amount of posts? Do clients have a role in this? Do relays?
How do we solve it? Do we even need to solve it?
View quoted note →
WoT is not a plug-and-play solution, it is a group effort of aggregated relational endpoints and edges.
What we can (and should) do with WoT is form trusted networks of relays (nip-66)
What we can do with WoT is offer verifiable consensus amongst moderated auth-enabled relays
What we can do with WoT is manage friend lists and trust scores and curate lists between users and groups.
However what we cannot do with WoT is wait for it to solve problems that are inherent to the protocol.
On dedicated community relays, hashtags don't conflict across a global feed of notes. Each relay has its own collection of respective hashtags.
I have to side with
@cloud fodder and nip-66 / nip-42 on the order of hashtag conflicts.
In a smaller world, individual conflicts can be addressed and resolved without mass, global dilution.
Nip29 groups solve all these things.
β₯οΈ
Underrated comment.
