Don’t they have a chat product?

Many. And Discord is among them.

Seems like I missremembered something.

Even better, do the work at compile time to respect the customers resources:

const bool isPrime = false

I suspect most speakers are not designed to play inaudible frequencies.

They are also going after Mail-In voting already:

A divided Supreme Court on Tuesday ruled that Americans can’t sue the U.S. Postal Service, even when employees deliberately refuse to deliver mail.

https://apnews.com/article/supreme-court-postal-service-missing-mail-7ce97a5b7d56373cdeaa6ecc9a9132f5

Klarna is a thing in Germany as well and personal bankruptcy absolutely is a thing here [https://www.verbraucherzentrale.de/wissen/geld-versicherungen/kredit-schulden-insolvenz/privatinsolvenz-in-3-jahren-schuldenfrei-11417] so I don’t know if your second point is that relevant. I’d agree on the first one though.

For that scenario you could also consider using certificate based login. Just store your root certificate in a safe place (like a Keepass) an then sign new keys for your new devices when you get one.

https://docs.ssh.com/manuals/server-admin/44/User_Authentication_with_Certificates.html

and I’d need to have password access enabled in order to add the keys

Besides the other points, you could just add the public keys directly in the .ssh/authorized_keys(2) file of the server as long as you still have access from another device. That way you don’t have to enable passwords.

I get a 502 bad gateway on the domain :(

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…

Claim: He’s 34.

True: It’s time to get your shit together.

Wow …

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?

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