r/computervision Community Analysis

1. Data Sources & Methodology

• Subreddit: r/computervision (147,948 subscribers)
• Total unique posts analyzed: 311 (after deduplication across 16 raw JSON files: 4 time periods x 4 pages)
• Date collected: 2026-04-10
• Score range: 0 to 2,525
• Median score: ~28 (heavily skewed — dataset is top-heavy in "all" and "year", thin-tailed in "week")
• Top 10 threshold: 706
• Top 25 threshold: 453
• Top 50 threshold: 287
• Top 100 threshold: 168

Period breakdown:

Cross-subreddit score calibration: r/computervision peaks at 2,525 (tomato counter video). This is dramatically lower than r/MachineLearning's 8,544 ceiling despite MachineLearning being ~20x larger by subscriber count, and lower than r/ClaudeAI (~8,084), r/macapps (~2,000), or r/LocalLLaMA. Among technical subs closest in flavor, it behaves most like r/learnmachinelearning — a teaching-oriented sub where tutorials and beginner showcases dominate. The median (~28) is very low because the week slice is full of under-10 help posts, but among the all/year leaderboard the median is ~200-300. A score of 200 is a good hit, 400+ is strong, 700+ is rare and viral, and 1,000+ happens maybe 3 times a year. Tutorial tool launches by known accounts (RandomForests92/Roboflow, Full_Piano_3448/Labellerr) reliably land in the 200-750 range — a predictable and reproducible ceiling.

This is a content strategy guide, not a sociological study.

2. Subreddit Character

r/computervision is a working-engineer's workshop dressed up as an academic subreddit — 80% "look what I built with YOLO this week," 15% "help me fine-tune YOLO this week," and 5% people quietly shipping SLAM boards, custom CNNs, and SAM pipelines that actually matter. It is not r/MachineLearning (which would nuke half the content here as low-effort), not r/LocalLLaMA (no running-models culture), and not r/learnmachinelearning (slightly more technical ceiling). The closest spiritual neighbor is r/gamedev — a sub full of practitioners showing in-progress demos to each other, tolerant of self-promotion if it's framed as a tutorial, and where "I made a thing with [standard tool]" is the default format.

Community identity: A mix of undergraduates, self-taught builders, Roboflow/Labellerr-adjacent content creators, a minority of industry CV engineers, and a steady trickle of academic researchers. The technical floor is high enough that beginners get helpful answers but low enough that "YOLO on pothole dataset, first project" (534 score) gets celebrated. There is a distinct tier of "content marketers who know CV well" — accounts like Full_Piano_3448 (Labellerr), k4meamea, RandomForests92 (Roboflow), leonbeier (ONE AI), and SKY_ENGINE_AI — who post weekly tutorials tied to their company's product. They are NOT banned. They are tolerated and often upvoted because the content is genuinely useful. This is the single most important cultural fact about the sub.

Product launches: Tolerated if they come with a working demo video, a GitHub link, and a technical writeup. Hostile to anything that looks like a pitch without substance. Rule 6 explicitly states "All commercial posts are subject to review. Content should be broadly beneficial to the community, and not just the company behind the posting." In practice this is enforced loosely — the Labellerr cookbook tutorials, the Roboflow workflows, the ONE AI comparisons, and the SKY ENGINE AI synthetic data posts all thrive despite being de facto commercial. The secret is that they teach something the reader can actually reproduce. A bare product post ("I built a platform, check it out") lands in the 10-50 range or gets auto-removed.

Humor: Rarely dominant but works in small doses. Tracking a dancing plastic bag with object detection - the American Beauty stress test (546) and the follow-up The plastic bag scene from American Beauty, but now the SAM version (117) are the closest to pure memes and they work because they're ironic applications of serious tools. Pure shitposts don't appear — there's no meme flair and the sub treats itself seriously.

Technical level: Moderate-to-high. Top comments reference Hamming distance on ORB descriptors, Wahba's problem for rotation estimation, Albumentations augmentation regimes, TensorRT INT8 quantization, SAHI tiling for small object detection, Kalibr for IMU calibration. But the content that wins is mostly applied-engineering, not cutting-edge research. Research papers get posted and ignored; applied tutorials get upvoted.

Key cultural values (ranked):

1. Working demos over abstract claims — Any post with a clean video of the system doing the thing beats a text post about the same technique by 5-10x. The top 25 is 92% video.
2. YOLO-pragmatism — YOLO (v8 through v26) is the unquestioned default detector. A huge fraction of top posts are YOLO + tracker + domain-specific twist. The community does NOT punish "just used YOLO" — it rewards anyone who gets YOLO working on a new domain.
3. Edge deployment and efficiency — Jetson Orin Nano, Raspberry Pi, CPU-only inference, 90 FPS on CPU, 600KB anti-spoofing models, $15 SLAM camera boards. These posts consistently out-perform bigger-hammer content.
4. Skepticism of AGPL / Ultralytics licensing — The YOLO is NOT actually open-source thread (295 score, 150 comments, 0.95 ratio) is a permanent reference point. RF-DETR and other Apache-licensed alternatives get explicit upvotes for being "free as in commercial."
5. Anti-LLM-replacing-CV sentiment — Everyone's wondering if LLMs are going to replace CV workflows... (97 score, 0.82 ratio) and Where VLMs actually beat traditional CV in production and where they don't (27 score, 0.73 ratio) show the community rewards nuanced takes and mildly punishes hot takes. They're tired of hearing VLMs will replace their jobs.
6. Reproducibility — GitHub links, notebooks, Colab links, and explicit "here's the code" are table stakes. Posts without them routinely underperform similar posts with them.

Enforcement mechanisms: Rule 3 mandates proper flair (Showcase, Discussion, Help: Project, Help: Theory, Research Publication, Commercial, OpenCV). Rule 5 requires that help posts state "approaches you've tried so far." Rule 6 subjects commercial posts to review. In practice, mod enforcement is light compared to r/MachineLearning — the sub lets a LOT of tutorial-style self-promo through. Community self-policing is polite but effective: comments will ask for code links, point out that a dataset is synthetic, or note that a tutorial is actually a Labellerr product demo. The sub rarely brigades or nukes contributors.

Mandatory posting flair: Every post requires a flair. The active ones in the dataset:

• Showcase — by far the dominant flair (~55-60% of top 50), used for demo videos, tutorials, and project reveals
• Discussion — opinion pieces, debates about SOTA, "what do you think" threads
• Help: Project — practical questions ("how do I detect X"), must include what you've tried
• Help: Theory — conceptual questions about algorithms
• Research Publication — papers, new model releases, weekly multimodal roundups
• Commercial — anything product-selling; instantly de-rates a post
• OpenCV — classical/non-DL content (rare, legacy)

How this differs from related subs: r/MachineLearning would remove 70% of this content as "low-effort project spam." r/learnmachinelearning lacks the applied-video culture. r/robotics has overlapping SLAM/perception content but reveres hardware over vision algorithms. The closest neighbor in spirit is r/MachineLearning's [P] tag — except without the gatekeeping and with more YOLO.

3. The All-Time Leaderboard

Median of full dataset: ~28 (dominated by weekly help posts). Median among all+year posts: ~250. Top-25 threshold: 453. Top-10 threshold: 706.

Key observations: 22 of the top 25 are VIDEO format. The 2 IMAGE posts (#3 favorite model, #18 YOLO26 vs RF-DETR) are both "what do you prefer" polls — low-effort but high-engagement prompts. The one TEXT post in the top 25 is a non-technical rant (AI-first hiring rejection) that generated 212 comments in the career-anxiety register — this is an outlier, not a repeatable pattern. There is zero pure research/paper content in the top 25. The top of this sub is 100% applied demo videos.

4. Content Type Dominance at Scale

Flair distribution across the full 311-post dataset:

The most surprising finding: Showcase is not only the most common flair — it is essentially the only flair that reliably hits 400+. Discussion can spike on polls and rants but typical discussion posts score 20-80. Help: Project occasionally hits 400+ (mostly when the help question comes with a polished demo video attached showing the thing already mostly works — see ranks 9 and the Follow-up: depth estimation road damage at 458). Commercial is a death flair for raw score — Computer Vision Prototypes is the only Commercial post in the top 50. If you want score, pick Showcase. If you want community goodwill, post something legitimately useful and don't flair it Commercial even if it's yours.

5. Content Archetypes That Work

Seven distinct archetypes emerge from reading the top 100. Ranked by score ceiling:

Archetype 1: "Useful-Weird YOLO + Tracker Demo" (score ceiling: 2,525)

• i developed tomato counter and it works on real time streaming security cameras (2,525)
• Player Tracking, Team Detection, and Number Recognition with Python (2,376)
• Built a chess piece detector to render overlay with best moves in VR headset (1,099)
• I built a face tracking full-auto nerf gun using OpenCV (632)
• basketball players recognition with RF-DETR, SAM2, SigLIP and ResNet (540)

The pattern: Take a standard detector (YOLO/RT-DETR/RF-DETR), apply it to a specific, visually-interesting real-world use case (sports, fruit counting, VR overlay), add tracking and a clean overlay, ship a 15-45 second clip. The "useful-weird" angle matters: pure object detection on COCO classes dies. Detecting tomatoes in security footage, players in NBA clips, chess pieces on a real board — these work because the viewer instantly gets what problem is being solved.

Why it matters for distribution: This is the single most reproducible archetype in the dataset. If you have ANY product that does detection-plus-something, you can make a video in this style. The score ceiling is 2,500 but the median of this archetype is ~400 — extremely consistent upside.

Archetype 2: "Labellerr/Roboflow Cookbook Tutorial" (score ceiling: 748)

• Real time vehicle and parking occupancy detection with YOLO (748, Full_Piano_3448)
• Real time deadlift form analysis using computer vision (710, Full_Piano_3448)
• Real-time assembly line quality inspection using YOLO (403, Full_Piano_3448)
• Visualizing Road Cracks with AI: Semantic Segmentation (653, k4meamea)
• Road Damage Detection from GoPro footage with progressive histogram (636, k4meamea)

The pattern: Weekly content grind by accounts with corporate backing (Labellerr, Roboflow, ONE AI, SKY ENGINE). Every post includes: a demo video, a high-level workflow bullet list, a notebook/Colab link, a YouTube tutorial link, a dataset link. The posts are de facto marketing for annotation platforms but they're so useful that the community welcomes them. Full_Piano_3448 alone has 15+ posts in the dataset scoring 200-750 each — all shaped identically.

Why it matters for distribution: If you publish a computer vision product (not a consumer app), this is your playbook. Build one cookbook per week on a different vertical, release the notebook publicly, and post. You'll score 200-500 reliably. The ceiling is lower than Archetype 1 (because the "demo" feels more commercial) but the floor is high.

Archetype 3: "Edge Device / Small Model Flex" (score ceiling: 710)

• Built a lightweight Face Anti Spoofing layer (707) — 600KB model, INT8, runs on 2011 laptop
• SLAM Camera Board (529) — $15 VIO board
• Added Loop Closure to my $15 SLAM Camera Board (378)
• Tracking Persons on Raspberry Pi: UNet vs DeepLabv3+ vs Custom CNN (287) — 57k params, 30 FPS
• 90+ fps E2E on CPU (307) — YOLOLite
• Real-time head pose estimation (347)

The pattern: Emphasize constraints. Small model. Cheap hardware. CPU-only. Old laptop. Low parameter count. The community adores efficiency claims with concrete numbers — parameter counts, FPS on specific silicon, model size in KB, power consumption in watts. These are not marketing claims, they are technical brags that resonate because many readers are deploying on Jetson/Pi/embedded.

Why it matters for distribution: If your product does inference on-device or at the edge, LEAD with the numbers. "Runs on Jetson Orin Nano at 30 FPS" beats "powered by advanced AI" by 10x in engagement.

Archetype 4: "Sports Analytics Build" (score ceiling: 710)

• Real time deadlift form analysis (710)
• Tracking ice skater jumps with 3D pose (578)
• Football juggle counter (616)
• I built an automatic pickleball instant replay app (471)
• Real-time cricket bowler's arm mechanics (312)
• F1 Steering Angle Prediction (174)
• Position Classification for Wrestling (188)

The pattern: Pose estimation (YOLO-pose, MediaPipe, MMPose) + sport-specific metric computation + live overlay graphs. The sub has a bizarre love of sports content — nearly 10% of the top 50 is sports. Fitness apps, ball tracking, player tracking, barbell path tracking, steering angle estimation. There's never not a sports post in the top 25.

Why it matters for distribution: Sports is a guaranteed vehicle. If you can plausibly frame your CV work as "I track a player/ball/barbell," you get a score boost just from the format.

Archetype 5: "YOLO vs X Comparison" (score ceiling: 626)

• YOLO26 vs RF-DETR (626, IMAGE)
• Comparing YOLOv8 and YOLOv11 on real traffic footage (331)
• Synthetic Data vs. Real-Only Training for YOLO on Drone Detection (381)
• Fast Object Detection Models and Their Licenses (363)
• Detecting Thin Scratches on Reflective Metal: YOLO26n vs Task-Specific CNN (199)
• Tiny Object Tracking: YOLO26n vs 40k Parameter Task-Specific CNN (165)

The pattern: Head-to-head comparison with metrics (mAP, FPS, parameter count, memory), a clear winner, and ideally a surprising result (the small custom model beats YOLO). The community loves this because everyone is picking a detector and wants the benchmark work done for them.

Why it matters for distribution: If you have your own model architecture or a novel fine-tune, ALWAYS post a comparison against YOLO in the same post. Don't just claim your thing is good — claim it's better than YOLO at a specific constraint (tiny objects, edge latency, small datasets).

Archetype 6: "Applied Research Highlight / Model Wrapper" (score ceiling: 540)

• SAM3 is out with transformers support (333)
• SAM3 is out. You prompt images and video with text... (272)
• VGGT was best paper at CVPR and kinda impresses me (304)
• apple released SHARP which creates a 3d gaussian from a single view (301)
• RF-DETR Segmentation Preview: Real-Time, SOTA, Apache 2.0 (261)
• I built RotoAI: open-source text-prompted video rotoscoping (SAM2 + Grounding DINO) (420)

The pattern: Spot a new model within hours of release, wrap it in a usable notebook/Colab/integration, post a side-by-side or a working demo. datascienceharp does this professionally on behalf of FiftyOne/Voxel51 and consistently scores 180-300. The pattern rewards SPEED — being first to share a working notebook for a new model.

Why it matters for distribution: Monitor paperswithcode, HF trending, and CVPR/NeurIPS accepted papers. When something hot drops, build the integration immediately and be the person who ships it first. Highest score-per-effort ratio if you can move fast.

Archetype 7: "Rant / Industry Anxiety Post" (score ceiling: 550)

• It finally happened. I got rejected for not being AI-first. (550, 212 comments)
• Dear researchers, stop this non-sense (377, 111 comments — complaining about overcomplicated research code)
• YOLO is NOT actually open-source (295, 150 comments)
• Everyone's wondering if LLMs are going to replace CV workflows (97, 0.82 ratio)
• What's one computer vision problem that still feels surprisingly unsolved? (54, 81 comments)

The pattern: Raw text posts tapping into shared grievances about the industry — AI hype, licensing traps, job market, overcomplicated codebases. These score high on comments per upvote (huge C/U ratio) but have controversial ratios. They're community bonding rituals, not promotional vehicles.

Why it matters for distribution: Do NOT try to launch a product via a rant. These work only when they come from someone sharing a genuine frustration. But if you post one and it hits, you get enormous discussion (200+ comments) which can build reputation capital for later Showcase posts. Use sparingly.

6. Format Analysis

The takeaway is unambiguous: video wins. 88% of the top 25 and 86% of the top 50 are videos. Every single Showcase post in the top 10 is a video. If you post anything other than video in the top tier, you're fighting uphill.

What Format to Use For What

• Tool / library launch → VIDEO (15-45s screen capture of the tool processing a real input, with overlays and labels visible). Example: Cool node editor for OpenCV (706), Interactive visualization of Pytorch models (408).
• Comparison / benchmark → IMAGE works if it's a clean table or side-by-side shot (YOLO26 vs RF-DETR = 626), but VIDEO still wins if you can show both models running simultaneously on the same frame.
• New model release / announcement → VIDEO of the new model running on a real-world input. "Paper X came out" posts without a demo die.
• Help: Project question → VIDEO of your system failing in the interesting way. The #9 top post (737 score) is a help post with a video showing the audience/ref detection problem clearly. This is 10x better than pasting a code snippet.
• Humor / meme → VIDEO with a cultural reference (American Beauty plastic bag at 546).
• Career rant / industry take → TEXT only. Videos of rants feel performative.
• Research explainer → IMAGE with paper thumbnail + short technical summary. Pure paper-link posts without commentary get ignored.

What Makes a Good Demo Video

From the top-performing videos in the dataset:

1. Length: 15-60 seconds. The tomato counter (2,525) and the basketball tracker (2,376) are both ~30 seconds. Anything over 90s hemorrhages viewers on the Reddit autoplay.
2. Show the problem first, then the fix. The deadlift analyzer (710) opens with the bar, then overlays the tracking. The ice skater jump tracker (578) cuts between a raw clip and a pose overlay.
3. Clean overlays with real numbers on screen. FPS counters, object counts, per-frame metrics. Top posts show actual data streaming on the video, not just bounding boxes.
4. No talking head, no voiceover, no intro music. Zero top-25 videos are vlog-style. They're silent screen captures with text overlays. Reddit autoplays without sound.
5. Use a real-world source (not COCO demos). Security cam footage, GoPro clips, live webcam, gameplay. Stock lab setups underperform.
6. Vertical or square crop is fine — mobile autoplay rewards it, but horizontal 16:9 also works. The key is "reads clearly at thumbnail size."

7. Flair/Category Strategy

Which flairs to use:

• Showcase — default for anything with a demo. 88% of the top 50 is here. Use it unless your post is unambiguously a question, research paper, or rant.
• Discussion — use for opinion posts, model comparisons ("YOLO26 vs RF-DETR"), or community polls ("What's your favorite CV model?"). It caps lower than Showcase but has higher C/U.
• Help: Project — use ONLY if you genuinely have a problem. The community is allergic to "help" posts that are actually stealth product ads. But if you have a real problem and attach a clean demo video showing the failure case, you can score 400+ (e.g., the audience/ref detection post at 737).
• Research Publication — use for papers and model releases. Low ceiling (~300) but it's the right signal for that content type.

Which flairs to avoid:

• Commercial — this is a death flair for score. The only Commercial post to crack 200 in the dataset is Computer Vision Prototypes (356) which is basically a personal service offering. Other Commercial posts average well under 50. Even if your post is commercial, flair it as Showcase with a disclosure in the body. The community's real rule is "no dead-eyed promo" — it doesn't care about the flair label if the content teaches.
• Help: Theory — goes almost nowhere. Theory questions belong in r/MachineLearning or MLQuestions. Average score under 20.

Distribution utility (different from raw score)

Help: Project is underrated as a distribution vehicle. A well-framed help post gets 30-90 comments full of experts explaining what to use — including, frequently, recommending specific tools/libraries/services. If you're building an annotation tool, dataset platform, or training framework, you want your product being recommended in those comment threads. You can accelerate this by posting as a helper yourself (see stealth tactics in Section 11).

Pricing model hierarchy (community-friendly to hostile)

Unlike r/macapps or r/ClaudeAI, r/computervision doesn't have deep opinions on pricing — most content here is self-hosted tooling. But there's a clear preference ordering:

1. Open source / Apache / MIT — celebrated. "Apache 2.0" in the title is a positive signal (see the RF-DETR post at 261).
2. Free with paid cloud tier — tolerated. Labellerr/Roboflow/Voxel51 all operate here and their content thrives.
3. One-time / lifetime paid — rare. The Firefly Fitness app (167, 0.95) used a "free lifetime" giveaway angle to gain traction.
4. SaaS subscription — accepted only if the content is pure tutorial and the SaaS link is below the fold.
5. AGPL — actively hostile. The 295-score Ultralytics rant is the baseline — everyone knows, everyone remembers, and posts about Ultralytics-licensed code get skeptical comments.

8. Title Engineering

Top 10 title deconstruction

1. "i developed tomato counter and it works on real time streaming security cameras" (2,525) — The magic here is the "it works on real-time streaming security cameras" second clause. Real-time + streaming + security cameras signals three constraints the viewer knows are hard. The lowercase "i" and typo-adjacent phrasing reads as authentic, not marketed. Technique: promise three specific hard constraints the community knows are hard.
2. "Player Tracking, Team Detection, and Number Recognition with Python" (2,376) — Three stacked capabilities + "with Python" = tutorial signal. Technique: list format capability stacking.
3. "What's your favorite computer vision model?" (1,397) — Pure engagement bait poll. Two-word subject. Technique: zero-effort community poll.
4. "Built a chess piece detector in order to render overlay with best moves in a VR headset" (1,099) — "In order to" structure surfaces the actual use case. Chess + VR is unexpected. Technique: detector + downstream application.
5. "Missing Object Detection [C++, OpenCV]" (931) — Square-bracket tech stack is a classic r/cv title. "Missing Object" is an attention hook — detect what's NOT there. Technique: inverted problem framing.
6. "[PROJECT] Heart Rate Detection using Eulerian Magnification" (837) — Cites a specific classical technique (Eulerian magnification) most readers won't know. Technique: name-drop an obscure algorithm.
7. "Real-time Abandoned Object Detection using YOLOv11n!" (810) — YOLOv11n specified, "abandoned object" is a surveillance-adjacent buzzword. Technique: version-specific model + domain-specific term.
8. "Real time vehicle and parking occupancy detection with YOLO" (748) — Plain applied use case. Technique: baseline Labellerr-style phrasing.
9. "How to correctly prevent audience & ref from being detected?" (737) — Help question framed as a solvable problem. "Correctly" implies the poster tried and failed. Technique: honest, specific help question.
10. "Video Object Detection in Java with OpenCV + YOLO11 - full end-to-end tutorial" (717) — "Java" + "OpenCV" + "YOLO11" + "end-to-end tutorial" = four search keywords stacked. Technique: keyword-dense tutorial signal.

Title formulas that work

1. "[Real-time/Real time] [X] detection using [YOLO/specific model]"

   • Real-time Abandoned Object Detection using YOLOv11n! (810)
   • Real time vehicle and parking occupancy detection with YOLO (748)
   • Real time deadlift form analysis using computer vision (710)
   • Real-time head pose estimation for perspective correction (347)

2. "I built/developed [specific thing] [with tool stack]"

   • i developed tomato counter and it works on... (2,525)
   • I built a face tracking full-auto nerf gun using OpenCV (632)
   • I built a program that counts football juggle attempts (616)
   • I built RotoAI: An Open-source, text-prompted video rotoscoping... (420)

3. "[X] vs [Y] [comparison/benchmark]"

   • YOLO26 vs RF-DETR (626)
   • Synthetic Data vs. Real-Only Training for YOLO on Drone Detection (381)
   • Comparing YOLOv8 and YOLOv11 on real traffic footage (331)
   • Detecting Thin Scratches on Reflective Metal: YOLO26n vs Task-Specific CNN (199)

4. "Tracking [something surprising] with [technique]"

   • Tracking a dancing plastic bag with object detection (546)
   • Tracking ice skater jumps with 3D pose (578)
   • Tracking Persons on Raspberry Pi: UNet vs DeepLabv3+ vs Custom CNN (287)

5. "[Built/Made] [specific hardware artifact] [cost/spec flex]"

   • Built a lightweight Face Anti Spoofing layer (707)
   • SLAM Camera Board (529)
   • Added Loop Closure to my $15 SLAM Camera Board (378)
   • 90+ fps E2E on CPU (307)

6. "[Model] is out with [capability]" (for new-release posts)

   • SAM3 is out with transformers support (333)
   • SAM3 is out. You prompt images and video with text... (272)
   • apple released SHARP which creates a 3d gaussian from a single view (301)

Title anti-patterns (community-specific)

• Do not brag about accuracy numbers without context. > 83 on my Yolo26x model (21 score) is the exact wrong way to post — the community wants to know what dataset, what class, what constraints. Compare to Synthetic Data vs Real-Only Training for YOLO on Drone Detection (381) which states the exact metric delta.
• Do not use pure research jargon in titles. DETR head + frozen backbone (9 score) is written for the 0.1% who already know the context. The same post framed as "I tried DINOv3 + DETR — here's why it doesn't work" would have scored 10x.
• Do not put "Day N/90" growth-journey titles. Day-1/90 of Computer vision scored 146 on day 1 then dropped to 52, 32 on days 2 and 3. The community does not reward commitment theater; it rewards artifacts.
• Do not use emoji-salad titles. AUTOMATIC NUMBER PLATE RECOGNITION (ANPR, LPR, ALPR) solution (226, 0.89 ratio) got friction points for the marketing-speak stacking of acronyms.
• Do not write hedging titles. Is this good enough to deploy? or New to CV, struggling with X (6 score) read as anxious. Confidence in the title correlates with upvotes.
• Do not title pure commercial announcements. [Hiring Me] posts (10 score) die in the 5-20 range regardless of author quality.

9. Engagement Patterns

Comments-to-upvote (C/U) ratios by content type, from the top 100:

Examples of high-C/U "debate generators":

• It finally happened. I got rejected for not being AI-first. (550 score, 212 comments, 0.39 C/U)
• Dear researchers, stop this non-sense (377 score, 111 comments, 0.29 C/U)
• YOLO is NOT actually open-source (295 score, 150 comments, 0.51 C/U)
• Oh how far we've come (413 score, 93 comments, 0.23 C/U — Lenna image nostalgia)

Examples of low-C/U "passive visibility":

• Tomato counter video (2,525 score, 137 comments, 0.05 C/U)
• Chess piece detector (1,099 score, 57 comments, 0.05 C/U)
• Cool node editor for OpenCV (706 score, 47 comments, 0.07 C/U)

Conditional recommendation: If your goal is VISIBILITY, post a Showcase video — you'll get 300-700 upvotes with low engagement. If your goal is RELATIONSHIPS and discussion, post a Discussion piece (comparison, rant, or poll) — lower ceiling but 3-5x the comments per upvote. If your goal is TECHNICAL CREDIBILITY, answer a Help: Project post with a detailed comment — this is the only vehicle that gets you recognized without making your own post.

Highest-discussion topics (regardless of score)

1. YOLO licensing and AGPL drama — any post that mentions Ultralytics licensing generates 100+ comments
2. "Is CV dead" career anxiety — Future outlook on cv career, Is the only bottleneck in CV hardware?, Starting a CV PhD without a mentor, Where VLMs actually beat traditional CV
3. Annotation workflow pain — any post about labeling, SAM auto-labeling, or annotation cost generates debate
4. YOLO version wars — YOLO8 vs 11 vs 12 vs 26 vs RF-DETR is a permanent flamewar topic
5. Edge hardware tier lists — Jetson vs Pi vs custom silicon posts attract 20-60 comments

10. What Gets Downvoted

Posts with ratios below 0.85 in the dataset (there are few — the community is relatively polite):

Ratio tiers:

• Above 0.94 — universally well-received. Most showcase posts live here.
• 0.85-0.94 — net positive but with friction. Usually indicates the post made strong claims (SOTA, "beats CNNs", "replacing CV"), had pricing/commercial overtones, or touched a cultural third rail (Lenna, licensing, career anxiety).
• Below 0.85 — controversial or community-hostile. Rare in this sub — usually VLM-replacing-CV hot takes, marketing-heavy "vibe coding for datasets" pitches, or nostalgia posts that age poorly.

Anti-patterns (named)

1. "SOTA Beater" Overclaim — Making strong benchmark claims ("beats CNNs", "SOTA", "90% accuracy!") without a clean head-to-head table. Example: Biological Wave Vision beating CNNs (251, 0.89). The community doesn't hate the idea, it hates the confident framing. Fix: post the exact confusion matrix and let readers make the claim.

2. "VLM Hot Take" Overreach — Posts arguing that LLMs/VLMs will replace traditional CV workflows die on ratio. Everyone's wondering if LLMs are going to replace CV (97, 0.82) and Where VLMs actually beat traditional CV (27, 0.73) both made this mistake. The community's priors are strong: VLMs are a tool in the stack, not a replacement. If you post on this topic, be even-handed.

3. "Vibe Coding for Datasets" — Pitching chat-to-dataset or AI-generated labels as a paradigm shift. I got tired of manually drawing segmentation masks... (16, 0.58) is the worst-performing post in the month slice. The community labels data for money and doesn't want to hear about its obsolescence from a demo.

4. "Career Anxiety Flood" — Low-score but high-ratio: Future outlook on cv career (12), Starting a CV PhD without a mentor (8), Got my first offer... (8). These don't get downvoted but they get buried. Post them to r/cscareerquestions instead.

5. "Growth Journey Day-N" — Day-1/90 of Computer vision (146) got one viral first post then drops hard on day 2 (52) and day 3 (32). The community rewards the artifact, not the journaling.

6. "Marketing Salad Title" — Titles packed with emoji, acronym stacking, and feature lists. AUTOMATIC NUMBER PLATE RECOGNITION (ANPR, LPR, ALPR) (226, 0.89) shows the pattern. Pays visibility but loses trust.

7. "Bare Paper Link" — Research Publication posts with no commentary, no demo, no integration. These average 20-80 score. The community wants the paper + a working notebook.

No public blacklist or hall of shame exists — this sub lacks the enforcement machinery of r/macapps or r/MachineLearning. Enforcement is cultural: your post lives or dies on whether it teaches something, and repeat offenders mostly just get ignored rather than punished.

11. The Distribution Playbook

Phase 1: Pre-launch (2-4 weeks before any post)

1. Read the last 50 Showcase posts of the week. Understand what the current YOLO/SAM/DINO version of the week is. Using "YOLOv8" in late 2026 will read as out of date — the community has moved to YOLO26 and RF-DETR.
2. Build a working demo on a REAL-WORLD video, not COCO. Your own footage, GoPro clips, dashcam videos, security cam, gameplay. The bias against stock demos is absolute.
3. Put your code on GitHub with a minimal README. Labelled as "Notebook included" or "Colab here." Readers will click.
4. Pick your archetype (Section 5). Don't try to be all seven. Pick one and execute. The Labellerr Cookbook format is the highest-floor template; the Useful-Weird YOLO Demo is the highest-ceiling.
5. Start answering help posts in the sub. Spend 2 weeks being useful in comments before ever making your own post. The top content creators (RandomForests92, Full_Piano_3448, datascienceharp, k4meamea) all have heavy comment history.

Phase 2: Launch day

• Format: Video, 15-45 seconds. Screen recording with overlays visible. Autoplay-friendly.
• Flair: Showcase. Not Commercial, even if your content is commercial.
• Title formula (pick one from Section 8):
  • I built [specific thing] using [model] — [unexpected constraint]
  • Real-time [domain] detection with [stack]
  • [X] vs [Y] on [real-world task]
• Body text template:

  [1-2 sentence description of what the video shows.]
  
  Stack:
  - Detection: [YOLO/RT-DETR/RF-DETR/SAM3]
  - Tracking: [ByteTrack/BoT-SORT]
  - [Other component]: [model]
  
  High level workflow:
  - [bullet 1]
  - [bullet 2]
  - [bullet 3]
  
  Numbers:
  - Parameters: X M
  - Inference: Y ms / frame on [hardware]
  - mAP@50: Z (if relevant)
  
  Notebook: [github/colab link]
  Video tutorial: [optional YouTube link]
  
  Feedback welcome, especially on [specific pain point you hit].
  

• Posting time: Analyzing the created_utc values of the top posts, most cluster around 13:00-19:00 UTC (US morning / European afternoon). Avoid weekends — engagement drops noticeably.

Phase 3: First 24-48 hours

• Monitor comments hourly for the first 6 hours. This is when the sub's self-policing activates. If someone asks "isn't this just a Labellerr ad?" — respond transparently with "yes, full disclosure, I work at Labellerr, but the notebook is free and Apache-licensed."
• Respond to every technical question. The comments are the actual conversation. A showcase post with 40+ helpful author replies converts ~30% of commenters into GitHub stars.
• Do NOT respond to praise with "thanks!" Respond with technical elaboration. "Thanks, happy to hear it!" is weaker than "Thanks — the tracking stability was actually the hardest part. I ended up using a 20-frame moving average to filter pose jitter."
• Handle the first 3-4 critical comments with technical humility. "Good point, you're right — I didn't test on X, let me run it and follow up" is golden. Defensive responses get downvoted.

Phase 4: Ongoing presence

• Post weekly on a recurring theme. The accounts that dominate (Full_Piano_3448, k4meamea, leonbeier) post one tutorial per week, each on a different vertical (parking, fitness, road damage, industrial inspection). This pattern is rewarded.
• Post follow-ups. Follow-up: Adding depth estimation to Road Damage severity pipeline (458) was a direct sequel to the earlier road damage post and scored nearly as high. Iteration is rewarded.
• Answer help questions in your area of expertise. Every 3-4 of your own Showcase posts, help-reply to 10-20 questions. This builds the reputation capital that shields your next commercial-adjacent post from skepticism.
• Release datasets. Any time you build a cookbook, release the annotated dataset on Kaggle or HF. The Santa Claus detection dataset (333) shows that even a joke dataset gets upvoted when it's actually shareable.

Community-specific comment strategy (pre-written reply templates)

Q: "Isn't this just a [company] ad?"

Full disclosure: I work at [company]. The notebook is Apache-licensed and the dataset is free to download. You can reproduce this exact pipeline on your own data without talking to us. Happy to answer any technical questions.

Q: "Why YOLO and not [RT-DETR / RF-DETR / custom]?"

Good question. For this use case I chose YOLO because [specific reason — small dataset / edge latency / existing tooling]. I actually tried RT-DETR first and got [result] — the YOLO11n was ~Xx faster for Y% less accuracy, which was the right tradeoff here. Happy to share the comparison if helpful.

Q: "What about the Ultralytics AGPL license?"

Yeah, this is a known concern. For commercial deployment I'd recommend RF-DETR (Apache 2.0) or [alternative]. I'm using Ultralytics here for the tutorial because it's the fastest way to show the pipeline. The core logic ports to any detector.

Q: "How does this compare to [LLM/VLM approach]?"

VLMs are great for zero-shot detection when classes change, but for this use case (real-time, fixed classes, edge deployment) a YOLO-class model runs 100x faster. I do think hybrid architectures (VLM reasoning + CV execution) are where things are going — there's a good thread about this [link].

Q: "Will this work on my [edge hardware]?"

Probably yes, with quantization. I tested on [hardware] at [FPS]. If you port to Jetson Orin Nano you'll get roughly [X] FPS with INT8. Happy to help you benchmark if you run into issues.

Stealth distribution tactics

1. Answer Help: Project posts with "I built a tool for exactly this" — only when it's genuinely relevant. Link to your GitHub, not your pricing page. This is the single highest-converting distribution channel in the sub because helping strangers builds trust that a Showcase post can't.
2. Release free datasets tied to your product. The Santa Claus detection dataset (333) and CCTV Weapon Detection: Rifles vs Umbrellas (166) both do this — they're technically marketing for SKY ENGINE / Simuletic's synthetic data platforms but they score because the dataset is free and genuinely useful.
3. Publish a "vs YOLO" benchmark — if you have your own model, the best way to get it on the community's radar is a side-by-side with YOLO showing a specific constraint you win on. See 90+ fps E2E on CPU (307) for the pattern.
4. Participate in the YOLO-version megathreads. When a new YOLO version drops, the sub generates 2-3 discussion threads about it. Comment in those threads with benchmarks from your stack — this gets your name associated with benchmarking expertise.
5. Post on CVPR/ICCV weeks. The sub pays extra attention during conference weeks. Post a "here's how to try [paper] in 5 minutes" integration in the first 48 hours of a paper release.

Score-tier calibration

If you need >3,000 visibility from a single post, you cannot get it here. Cross-post to r/MachineLearning ([P] tag, polished), r/artificial, or r/LocalLLaMA where the ceilings are higher. r/computervision is your base — not your megaphone.

Post-publication measurement

• Hour 0-2: If you don't have ~30 upvotes in 2 hours, the post is dead. The algorithm here is fast. Don't expect recovery.
• Hour 2-6: This is where Showcase posts crystallize. 100+ upvotes by hour 6 means you'll end in the 300-700 range. 200+ by hour 6 means you're headed for top 25.
• Ratio below 0.90 in the first 4 hours: Someone didn't like your framing. Check comments for the specific objection. Usually it's a commercial smell, an overclaim, or a cultural trigger (Lenna, Ultralytics). Respond with humility.
• Comments outpacing upvotes (high C/U early): Discussion generator. Lean into the debate — don't delete.
• Comments full of "what model did you use?": You buried the stack. Edit the post body to add the stack list. This will push upvotes up by 20-30%.
• Zero comments but 100+ upvotes: Passive visibility win. Good for reach, bad for conversion. Next time, add an explicit question at the end of the post.

12. Applying This to Any Project

Quick-reference pre-post checklist

1. Is your format a 15-45 second video? (If not, reconsider.)
2. Is the video silent, with text overlays, showing real-world data?
3. Does the title follow one of the 6 formulas in Section 8?
4. Is the flair Showcase (not Commercial)?
5. Does the body include the stack list (detection + tracking + other)?
6. Is there a GitHub/Colab/notebook link above the fold?
7. Is there a number the community cares about (FPS, params, latency, mAP)?
8. Did you pick a real-world domain (not COCO classes)?
9. Do you have a plan to respond to the first 10 comments within 4 hours?
10. Have you answered at least 5 Help: Project posts in the last week?
11. If your post has commercial overtones, is there a disclosure paragraph ready?

Scenario-based launch guides

Scenario A: Your product is free / open-source

• Optimal launch formula: "I built [specific thing] — Apache 2.0, GitHub in comments"
• Lead with the license in the title or first line of body text
• Include a screenshot of the license file in the repo
• Add a "contributors welcome" line
• Key risk: Announcing without a working demo. "Open source but beta" underperforms vs. "here's a 30s demo of it working."

Scenario B: Your product is one-time / lifetime pricing

• Optimal launch formula: Soft-launch via a free tier tutorial, not a product announcement
• Build a public notebook that uses your tool, label it a tutorial, post as Showcase
• Put the pricing link in a comment, not the post
• Key risk: Direct pricing pitches. A single "starts at $X" line will tank the ratio.

Scenario C: Your product is subscription SaaS

• Optimal launch formula: Publish a weekly tutorial cookbook (Labellerr pattern)
• Use your product in the workflow but never lead with it
• Free notebook, free dataset, free video — the SaaS is mentioned once in the "about us" footer
• Key risk: Sounding like a sales team. If your post uses "We at [company]..." more than once, cut it.

Scenario D: Your product was built with heavy AI/LLM coding

• Optimal launch formula: Don't advertise that it was AI-coded. The community doesn't care the way r/ClaudeAI does, but it also doesn't reward it.
• Lead with the technical artifact, show working code, show real metrics
• Key risk: Framing the post around "vibe coding" or "built with Claude" — the anti-vibe-coded-dataset sentiment (see Section 10, anti-pattern 3) will apply to you.

Scenario E: You are publishing a paper / model release

• Optimal launch formula: Drop a Colab notebook with your release, post as Showcase with a demo video
• Include: paper link, code link, model weights link, Colab link, HF Spaces link (if applicable)
• Lead with the constraint you beat ("SOTA on COCO at 312 FPS fp16" — see RF-DETR at 261)
• Key risk: Pure paper-link post with no demo. These score 20-80 regardless of quality.

Cross-posting guidance

The same core content can be reframed for different subs:

• On r/computervision: Lead with the applied pipeline — "Real-time [domain] detection with YOLO11 + ByteTrack." Focus on the video and the notebook.
• On r/MachineLearning [P]: Reframe to emphasize methodology — "I trained a task-specific CNN that beats YOLO26n at N% the parameters." Remove all commercial links, add explicit method description.
• On r/LocalLLaMA: Reframe as an edge/VLM hybrid — "Running YOLO + Gemma as a real-time multimodal pipeline." Lead with the LLM angle.
• On r/robotics: Reframe around the hardware — "I built a SLAM camera board for $15 that runs VIO + loop closure on NPU." Emphasize the physical artifact.
• On r/gamedev: Reframe as a gameplay application — "Tracking pose with MediaPipe to control a 3D character." Focus on the interaction loop.

The same 30-second video can work on all 5 subs with 5 different titles and 5 different first-paragraphs. The core asset is reusable; the framing is not. Do not cross-post without rewriting. Reddit's cross-post mechanic shows the original title, and a misfitting title tanks the secondary post.