Bout to say, pic needs more nudibranchs

VeronicaExplains and not linking to the Peertube video? That’s a paddlin’

https://tinkerbetter.tube/w/hR4wubPUhEW3LR8ZckEAsn

Mlem in app browser is using an in app browser API that is secure by design. It doesn’t allow snooping or injecting anything. This article is talking about abusive apps like Facebook that roll their own in app browser.

Edit: although on iOS, the secure iOS in app browser api is always using safari engine, so the user choice argument is still valid.

It’s crazy that the in-app browser isn’t an OS-level overlay that the app can’t influence or look at what the user is doing in it.

Android and iOS both have apis for in app browsers that are secure by design. Voyager for Lemmy uses this. Mastodon uses this. Last I checked even Twitter used this. However Facebook does not.

these platforms also offer lower level APIs to build custom interface which are more powerful and flexible (but can be abused). This isn’t necessarily a problem. Custom browser apps need that functionality, and apps sometimes display their own content with web views.

The problem is that app stores allow slapping a skin on this more powerful API and treating it like an in app browser to connect to arbitrary sites. Dumb imo. If you offer an in app browser, it should be required to use the platforms secure in app browser API.

More powerful APIs should only be available to browser apps and displaying your own content in a web view.

I’m a monthly donor :)

That’s wizards chess

:( Best Buy has the best shuckable hdd deals

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.

Meh. I’d rather make pixel perfect to designs than not have designs…

This wasn’t the result of US airdrops. Might want to read the article

“We are aware of reports of civilians killed as a result of humanitarian airdrops,” CENTCOM said. “We express sympathies to the families of those who were killed. Contrary to some reports, this was not the result of U.S. airdrops.”

Ok but as a rule use voyagers share as image feature next time (/¯ ಠ_ಠ)/¯

Anything web?

https://motherfuckingwebsite.com

Wat? Helmet mandates reduce cycling numbers.

https://www.publichealth.columbia.edu/news/counterintuitive-argument-against-bicycle-helmet-laws#:~:text=And evidence backs up the,for uneven and discriminatory enforcement.

That’s not quite true - images are only shared if you attach the image to federated content, such as a post or comment. Then yes other instances will cache the image.

If you never do that, and just upload an image accidentally like OP then it will not be federated AFAIK.

That sucks. As a 3rd party Lemmy app developer, I’ve only had positive interactions with the Lemmy devs. They’re even being proactive in communications.

git: 'gud' is not a git command. See 'git --help'.

rekt

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.