The way I intend to handle this is with my keypass password manager since the file database has to be synced manually. The way I handle this is one copy of the database lives on my phone, which is my primary device. Then I copy this database to a flash drive, and then copy it to my laptop. The update process goes something like update the credential on my phone and then a few months later, during my scheduled backup routine, copy the database to the flash drive and then copy the database over to the laptop. So the most I could lose is a few months worth of data instead of all of it. If my phone is ever stolen, I still have a copy of the database on both the flash drive and the laptop, which at most might be a few months out of date, but nothing severe.

This is the best summary I could come up with:

It’s clear that the industry is increasingly betting on passkeys as a replacement for passwords, a way to use the internet that is both more secure and more user-friendly.

But for all that upside, it’s not always clear how we, the normal human users, are supposed to use passkeys.

On this episode of The Vergecast, we bring in an expert: Anna Pobletts, the head of passwordless (best title ever?)

She’s convinced that passkeys are the future but also has some ideas on the right (and not-so-right) way to get started.

Vee weighs in on Fossil’s exit from the market, the rise of the smart ring, and much more.

If you want to read more on everything we discuss in this episode, here are some links to start with, beginning with passkeys:

The original article contains 241 words, the summary contains 131 words. Saved 46%. I'm a bot and I'm open source!

People are making things more complicated than they already are. I simply keep my passwords and passphrases inside my memory.

P.S. My password is not 'Password123456'