We stopped AI bot spam in our GitHub repo using Git's –author flag
A GitHub repository faced an influx of spam from AI bots, which disrupted legitimate contributions and conversations. The team implemented measures to combat this issue, including restricting comment and pull request capabilities to prior contributors only. They utilized Git's --author flag to allow legitimate users to gain contributor status while blocking AI-generated spam.
- ▪The repository was overwhelmed by AI bot comments, making it difficult for real contributors to engage.
- ▪The team created an 'AI sheriff' bot to manage spam but found it insufficient.
- ▪They decided to restrict contributions to prior contributors to maintain quality in their open source project.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,939 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 | Hacker News (AI / LLM) |
| Canonical URL | https://archestra.ai/blog/only-responsible-ai |
| Publication time | Mon, 18 May 2026 15:24:19 +0000 |
| Retrieval time | 2026-05-18T15:29:56.629Z |
| Last seen | 2026-05-18T15:29:56.629Z |
| 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 | ruRyBU3paMt5 |
| 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
2026-04-17Let's talk about AI slopIs it the end of open source we know and love?Written byIldar Iskhakov, CTOThe End of Open Source as We Know It When a few months ago GitHub shared statistics about celebrating an enormous contribution of AI in their product metrics, completely missing the point of degraded contribution quality, we already felt that things were going south. The first worrying moment was the issue we posted with a $900 bounty. We were hoping to motivate someone to contribute and bring shiny new "MCP Apps" support to our platform. We quickly got the attention of legitimate contributors proposing plans, asking questions, submitting attempts — but soon...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).
Discussion
0 commentsMore from Hacker News (AI / LLM)
