惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
爱范儿
爱范儿
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
雷峰网
雷峰网
V
V2EX
博客园_首页
Engineering at Meta
Engineering at Meta
博客园 - 聂微东
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Apple Machine Learning Research
Apple Machine Learning Research
GbyAI
GbyAI
H
Help Net Security
A
About on SuperTechFans
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Blog — PlanetScale
Blog — PlanetScale
W
WeLiveSecurity
云风的 BLOG
云风的 BLOG
D
Docker
Security Archives - TechRepublic
Security Archives - TechRepublic
Help Net Security
Help Net Security
N
News and Events Feed by Topic
Simon Willison's Weblog
Simon Willison's Weblog
G
Google Developers Blog
A
Arctic Wolf
T
The Blog of Author Tim Ferriss
博客园 - 叶小钗
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Google DeepMind News
Google DeepMind News
博客园 - 三生石上(FineUI控件)
aimingoo的专栏
aimingoo的专栏
Hacker News: Ask HN
Hacker News: Ask HN
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 司徒正美
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
P
Privacy International News Feed
T
Troy Hunt's Blog
T
Tenable Blog
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Recorded Future
Recorded Future
F
Fortinet All Blogs
D
DataBreaches.Net
B
Blog
T
Threat Research - Cisco Blogs
MyScale Blog
MyScale Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
The GitHub Blog
The GitHub Blog
Security Latest
Security Latest
M
MIT News - Artificial intelligence

Hacker News - Newest: "AI"

AI can't read an investor deck AI as an attorney? Student uses ChatGPT, Gemini to sue UW over alleged racial discrimination Hacking MCP Servers in AI Systems – The Rug Pull: Tool Changes After Approval GitHub - MeepCastana/KubeezCut: Free Web based video editor GitHub - GenAI-Gurus/awesome-eu-ai-act: Curated tools, official sources, OSS, templates, and guides for EU AI Act compliance. Can AI judge journalism? A Thiel-backed startup says yes, even if it risks chilling whistleblowers Coming soon: 10 Things That Matter in AI Right Now DARPA built an AI to fact-check enemy weapons claims What explains heterogeneity in AI adoption? When AI Meets Muscle: Context-Aware Electrical Stimulation Promises a New Way to Guide Human Movements - Department of Computer Science AI Changed How We Build. It Did Not Change What Matters. Linux rules on using AI-generated code - Copilot is OK, but humans must take 'full responsibility for the… Meta spins up AI version of Mark Zuckerberg to engage with employees Code Mode: Let Your AI Write Programs, Not Just Call Tools | TanStack Blog GitHub - Delavalom/graft: Go framework for building AI agents. Type-safe tools, multi-provider (OpenAI, Anthropic, Gemini, Bedrock), zero vendor SDKs. India's TCS tops estimates, says new AI models did not dent services demand Gen Z's fading AI hype Strong feeling: we are in a folded AI reality GitHub - machinarii/total-recall-catalog: A reference catalog of latest knowledge retrieval, memory & RAG systems GitHub - mensfeld/code-on-incus: Give each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.. Quantization, LoRA, and the 8% Problem: Benchmarking Local LLMs for Production AI Iran war: We spoke to the man making Lego-style AI videos that experts say are powerful propaganda Powell, Bessent discussed Anthropic's Mythos AI cyber threat with major U.S. banks GitHub - immartian/bellamem: Persistent belief-graph memory for AI agents. Retrieves decisive context by importance — not recency, not RAG, not /compact. recursive-mode: The Repo-Native Operating System for AI Engineering After the attack on Sam Altman's home, will AI CEO's go on the offensive? The biggest advance in AI since the LLM Opus 4.6 vs GPT 5.4 One Prompt Unity World Generation Test “AI polls” are fake polls Client Challenge Can AI be a 'child of God'? Inside Anthropic's meeting with Christian leaders How to Switch AI Chatbots and Why You Might Want To GitHub - MattMessinger1/agentic_refund_guardrail: Safe refund policy layer for AI agents — Python + TypeScript. Same behavior, shared tests. Adam/papers/emergent_values_whitepaper.md at master · strangeadvancedmarketing/Adam Ask HN: How do you stop playing 20 questions with your AI coding tools How far can automation and AI support psychotherapy? - @theU GitHub - stagas/rtdiff: realtime git diff gui and AI-assisted commits A Mac Studio for Local AI — 6 Months Later A History of the Early Years of AI at the University of Edinburgh Why AI Coding Tools Still Feel Stuck on Localhost MSN AI Datacenters Are Becoming Strategic Targets twitter.com Penn Researchers Use AI to Surface Unreported GLP-1 Side Effects in Reddit Posts Show HN: MoodSense AI (ML and FastAPI and Gradio, Deployed on Hugging Face) Moodsense Ai - a Hugging Face Space by aman179102 AI models are terrible at betting on soccer—especially xAI Grok GitHub - xialeistudio/echoic GitHub - HimashaHerath/github-dev-wrapped: AI-powered weekly GitHub activity reports deployed to GitHub Pages GitHub - alejandrobalderas/claude-code-from-source: Architecture, patterns & internals of Anthropic's AI coding agent — reverse-engineered from source maps AI and Tech brief: Ireland ascendant GitHub - Titovilal/context0: Context0 - Never Surrender Training for a Marathon with an AI Coach: What Worked and What Didn't Cyber Pulse: Agentic Intel - Apps on Google Play I Built an AI PR Reviewer That Catches Bugs by Not Looking for Bugs Gen Z workers are so fearful AI will take their job they’re intentionally sabotaging their company’s AI rollout | Fortune How AI Is Reimagining the Game of Golf–For Both Players and Courses GitHub - nattergabriel/reseed: A CLI tool for managing and distributing agent skills across projects Is SVG the final frontier? My AI workflow evolved from prompts to a near-autonomous workflow MLSharp Help - 3DGS Viewer & Generator I put my cognitive field based AI's runtime on GitHub Is Numble the first AI-proof game? A3: Kubernetes for autonomous AI agent fleets | Emergent Principles Deepali Vyas ("The Elite Recruiter") GitHub - msmarkgu/RelayFreeLLM: A restful API designed to route user prompts to various AI model providers. Unionized ProPublica staff are on strike over AI, layoffs, and wages Unleashing the Advantage of Quantum AI We're heading for an AI-fueled 'dementia crisis,' brain scientist warns The AI-Assisted Breach of Mexico's Government Infrastructure [pdf] GitHub - stef41/lmscan: 🔍 Detect AI-generated text and fingerprint which LLM wrote it. Open-source GPTZero alternative. Zero dependencies, works offline. MSN GitHub - visionscaper/collabmem: Enabling long-term collaboration with Agentic AI - building up episodic and world model memory over time with in-context awareness We gave an AI a 3 year retail lease in SF and asked it to make a profit | Andon Labs AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way What leaked "SteamGPT" files could mean for the PC gaming platform's use of AI AI is the boss at this retail store. What could go wrong? GitHub - Wuzu11517/agentic-proxy: Local proxy meant to help reduce With Drones, Geophysics and ArtificiaI Intelligence, Researchers Prepare to Do Battle Against Land Mines A Single Operator, Two AI Platforms, Nine Government Agencies: The Full Technical Report 在 Steam 上购买 FriedrichAI: Offline AI 立省 10% GitHub - inevolin/resume-cli: Hit Claude usage limits? Resume any AI coding session elsewhere. Switch tools at zero friction. GitHub - atripati/ark: AI Runtime Kernel — a context operating system for AI agents. Eliminates tool bloat, loads only what’s needed, and gives LLMs their reasoning space back. How to Build a Secure AI PR Reviewer with Claude, GitHub Actions, and JavaScript This Startup Wants You to Pay Up to Talk With AI Versions of Human Experts Intel Arc Pro B70 Brings 32GB VRAM to Local AI for $949 WordPress 7.0: The Good, the AI, and the Still Missing AI on the couch: Anthropic gives Claude 20 hours of psychiatry IatroBench: Pre-Registered Evidence of Iatrogenic Harm from AI Safety Measures AI Agents Know About Supabase. They Don't Always Use It Right. The history and future of AI at Google, with Sundar Pichai Inside an AI‑enabled device code phishing campaign How Meta Used AI to Map Tribal Knowledge in Large-Scale Data Pipelines AI for Systems: Using LLMs to Optimize Database Query Execution Forecasting the Economic Effects of AI Introducing Tinker: Play with AI, bring your ideas to life AI sheds light on an ancient gaming mystery People really hate AI but not as much as Iran—or Democrats | Fortune What is an AI Product Engineer? Phoebe Gates wants her $185 million AI startup to succeed with 'no ties to my privilege or my last name': 'I have a chip on my shoulder' | Fortune
The anti-AI position has an information problem
JonAtkinson · 2026-04-30 · via Hacker News - Newest: "AI"

Some scenarios.

A game ships. Someone digs through the credits, finds an AI tool listed, and the review-bombing begins. A few weeks later a different game ships, the same tool sat in the pipeline, but nobody notices. That game does fine. The difference between the two outcomes is disclosure, not use.

The same pattern shows up in film. A studio quietly uses a generative tool to clean up a background plate and nobody objects, because nobody finds out. A different studio admits to using one for concept art and gets dragged for a week.

In publishing, a novelist gets accused of “AI-assisted” writing because their prose has a particular rhythm, while every traditionally-published author this year has been edited in Word, which has had AI-assisted suggestions on by default for two years.

In professional service, half the legal briefs filed this quarter went through a tool with a generative summarisation feature, and nobody seems to be boycotting their solicitor.

This is the shape of the problem with maximalist anti-AI consumer positions. The stated rule is “I won’t consume AI-touched work.” The operational rule that actually governs behaviour, is “I won’t consume work where AI use was disclosed or discovered.” Those are very different rules, and the gap between them is where the position falls apart.

The tools have been here for a long time.

Generative AI in the headline sense (Sora, Veo, Claude, Gemini) is one small slice of what “AI in production” is in 2026. The rest is woven into the tools every studio, publisher, and firm uses every day:

  • Upscalers, denoisers, and frame interpolation in film and TV post-production
  • Voice cleanup and dialogue restoration in audio
  • Tweening, motion matching, and lip-sync in animation
  • Concept exploration and reference generation in art departments
  • Code completion in every major game engine
  • Localisation and subtitle passes
  • Content-aware fill, sky replacement, and rotoscoping in editing suites
  • Grammar and style suggestions in Word, Google Docs, Grammarly
  • Drafting and summarisation tools in legal, finance, and consultancy
  • Marketing copy and product descriptions across every retailer

Some of this is disclosed. Most of it isn’t. None of it is going to be unwoven, because the features shipped inside Adobe, Maya, Pro Tools, Word, the engines, and the major DCC suites years ago. Opting out of “any pipeline that touched AI” means opting out of contemporary consumption entirely, including from artists who would describe themselves as anti-AI.

Any boycott selects against the behaviour it wants, and here is the structural problem. A boycott needs a legible signal. When the signal is “did this product use AI,” and the answer is almost always yes in some form, enforcement collapses onto whatever happens to be visible. Visibility depends on disclosure. Disclosure is voluntary.

Studios and publishers that are honest about their tooling get review-bombed. Pearls are clutched about the end of creativity. Quiet ones sail through. The market has now taught everyone the lesson: do not volunteer information about your production pipeline. Commentators have already selected against the behaviour it claims to want. It rewards concealment and punishes transparency, which is the opposite of how a functioning consumer signal should work.

You can watch this happen in real time when a beloved product gets caught. The response shifts. “That kind of AI is fine.” “It’s only the bad kind that counts.” “DLSS isn’t really AI.” “Spell-check has been around for years.” “Photoshop’s content-aware fill is just a feature.” The category of “AI-tainted” gets quietly redrawn to protect prior consumption choices. The line moves to wherever it needs to be.

This is a No True Scotsman fallacy in plain sight. “No real anti-AI consumer would object to motion matching.” “That’s not the kind of AI we mean.” Each redrawing of the category protects something the speaker wanted to keep. The move is structural, not personal, and the position requires it. If you commit to an absolute rule about a category that cannot be reliably observed, the only way to maintain consistency is to keep redefining the category.

People sometimes respond by arguing for stricter disclosure norms or better detection. Neither gets you out of the problem:

First, detection asymmetry. You cannot reliably tell from the artefact whether AI was involved. Output that looks generated often is not. Output that looks fully human-made often is not either. The artefact does not carry the signal, so enforcement has to depend on disclosure or leaks, which fail in opposite directions.

Second, tooling diffusion. The features are inside the software. They are not optional plugins you can audit. When Photoshop’s “Generative Fill” sits next to “Content-Aware Fill” sits next to the healing brush, the line between “AI” and “not AI” is a UI decision made by Adobe’s product team. Word’s editor pane, Grammarly, and the suggestion engine in Final Draft all sit in the same category. There is no clean place to draw the line from the outside.

Third, definitional drift. Yesterday’s AI is today’s just-a-feature. Spell-check was AI. Autocomplete was AI. Auto-tune was AI. Motion matching was AI. Each was controversial when it arrived and invisible now. The category is a moving target, and the people most invested in policing it are the least likely to notice when something they already accept gets reclassified.

There is a coherent anti-AI stance available. It just has to be narrower than “no AI.” Something like:

I object to generative AI replacing creditable human creative labour, and I will boycott when I can identify it.

That is defensible. It names the specific harm (displacement of paid creative work), it acknowledges the limits of detection (“when I can identify it”), and it does not require you to pretend that the upscaler in your favourite movie’s HD remaster is somehow morally distinct from the 2026 image model that did not make the cut.

The maximalist version (no AI anywhere in the pipeline) collapses into one of two things. Purity theatre, where the rule is performed but never applied, because applying it consistently would mean consuming almost nothing. Or selective enforcement, where the rule is applied to whichever studios got caught and ignored for whichever ones you wanted to keep enjoying. Selective enforcement is where the goalpost-shifting kicks in, and it is why the same person can rage about a Sora-generated cutscene and praise a Pixar film without noticing they are holding two incompatible positions.

The interesting question is not whether the maximalist position is inconsistent. It is, and so is most of how anyone consumes anything. The interesting question is what a coherent disclosure regime would actually look like.

If you want to know what tools touched a piece of work, you need a labelling standard. Studios, publishers, and firms would have to declare specific uses (training data, generation, editing, in-betweening, upscaling, cleanup, drafting, summarisation) at a granularity that means something. Consumers would have to read those labels and apply consistent rules to them. Detection would not go away as a problem, but the question “what am I actually objecting to” would have an answer.

I suspect the people loudest about wanting this regime would not, in practice, accept its outputs. A label that says “AI-assisted upscaling” on a beloved remaster, or “AI-assisted copy-edit” on a novel, would force a choice that the current vibes-based system lets people avoid. The current system is not a failure of disclosure. It is a preference for ambiguity, dressed up as a principled stance.

I am not arguing that AI in media is ‘fine’, or that concerns about creative displacement are misplaced. They are not. The labour question is meaningful, the credit question is meaningful, and I write this as someone who has worked all my life in a labour category which is seriously under threat - software engineering!

I am arguing that the absolutist consumer position does not address any of those questions. It rewards creators for hiding their tooling, punishes the ones being honest, and requires a steady supply of redefinition to stay internally consistent. It is a vibes-based loyalty test wearing the costume of a principled stance.

The narrower version of this stance is harder to perform but easier to defend.

It is the only one that survives contact with how media actually gets made now.