The article mentions this, but this is an opportunity not a problem.
If a hyperscaler wants to connect a 500MW datacenter, great. That's a huge investment, with various positive externalities. Requiring the builders of the datacenter to also pay for whatever transmission, substations and generation upgrades their demand requires is just not that big of a deal compared to the total size of the investment, which is part of why companies like Microsoft and Anthropic have committed to doing just this.
The article notes that some states are already moving to require this, and more should do the same.
There's a huge opportunity here; the AI buildout is probably the biggest wave of private industrial investment in decades, if not ever, and it comes at a time that we need to accelerate the buildout of our electrical grid. Let's have the hyperscalers pay for it in a way that makes this positive sum for everyone.
As an aside, it's kind of funny that this article reads like it was written by Claude.
Back when I was an OSU student I taught myself a lot about practical systems programming, and I was consulting Beej's Guide to Network Programming daily. I kept lamenting to myself that I wished the expensive university was proving as useful as this guy's free website.
Awesome that it has come full circle, great hire by someone.
Thanks! :) Crazy time for it, for sure. I'm teaching the two Software Engineering courses next year and have basically thrown the existing ones out. We'll see what rises from the ashes. More systems-level design stuff, more AI forward, larger projects, larger teams.
I still believe it's vital to learn how to code, but now we have to front-load more of the SE skills that have historically been obtained on the job.
"What a time to be alive!" I admit that I wouldn't have minded if all this LLM stuff has waited another 15 years to happen. :)
MCP auth has been a huge pain point for us at C1 - both for our own internal MCP use and in our in-product MCP Gateway - so very glad to see this landing.
We launched support today for C1 to act as an EMA identity provider (we mint the short-lived scoped tokens), so I'm excited to hook this up for Linear and some of the other MCPs we use, and get out of the business of constant OAuth flows. Claude has been doing this magically for some of their built-in connectors (at least Slack I think) and the experience is pretty great.
I think the argument would go that if people are clicking through certificate errors and you're in a position to MITM their traffic, you can just serve them a different certificate and they'll click through the error without noticing or understanding the specifics.
That could happen either way regardless of expiry. The only reason for an expiration date is to force site owners to cycle their certs at regular intervals to defeat the long time it takes to brute force a successful forgery.
Fair point, but I think the situation is a bit more complicated when a user "needs the site for work", or something urgent. You might have smart cautious users that feel like they have no choice but to proceed and click through the warnings since the site is most likely still legitimate
ConductorOne is building the platform for identity security and least privilege automation — helping companies secure access to everything, without slowing people down. Our engineering culture emphasizes small, high-ownership teams that deliver measurable impact and move quickly.
We’re hiring across many areas:
- Software Engineers – We’re growing our product development teams in SF and Portland.
- Site Reliability Engineering – We’re looking for SREs and a hands-on SRE manager (SF or Portland) to own reliability, performance, and infrastructure as we scale.
- Forward Deployed Engineering (FDE) – We’re building a brand-new customer-facing engineering org: we're looking for engineers who want to work closely with customers to modernize and automate identity operations, and a Manager, FDE to lead the team.
- Governance, Risk & Compliance (GRC) – We’re building a new GRC function and hiring our first Compliance Engineer to help scale our security and audit programs.
We work primarily in Go and TypeScript, on AWS + Kubernetes.
Correct - though the dirty secret is some percentage of the economy is run on rolling loans against house equity, and prices stagnating or dropping would slow that down.
I don't quite understand the goal of this project.
It says they're preventing 15,000 tons of emissions, but there are all kinds of ways to prevent or offset greenhouse gas emissions for under $10/ton. So at a glance this project appears to be allowing almost 2 million tons in preventible emissions in order to... pay people to bike around and collect food scraps?
The actual cost to retire a 1 ton co2e carbon credit should be $70-$80. A lot of these $10 programs do not actually retire the credit and sell it to somebody else, so you are in effect subsidizing the credit.
TBF, this may still enable a legitimate project that is viable at $80-90 that is not at $70-80. So if you want to support a particular tree planting effort go for it.
If a hyperscaler wants to connect a 500MW datacenter, great. That's a huge investment, with various positive externalities. Requiring the builders of the datacenter to also pay for whatever transmission, substations and generation upgrades their demand requires is just not that big of a deal compared to the total size of the investment, which is part of why companies like Microsoft and Anthropic have committed to doing just this.
The article notes that some states are already moving to require this, and more should do the same.
There's a huge opportunity here; the AI buildout is probably the biggest wave of private industrial investment in decades, if not ever, and it comes at a time that we need to accelerate the buildout of our electrical grid. Let's have the hyperscalers pay for it in a way that makes this positive sum for everyone.
As an aside, it's kind of funny that this article reads like it was written by Claude.