They’re only banning super intelligence. That doesn’t exist as a product.

They didnt?

An argument could be made that someone untrained (many vibe coders) shouldn’t be in positions that would fall for this. A stretch, but still valid.

us

movement

Mmhmm. Thanks for the ad.

My favorite part is Auth0 is the sponsor of Passport.js, you guessed it, an Open Source identity management library. And they play a big role at places like IETF where standards are actually written.

I bought a 16G for a project shortly after they came out on sale at Microcenter. It’s sitting in a closet right now, and it makes me feel bad that it’s not in use. I have Pi3Bs deployed everywhere, but no need for this monstrosity. Today.

I have found if you choose providers that do things like run on 100% sustainable energy, you tend to find the places where leadership’s morals overtake their pockets. There are a few mail providers like this.

Or support your local coffee shop.

Ahh makes sense

The entire global military aparatas, from mobile headquarters, in-country bases, and submarines, is hardly a niche. And no, that’s also not how it’s done all over the world, that’s how it’s done in modern western countries. SMRs would work very well in rocky or rainforest regions, or areas where speed of deployment is more important (kick starting a region pre-solar, or brownout coverage, for instance).

Dont get me wrong, I’m making this point because SMRs have a place. I do believe solar should be the vast, vast majority of global energy production until something better comes along.

Doesn’t the title of the article once you tap the link say who did it? Yes, yes it does.

Two posts above is Musk taking 16B of taxpayer dollars.

I did a pretty deep dive for my company recently. We are very data-privacy centric. Here was my Lemmy post on it: https://lemmy.world/post/51963153

Some of the items there are mentioned here, but after the evaluation, my hunch was correct and we are likely switching to https://runbox.com/

Good service, pricing, privacy focused but not so much that you need to host your own proxy like with Proton, and runs sustainably.

I… don’t think you are thinking this through.

He’s not wrong.

Think Solar. Wayyyy more affordable to share a farm than build your own, and less battery required if load is shared when not in use by some. This is an extreme of that, even.

BUT. People want sovereign API because of trust, not efficiency. I don’t mind a shared solar farm, but I want my own Safe Deposit Box for my important documents, not one shared with a bunch of smokers who have proven they drop ashes everywhere.

I’m about to have a convo with my team, which to be clear is a good team. It’s going to go like this:

“If I write a comment where there has been a pattern of that same comment more than twice across your PRs in the past month (missing indexes, rewritten code for no reason, duplicate code, etc), I will immediately reject the review. If I have to do this twice for the same PR, there will be accountability. And unlike when something proves a challenge and we are flexible, timelines will not shift if one of these occur.”

I personally think this is fair, as we rarely ever put our team into any kind of cram mode. I’m all for heavily assisted dev if it makes life easier, but it should not fall on the seniors to catch the obvious issues.

From personal (family) experience, you are correct.

Sure they are, they’re just relegated to government use atm.

Uhh any major metropolitan area without US large area infrastructure? Also, underwater.

So I posted this quote as well but for a different reason. Google and Anthropic chose responsible disclosure, unlike OpenAI with the lovely weekend fiasco for PR.

In this one, AMI made a mistake. I don’t think making a mistake should be punishable to the extent that ignoring responsible disclosure should. Some dev pushed a PR out of habit, sucks but I’ll take the last minute patch requirement on that. Some business lead once to see if they can push the stock? No thanks.

I’ve been advocating for years that international legislation needs to be put in place to enforce responsible disclosure practices.

The parties that discovered CVE-2026-97631—Alex Matrosov of Anthropic and Dan Holmes-Mitra of Google—had arranged for it to stay under wraps until a coordinated disclosure that was scheduled for January. AMI, a maker of motherboards and other hardware, published this pull request last month that detailed the vulnerability and included a code fix. Once the post came to the attention of the discovering parties, TianoCore Project members published a public advisory last week.

Dear OpenAI: This is responsible disclosure. Please take note as to not ruin peoples weekends so you can say “look what our API did!”