How much AI can a maintainer get away with using without losing their humanity?
This data has all been analysed between January-July across 2024, 2025, and 2026.At a high level, we see:Something I also wanted to investigate is how GitHub Discussions interactions have changed, given it is our key interface with users. Although we're generally seeing increased adoption of Renovate, it appears like more folks are using AI to answer the sorts of questions they'd come to our Discussion forums. Which begs the question - how do we keep our work sustainable?
- ▪This data has all been analysed between January-July across 2024, 2025, and 2026.At a high level, we see:Something I also wanted to investigate is how GitHub Discussions interactions have changed, given it is our key interface with users.
- ▪Although we're generally seeing increased adoption of Renovate, it appears like more folks are using AI to answer the sorts of questions they'd come to our Discussion forums.
- ▪Which begs the question - how do we keep our work sustainable?
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,278 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Jamie Tanna | Software Engineer |
| Canonical URL | https://www.jvt.me/posts/2026/08/02/ai-maintainer/ |
| Publication time | Sun, 02 Aug 2026 21:47:45 +0000 |
| Retrieval time | 2026-08-02T21:55:41.725Z |
| Last seen | 2026-08-02T21:55:41.725Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | NviraqTehVDj · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Written by Jamie Tannaon August 2, 2026 CC-BY-NC-SA-4.0 Apache-2.08 mins🤖 This post includes some LLM-derived content 🤖How much AI can a maintainer get away with using without losing their humanity?Table of ContentsWhy am I feeling the pressure?Keeping my humanityPlease respond!I've been recently thinking about how Open Source maintenance seems to be becoming a little more a slog recently - largely with the increased amount of contributions possible with AI agents - and how it impacts being a maintainer.I'm very fortunate that my literal job is to be an Open Source project maintainer (among other things) and that it's a privilege not many others have.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Jamie Tanna | Software Engineer.
Discussion
0 commentsMore from Jamie Tanna | Software Engineer
