
Sean Michael Kerner's Spring 2023 Human Writer certificate authory.com/SeanMichaelKerne… That's write I'm human. I write about #AI. Skynet hasn't won (yet).

IT consultant, technology user, tinkerer and sometimes Klingon ; tips pitch@technologyjournalist.com

Sean Michael Kerner's Spring 2023 Human Writer certificate authory.com/SeanMichaelKerne… That's write I'm human. I write about #AI. Skynet hasn't won (yet).

guess what @microsoft isn't even hiding that it's Skynet now - in an Ignite session now - an exec is detailing the Myles Dysan agent (yeah I 've seen that movie and I know how this ends

Oooof. Opus 5.5 really fucked up OpenAI for while, it seems.
Theo - t3.gg @theo 23h Why I hate GPT-6.2 Astra During early testing, I found myself so frustrated with this model that I spent a day writing a letter to OpenAI about it. They fixed a small handful of my complaints, but not enough for me to

6.2 Astra is here. I’ve been testing it for awhile. I think this is the worst model OpenAI has ever released. I’ll share more soon.

The whole Internet is likely to crash this Thursday. How do I know? GTA VI gets released.

oh and just in case anyone is keeping score.. @Oracle had an AI/ data event in Toronto too (sorry no pics..busy day and sucky connectivity for me..) oracle.com/artificial-intell…

IKEA got hacked. The hackers were inside for six hours and still couldn't find the exit.
Some of the world's most visited websites, including those belonging to Zoom, HSBC, Equifax, CNN, Salesforce and IKEA, were subverted in an effort to steal cryptocurrency and infect iPhones, a security researcher said reut.rs/4ztZvC2

"Within @databricks , 92% of prompts were going to too large of a model. That translates into millions of dollars a year wasted on what could have gone to a more right size model for the problem." yeah model routing is a real need. #DAAIWTT

"Every payment, every loan, every trade is a decision that we make on the information that we have, and trust is what we have earned by getting all of these decisions right for the last nearly 200 years. So what's changed is in the data, and obviously we have new capabilities. But what's changed is in the data. It's what now intelligence can do with all of this, with AI and increasingly with agentic AI." @scotiabank CIO Valli Musti speaking at Databricks #DAAIWT @databricks


Line just keeps going and going - meantime really enjoying listening to all the conversations in the line. Wowowow so much interest in data + AI


Finding Linux bugs is easy now – fixing them is another story zdnet.com/innovation/ai-bug-… via @ZDNET & @sjvn Some #Linux maintainers are quitting under the crushing strain of AI bug reports, but there are signs of hope.

We are tracking a breach of a 3rd-party JS host impacting hundreds of high value websites. This is staggering.

AWS is scared of @Cloudflare so they kicked us out of Re:Invent. No problem, we’ll just throw a more fun side event in Vegas. Register now: cloudflare.com/events/vegas/

FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them. Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem. What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix. Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited. The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked. But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns. Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it. I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't. Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
FFMPEG was right all along and people gave them too much shit for it