-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display names for communities are shown where name would be more appropriate. #234
Comments
This is the reason why in lemmur we show |
@dessalines I dont find the case you make convincing at all.
That doesnt mean its a good idea for every use case.
It can be a good thing, but it also has disadvantages. For example, the displayname can be misleading, especially when it gets changed to something completely different. And hovering to see the read ID doesnt work on mobile. I can definitely see that there are some advantages to showing displaynames by default, such as:
But there are also clear disadvantages which we cant ignore:
I think we should switch back to the previous behaviour of showing the name@instance, at least for communities but maybe also for users. Then we can have a more extensive discussion about it, and find a solution that most people agree with (like an option which one should be shown, deciding carefully what to use as default). And I really dont like that you originally changed this without discussing it with anyone. In fact I cant find any issue or pull request for this change. |
The display name is a poor choice for in the messages on the front page imo. In this image, having the name be free form is extremely confusing to know which community this is going to, when the "title" of the community can be anything. Especially since it can scroll off the window. I realize the community in the image isn't a great example because its title is a good indicator of what it is. But I've seen some nonsense that really leads to confusion |
similarly, I think the community name and the URL bar should always include the @instance even when you're on that instance like it shouldn't be https://beehaw.org/c/technology because then sharing stuff is a little more clunky instead it should be the full name like https://beehaw.org/c/technology@beehaw.org same thing for user names and user URLs |
Context
A community
name
is an unchangeable an unambiguous identifier for communities (e.g.!vaporwave@lemmy.ml
). Unlike communityname
, "display name" (comparable to a subreddittitle
) is mutable and potentially ambiguous.Expected Behavior
Reddit only displays a subreddit
![image](https://user-images.githubusercontent.com/46303203/113481268-8db5a980-9466-11eb-854e-e212ef03a15a.png)
title
value as a header when viewing the subreddit. In all other contexts, Reddit displays thename
value.In all other contexts, Reddit displays the
name
value.This is preferred behavior for a number of reasons:
name
valuesr/wholesomememes
is referred to as "r slash wholesome memes" when spoke aloud.title
values often very widely from thename
values.name
values can be consistently and easily resolved to the URL of the subreddit.Actual Behavior
In Lemmy,
display name
is used for all contexts. This makes it difficult for users to resolve the URL of a given community. For instance, in the image below, there is no way for users to figure out thatIt's always dns
is supposed to resolve tohttps://lemmy.ml/c/sysadmin
.Solutions
The only adequate solution is to mimic Reddit's behavior, and use the
display name
value for community headers.Other proposed solutions to some of these complaints—such as more-clearly documenting the meaning of
display name
, or limiting it to 20 characters—would be inadequate because there is no way to force community moderators to use this value as intended.The text was updated successfully, but these errors were encountered: