aeharding @ aeharding @vger.social

Punch nazis, trebuchet TERFs.

---

Read more

Posts

14

Comments

542

Joined

1 yr. ago

Moderating

---

https://www.fmcsa.dot.gov/newsroom/crash-not-accident

It should be purple, vs blur. Maybe I could tweak it to be more obvious though!

FWIW the native app of Voyager definitely has more features than the PWA. Probably most notably haptics… PWA is a good options for those that want it though

Hey thanks ☺️

Yeah! Well purple

It’s scraped by your instance, so if Lemmy doesn’t return it then nothing is there.

But also, lemmy devs seem to always be tweaking the scraping so it’s possible it’s better, but Lemmy.world is running outdated version rn.

Good question. If it’s anything like iOS, no unfortunately not

Possibly, but I don’t think I would ever link directly to Google in app haha. Maybe libretranslate though?

iOS also has a built in translate tool, so that at least is much more straightforward.

Awesome, thanks for confirming

You might have missed it, but I mentioned there will probably be an option added in the future to turn on display names (off by default).

As for other Lemmy clients, I always encourage people to look around and find what works best for you! There are a lot of great apps and what is “best” depends on the person using it.

Ehh, I wouldn’t consider Safari “using chromium” at this point. It has been hard forked for years. Chrome could disappear tomorrow and it wouldn’t affect Safari development.

FWIW Voyager doesn't have a server, there is no backend at all. Just you and your lemmy instance. ;)

To be completely honest, if you want a healthy 3rd party app ecosystem, the official UI and backend need to be completely separated with a publicly documented API.

Biggest win with Lemmy, and biggest fluff with kbin. And it shows when it comes to 3rd party app ecosystem. People wanted to build apps for kbin….

OK, thanks. I'll try and fix for next release

Are you using from Docker?

Hi, good idea. This feels similar to https://github.com/aeharding/voyager/issues/1056, so maybe you could add a request for ability to share with specific custom instance there? Thanks

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.

if you hold and tap username you can tag. If you do that it will store a reference to the comment/post you tagged from

It looks fine for me on voyager. Maybe connection issues.

What do you mean?