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.

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

:==(

Because this is actually the bad place!

Thihihi

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.

And that is if they lose…

Avocado?

Thwre is a running joke that Dutch just sounds like German but drunk.

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

Also, I wouldn’t shy from keeping the database on the same, fast storage as the OS, even if that’s flash. Move to an external SSD when you can. HDDs have such long seek times.

Very much true. I installed Immich on my dads Synology for him and compared to my own setup at home the speeds are abysmall (it even crased a few times during the first indexing and ML run). I suspect a major part is that the whole os runs on an hdd.

If you put the database on an sd-card just ensure you make frequent backups somwhere else. I wouldn’t trust flash storage to keep my data safe.

https://feddit.org/post/19150492

Literal translation of the headline: The rich agains inheritance tax.

(Beacuse the name of our minister for the economy translates to “The rich”)

https://lemmy.world/comment/19501592