there’s not much benefit to using a passkey if you’re using a password manager, but there’s not much of a drawback either. websites often treat it like “password + 2FA” so it can be a little faster of a flow (e.g. for GitHub sudo mode)

With 1Password, there’s very little difference when using a passkey: you unlock your vault (if locked), the click the “use passkey” toast. No second layer of auth

IIUC it prompts you to save a passkey when the website requests it (since the extension acts as a passkey provider)

IIRC the idea with poisoning was: some critical code locks a mutex, partially updates it but panics, leaving a bad value in the mutex. poisoning prevents future code from using this bad value

if std didn't poison, a library could handle it, but i'd guess most code doesn't really need it anyway

both tokio’s and parking_lot’s mutexes just release the lock on panic instead of poisoning. I think poisoning is well-reasoned, but it feels a little too opinionated for a std primitive. i personally would’ve preferred std’s mutex to not poison and to just release on panic too

- get rid of Mutex poisoning
- compile-time reflection system to greatly simplify serialization, etc (don’t know what this would look like actually)
- Either type in std… or even better: unions
- make orphan rules into a deny-by-default lint

biblically accurate ps4 controller

i’ll be looking for the one wearing a shirt that says “please add gifs” and holding a sign that says “please add gifs”

congrats!!! very clean run!