WeSearch

YouTube's AI Detection Kicked Us in the Face

https://x.com/Kurz_Gesagt· ·1 min read · 0 reactions · 0 comments · 3 views
YouTube's AI Detection Kicked Us in the Face
TL;DR · WeSearch summary

Kurzgesagt@Kurz_GesagtYouTube’s AI Detection Kicked Us in the Face Every creator's worst nightmare just happened to us: The YouTube algorithm actually blocked us. Some videos started showing strange view fluctuations. Our second to last video did very badly, but this just happens sometimes, so we didn’t think that much about it.

Key facts
About this source

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

Original article
X (formerly Twitter) · https://x.com/Kurz_Gesagt
Read full at X (formerly Twitter) →

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 publisherX (formerly Twitter)
Canonical URLhttps://twitter.com/Kurz_Gesagt/status/2083191397981561232
Publication timeFri, 07 Aug 2026 20:50:09 +0000
Retrieval time2026-08-07T20:55:43.845Z
Last seen2026-08-07T20:55:43.845Z
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.
Cluster1aJf9z-yxgkQ · 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

Kurzgesagt@Kurz_GesagtYouTube’s AI Detection Kicked Us in the Face Every creator's worst nightmare just happened to us: The YouTube algorithm actually blocked us. It started slowly at first. Some videos started showing strange view fluctuations. Our second to last video did very badly, but this just happens sometimes, so we didn’t think that much about it. But then our last video, about Superpredators, did *extremely* badly. It was our worst upload since 2013. But it did badly in a weird way: Almost every single metric was well above average: People clicked the video more often and watched it for longer, and the people who watched it, on average, loved it! So it should have been at the very least an average upload, not the worst in over a decade.

Excerpt limited to ~120 words for fair-use compliance. The full article is at X (formerly Twitter).

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

Discussion

0 comments