I'm self-hosting Vaultwarden on my LAN, a Bitwarden-compatible backend written in Rust. I have it running inside a jail on TrueNAS Core (which, alas, is now end-of-life). It hosts its own Web interface, but also is compatible with Bitwarden's Android app and browser plugins.

So far, it's worked out pretty well for me.

...Because no one uses Edge.

Clearly you have never worked in a large corporate environment that has shackled itself to the entire Micros~1 ecosystem -- Office, Outlook, Exchange, OneDrive, Teams, Engage, SharePoint... The whole ball of earwax.

That's what the *purpose* of a child window is.

You can easily make more top level windows if that's what you want.

Sounds like you just had bizarre expectations.

Except it didn't, it just strung together words that the user wanted to hear.

It has no concept of if it did it or not.

I mean to generate electricity, like offshore windmills.

"How does someone get access to his location data?"

He had an iPhone.

new corporate password policy requires a mix of letters, numbers, and emojis.

Best case the kite would be flying over water, where 'land' is at a premium.

Could even setup on a large ship maybe?

a consumer helping potential use of NFTs to track license purchases; but the companies would rather you have to rebuy.

I bought my house with BTC.

I thought that's what the front page was. It keeps wasting space with things I'm not interested in, or actively dislike.

New Video from The Primagen!
<block channel>

NotAIHonestly Gets Rare Interview with The Primagen!
<block channel>

FrierenFan04 Reacts to !AIH's Interview with Primagen!
<smashes keyboard>

Yeah, just shove the worms back into the can.

This is how I've come to understand it. I welcome any and all corrections.

Passkeys are a cryptographic key stored in a Secure Element. This is usually a private key inside a small cryptographic engine. You feed it some plaintext along with the key ID, and it encrypts it using that key. The outer software then decrypts the ciphertext using the public key. If the decrypted text matches the original plaintext, then that proves you're holding a valid private key, and authentication proceeds.

The private key can be written to and erased from the Secure Element, but never read back out. All it can do is perform operations using the secret key to prove that it is indeed holding the correct secret key.

On phones, the Secure Element is in the hardware of your handset. On PCs, this is most often the TPM (Trusted Platform Module) chip. In both cases, the platform will ask for your PC's/phone's password/fingerprint/whatever before forwarding the request to the Secure Element.

Yubikeys can also serve as a Secure Element for Passkeys; the private key is stored in the Yubikey itself. Further, the Yubikey's stored credentials may be further protected with a PIN, so even if someone steals your Yubikey, they'll still need to know the PIN before it will accept and perform authentication checks. You get eight tries with the PIN; after that, it bricks itself.

The latest series 5 Yubikeys can store up to 100 Passkeys, and Passkeys may be individually deleted when no longer needed. Older series 5 Yubikeys can store only 25 Passkeys, and can only be deleted by erasing all of them.

Theoretically, you can have multiple Passkeys for a given account (one for everyday access; others as emergency backups). Not all sites support creating these, however.

I noticed that when Formerly-known-as-tweets are embedded on another web site, they put the 'X' logo in the upper right corner now.

scammers gonna scam.