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).
post
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 ?
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.
You would have to ban more than just the hyphen, so might as well leave it as is
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.
all 12 comments