skywhopper

These are intermediate roots, signed by trusted root certs, so the trust from your OS or browser is implicit to the roots it trusts.

Sounds more like extremely sloppy procedures. Which depressingly I doubt are unusual among CAs.

“Stuff FreeBSD does” falls pretty neatly into the “almost no software” category, to be fair.

The post you are responding to lists several possible actions. Another good start would be to stop providing the weapons that have done this damage.

Sounds like old news, we already knew they were integrating advertising.

At least US pro leagues (other than MLS and racing) haven’t yet gone all in on desecrating the team uniform with ads. I can’t bring myself to buy a team jersey that’s 75% an ad for an unrelated corporation that I don’t want to support.

“ A Hyundai executive told the media in 2024, "we also tried out putting touchscreen-based controls, and people didn’t prefer that", "people get stressed, annoyed and steamed when they want to control something in a pinch but are unable to do so".”

I always wonder if the folks who make these decisions themselves ever drive a car. Because this nonsense is wildly irritating. No one who regularly drives long distances could possibly think these are positive features, right?

Yeah, I’ve seen it working. It does work well to implement a multi-system transactional workflow broken down into retryable steps. So, eg, if you are operating a SaaS and need a workflow for new customer signup to wait for multiple steps that might last for hours or days like: validate credit card info, wait for email confirmation, add entries to customer database, set up workspaces in downstream systems, spin up cloud resources, initialize systems, notify customer, start billing cycle, etc. and if any step fails, you might want to retry or send alarms or internal notifications, or roll back other steps, or kick off other workflows. Then you can define all of that, in code. Each step can be different runtimes run on different worker systems, etc, all coordinated through a central database.

You can scale the workflows up and down to as complex or simple as you want for whatever your business is. The example above is one I’ve seen, but it works on a smaller scale as well. But you have to write the implementation code in very specific ways to get the benefits, and the overhead ends up being very difficult to plan and reason about, and a lot of business logic actually gets hidden amongst the weeds of the tool’s overhead.

There’s probably a fuse to turn off the cellular radio that transmits the data. Whether that’s all it covers may vary from car to car. Or in some models it’s probably possible to just disconnect the radio entirely.

You’d think, wouldn’t you? But there are so many promotions and discounts and bundles going on that it’s never a linear relationship. So no one would be able to easily tell the numbers were diverging for at least a few quarters. And as long as they are both headed up, no one actually cares anyway. But if you wanted to juice the growth rate or slow the churn rate just a bit to look better or hit some target that you were just shy of, it’d be easy enough to add a “bug” to forget to bill some certain percentage of trial accounts.

Or maybe they just suck at the coding that handles trial accounts. As rapidly as this stuff was rolled out, and as late as the decisions about actual promotions probably get made, I’d be surprised if it wasn’t buggy.

You realize government services that support that home cost money, right? You act like if you own your home that your living there doesn’t impose any costs on your neighbors.

Good, I wonder how much money they’ve wasted over the years paying for RHEL.

The point is that the enforcement agencies make the assumption that GPS data is always correct. But there are any number of issues that can cause problems with it. People making decisions about how to enforce house arrest or design autonomous farm equipment need to take GPS flakiness into account. Differences in scale are not the point.

It’s the same category of error, is the point he was making. Relax a bit.

Really large companies have lots of domains even if they aren’t “hoarding” them. But even a few dozen domains is enough to need automation.