The logic behind it is that a smartphone-bound passkey represents two factors of authentication: what you have (the phone) and who you are (the fingerprint used to unlock the phone’s passkey store).

Anything on a PC is easily copied and can only ever be safely assumed to represent one factor: what you know (the password to unlock your password manager). Thus the benefit of getting a two-factor authentication in one convenient step falls away.

Of course it’s still super annoying, especially if you don’t really trust your smartphone OS vendor and use a portable password manager already.

I also often see implementations where there’s a first step where you have to select how to log in. It’s an extra click but very clear (and usually one of the options is some form of SSO where that one click fully logs you in if you already have a session open).

Also, according to certain “news” publications and an army of totally legitimate people on the internet, he’s as incompetent as he’s evil and he’s singlehandedly responsible for every single problem anyone in Germany has had for the last 20 years.

My company uses Entra ID (or whatever they’ve renamed it to this week) and it’s a pretty common sight in our login flow. I think our SharePoint instance does it so it should be something MS does.

Of course it all depends on w how the company configures it.

Passkeys are supposed to be bound to one device and protected by that device’s OS’s secure enclave. If you have a second device you’re supposed to create a second passkey.

That’s why many sites will flat out refuse to let you create a passkey with a desktop browser since a PC-stored passkey doesn’t fit the security model.

It’s not like you can’t add a “Log in with your company’s SSO” button to the form. That works just fine and at least Microsoft does something like that.

Except these stamps can’t even be handed over to someone else so you can’t even pay for anything with them. So the delusion is that you’re going to want to spend a significant part of your income on LM tokens no matter what.

I got it as soon as I got a GPU that could comfortably run it… because it was bundled with said GPU. I did activate the key but never bothered to actually install it. Maybe later in case the handful of modders actually make something cool in there.

I was kinda interested before launch, hoping that this would be the game to finally force them to meaningfully overhaul the engine they’ve been carrying around since Morrowind (with some bugs dating back to then). Of course it wasn’t and of course they didn’t.

It’s called group exercise. You’re welcome.

Processor architectures maybe. They put Rust into Debian and it’s so bad that now e.g. amd64 is ruined forever for any OS and won’t see any new processors in the future. We’ll have to move to a different architecture. I didn’t watch the video since I treasure my brain cells too much but that’s what I choose to read into it.

(A more reasonable reading is that Debian now ships a kernel that includes Rust code and coincidentally has also dropped builds for several obscure architectures but I do not feel obliged to assume reason with a title and thumbnail like that.)

Pushing to prod without review and breaking the running application is a resume-generating event in many companies. In many others it’s not even possible because of programmatically enforced policies.

If your company’s response is not to prevent or dissuade it but to have other people work overtime to fix the mess then that’s a major management fail.

Try to educate your boss about best practices. This incident should give your arguments some more weight.

Deployment to prod should not be something a developer can do by themselves; a proper CI/CD system can be configured so that prod can only be deployed to by people with an appropriate role (product owners or lead devs if your company doesn’t have POs).

If you don’t have such a system, make it an explicit policy: Only Steve the lead dev (or someone specifically appointed by him while he’s absent) can push to prod; if anyone else does it they get invited to an uncomfortable meeting with Steve. If they do it again the meeting will be with HR.

But seriously, you should lobby for a proper CI/CD system (if none is present) and for the system to be configured so that a) you can’t merge to the main branch without a code review and b) deploying to prod only works from main and with explicit approval by a PO/lead dev. That should stop most of the shenanigans.

No. Firstly, no means of contraception is 100% effective; stacking them further reduces the likelihood of unwanted conception. Defense in depth is your friend.

Also, sometimes people can catch something without being aware of it. He might have an infection he’s not aware of. You might have one. The condom protects both of you. If you want to do it without, get yourselves tested.

And all of that is under the assumption that everyone is honest and has the best of intentions, which… isn’t always the case.

And exist in a system that can only support two parties, which means that the most effective strategy is not to convince voters that your pictures are superior but to convince them not to vote for the other party. Cue a race to the bottom.

Well, the content is the same and it works the same as far as I can tell. I’m not terribly attached to the old domain name when the (rebooted) radio works just fine.

As long as the penguins haven’t discovered warp drive, that is.

Again, possibly sensible in a vacuum but not a great move when you need the ship to work properly right now. Changeovers like this incur temporary inefficiency as new schedules have to be drawn up and adapted to. Showing up out of nowhere, demanding that everyone execute the changeover (planning and all) within several hours doesn’t sound like a very good idea to me at the best of times, much less when the ship is going to do double duty with delicate diplomacy work and backup for a covert ops mission.

And that’s not the only time he pisses people off with no explanation. He shows up in engineering and demands a two-day death march project to overhaul the warp drive for no reason other than he thinks it should be more efficient. Sure, Starfleet engineers routinely deal with such circumstances but it’s usually for a well-known reason and not “because I say so” over the active objections of the department head. And overworking the engineers doesn’t sound very efficient in anything but he short term.

I maintain that Jellico may have a decent understanding on how to efficiently operate a starship but he’s not very good at actually leading a crew.

Fair points. I think in the end, given only what we see, neither of them seemed to have shown particularly good judgment.

Jellico was temporarily given command over the flagship of Starfleet, which had so far performed well. He immediately decided to implement his personally preferred policies across the ship, which would’ve been fine if he had been given a long-term posting under normal circumstances but wasn’t when he was temporarily in command during a time when the crew needed to perform reliably. Heck, he even had the fish removed from Picard’s office despite knowing full well that it was a temporary posting.

Riker was rightfully concerned about all this but took far too much leeway in dealing with it. Honestly, Picard wouldn’t have acted much differently than Jellico by the time Riker flatly refused to do his job. Jellico might’ve acted unwisely in a professional sense and inappropriately on a personal level but Riker wasn’t acting like an officer at all.

It’s like the two of them were trying to make a case study on how many different kinds of dysfunction you can cram into just two officers aboard a single starship.

I’d argue that upending the duty roster in the middle of a crisis is a bad move. You want people to perform optimally and they probably won’t immediately do that while adjusting to a new schedule.

Jellico’s changes might’ve been sensible in a vacuum but I think that he tried making them at an inappropriate time.

You mean this Nectarine Demoscene Radio? https://scenestream.net/demovibes/

Is that dog driving a car?

Nope, Chuck Testa!