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

推荐订阅源

B
Blog RSS Feed
量子位
Y
Y Combinator Blog
大猫的无限游戏
大猫的无限游戏
B
Blog
U
Unit 42
C
Check Point Blog
I
InfoQ
aimingoo的专栏
aimingoo的专栏
雷峰网
雷峰网
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 【当耐特】
人人都是产品经理
人人都是产品经理
The Cloudflare Blog
H
Help Net Security
MongoDB | Blog
MongoDB | Blog
博客园 - Franky
H
Hackread – Cybersecurity News, Data Breaches, AI and More
J
Java Code Geeks
Microsoft Azure Blog
Microsoft Azure Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
云风的 BLOG
云风的 BLOG
宝玉的分享
宝玉的分享
爱范儿
爱范儿

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 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
Scholarship in the Age of AI
map[email:bastian@rieck.me name:Bastian Grossenbacher Rieck] · 2026-05-29 · via Hacker News - Newest: "AI"

While academic institutions are scrambling to pretend that they are at least partially in control of the AI revolution, some more established actors have already had to adopt new measures. The venerable arXiv, for example, recently announced that they will ban authors for a year under certain circumstances:

If a submission contains incontrovertible evidence that the authors did not check the results of LLM generation, this means we can’t trust anything in the paper. The penalty is a 1-year ban from arXiv followed by the requirement that subsequent arXiv submissions must first be accepted at a reputable peer-reviewed venue. Examples of incontrovertible evidence: hallucinated references, meta-comments from the LLM (“here is a 200 word summary; would you like me to make any changes?”; “the data in this table is illustrative, fill it in with the real numbers from your experiments”)

I believe that the policy is right in spirit but I am worried about the way it will be imposed and whether there is due process for all. That being said, in this post, I am more interested in a high-level discussion on what it means to follow the norms of scholarship in the age of AI.

In a nutshell, my position is this: You are ultimately responsible for your work and cannot abdicate that responsibility to a tool.

The moment we start assigning personhood to an AI system, it becomes a proper coauthor and collaborator, requiring direct credit authorship. But until we are there,1 you cannot shirk your duties. It is perfectly acceptable to use whatever tools you have at your disposal to write your papers, but you are supposed to remain in charge. If you use AI for literature search, for instance, you need to check the results for (a) existence, (b) correctness, and (c) content. You need to do this because scholarly work relies on citations the way good detective work relies on a chain of evidence. You, as an author, have the duty to tell your readers about the relevant literature landscape. It needs to be clear to what extent you are extending the state of the art, relying on earlier models or arguments, and so on. The existence of AI does not change this fundamental prerequisite of scholarship.

Mistakes can happen and will happen,2 but not all mistakes are equal. For example, referring to a non-existent work is highly problematic. It erodes trust in your own work and, beyond that, the trust of the public in science itself—at least to some degree. Referring to claims in a work that are not part of that work is similarly problematic. You are misleading readers while also misrepresenting the work of others. By contrast, referring to a preprint instead of the published version of a paper is, ultimately, harmless. The discourse around the aforementioned arXiv policy misses this type of distinction, unfortunately.

Enough about bibliographies, though! Scholarship is much more than that, but the same principle applies: You are ultimately responsible for your work and cannot abdicate that responsibility to a tool.

Here are some more concrete examples:

  • Using AI to (re)write your paper implies that you need to understand editorial suggestions before accepting them.

  • Using AI to (re)write your code implies that you need to defend or justify modeling choices.

  • Using AI to (re)write your proofs implies that you check their correctness.

None of these examples ask whether it is a good idea to use AI for these purposes. Since I lack concrete data, we are now entering deeply speculative and personal territory. I am going to start with a confession: I derive most of my enjoyment from mulling over things and solving problems. Whether it is writing, reading, or coding, I just love the process as such. Offloading certain tasks to AI robs me of that joy; Terence Tao used the following analogy in a recent Atlantic interview:

AI tools are like taking a helicopter to drop you off at the site. You miss all the benefits of the journey itself. You just get right to the destination, which actually was only just a part of the value of solving these problems.

Since I do not know what, in the words of Marie Kondo, “sparks joy” for you, I can only leave you with the generic piece of advice that you need to decide when to take the helicopter and when to hike yourself. However, when you do take the helicopter, make sure to (a) acknowledge it and (b) check that it actually put you where you wanted and needed to go in the first place.

We are all figuring things out in these times. Have courage to be truthful to yourself, and the rest will follow.