Skip to content
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

Use showApubName in comment and post listings #1975

Closed
wants to merge 1 commit into from

Conversation

lionirdeadman
Copy link
Contributor

Description

This helps distinguish people from other instances which use a Display name and can help prevent impersonations which we've seen in the past.

Fixes #1974

Screenshots

Before

image

After

image

Copy link
Member

@dessalines dessalines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very much against this. Bloating the username lengths massively everywhere. The lack of a @ tells you that its a display name, and that if you want to see the actual identifier, you can either click and hold, or go to their profile page.

@lionirdeadman
Copy link
Contributor Author

Then there is no way to differentiate from a local user and someone who is outside of the instance.

Now, if you want to propose Displayname@instance then it causes another problem because it can be made to look like someone else's user@instance.

I will note that other federated services like Mastodon, Firefish do show both:

image
image

@creesch
Copy link
Contributor

creesch commented Jul 25, 2023

The lack of a @ tells you that its a display name.

It no longer makes it clear if a user is from your own instance or from a different instance.

Not to mention, the lack of @ is a really easy to overlook and not some established UI/UX paradigm people will easily pick up on.

@SleeplessOne1917
Copy link
Member

I'm with @lionirdeadman and @creesch on this one. The "@" and instance name will not show up when a display name is set regardless of whether a user is on the same instance as you or a different one.

@dessalines
Copy link
Member

Having really long names is terrible for mobile. Having display names like this: , or even just A pretty long display name@instance.TLD will cause a ton of line-wraps and noise on mobile.

It no longer makes it clear if a user is from your own instance or from a different instance.

You can easily click-and-hold. I followed matrix, which is to stay mobile-friendly, and have the display name being an actual display name. If people want to know your specific instance, and full identifier, they can click and hold, or go to your profile page.

I tested fully qualified names on mobile before both in lemmy-ui, and jerboa, and they cause a ton of incredibly ugly line wraps.

@lionirdeadman
Copy link
Contributor Author

Comparing a chat app and a forum app is not really a fair comparison because for a chat app, the members in the room are a lot less likely to use the same display name.

That said, if two people have the same display name on matrix - here's how that looks :
image

Unless we can somehow know if two people have the same display name and act accordingly, it seems best to simply do it.

@SleeplessOne1917
Copy link
Member

We could also do an approach similar to the Mastodon screenshot and display the apub info on a separate line under the display name in a less prominent color. That could make apub names easier to see while also avoiding overlong lines and line wraps.

@ruffsl
Copy link

ruffsl commented Jul 27, 2023

We could also do an approach similar to the Mastodon screenshot and display the apub info on a separate line under the display name in a less prominent color.

This could give more room in the future for things like user flares as well, like when a user is flared as verified domain expert in a Q&A community, or marked as frequent contributer. If these multiple line could match the height of the avatar icons, then it might not be too bulky, while still leaving space for other info later.

@creesch
Copy link
Contributor

creesch commented Jul 27, 2023

You can easily click-and-hold.

People will not do that if there is no obvious reason to do so. It therefore can lead to confusing situations at the very least but escalate to people actively abusing it to impersonate other users on an instance.

I tested fully qualified names on mobile before both in lemmy-ui, and jerboa, and they cause a ton of incredibly ugly line wraps.

Isn't that simply deciding that form is more important than function? Something that might even be addressable, one proposal, has already been done. There might be other things as well that improve the "prettiness" of it all.
But, in the meantime really just flips a boolean for something that is already implemented.

In addition to this, this change already has been implemented in beehaw.org for almost a week. In that time I haven't seen any support posts about it or confusion about it in support chat on either matrix or discord. So, to me, that indicates that it might not be as big of a dealbreaker.

Wouldn't it make sense to then simply merge this PR now and then address the exact looks that need to be adjusted in a future change?

@makotech222
Copy link
Contributor

makotech222 commented Aug 7, 2023

Just noting that for hexbear, upon federation we almost immediately changed the frontend to display 'display_name@domain' to aid in moderation efforts and to make it clear if someone is outside our instance. It would be shorter than 'display_name (username@domain)' so that might be better for upstream.

Also, for hexbear users ourside our domain, we have almost 100% of our users using display_name because we use it to force pronouns on username. So our domain name ends up not showing up anywhere.

@dessalines
Copy link
Member

I'll go back against what I said previously, and am willing to use the larger apub name. But it needs some testing and before / after pics, because its going to cause a ton of wrapping on mobile.

@lionirdeadman
Copy link
Contributor Author

I already put the before/after pics. We've been using it on Beehaw ever since this PR was made. I've not noted any complaints about it.

I agree with @SleeplessOne1917's design with adding height to names to show this information rather than width but I honestly have no web dev knowledge so I wouldn't be able to deliver on that.

@dessalines
Copy link
Member

Closed in favor of #2064

@dessalines dessalines closed this Aug 30, 2023
dessalines added a commit that referenced this pull request Apr 16, 2024
SleeplessOne1917 pushed a commit that referenced this pull request Apr 16, 2024
…#2064 (#2425)

* Use muted display names. #1975 #2064

* Removing pointless undefined equality.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Federated user home instance should still be visible even with a display name set
6 participants