Should we all drop the "coso" part of hashtags going forward? It hasn't really made sense since the fork, and that was ages ago.
Upside: Tags become shorter.
Downside: Unlinking from older posts using the prefix.
Examples:
cosomusicians vs. musicians
dogsofcoso vs. dogs
cososec vs. sec
@voltronic I do both.
@voltronic Feels kinda hokey, to me, to jam "coso" into every single hashtag. Like... I know where I'm at. 😅
When in Rome, though.
@voltronic
2 reasons.
First, we've been doing it from the start.
Second, it flags any content stolen amd reposted elsewhere.
@ArcturusSaDiablo
Just taking the counter argument here:
1. From what I remember, it was only done from the start because we were a federated instance of Mastodon and we were trying to identify posts from our instance. That hasn't been necessary in years.
2. Maybe, assuming someone screenshots the entire post including hashtags. If having your posts stolen is a concern, the way to mitigate that is to post to followers only and tightly screen your followers.
@voltronic
I think of it as more of a way to ID the source in case it show up elsewhere. See also, "If it ain't broke, don't mess with it."
@voltronic
Agreed that if a screenshot is shared elsewhere cropping and actual work will have to go further than otherwise.
Also I just like the sense of community.
@voltronic I kind of like it. Gives a unique sense to the community. But I see the advantage in maybe including both versions of the hashtag (#music/#cosomusic) to make it easier for new members to find things.