In my opinion the only good thing it does is to create copies of already existing communities, so basically people tend to follow one community or the other and it divides the people who could be active.
If you want to create a community that’s similar to one and for some reason you don’t want to be a part of it, find another name, if you can’t find another name, create your own instance. So if Lemmy is federating now we could have /c/worldnews, /c/world_news, and the same applies to every other instance that decides to do the same. In my opinion this only segregates people.
The same applies to uppercase letters, which Reddit uses but luckily Lemmy does not, imagine how many copies of a community could be created if you use both.
i say !WorldNews & !world_news should be (~symlinked to ?) the same !wordnews community unless exceptions (for different /c/…) permitted by administrators or upvoted somehow. With this, uppercase is no problem & readability would be nice.
Adding upper case letters to addresses would indeed increase what the “_” does, I don’t think we should add them. Your method also requires manual intervention which is just not a good idea.
I’m not sure… I’m pretty sure sometimes and in some languages, separating two words can really change the meaning of a title, don’t you think ?
Example?
super_bowl
superb__owl
This applies to a username, not to a community, unless you want to create a community for the Super Bowl in which case it’s already obvious because the community name, not the community address, is “Super Bowl”, and all of the community like the description, banner and icon are related to the Super Bowl.
Absurd example, but there is a city named “Chicken” (It actually exist !) A community about cooking chicken : eatin_chicken A community about places to eat in the city of Chicken : eat_in_chicken
I mean… I think there are a couple of valid examples, I think it would make more sense to create a community named /c/chickencity and there you’d ask for places to eat, though. But let’s say it’s a valid example, in my opinion the pros are more than the cons. How many copies of communities can be created by adding the _ and how many communities will need to phrase their address in a different way because of it?
I don’t know tbh. You can make two copies of essentially the same community around the same interests/subjects with different names, underscore or no underscore. I think “mechanically” solving a problem like that is not a great idea, and that defining if two community should be merge fall into the hands of admins and administrators, not developers. If you are a mod of a community, or admin of an instance, chances are you know that such “clones” exist, and you either think you should merge and do it, or think you have a valid reason to stay apart and are free to do so.
Of course you can make similar copies, the thing is that with this issue people create them without realizing it and it super common, whereas having to find a similar name it’s done on purpose.
It can be useful as a word seperator. If its a copy, instance admins can remove it if necessary. Also, it seems inconsistent to allow _ in community names, but not in usernames (if thats what you’re suggesting).
That precisely is one of the things I found it irrelevant for, what do you want to use a word separator for? It makes sense in names because there can be a million users, but with communities it’s not the same, we don’t need 5 communities with similar names.
Imagine this: /c/league_of_legends /c/leageof_legends /c/league_oflegends /c/leagueoflegends I just don’t see the point and I don’t think it makes it so much easier to read, since anyway most of the time you will be reading the display name, not the address.
You would have to ban more than just the hyphen, so might as well leave it as is
That’s the only character allowed, so everything else is already banned. If you try to create a community it says “lowercase, underscores and no spaces”.
