HumanVerify: Forensic Human-Post Filter for X Feeds
Cannot reliably distinguish human-written posts from AI-generated ones in social media feeds, leading to degraded user experience.
Is the problem real?
Inability to distinguish human-generated posts from AI-generated content on social media feeds
EVIDENCE
I spent six months building a social network that forensically proves every post comes from a real human
I spent six months building a social network that forensically proves every post comes from a real human
I spent six months building a social network that forensically proves every post comes from a real human
Who feels this pain?
TARGET USERS
Casual scrollers spending 30+ minutes daily on feeds overwhelmed by indistinguishable AI slop, seeking purely human content.
Context
Current Workarounds
Where's the gap?
EXISTING SOLUTION GAPS
OPPORTUNITY & VALUE
Single complaint but escalating over time; gaps in forensics repeated in signals.
Device-level forensics beyond LLM detectors, focusing on capture method (live vs pasted/gallery) absent in current platforms.
Chrome extension that analyzes posts in real-time using forensic signals like EXIF data, moire patterns, keystroke dynamics proxies, and text paste rejection to filter and hide AI content.
How does it make money?
MONETIZATION
Model
Users complain feeds are 'way worse' now, akin to paying for ad-free experiences like Twitter Blue; no direct payment signals but parallels to premium social features suggest tolerance for low-price upgrade.
How do you ship it?
MVP PLAN
“Filter AI slop from your X feed to see only human posts instantly.”
Chrome extension that analyzes posts in real-time using forensic signals like EXIF data, moire patterns, keystroke dynamics proxies, and text paste rejection to filter and hide AI content.
Core Features
Weekly Roadmap
- •Implement text entropy and paste detection JS
- •Build EXIF/moire image parser
- •Test on 100 X post screenshots
- •Chrome extension scaffold with content script
- •DOM observer for new posts
- •Visual overlay: green check/human, red X/AI
- •Add hide/filter toggle UI
- •Local storage for user prefs
- •Beta recruit via X/Reddit, accuracy logging
- •Freemium paywall stub
- •Analytics for scan accuracy
- •Launch post on HN/X/r/technology
Chrome Web Store launch, promote via X threads on AI flood, Reddit r/Futurology/r/technology, Hacker News.
RISKS & ASSUMPTIONS
Top Risks
Over-filtering human posts could frustrate users and drive churn; signals highlight need for live capture but implementation accuracy uncertain.
X may block extensions scraping feeds, halting MVP post-launch.
Single complaint signals frustration but no evidence of active seeking dedicated tools.
Posters can bypass via screenshots or advanced tools mimicking forensics.
Should you build it?
Run an Investment Memo to get a structured Go / No-Go verdict, competitor landscape, unit economics, and a 90-day validation roadmap for this opportunity.
Generate an investment memoWhat this score means
This idea scores in the upper-middle range of opportunities surfaced by MonetScope, with a validation sub-score of 4/10 against 3 independently sourced evidence signals. A "promising" rating usually indicates a real pain has been detected and discussed in the open, but the pipeline did not find enough signal to flag it as urgent or high-frequency. These opportunities can still produce excellent businesses — they often correspond to "boring" problems that established players have ignored — but the founder should expect a longer customer-development cycle to confirm willingness to pay.
Why this matters for SaaS founders
It sits at the intersection of "ai-detection", "automation", "browser-extension", which makes it relevant to a specific subset of founders rather than a generic horizontal opportunity. SaaS opportunities at this stage tend to win on the strength of their initial wedge — a single workflow that the target user runs every week, where the existing solution is either spreadsheets, a clunky incumbent feature, or a manual process they hate. The build cost is moderate; the distribution cost is everything. The MonetScope pipeline surfaces this category alongside other saas signals, which is why it appears here rather than in a generic "trending ideas" feed.
Scores are derived from real forum discussions across Reddit, Hacker News and X, weighted by evidence volume and signal quality. How scoring works
Frequently asked questions
Is "HumanVerify: Forensic Human-Post Filter for X Feeds" a real validated startup idea or just an AI-generated suggestion?
MonetScope does not generate ideas from a language model's imagination. Every opportunity on this site is anchored to specific source posts and comments from real public discussions — typically on Reddit, Hacker News, or X — where actual users describe the pain in their own words. The AI's role is structuring, scoring, and grouping those signals into a navigable opportunity, not inventing the problem.
How recent is the underlying data for ai-detection?
MonetScope's spider pipeline runs continuously and surfaces opportunities as new evidence accumulates. The "Updated" date in the header reflects the most recent re-scoring of this specific opportunity. Most saas opportunities visible in the public catalog draw from discussions in the last 30-60 days; older signals are de-prioritized because user pain shifts faster than most founders assume.
What's the difference between "overall score" and "validation score"?
Overall score is a composite across six dimensions — pain, urgency, willingness to pay, market size, defensibility, and execution ease — designed to give a single number for triage. Validation score is narrower: it asks "how cleanly does the same signal repeat across independent sources?" An opportunity can score high on overall but lower on validation when one or two large discussions dominate the evidence; conversely, validation can be high on a smaller-overall idea where the signal is consistent but the addressable market is modest.