WeSearch

AI didn't break open source. It removed a filter nobody designed

·7 min read · 0 reactions · 0 comments · 2 views
TL;DR · WeSearch summary

By erickdevz · full-stack developer, Viçosa, Brazil In January 2026, the curl project shut down a bug bounty it had run since 2019. Not because the money ran out — it had paid out more than US$100,000 across dozens of confirmed vulnerabilities. It shut down because the economics of triage had collapsed.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,328 of its stories.

Original article
Vercel
Read full at Vercel →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

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 publisherVercel
Canonical URLhttps://erickxdev.vercel.app/en/blog/ai-didnt-break-open-source/
Publication timeMon, 10 Aug 2026 18:04:24 +0000
Retrieval time2026-08-10T18:10:44.212Z
Last seen2026-08-10T18:10:44.212Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusternwavdArClzP4 · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

By erickdevz · full-stack developer, Viçosa, Brazil In January 2026, the curl project shut down a bug bounty it had run since 2019. Not because the money ran out — it had paid out more than US$100,000 across dozens of confirmed vulnerabilities. It shut down because the economics of triage had collapsed. Around the same window, the Jazzband collective, which maintained 84 Python projects, announced it was winding down. tldraw's founder flipped the repository to auto-close every external pull request. Ghostty adopted a zero-tolerance policy for low-effort AI submissions. None of these projects hit trouble from a lack of people wanting to contribute. They buckled under the opposite.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Vercel.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Vercel