“Critics”

Very cool idea! Going with the Coyote theme maybe name it Wile E?

That’s true but the pricing doesn’t match the expense by a long shot. The question is - what is going to give out first? Capital, or the all-you-can-eat pricing? (and yes the latter is closing as we speak)

Oh that’s fun!

Or, install ghostwriter to launch at login.

2026’s Google I/O (Google’s annual developer conference) has been a disaster for the web. The conference-driven development’s forcing through of the Prompt API, a set of Modern Web Guidance skills for AI systems to use that are already showing major accessibility shortcomings, and a whole ton more AI-spangled sloppery, is rushed and unwelcome.

I think the most damaging announcement is the changes coming to Google Search. Rather than a list of relevant links, a search on Google will be more aggressively prioritising the LLM-generated summary, now complete with vibecoded tables, graphs, and interactive elements.

There has until now been a social contract. Website owners let Google scrape their sites and present them in Google Search, and, in exchange, Google Search sends traffic back to those sites. Google wins via adverts on the search page, and sites win due to however they monetise traffic. More largely, everyone wins because there is a financial incentive to create and produce new content.

However, Google killing their side of the contract ends this. If Google only takes and never gives, then sites cannot profit. What is the incentive to publish if the only outcome is feeding Google’s AI with no return? What sources will LLMs have to pull from if all the sources are defunct? How far will Google go folding adverts into their AI output?

I can see the huge short-term gain for Google, but I see no long-term path – not even an unsustainable one. This feels like the end, but of exactly what I’m uncertain.

All of my peers (bar the ones that work at Google) are shattered in a way I’ve never seen before. I don’t know where we go from here.

Great.

Great.

I thought it said 170. But that’s the full version. 20GB for the shell & OS’es d/l a la carte.

How are you feeling about that now?

I feel torn. Working here is not easy. From the outside, there’s massive negative sentiment, and there’s certainly something there. But the pain of working here is not very well understood. It’s this grand calculus of what it costs to live in the Bay Area and what personal sacrifices you are willing to make and what you’re willing to do for money. On the one hand, I feel massively privileged and lucky to work at a place like this. On the other hand, I’m like, where is my line?

Christ.

Bluesky has an algorithm?

I was gonna go with banning all UK regulators.

What’s “Meta”? Is that like a clothing brand or something?

/s

I don’t see it. Like the guy in the article said, it starts out looking like a joke . . . Buuuut it ain’t.

Woke computer nerds fucked us

Edit: just to reassure the more anxious amongst us, I mean ‘woke’ in the maga sense of anything-i-don’t-like-is-woke. Not actually woke.

Actually woke computer nerds observe proper security protocols ffs.

I’m sure that will be an excuse but no, this was lazy-ass we-dont-wanna incompetent garbage devs.

Government contractors were a mistake

Mmmmm . . Nnno, i don’t have that one. Oh - there’s a “Ghyynah”, is that it?

All going to plan, comrade

Sorry, I hear ya. You are so not the only one either. Hang in there. Hey - this place may have some open positions soon?

Valadon’s company constantly scans public code repositories at GitHub and elsewhere for exposed secrets, automatically alerting the offending accounts of any apparent sensitive data exposures. Valadon said he reached out because the owner in this case wasn’t responding and the information exposed was highly sensitive.

But wait

Valadon said the exposed CISA credentials represent a textbook example of poor security hygiene, noting that the commit logs in the offending GitHub account show that the CISA administrator disabled the default setting in GitHub that blocks users from publishing SSH keys or other secrets in public code repositories.

“Passwords stored in plain text in a csv, backups in git, explicit commands to disable GitHub secrets detection feature,” Valadon wrote in an email. “I honestly believed that it was all fake before analyzing the content deeper. This is indeed the worst leak that I’ve witnessed in my career. It is obviously an individual’s mistake, but I believe that it might reveal internal practices.”

One of the exposed files, titled “importantAWStokens,” included the administrative credentials to three Amazon AWS GovCloud servers.

This is shameful incompetence. Just head-rolling abysmal incompetence. These are the people they hired, for all you 1337 hax0rz currently looking.