WeSearch

Automatically detecting AI text in my browser

·5 min read · 0 reactions · 0 comments · 3 views
More from Seangoedecke ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

The author developed a Chrome extension named Deckard that uses local AI models to automatically detect AI-generated text on websites. While these local models have lower accuracy than the commercial service Pangram, they offer a privacy-preserving alternative that avoids sending user data to third parties. The tool is currently functional and lightweight, with the expectation that future improvements in local model capabilities will significantly enhance its detection performance.

Key facts
About this source

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

Original article
Seangoedecke
Read full at Seangoedecke →

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 publisherSeangoedecke
Canonical URLhttps://www.seangoedecke.com/deckard/
Publication timeThu, 24 Sep 2026 02:31:32 +0000
Retrieval time2026-09-24T02:40:09.419Z
Last seen2026-09-24T02:40:09.419Z
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.
ClusterfC4J1mL0_fpc · 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

Automatically detecting AI text in my browserAutomated AI text detection is currently an underserved niche. The only game in town is Pangram, which does an excellent job but desperately needs more competition. In a few years, I would be surprised if every major social network doesn’t scan new posts1 and comments for AI content in order to tag them (or simply remove them). I like that I can rely on Pangram to confirm my suspicions when I read something that sounds like AI. But it’d be much better if I could choose to avoid AI-generated text in the first place. What I want is something that runs in the background and automatically scans text on websites I visit, without me having to ask for it.

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

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

Discussion

0 comments

More from Seangoedecke