The way it is in lemmy-ui now is fine.

Now do jxl support

Back in my day we couldn’t walk or bike to the grocery store because the streets were so dangerously designed

It’s supposed to be getting better, but moving very slowly.

spoofing is pretty common still afaik.

I made a purchase on a sketchy site (during Covid when things were hard to find). A day or so later, some unauthorized transactions were made on my card. “Bank” called from actual number of my bank, to verify if I actually made the transactions. provided some of my personal information, transaction amount etc then asked to verify ssn. It was very convincing.

Luckily I refused because I know anyone can call you claiming to be any number, and I didn’t give out any info, and said I would call back that number (my bank).

Bank had no knowledge of a call.

15 minutes later, get real fraud department call from my bank. They just wanted to know if it was fraud or not and didn’t ask for any other info.

Moral of the story: if someone calls you, never give out personal info. Tell them you will call back if needed.

Voyager has spoilers! It’s not in the markdown toolbar yet but if you know the syntax it works

Nice

There are absolutely reasons where a native app is worth it - I just don’t think building your own backend or not factors into that decision much.

Maybe the point you are trying to make, is when you have enough resources/large enough company, having duplicate teams for each native app isn’t that big of a deal? I agree financially, although is is harder to technically coordinate two teams with dual releases and implementing features twice, with twice the bugs, and it slows things down. (Maybe not a big deal to Bitwarden - their app featureset may be quite stable, IDK)

(Disclaimer - I’ve been on teams building kotlin/swift apps and also cross platform apps professionally, so this is my firsthand anecdotal experience.)

I don’t really see how developing a backend or not has anything to do with the decision to build a native or cross platform app.

But for Bitwarden, the interface is a much smaller proportion.

Can you elaborate on that? Bitwarden’s apps use Bitwarden public API, similar to how the Voyager app uses Lemmy’s public API.

Everyone on this thread: I can recognize native apps when I see them 😤

Native apps when they see them:

React Native is just a fancy web browser wrapping with some helper APIs.

React native is not a browser. It uses native components.

So you’re going to maintain two separate code bases with two separate teams as a knee jerk reaction to using one of the worst cross platform frameworks out there…

For an app that does little more than display encrypted text in a list…

weird flex but ok ¯\_(ツ)_/¯

Sunshine soup!

Yeah, exposing what report goes to who in the create report API is my main problem with this proposal. You’re approaching this from a power user perspective.

I haven’t seen any spam ¯\_(ツ)_/¯

This is trying to solve what having report reasons would solve. If you had admin report reasons and mod report reasons then users can focus on what is the problem with the reported content, rather than who it should go to (casual users dgaf and probably don’t even know the difference between an “instance admin” and a mod)

So I’m not a fan. Again, this feels like trying to fix a symptom of the problem (no report reasons)

Take a few minutes and look how any other site does it.

Probably too often

Those in the EU do with NLNet! (Although arguably not nearly enough)

Its a feature of Voyager (and other 3rd party apps)