2
1 Comment

Built a first-pass AI video screening tool — looking for feedback on cautious report wording

I’m working on AI Video Detector, a web tool for people who see a suspicious social video and want a quick first-pass signal report before sharing it.

Link: https://aivideodetector.video/?utm_source=indiehackers&utm_medium=community&utm_campaign=launch_aivideodetector_video_202606&utm_content=build_feedback_post

The main product constraint is that this is a sensitive category. I don’t want the tool to overclaim that it can prove a video is real or fake. The report uses likelihood, confidence, source/media access, visual artifact, motion, compression, and audio-video consistency signals where available.

I’d appreciate feedback on:

  1. Is the positioning clear enough for a non-technical user?
  2. Does the wording avoid overclaiming?
  3. What would you want to see before trusting a report enough to investigate further?
on June 19, 2026
  1. 1

    The part I'd pay attention to isn't whether the wording overclaims.

    It's whether users interpret uncertainty the way you intend them to.

    Two people can read the same cautious report and walk away with completely different levels of confidence.

    That's the kind of thing that can be hard to notice early because the wording itself may look perfectly reasonable.

Trending on Indie Hackers
Priorities for launching a SaaS solo, with no budget User Avatar 172 comments I Rejected a $15K Acquisition Offer for My Multi-Agent IDE — Here's the Full Breakdown User Avatar 29 comments I built a tool directory that doesn't pretend every founder has the same needs User Avatar 25 comments 5 Books, Make Smarter User Avatar 10 comments Why founder-led outbound breaks the moment you try to delegate it User Avatar 7 comments I built a browser-based photo geotagging tool. What should I lead with? User Avatar 6 comments