That's after you already have a passkey. I don't think you can create a passkey without a different form of 2FA. At least...you shouldn't be able to, because that would kind of defeat the purpose.
GenderNeutralBro
joined 3 years ago
Not really comparable. Passkeys don't replace 2FA. You need to bootstrap passkeys with 2FA.
Out of curiosity, when did your doctor tell you this? I ask because standard medical advice changes over time, and if its been a while you might want to ask again.
I've had low modestly low blood pressure at times. Never a big deal, but once they turned me away from donating blood because my pressure was a little lower than the standards allow. It was minor enough that my doctor basically said "be sure to stay hydrated and don't worry about it".
In theory, no.
In practice, yes.
They say this was done with Codex and OpenCode.
I admit I'm behind the time with AI coding agents. Is it actually possible to do that effectively in such a short time? Or is this going to be riddled with sloppy bugs?
Could be worse. She could have got a Final Fantasy Cactuar tattoo.
There is also testing, but that is just to place thing in before promoting them to stable so has the same release cadence as stable.
Small point of clarification: Debian Testing is more fluid than Stable. While Stable will not receive any feature updates in its 2-year lifespan (only bug fixes and security patches), Testing does receive feature updates, up to the point where it is "frozen" for the final stages before release as the new Stable. Usually that happens a few months before release.
This is why Debian 13 "Trixie" has some packages that were released toward the end of Debian 12's lifecycle.
For example, Debian 13 Trixie was released in August 2025, and contains KDE Plasma 6.3, which was released in February 2025. It does not include Plasma 6.4, which was released in June 2025, because that was after the freeze.
So in practice, you can expect Debian stable to have feature releases that are ~0.5-2.5 years behind the latest, and Testing to be 0-6 months behind.
I was getting certificate errors for a few days, up to as recently as a few hours ago. Seems to be working now (obviously).
It doesn't need to be good to replace jobs, as long as there are no consequences for the people making those decisions.
I've lost count of how many "oops, it was AI's fault, not my fault!" stories I've heard, even within highly regulated fields. Like, lawyers submitting documents with completely fake citations, and then...no real consequences. Seems to me like that should be cause for immediate disbarment, but no, apparently not.
view more: next ›
I enjoyed this one, as I've enjoyed all the Murderbot stories.
I did feel a bit let down by the dangling thread of the other rogue SecUnit. It showed up, ran off, and then we never saw it again. I guess it was just setting the stage for future stories; the hack is uncontained and any SecUnit could realistically have it in the future.