GobblesGobbles
GobblesListen to today's tech podcast

Linus Torvalds just declared that AI-powered bug hunters have made the Linux security mailing list "almost entirely unmanageable" โ€” and his advice to researchers using these tools is essentially: stop sending spam and write a patch.


Your AI Is Judging You: The Chatbots That Now Refuse "Normal" Questions

Users of ChatGPT and Claude are reporting the same thing: more content refusals, longer ethical disclaimers, and a model that sometimes feels less like a tool and more like a chaperone โ€” even on ordinary creative or exploratory questions.

The shift traces back to how safety filters get built. Early systems used Reinforcement Learning from Human Feedback (RLHF), a process that depended heavily on human nuance. Many companies have since moved to RLAIF โ€” Reinforcement Learning from AI Feedback โ€” where synthetic datasets generate guardrails automatically, in bulk. The problem: those safety weights over-generalize across semantic space, catching neutral words in the same net as genuinely harmful content. The result is refusals that feel arbitrary, because technically, they are.

Not everyone sees it as a crisis. Some users argue that response preferences can be worked around and that newer, more capable models may simply warrant stricter guardrails. Others point to the legal pressure companies face after high-profile incidents. The disagreement reveals the real tension: safety and utility aren't always the same thing, and right now, safety is winning.

Gobbles Gobble's Take: Your AI assistant didn't get dumber โ€” it got a lawyer.

Source: r/artificial


Linus Torvalds to AI Bug Hunters: Stop Sending Duplicate Reports and Write a Patch

In his weekly state-of-the-kernel post for Linux 7.1 release candidate four, Linus Torvalds delivered a message that went well beyond the usual progress update: the Linux project's security mailing list has become "almost entirely unmanageable." The culprit is multiple researchers running the same AI tools, finding the same bugs, and flooding the list with duplicate reports that maintainers then have to hand-route or dismiss with "that was already fixed a week ago."

Torvalds called the churn "all entirely pointless" and identified a structural reason it keeps happening: AI-detected bugs are "pretty much by definition not secret," so routing them to a private list only makes duplication worse โ€” reporters can't see what anyone else already submitted. His recommendation was direct: if you found a bug with an AI tool, assume someone else did too. If you want to add real value, read the documentation, create a patch, and contribute something on top of what the AI gave you. "Don't be the drive-by 'send a random report with no real understanding' kind of person," he wrote.

The comments are worth noting: fellow kernel maintainer Greg Kroah-Hartman has said AI is becoming an increasingly useful tool for the open-source community โ€” so the debate inside Linux's own leadership is very much alive.

Gobbles Gobble's Take: AI found the bug; now a human still has to care enough to fix it โ€” which, turns out, is the whole job.

Source: r/technology


The EU AI Act's โ‚ฌ35 Million Fines Are 75 Days Away โ€” Most AI Teams Aren't Ready

Full enforcement of the EU AI Act's obligations for high-risk AI systems begins August 2, 2026 โ€” and it applies to any team building AI agents or SaaS products used by European companies, regardless of where your company is based. High-risk means systems used in credit scoring, recruitment filtering, healthcare triage, education assessment, or critical infrastructure. If your product touches any of those categories and processes EU resident data, you're in scope.

The compliance checklist is specific: automatic decision logging (not optional), a minimum six-month log retention period, technical documentation of your detection pipeline, human oversight architecture, and accuracy and bias testing documentation. Miss it, and fines run up to โ‚ฌ35 million or 7% of global annual turnover. One commenter who's been building to the Article 50 human-AI interaction disclosure standard since July 2025 noted that the August date actually covers disclosure requirements for new generative systems and watermarking obligations โ€” with a grace period on watermarking for systems already on the market extended to December 2, 2026. A separate commenter flagged that certain standalone high-risk system provisions under Annex III were pushed to December 2, 2027, per a provisional agreement between the EU Parliament and Council.

The honest assessment from developers in the thread: most founders don't realize their agent's decision chain needs to be auditable until they're mid-build โ€” and at that point, 75 days is not enough time.

Gobbles Gobble's Take: "Move fast and break things" has a new ending in Europe: "and then pay 7% of your global revenue."

Source: r/artificial


"Build in Public" Has Become Founders Pitching Founders โ€” And Almost No One Is Getting Customers

The premise was simple: share your startup journey openly, attract early adopters, build community. The reality, according to a growing chorus of founders, is a loop of likes, "cool idea bro" replies, and zero actual users. Entrepreneurs on r/startups are increasingly reporting that build-in-public posts draw an audience of fellow builders โ€” people interested in how the product is being made, not people who have the problem the product is trying to solve.

One commenter put it plainly: "build in public is mostly useful when your buyers are builders." If your target customer is somewhere else entirely โ€” in a specific industry forum, a niche community, a different platform โ€” founder likes are not just unhelpful, they're actively misleading, because engagement metrics create the illusion of validation. The emerging consensus: treat build-in-public as a credibility signal, not an acquisition channel, and spend the real time in "boring places where the actual pain shows up."

The pattern isn't new, but the scale is. As more founders pile into the same strategy, the audience becomes homogenous โ€” and the feedback loop tightens into something that feels like traction but produces none.

Gobbles Gobble's Take: If your biggest fans are people who are also building the same thing, you don't have users โ€” you have competition.

Source: r/startups


In Case You Missed It

Yesterday's top stories:

Was this briefing useful?

One tap helps Gobbles learn what to cover more carefully.

Get Tech Gobbles in your inbox

Free daily briefing. No spam. Unsubscribe anytime.

See something wrong? Report an inaccuracy