Oh, I see. Voyager doesn’t show that because display names are confusing for mentions, can be used to impersonate, and distracting. It might be an option to enable in the future, off by default.

Edit:

Claim

To clarify how I really feel, here’s my hot take: display_name is a really awful feature and should be removed from Lemmy.

Why?

They are dangerous by default because the very concept implies that clients should render display_name instead of the username, if it exists. Which is unwise: Apps have to choose between replacing (bad for impersonation/UX/distraction reasons) and showing both (which just looks duplicative most of the time).

What makes this feature even more frustrating is that people are now using display names for their username + flairs of actually important things, like gender identities. (for example, display_name="Alex (he/his)")

It’s a damned if you do, damned if you don’t situation for Lemmy clients. Some people are using display_name for important info like gender identities, and yet display_name is so incredibly easy to impersonate people and otherwise abuse.

Solution?

What is the solution? I think Lemmy should ditch display_name and replace with flair (or something like this). The general idea is that flair is NOT a replacement for your username, but rather it will be displayed alongside it.

Maybe even make flair per-community like Reddit. I think that was a much better design than what Lemmy currently has.

What do you mean?

The labeling is heavily regulated, it must contain a certain amount of actual cream too. Unfortunately shit tier “frozen desert” can be sold on the same shelf intermingled with the good stuff.

And the marketing doesn’t help either.

But it is very easy to check for the initiated bc it wont be labeled as ice cream. And easy to check ingredient list too. When I buy ice cream, I only buy when the first ingredient is actual cream.

Shameless plug for my sort lib

edit: Looking at my old code it might be time to add typescript, es6 and promises to make it ✨  p r o d u c t i o n   r e a d y  ✨

That’s true I would make feature request to those clients to add this very important functionality.

I am the developer of Voyager, but there are many great Lemmy clients out there! ;)

literally harmless accessibility solution “abuse” because they don’t like it for whatever reason.

Well, I am calling it “abusing the post body” because it doesn’t federate to all services. Captions (or as Lemmy calls them, alt text) does federate better as it was designed to use a more standard federation data type that Mastodon understands.

So, using the post body for captions actually kinda is harmful in the lens of Mastodon users, and other federated services that don’t support Lemmy’s post body.

Yeah, that’s fair… it’s unfortunate, it’s a really important feature

Im just trying to help. The post body doesn’t federate to mastodon, so nobody there will see it. Alt text e.g. captions does though. This is one of the main reasons image captions were added to Lemmy.

Nobody is stopping you from using both either. However is you have an accessibility concern with captions, you should definitely report is to the Lemmy devs so they know and can make the implementation better.

Lemmy 0.19.5 has captions, no need to (ab)use the post body