And someone hasn’t ICEd it.

Damm, I know electric cars are woke and all, but it’s still wild they are putting chargers in inhumane camps now.

Skill issue

You end up with no superpowers at all

The lever guy is smiling

Then that is not what the article is about…

How do you currently store your passwords? I would also consider that a third party with an adittional atack surface if you are considering the passkey location one.

Also your argument

(if you ignore the operating system, web browser, network protocols, etc., but that’s part of using the tech).

is faulty. That is because passkeys exist in part to mitigate those atack vectors. Mitm, a compromised browser or client, etc. is less of an issue with passkeys. The information transmitted during an authentication can not be reused on another authentication attempt.

I don’t agree on passkeys complicating things either. For me the authentication-flow is not more complicated then KeePasses autofill.

Assuming one can be ‘tech savy’ enough to not fall for fishing is bad. There are quite advanced attacks or you might even just be tired one day and do something stupid by accident.

What’s that now? The weak point is the user’s ability to implement MFA and biometrics? The same users who couldn’t be bothered to create different passwords for different sites?

You don’t expext the user to ‘implement’ mfa or biometrics. You expect them to use it. And most places where a novice would store passkeys don’t just expect but enforce it. It is also way simpler to set up biometrics on one device compared to keeping with a good password strategy.

You can set a pin on most passkey devices so that it doesn’t serve the authentication without it.

Assistant District Attorney Michael Mattson said Woeltz and Duplessie allegedly lured the man to New York from Italy by threatening to have his family killed.

Really a stretch of the word lured…

Why would they, there’s like five of them…

I was hinting at your last sentence. It seems, they do indeed target a lower sdk: https://gitlab.com/fmd-foss/fmd-android/-/issues?show=eyJpaWQiOiIzNTQiLCJmdWxsX3BhdGgiOiJmbWQtZm9zcy9mbWQtYW5kcm9pZCIsImlkIjoxNzI3NjgxMTN9

F-droid also warns me, the target sdk ist too old and automatic updates will not be possible.

(Thank you for the post anyhow, I didn’t know the app existed before)

The app seems to target an older sdk, right?

Not intentionally, although it could pass as sadam tbh

:==(

If your needs are not that complex, you could maybe stick with kde and use kate.

Because this is actually the bad place!

Thihihi

Literally. Especially on a mountainbike averaging 50kmh is insane.

what sort of bike rides is he doing where you have to recharge that more than once a month?

My distance to work is 12 km one way, so your battery would be empty afer two days…

However, it is that seemingly arbitrary three-times-a-year limit applied to the People section that is most concerning. Why not four? Why not as many times as a user wants?

If it works the same way Immich does, probably because they have to retrain the models every time you turn it back on and want to aboid poeple turning it on when they need it, then off again, then back on, … Although a less shitty mehod would be to limit the amount of times you can turn it on but I guess that iterferes with their goal of harvesting your data.

Every 5mins seems insane. Why do you need to schedule it that frequently?