<p><span class="h-card" translate="no"><a href="https://mastodon.social/@glyph" class="u-url mention">@<span>glyph</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> i am using a password manager with a browser extension that lets me do passkey logins in most places i&#39;ve tried to do them</p><p>keepassx stores them in the password database, like everything else it stores</p><p>it&#39;s a normal file</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@glyph" class="u-url mention">@<span>glyph</span></a></span> ok this doesn&#39;t work for one of my use cases. I may be seeing this up sooner or later with [other tool] for the machines where it works tho</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> I&#39;m not really clear on what &quot;non-vendor-locked&quot; means here, but it sounds like people aren&#39;t paying attention to an extremely stupid corner of the spec, so: great</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@glyph" class="u-url mention">@<span>glyph</span></a></span> yes</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@glyph" class="u-url mention">@<span>glyph</span></a></span> 🤔 are the passkeys stored on the same physical device that they are utilized on</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@glyph" class="u-url mention">@<span>glyph</span></a></span> i am using non-vendor-locked passkeys with zero bluetooth</p><p>(keepassx supports it)</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@glyph" class="u-url mention">@<span>glyph</span></a></span> I&#39;m going to add something, it&#39;s not as big as the other problems you raised but I think it&#39;s a problem: Someone, somewhere, set it up so the non-vendor-locked version of passkeys so it *requires*, per the spec, for you to use Bluetooth, which simply means I will never use it. This is probably childish. But I am probably not the only person who hears &quot;bluetooth&quot; and immediately tunes out.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@dabeaz" class="u-url mention">@<span>dabeaz</span></a></span> I can imagine!</p>

<p><span class="h-card" translate="no"><a href="https://haunted.computer/@iximeow" class="u-url mention">@<span>iximeow</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.world/@cfallin" class="u-url mention">@<span>cfallin</span></a></span> it&#39;s like 6502 sized</p>