I fear every single time I have to switch phones. Being degoogled means I first have to choose hardware based on custom ROMs compatibility, and fight the thing to just install the ROM. Then the fun begins, for every single stupid feature I have to install and setup a solution (app) optionally restoring a backup individually. Contacts, calendar, files, maps, passwords, airtag protection, email, IM, keyboard, weather, notes, smart garbage:tm:, alternative YouTube client...The state of current tech is pityful, if it wasn't what I was doing to put food on the table I wouldn't want any of this garbage 10 meters near me.
Edit: Before any of the geniuses here says "at least you can use alternatives" I don't want to hear your copium, it's obvious this won't last.
Too bad the spec is stupid and requires password managers to be identifiable so servers can deny the "insecure ones".
It's already a pain to use Keepassxc for otp since they all want you to use their apps but it's still doable (the worst offender being steam where you have to hack your own app to extract the otp secret). With passkeys you won't have a choice to use The Google AuthenticatorTM etc because eventually some exec will find they can block every provider except their own to boost app download KPI.
I really like concept of passkeys, the simple fact of using asymmetric keys is so much better than giving the secret to prove you have it, but the spec is hostile and thought for vendor closing.
No, the spec is for companies that need to enforce higher levels of security so that you can e.g. only enable Yubikeys in your env.
I hate big tech just like anybody else but this is just spreading FUD right now.
Also execs can already enforce their apps only - banking apps for approving transactions are already a thing at least in europe, no fido passkey needed.
what in hell is "Windows 365" ? Windows 11 ?Defunct Office 365 now Copilot ? Will this thing be renamed "Windows Copilot" eventually becoming even more confusing as M$ knows to do oh so well ?
I don't know if this could count as "corrupting": I made the mistake of syncing my keepassxc database to my macbook with finder webdav client (nextcloud backend) it read the file alright but when I tried to write a new secret it helpfully wrote an empty file in place, wiping nextcloud file versions in the process.
Thankfully, Nextcloud was smart enough to move the previous file in the trash bin and I could restore it.
It seems keepassxc "save" procedure here was to delete the old file and replace it with a new one and something went catastrophically wrong in the process ?
Looking at the settings there's is a parameter for this method for particular circumstances but I didn't enable it back then. Now I just have a second database only on this mac synced to icloud and never letting it near my nextcloud again.
I actually had a similar thing happen with gvfs-fuse (Google drive). It was a bug in gvfs using the quota usage of a file as it's file size (because libgdata didn't provide a method to get file size), but I was using a file shared to me so it had zero quota usage.
All of which is to say I would bet on something in the webdav-nextcloud line being at fault instead of keepassxc.
I sync'd this file using various means on different platforms, nextcloud apps on windows using virtual files and android with Storage Access Framework cloud integration, and on linux with rclone and somehow never had such a catastrophic issue
I don't think it's clear sarcasm in the sense you are making. I think GP was pointing out that doing what OP does yourself (HA git) comes with a lot of costs.
My point is that Pierre CC has really exorbitant pricing that would cost even more.
reply