That's not how it used to be, though. It used to be that you had to prove a much higher level of ownership, even for standard, non-"enhanced" certs. There was one time we discovered that the business hadn't had its articles of incorporation renewed in the state, and the validation process by the cert issuer caught it.
I do prefer the current model (the trade-offs are worth it, IMHO), but it wasn't always this way.
I went through the standard validation many times and the entire process felt like a security theater. For example, I had to upload a scan of my ID, but I know for a fact that in my jurisdiction no private entity can access government databases to validate that it is a genuine ID and not a photoshopped image. The government provides a SSO that third parties can use, but none of the main cert issuers implemented it, even for EV certs. They just trusted a JPEG.
It's like those arcane verification checks used by US-based services that ask for utility bills, as if they had any way of verifying an invoice issued by a small utility provider in rural Finland.
Arguably in the extremely early days of SSL this is how it works, because the Certificate Authorities have never done this before and so sure, we fly our account excecutive out to your New York HQ and they sign (with a pen) a contract for $5000. Those early certificates are, by modern standards, worthless garbage, Chat GPT can probably teach you how to forge one though it might be too expensive for an amateur to do at home - but they do have street addresses and so on if you cared to read them. A web browser of course did not read those street addresses, and it has even less idea than you do whether the details correspond to reality.
Within a few years at most the Race to the Bottom is well underway - if I spent $10 on my "streamlined" process to offer 1000 certificates for $10 each I make more money than a rival spending $1000 to offer 100 certificates for $100 each. As a result "Domain Verification" is normal by the turn of the century. If you weren't here for the Dotcom boom, you have never seen any of this. If you bought books on this stuff on Amazon, or worse you've never read any books about it because it was all online, you arrived after DV was everywhere.
A peer mentions EV, that and OV are actually newcomers, the CAs realised that customers don't want to pay $100 for a "better" certificate when customers can't tell the difference so there began a meeting, the CA/Browser Forum sometimes just referred to as "cab" or "cabf". This meeting had two initial outputs. One of them endures to this day and only got stronger:
1. Certificate Authorities must meet at least certain Baseline Requirements (the "CA/BF BRs") for all certificates. You can't issue certificates which do not meet these requirements, putting a floor on how terrible your verifications can be.
2. Browser Vendors will add shiny UI for a new "Enhanced" verification certificate so that customers can see it's better and that's a new sales opportunity for CAs.
In practice after some years (2) stopped making sense. A shiny UI works on a desktop PC but there's no room on an early smartphone, so you just don't add this. Soon enough you make Desktop browsers look the same as your smartphone product and all the time your UX experts are telling you users do not undertand this UI (no surprise it was just a sales gimmick) and Safety experts are telling you that it's a net negative for user safety. So, bye bye EV UI in browsers.
But the other side of the bargain went very well. The BRs were a ratchet. In 2012 a ten year certificate issued based on some sales guy who met the director of a company at lunch was fine. By 2016 even five years is clearly too long and we should check some actual official records or have some kind of formal process. In 2012 it's fine to issue for mysql.test.internal because that's not a public name right? By 2016 uh, no, that's why it's not OK to issue that certificate, nobody could possibly own that name, do not issue bogus certificates, this is Serious Business. The BRs are how, gradually, we got where we are today.
> An Extended Validation (EV) Certificate is a certificate conforming to X.509 that proves the legal entity of the owner and is signed by a certificate authority key that can issue EV certificates. EV certificates can be used in the same manner as any other X.509 certificates, including securing web communications with HTTPS and signing software and documents. Unlike domain-validated certificates and organization-validation certificates, EV certificates can be issued only by a subset of certificate authorities (CAs) and require verification of the requesting entity's legal identity before certificate issuance.
This was before Extended Validation was available. I don't remember the exact year, but I know for sure it was before 2007 (it was my dad's business, and he passed away in 2007).
> As long as the battery has enough energy to cover the outage the end result is the same.
That is the key—having enough battery to cover an extended outage is very expensive.
My generator can run on natural gas, which is piped to our house and only had one outage in the fourteen years we've lived there (when the gas company replaced lines as part of preventative maintenance). So effectively, we have a redundant electricity source coming into the house. If that was also down, I could also run it on propane or gasoline.
That being said, if I had to pick batteries _or_ a generator, I'd prioritize batteries. We have both, and the batteries cover the majority of outages, while also providing other benefits.
>having enough battery to cover an extended outage is very expensive
It sure used to be, but I think battery backups that cover a whole house for 24h is cheaper than a diesel generator that can do the same now. Depending on your situation you can make it back in savings even without solar panels. (Charge when electricity is cheap, use when expensive).
Piped gas generators is a thing I had no idea existed until now! Edit: Curious to learn if they are a common thing?
25 kWh covers maybe 1-2 hours in a worst-case scenario, and that’s with only a peak eleven-kilowatt output. You’d need ~24 kilowatts peak to cover a full 100-amp old-style mains feed for a house. This is just basic math — 100 amps times 240VAC == 24 kilowatts.
Most houses here in Texas are now built with 200-amp mains feeds. So, you’d need ~50 kilowatts peak. And if you really can get two hours of runtime for 25 kWh, then you would need 300 kWh to get 24 hours of runtime.
Check the prices for batteries and inverters. 50 kilowatts peak and 300 kWh runtime is a lot more expensive than you realize.
Maybe one day, when batteries get much, much, much cheaper than they are today, you will be able to afford that kind of system. But today, a 24 kilowatt natural gas generator is a lot cheaper.
My utility doesn't have a program quite like this, but they do have a peak power rate that incentivizes similar behavior. I have our system configured to charge up to 90% at 12pm, and then consume no grid power until 7pm (peak rate is 1-7pm), or if the battery gets down to 35%.
I also have it configured to charge to 100% if there are any weather watches or warnings. That overrides the time-of-use configuration.
We do also have a generator that I can hook up if the batteries get too low. We have enough battery to get us through the night, but we don't have enough solar to keep up in an outage during the darker months, or if we want to run the A/C.
I wonder how many datacenters bother with those sorts of things anymore, given how many workloads are no longer tied to individual nodes. Seems like it would just be easier to accept that a certain percentage of nodes will be down at any one time, and go through and repair/replace them as needed.
Cloudslop doesn't provide high availability the way high-availability platforms provide high availability. IBM is still doing brisk mainframe business. You won't find mainframes in many data centers because you need nearly a data center's worth of hardware to provide the volume and availability of one mainframe, and that can fit in one cabinet. (Mainframes also benefited from VLSI; new ones aren't dinosaurs that require three-phase power, their own floor of a building, and their own aircon infra.)
Given that the root of the discussion is about Internet Archive being hit with huge traffic and not the functionalities provided by Wayback Machine, it very much is a distinction with a difference.
Internet Archive's traffic may not matter to you, but that's the main topic of this discussion, regardless of what you care or use website archival tools for.
No they don't. Archive.org is co-operative, it respects robots.txt and allows deletion. It's also very slow. Archive.* is adversarial and archives sites that don't like it. That's why the FBI is trying to take it down.
They are 2 different services, run by different people, one goes out of their way to bypass paywalls while the other doesn't, one is banned by Wikipedia and the other isn't, etc.
I think it's a distinction worth making.
Not to mention that the Wayback Machine itself isn't exactly a good tool to bypass paywalls as most paid sites don't let them archive paywalled content anyway.
Yeah, you're mistaken. One archives web pages, the other maintains a list of paid-access accounts and fetches information from behind paywalls as a service.
archive.org is the more straight-laced archive that doesn't circumvent sites that try to block it, and removes content they deem 'problematic' even if not illegal or requested by the site owner.
Meanwhile archive.today/ph/is/etc is the guerrilla alternative run by a die-hard datahoarder that seeks to archive the information itself, bypassing whatever blockers/login pages/whathaveyou to achieve the result.
It's nice to have both options. When I archive a site, I usually use both for added resiliency.
Of course you can, but that's not what's implied by the quote.
In addition to microtonality, many instruments (and the human voice) are capable of infinite tuning, and musicians will deviate from the "correct" note (as played by an even-tempered instrument) based on chord structure, voice leading, etc.
That's not what "tuning" means. Yes, fretless string instruments, the human voice, instruments like the trombone are all capable of being played with arbitrary or semi-arbitrary pitch. But they are still either tuned in some way, or never tuned at all. Performance is not tuning.
Just like any engineering and business decision, this is a tradeoff.
I probably don't see things from the same vantage point.
Can't help but notice a trend however. What if this accelerates, especially with AI being an enabler?
I do prefer the current model (the trade-offs are worth it, IMHO), but it wasn't always this way.