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?

Use the all feed if you want to browse posts from everywhere.

If you want to actually connect to an instance without signing in, to view its local feed for example, you can go through the normal login process and login with empty credentials. It will prompt you to connect as guest.

Yeah, agreed. Make a GitHub report if there isn’t one already so I don’t forget

Voyager stores the source comment/post of the tag if you have it enabled.

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.

🤔

Voyager has recently started automatically building and deploying every commit on main to testflight/android open testing (new!)/beta.vger.app (new!) as part of continuous deployment, so it’s actually testing. ;) Before testflight didn’t really do anything because I only pushed releases there lol.

Two options:

1. Scroll down in your second screenshot to “notifications” and turn them off. Recommended if you want to keep testing and helping find bugs and are OK with your app breaking occasionally, or
2. Use app from App Store instead of testflight. Recommended if you aren’t really testing and want a functional app without surprises.

I think that’s what Lemmy is looking to add support for soonish.

Yes, temporary bans should be fixed.

Thank you! 💜

Fdroid is lagging behind because the build changes I’ve made at the same time broke the reproducible builds. It’s slow turnaround but hopefully fixed soon.

No prob. And don’t worry, it’s for the greater good, the new build process is amazing. :)

ppls that want to live on the bleeding edge can now use https://beta.vger.app/ (PWA), Testflight (iOS) or Open Testing (Android) and they will get every single update to main branch! Should help catch bugs earlier too.

There was a very short period with a bad deploy of the PWA a couple days ago (not native apps) where it would show a blank screen. However your device should auto update once you close ALL vger.app tabs and reopen 2x (once refresh to fetch latest updates, one to reflect on page) – I checked on my device.

If that doesn’t fix it, can you please check your browser console if you’re technically inclined? You could try this browser extension or, the official but more complex method

And if you dont want to do that, you can always try deleting site data for vger.app. That will clear your settings and login though.

I’ve been upgrading the build process and there was a bug with the PWA deployment where it was deploying changes directly to vger.app. It should be fixed now though, and only update with releases :)

If you see any issues in the future just lmk

Apparently called 911 from inside the car.

In my neck of the woods a couple weeks ago five people burned to death in a Tesla. Apparently called 911 from inside the car too. No national news on this either.

https://www.veronapress.com/townnews/highway/update-on-nov-1-town-of-verona-crash-that-killed-five-people/article_39070b78-9ad8-11ef-8de9-a7707b602caa.html

Maaaaaaaaaybe that’s an interesting idea. I’d have to check out how performant lemmy API is. Also worth noting that tagging is app wide not per-account. Also since it’s a vote counter, in the process it would have to clear the existing counter (or just add to your existing count) since there’s nothing to cross reference.

The other/lazy option? I add an import button that takes a CSV or something and then the community just builds whatever they want haha.