You seem to be falling for what the author was writing about. Only because you could technically try to use keepassxc to store passkeys, that does not mean that it will work. You see passkeys were build in a way the service you’re trying to login to can decide if they accept your keepassxc for passkey storage or not. It looks like you are in control when you are actually not.

There is no good reason so send the passwors itself to the server. Send the hash and you will have a fixes length of data to send anyway.

And even if insist in sending the password over the wire, there is no problem on the backend to handle longer passwords than that, so that no one will run into a limit in practice. We’re talking about bytes here, not even a kb.

The Varia Vue requires a Garmin Vault subscription at £9.99 / $9.99 / €11.99 per month (or £99.99 / $99.99 / €119.99 per year).

Lol what a shit show

Gut, dass nun auch die Verbraucherzentrale aktiv wird. Ich fage mich ja, wie ebay ein berechtigtes Interesse begründet, wenn ich kündigte und meine Daten gelöscht haben möchte. Die können den gesetzlichen Vorgaben ja gar nicht nachkommen was das Recht auf Löschen angeht.

If you’ve got a nextcloud somewhere, you already have everything you need running. Install required extension and login in antenna pod. Works nicely, can recommend it.

Good point. The author argues that:

they buy the device on your behalf so your real name never gets attached to it.

However it is relatively easy to attribute a sim card to person simply based on its usage. You also leave the same movement patterns on the mobile network. I don’t see a benefit here compared to just using a sim card from a service provider that does not sell their customer data.

Just don’t use flatpaks. Let your distribution handle updates like it is supposed to do.

Bummer… no mention of the drawbacks whatsoever.

I would contradict you. The internet is not overreacting, Mozilla and parts of its community try to downplay the issue at hand.

Hopefully the court was clever enought to specify that the side loading must not be more difficult than installing via the store. Apple will for sure make it as complicated and user hostile as possible so they fulfill the ruling without having any practical impact.

Finally some good news

Kudos to Niccolò for openly speaking about his mistake of incorrectly stating his video was not sponsored. However I think he made a second mistake which is more serve. As a content creator he must pay more attention to what companies he’s accepting sponsorship from. Given the track record of malibal, this should have been a red flag in the first place.

Learned something new. Thank you!

Da fragt man sich was die Personenschützer so beruflich machen 🤔

Wer hat was von bezahlen gesagt /s

I also use openScale from F-Droid, in combination with this Bluetooth scale:

https://sanitas-online.de/de/p/sbf-70-bluetooth-glas-diagnosewaage/

Dito

Vorbild Skandinavien […] Manche möchten wohl auch deshalb teilweise arbeiten, um die eigenen Lohnverluste zu begrenzen.

Tolles Vorbild. Und ein Schlaglicht darauf, um was es eigentlich geht. Angst und Ausbeutung.

Signal forks can have unexpected behaviours like retaining deleted messages and also they don’t get updated at the same rate that Signal get updated.

There are ways to save messages before they are deleted even if the stock app is used. Do not ever rely on this feature to work in a “safe” way.

Every couple of years I hear a story about hackers disturbing signal with backdoors, which would be impossible or very hard to be done If they blocked third party clients. (Ex: 1)

That is a problem the users who prefer 3rd party clients have to deal with. Obviously if you care enough to not use the official build, you of cause have to take care of using a trustworthy source. That is not “your problem” though.

The amount of people who use third party Signal clients are very few anyway.

That sounds a lot like “I don’t use it, so none else needs it either” argument. In my opinion, none of your arguments above are a good reason to combat 3rd party clients.

Not in all situations. And in a way a user will not be aware of. The service or website can define what type of passkey is allowed (based in attestation). You may not be able to acutally use your “movable” keys because someone else decided so. You will not notice this until you actually face such a service. And when that happens, you can be sure that the average user will not understand what ia going on. Not all passkeys are equal, but that fact is hidden from the user.