Reddit Community Analysis: r/opensource

1. Data Sources & Methodology

• 278 unique posts after deduplication across 4 time periods (all-time, year, month, week), 14 raw JSON files (month has 4 pages, year has 4 pages, all has 4 pages, week has 2 pages).
• Date collected: April 10, 2026
• Subreddit subscribers: 342,483
• Score range: 0 to 2,259
• Median score: ~99
• Top 10 threshold: ~1,148
• Top 25 threshold: ~691
• Top 50 threshold: ~437
• Top 100 threshold: ~207

Period overlap: Only 1 post appears in all four periods ("Microsoft terminates account of VeraCrypt developer" — 539). Posts that appear in "all + year" but not "month/week" represent the 2025–early 2026 drama/news canon. Roughly 45 posts appear only in "year" (2024–2025 content that didn't crack all-time), and another ~70 posts appear only in "month" or "week" (recent promotional and Q&A posts).

This is a content strategy guide, not a sociological study. The dataset skews heavily toward top performers; the long tail of <10-score posts is represented by "week" only.

Cross-subreddit calibration: r/opensource peaks at only ~2,259 — remarkably low for a 342K-subscriber sub. Compare: r/selfhosted (738K) peaks at 9,564, r/ClaudeAI (~8,084), r/LocalLLaMA (~6,875), r/programming (~10,000+), r/macapps (~2,029). r/opensource scores more like r/macapps in ceiling despite having nearly 2x the subscribers, which tells you something fundamental: this community upvotes but doesn't go viral. A "hit" here is 800-1,500. A canonical top-10 post is 1,000-2,200. There is no meme-viral upper layer the way r/selfhosted and r/LocalLLaMA have. Compared to its closest sibling r/selfhosted, r/opensource is smaller, slower, more news-oriented, less meme-native, and far more punitive toward self-promotion.

2. Subreddit Character

r/opensource is a news-and-advocacy watchtower run by FOSS purists, where the dominant activity is surfacing corporate villainy and the dominant emotion is indignation. It is not a product launch platform. It is not a help forum. It is not a meme sub. It is the place where FOSS-identified developers gather to share license violations, corporate enclosure stories, government policy updates, and occasional celebrations of FOSS projects making it into the mainstream. If r/selfhosted is anti-SaaS, r/opensource is anti-enclosure — everything that reduces software freedom is hostile, everything that preserves or expands it is friendly.

Product launches are tolerated but rarely welcomed. Rule 2 ("No Spam / Excessive self-promotion") enforces a <10% promotional-content ratio per account, and rule 8 ("Use Correct Flairs") forces promotional posts into a flair that is openly viewed with skepticism. A solo-dev launch post typically scores 5–50. The launches that DO break through (Puter, Timeful, RapidRAW, Senlo, LastSignal) all have one of three things in common: (1) they solve a problem the community actively cares about (privacy, lock-in escape, FOSS alternative to proprietary tool), (2) they come with a personal drama narrative (stolen code, DMCA, legal threat), or (3) they are from repeat, trusted authors. Most raw "I built X" posts die at double digits.

Humor is almost entirely absent. Unlike r/selfhosted, where memes dominate the top tier, r/opensource has essentially zero viral humor. The top 25 contains exactly one joke post ("Most useless thing I've ever done: install-nothing" — 739) and one image ("An honest explanation" — 1,952, from 2019). Nothing else. There is no "wife-approved" shitposting, no docker-compose memes, no in-joke culture. The tone is earnest, ideological, and news-oriented.

Technical level is intermediate. Readers understand licenses (GPL, AGPL, MIT, Apache, BSD), know the difference between "open source" and "source-available," can compile from source but mostly consume packages, and hold strong opinions about FSF vs. OSI definitions. They are not kernel hackers; they are FOSS-aligned developers, sysadmins, privacy advocates, and Linux users who care about the ecosystem politically as much as technically.

Core cultural values, ranked:

1. License purity and enforcement. License violations (stripping attribution, re-closing open code, GPL violations) are the community's most reliable engagement driver. "Open sourced my project less than 2 weeks ago. Today I found a fork where the user stripped my license" (1,580), "Someone forked my open source project, removed the license... illegal F1 streams" (1,520), "Someone from the Indian government took my code" (641), "Apple has released the Lisa OS source code under a ridiculous fauxpen source license" (519). Fauxpen source is a slur.
2. Anti-corporate enclosure. Stories of corporations closing formerly open projects, DMCA-ing FOSS tools, or using the courts to threaten solo devs dominate the all-time leaderboard. "Large US company came after me for releasing a free open source self-hostable alternative!" (2,259) and its resolution update (1,543) are the #1 and #5 posts. Open WebUI going closed (691), MinIO (281), Bear going source-available (180), VeraCrypt MS account termination (539), and the curl/AI-slop saga (1,005) are canonical.
3. Data sovereignty & privacy. GrapheneOS, Signal, LibreOffice, OpenStreetMap, Mozilla, Tuta — these are praised; their proprietary counterparts are treated with suspicion. "GrapheneOS is being threatened by the French government" (1,314) became a community cause.
4. Anti-AI-slop / skepticism of vibe coding. Rule 3 explicitly declares: "All AI-generated content is low-effort and ban worthy." The community is deeply worried about AI-generated PRs overwhelming maintainers. "Open source is being DDoSed by AI slop" (1,084), "Drowning in AI slop, cURL ends bug bounties" (1,005), "Help! how do I deal with vibe coders that try to contribute?" (329), "How Vibe Coding Is Killing Open Source" (403), "Why build anything anymore?" (179). Disclosing AI use in a launch post is a coin flip — it can defuse criticism or trigger it.
5. Government/institutional adoption of FOSS. European stories (EU OS, Germany ODF, ICC ditching MS Office, Netherlands) and "public money, public code" consistently score 300-1,300. The EU is the spiritual hero of the sub.
6. Maintainer burnout and sustainability. "Sudo maintainer looking for support" (682), "core.js single developer" (553), "A single developer has been maintaining..." threads reliably score in the 400-700 range. The community is acutely aware that FOSS runs on unpaid labor.

Enforcement mechanisms:

• Rule 2 (No Spam / Excessive self-promotion) is the single most important rule. Reddit's <10% self-promotion guideline is cited directly. The sub pre-empts link-farm accounts by removing drive-by promoters.
• Rule 3 (No Memes/Low-Effort, AI-generated = ban-worthy): Explicitly makes AI-generated content bannable. This is uncommon on Reddit and a significant differentiator.
• Rule 4 (Be On-Topic): "Code or repositories linked to MUST have a LICENSE file that MUST be an OSI listed Open Source license." Linking a project without an OSI-approved license is removal grounds.
• Rule 5 (No Sensationalized Titles): For link posts, the title must match or closely follow the source article. This kills clickbait rewriting.
• Rule 6 (No Drive-By Posting / Karma Farming): Accounts with no engagement history on the sub are removed.
• Rule 8 (Use Correct Flairs): Flairs are: Promotional (project sharing), Alternatives (asking for OSS that fills a need), Discussion (general), Community (news/events). Using the wrong flair is removal grounds and actively enforced.
• Community self-policing: Commenters call out source-available masquerading as open source, non-OSI licenses ("fauxpen source"), AI-generated posts (tells: em-dashes, "I hope this post is ok", overly polished formatting), and projects without a LICENSE file at root.

How this sub differs from similar subs: On r/selfhosted, you launch a deployable app; on r/sideproject, you celebrate shipping; on r/programming, you discuss languages and paradigms; on r/macapps, you run a Problem-Comparison-Pricing pitch. On r/opensource, you do not really launch anything — you report news, share a drama, discuss a license, or ask for an alternative. The community is built around vigilance, not discovery. A raw product launch competes with anti-corporate news stories and almost always loses.

3. The All-Time Leaderboard

Median of full dataset: ~99. Top-25 threshold: ~691. Only one post breaks 2,000.

Ironic flair observations: Post #6 ("Someone forked my project...") is tagged Promotional but is actually a complaint/story; same with #14 (Puter drama) and #15 (Puter milestone). Drama posts about FOSS projects get filed as Promotional because that's the closest flair to "I built this, here's a story about it." The Promotional flair is therefore a mixed bag: launches, complaints about stolen projects, milestone announcements, and license drama.

4. Content Type Dominance at Scale

Most surprising finding: Promotional has the LARGEST count in the full dataset (~75 posts) but the LOWEST average score (~150). It is also the flair where the long tail of <20-score launches lives. By contrast, Community (only ~30 posts) has the HIGHEST average score (~480) because it is the flair that drama/milestone/news stories cluster into. If you want score, you file as Community. If you must file Promotional, expect to be median.

Empty flair (~85 posts) is dominated by old posts (pre-flair-system) and news link posts that moderators didn't force-flair. The fact that empty-flair posts average ~350 is a reflection of the all-time canon being largely pre-flair.

5. Content Archetypes That Work

Archetype 1: "I Got Screwed By A Corporation (But Then...)" — Drama narrative

Score range: 1,156 to 2,259 (the #1 and #5 slots belong to this archetype) Examples:

• "Large US company came after me for releasing a free open source self-hostable alternative!" (2,259)
• "Update: Large US company came after me... Resolved in our favor" (1,543)
• "Open sourced my project less than 2 weeks ago. Today I found a fork where the user stripped my license" (1,580)
• "Someone forked my open source project, removed the license... illegal F1 streams" (1,520)
• "A company approached my open-source project pretending to want to help... stole the idea" (1,156)
• "Someone from the Indian government took my code" (641)

The pattern: Solo FOSS dev is wronged by a bigger entity (corporation, government, pirate forker). Post is a long TEXT post with the story, TL;DR at top, specific details, calls for community help, or a resolution. The community rallies. Engagement is enormous (180-261 comments). The follow-up "Resolved" post also scores in the top 10.

Why it matters for distribution: This is the single most reliable path to top-25 visibility on this sub, but it cannot be manufactured. What can be controlled: if something bad happens to your project, document it immediately and post it here. The story IS the content, not the product. Mention of your project (with link) is acceptable because the post is ostensibly about the drama. This is the only archetype where linking your repo is welcomed.

Archetype 2: "Corporate Betrayal / Enclosure News"

Score range: 507 to 2,131 Examples:

• "LibreOffice downloads on the rise as users look to avoid subscription costs" (2,131)
• "Google will develop Android OS entirely behind closed doors starting next week" (1,215)
• "Open WebUI is no longer open source" (691)
• "Microsoft terminates account of VeraCrypt developer" (539)
• "Microsoft locks Libreoffice developer out of account" (507)
• "Bear is now source-available" (180)

The pattern: LINK post to a news article about a formerly-open project going closed, or a corporate action that hurts FOSS. Title matches the article title (Rule 5). Very low comments-to-score ratio — the community upvotes to signal outrage and moves on.

Why it matters for distribution: Not relevant to launches, but important for understanding the community mood. If your launch can be framed as a reaction to a specific corporate enclosure story, that story becomes your distribution vehicle ("Since Open WebUI is no longer open source, I forked the last open commit and am maintaining it as...").

Archetype 3: "The FOSS Gem Celebration" — news that something open won

Score range: 331 to 2,131 Examples:

• "LibreOffice downloads on the rise" (2,131)
• "EU OS: A European Proposal for a Public Sector Linux Desktop" (1,279)
• "Linux runs on 500 of the top 500 supercomputers" (993)
• "'Flow' wins best animated feature film Oscar. Rendered entirely in Blender" (765)
• "FFmpeg got $100k donation from Zerodha's Foss fund" (781)
• "International Criminal Court to ditch Microsoft Office" (601)
• "EA released the full source code for several antique Command & Conquer games under GPL" (458)
• "OBS became so popular Steinberg dual-licensed ASIO under GPLv3" (332)
• "The Windows Subsystem for Linux is now open source" (315)

The pattern: News that a FOSS project has crossed a threshold, won an award, gotten funding, or been adopted by a prominent institution. LINK post. Very high ratio (0.98-1.00). Comments are low because everyone just upvotes to signal joy.

Why it matters for distribution: If your project hits a milestone (1M users, EU adoption, major corporate sponsorship, award), report it here. Frame the TITLE as the milestone, not as your product.

Archetype 4: "Ask the Community" — Discussion/Alternatives recommendation threads

Score range: 188 to 1,134 (and generate the highest comment counts) Examples:

• "What's an open-source tool you discovered and now can't live without?" (1,107, 468 comments) — repeated as 1,016/410 comments
• "Killed by open sourced software. Companies that have had a significant market share stolen" (1,035, 677 comments — highest in dataset)
• "What open source solution doesn't exist for you?" (260, 470 comments)
• "Which open sourced projects will blow up in 2024?" (714, 223 comments)
• "OpenStreetMaps is a godsend" (1,134, 67 comments)
• "What's the most underrated open-source program every student should know about?" (348, 184 comments)
• "Which open source password manager is the best in 2026?" (188, 122 comments)

The pattern: An open-ended question that invites long comment threads where users mention their favorite tools. These threads become product discovery engines for the whole community. The OP scores moderately; the comments are where the action is.

Why it matters for distribution: This is the single highest-value stealth distribution channel in r/opensource. When one of these threads appears, you can comment "I'm biased because I'm the maintainer, but [project] solves this for me because..." and get dozens of upvotes and stars. The community does not punish self-promotion in this context because you're answering a question, not shouting a launch. Set up alerts for "open source alternative to", "FOSS tool for", "what open source" in the sub.

Archetype 5: "Maintainer Burnout / Sustainability Concerns"

Score range: 329 to 1,084 Examples:

• "Open source is being DDoSed by AI slop and GitHub is making it worse" (1,084)
• "Drowning in AI slop, cURL ends bug bounties" (1,005)
• "Sudo maintainer, handling utility for more than 30 years, is looking for support" (682)
• "A single developer has been maintaining core.js with little recognition or support" (553)
• "Help! how do I deal with vibe coders that try to contribute?" (329)
• "Inkscape project struggling with lack of active contributors" (287)

The pattern: A story about unpaid FOSS maintainers suffering under the weight of community demands, AI-generated PRs, or legal threats. Often a LINK to an external article; sometimes a first-person TEXT post from a maintainer.

Why it matters for distribution: If you're a maintainer struggling with contributions, AI slop, or burnout, a first-person post here will get 300-1,000 upvotes. This is a way to build reputation as a "real" maintainer (non-vibe-coded) before ever posting a launch.

Archetype 6: "Launch Post That Actually Worked"

Score range: 165 to 1,437 (the vast majority of launches die at 5–50) Examples:

• "I made a better when2meet" (1,437) — solves a clear problem people know and hate
• "My Open-Source 'Internet OS' Just Hit 2,000,000 user!" (1,148) — milestone framing, not launch framing, from a repeat trusted author (mitousa)
• "Thank you! Open-sourcing my project was one of the best decisions of my entire life" (468) — same author; gratitude + milestone
• "Most useless thing I've ever done: install-nothing" (739) — humor + absurd premise
• "I built LastSignal — a self-hosted, end-to-end encrypted dead man's switch" (567) — privacy-forward, technical specifics, AGPL
• "I built RapidRAW, a lightweight, GPU-accelerated Lightroom alternative in Rust + Tauri" (288) — clear proprietary alternative, Rust, young author narrative
• "I just opensourced Peersuite, a decentralized alternative to slack/discord" (393) — clear alternative framing
• "SQL Noir – An open-source detective game to learn SQL" (516) — unique, playful, clear value
• "Relaticle - Open-source CRM alternative to HubSpot/Salesforce" (307) — explicit proprietary alternative framing

The pattern: Launches that work here share FIVE properties:

1. Explicit proprietary-alternative framing in title ("alternative to HubSpot", "better when2meet", "Lightroom alternative")
2. Clear privacy/offline/self-hosting value (LastSignal, Peersuite, RapidRAW)
3. AGPL or GPL license (not MIT, not source-available)
4. Author humility in title or opening line ("kinda scared of posting this", "as a lazy ass procrastinator", "most useless thing I've ever done")
5. Technical specificity in body (stack, architecture, dependencies, license)

Why it matters for distribution: If you are going to launch here, design the launch around these five properties before posting. A "Promotional" launch without at least three of these will be median-or-worse. With all five, you can reach 300-500.

6. Format Analysis

r/opensource is a TEXT and LINK community. Images and videos are almost completely absent from the top tier. The only top-25 image is a 2019 legacy meme ("An honest explanation" — 1,952) and a 2019 news photo of Stallman at Microsoft (1,465). The only top-25 video is "Citadel - an open source project management tool" (691) — and that is from 2020. In the 2025–2026 data, zero new visual posts cracked the top 50. This is radically different from r/selfhosted, r/macapps, r/sideproject, and every other dev-adjacent sub.

What Format to Use For What

• Tool/app launches → TEXT post with repo link embedded. Not LINK-to-GitHub. Not screenshot. Not demo video. A long, well-structured markdown post with Problem, Stack, License, Why FOSS, Links.
• News / corporate drama / FOSS milestones → LINK post to an original news source. Title must match the article (Rule 5). Do NOT rewrite the headline.
• Maintainer complaints / first-person drama → TEXT post. Long-form. TL;DR at top.
• Community Q&A (what tools do you use?) → TEXT post with an open-ended question. Explicitly invite comments.
• Humor/memes → Do not. This is not the sub. On average they're removed per Rule 3. The rare exceptions are 5+ years old.

Why visual content fails here

r/opensource is ideological, not visual. Users are not shopping for a pretty app; they are auditing whether a project is ideologically correct (OSI license? AGPL? non-AI? non-corporate?). A screenshot cannot convey any of that. A TEXT post can. The top-performing launches all invest in the body text: license, stack, problem framing, privacy/offline claims, and self-deprecating humility.

If you still want to use visual content: LINK post to an external blog or release page that contains the visuals (the launch is framed as a news link about your release, not as a self-post). "Krita 6 released" (7) and "OBS 32.1.0 Releases with WebRTC Simulcast" (69) use this pattern. It doesn't score well but it's allowed.

7. Flair/Category Strategy

Raw performance ranking (avg score per post):

1. Community (~480 avg) — drama updates, milestone news, FOSS political events
2. (None/empty) (~350 avg) — legacy posts and LINK news
3. Discussion (~290 avg) — open-ended questions, philosophical threads, first-person complaints
4. Alternatives (~220 avg) — asking for OSS that fills a need; rarely hits top 25
5. Promotional (~150 avg) — project launches; heavy long tail of <20

Distribution utility ranking (best for actual product promotion):

1. Discussion (best) — You can post "Help! how do I deal with vibe coders that try to contribute?" (329) and get a trusted-maintainer reputation that carries into later Promotional posts. Or post "How do I handle a trademark notice?" (165) and get sympathy engagement. Or post a first-person "I got sued" story that mentions your repo. High engagement, low defensiveness.
2. Community — Reserved for news/drama/events. Only use if your post is genuinely community news (milestone, award, adoption).
3. Promotional — Use if you must, but understand the ceiling is ~500 and the floor is single digits. Follow the Archetype 6 pattern.
4. Alternatives — Useful if you're comment-farming (answer "alternative to X" posts as a reply), not if you're original-posting.

Title-prefix tags

Unlike r/macapps, r/opensource does not have bracketed title-prefix tag conventions. The title is mostly flat. However, the following informal conventions appear in the data:

• "Open source X" or "open-source X" prefix (40%+ of launch titles) — mandatory framing.
• "FOSS X" (more niche, signals FSF alignment).
• "alternative to [proprietary name]" — extremely common and very effective.
• "[Project name] - description" — Project Hunt-style format. Underperforms "I built X" format.

Pricing model hierarchy (community-friendliness, ranked)

1. AGPL-3.0 with no commercial component — the gold standard. "I chose AGPL specifically to prevent enclosure" is a positive signal. Puter, Relaticle, Senlo, LastSignal all chose AGPL and it was mentioned in comments approvingly.
2. GPL-3.0 / GPL-2.0 / LGPL — trusted, old-school FSF-aligned.
3. MIT / BSD / Apache 2.0 — accepted but often followed by "why not GPL? You'll get ripped off" comments. The Indian government / Microsoft / fork-that-stripped-attribution stories all feature MIT-licensed projects.
4. Dual license (open core + commercial) — tolerated if the open tier is actually usable. Gravitee vs Kong comparison post (8, but well-received) shows the community values "how much the free tier gives you" as the ranking metric.
5. Optional paid cloud hosting on top of open self-host — tolerated. Must have a self-host docker image.
6. Self-hosted free + paid SaaS tier for "advanced" — suspicious. "Why is everything a SaaS nowadays?" (246) is a warning shot.
7. Source-available (BSL, SSPL, "functional source", non-commercial clauses) — HOSTILE. "Apple has released the Lisa OS source code under a ridiculous fauxpen source license" (519), "Bear is now source-available" (180), "Open WebUI is no longer open source" (691). Posting a source-available project here and calling it "open source" is the fastest way to be downvoted and publicly corrected.
8. Non-OSI licenses / "Commons Clause" / "source available but no commercial use" — will be removed per Rule 4.

8. Title Engineering

Deconstructing the top 10 titles

1. "Large US company came after me for releasing a free open source self-hostable alternative!" — Technique: victim framing + specific stakes + "self-hostable" keyword. The exclamation mark signals urgency.
2. "LibreOffice downloads on the rise as users look to avoid subscription costs" — Technique: news-headline format (Rule 5 compliant) + anti-subscription framing.
3. "An honest explanation." — Technique: curiosity gap. (2019 legacy; would not work today.)
4. "Open sourced my project less than 2 weeks ago. Today I found a fork where the user stripped my license and attribution to claim it as theirs." — Technique: specific timeline + betrayal narrative + no project name in title.
5. "Update: Large US company came after me... Resolved in our favor" — Technique: "Update" prefix reuses the reputation of the original post.
6. "Someone forked my open source project, removed the license... and then used it to host illegal F1 streams 🤦" — Technique: escalating absurdity + emoji (one of very few title emojis).
7. "Richard Stallman was speaking about free software and privacy at Microsoft HQ" — Technique: ideological contradiction as spectacle.
8. "I made a better when2meet" — Technique: implicit proprietary-alternative framing + humility.
9. "GrapheneOS is being threatened by the French government" — Technique: embattled-FOSS-project framing + state actor as villain.
10. "If it is public money, it should be public code as well" — Technique: slogan as title.

Title formulas that work

• "[Proprietary tool] alternative" formula: "I made a better when2meet", "Relaticle - Open-source CRM alternative to HubSpot/Salesforce", "Europe builds Microsoft-alternative 'Euro-Office'", "I reverse engineered an amazing old MMORPG server, and made it the first public open source project for it"
• "I got wronged" formula: "Large US company came after me...", "Open sourced my project less than 2 weeks ago. Today I found a fork where the user stripped my license", "Someone from the Indian government took my code"
• "Corporate enclosure news" formula: "Open WebUI is no longer open source", "Google will develop Android OS entirely behind closed doors", "Microsoft terminates account of VeraCrypt developer", "How MinIO went from open source darling to cautionary tale"
• "Humble builder" formula: "kinda scared of posting this to reddit lol, but here's an open-source app i built that maybe can help some of you" (408), "Most useless thing I've ever done: install-nothing" (739), "I got tired of hidden fees, ads, tracking, data breaches, so i built two very simple but open source apps" (444)
• "Community Q&A" formula: "What's an open-source tool you discovered and now can't live without?", "What open source solution doesn't exist for you?", "Which open source password manager is the best in 2026?"
• "Maintainer/sustainability concern" formula: "Help! how do I deal with vibe coders that try to contribute?", "Open source is being DDoSed by AI slop", "Inkscape project struggling with lack of active contributors"

Title anti-patterns (community-specific)

• Star counts, GitHub metrics, growth numbers in title — "Apple ranks embarrassingly low and barely makes the top 20 in the Open Source Contributors Index" (425) is the rare exception because it's about Apple's shame, not self-promotion. No solo-dev post in the top 50 mentions their own star count in the title. The community reads these as vanity metrics.
• Title in ALL CAPS or with ALL CAPS words — none in top 50.
• Sensationalized rewrites of article titles — removed per Rule 5.
• "Feedback wanted" / "Beta testers needed" / "Looking for contributors" — Long-tail territory. "Feedback wanted for local-first study app" (0), "Looking for contributors for a flutter package" (0), "Really good open source project to join as an unemployed developer" (7). The community treats "feedback" framing as a sign of incompleteness.
• Vague titles — "Why build anything anymore?" (179) is a borderline case that worked because the body was a specific grievance. But generically vague titles like "Am I Cheating?" (382) only work with first-person stakes and rarely otherwise.
• Emoji-heavy titles — rare and underperform. The one exception (🤦 on #6) is borderline.
• Title: "[X] — open-source [description]" without story framing — Launches with dry-descriptor titles average ~15. "ZLID: an open source alternative to UUID/ULID" (8), "ENIGMAK, an open source custom rotor cipher" (17). These fail because they skip the "why should I care" hook.
• Mentioning AI or "vibe coded" or "AI-assisted" anywhere in the title — double-edged. Can work as a confession narrative (see "Full transparency: This project was made in combination with AI" in body text and ~270 average), but in the title it triggers Rule 3 reflexes.

9. Engagement Patterns

Comments-to-upvote ratio by content type

The pattern is clean:

• News / link posts → very low C/U (0.01–0.06). People upvote and scroll. These are signal posts, not discussion posts.
• First-person drama / launches → moderate C/U (0.15–0.25). People engage but the drama does the work.
• Open-ended Q&A / "what do you use" / "what's missing" → very high C/U (0.40–1.81). These are comment-thread engines.
• License / legal / philosophy discussions → high C/U (0.47–0.72). These are argument magnets.

Visibility vs. Relationship decision rule

• If your goal is VISIBILITY (upvotes, GitHub stars, traffic spikes): Use a Corporate Enclosure News LINK post (Archetype 2) or a Drama Narrative TEXT post (Archetype 1). Aim for a 1-3-day window while the story is hot. Score ceiling: 500–2,200.
• If your goal is RELATIONSHIPS and discussion (long tail, installs, contributors): Use a Community Q&A TEXT post or comment heavily on existing Q&A threads. You'll get less raw visibility but the people who find you via comments are hand-picked by their own question. These are your best customers and contributors.

Highest-discussion topics (regardless of score)

1. "What open source tool do you use?" variants — consistently drive 200-677 comments. The highest-discussion topic on the sub.
2. License arguments — "It's time for GPL4", "Why isn't there a viral license", "I'm open-sourcing stuff. Everybody can use it for free but I don't want big companies to use it", "What happens if you violate the terms of an open source license?" all generate 85-140 comments.
3. "Should I open-source?" existential questions — "Open source in today's world is mind boggling" (171), "Why is open source software so good?" (172), "Github in decline?" (232).
4. Vibe coding / AI slop debates — "How do I deal with vibe coders that try to contribute?" (122), "Google's certified developer sideloading policy is more than a security measure" (113), "Any developer work I can do against ICE" (122).
5. "Open source printers / smartphones / internet" blue-sky threads — "We should create an open source 2D printer" (176), "How long are we from Open source smartphones?" (86), "Open source Internet" (65), "What's stopping open-source printers..." (61).

10. What Gets Downvoted

Posts with ratio below 0.85 (friction zone)

Ratio tier interpretation

• Above 0.94: Universally well-received. Most news/drama/launches that actually worked sit here. This is "the community did not fight you."
• 0.85–0.94: Net positive but with friction. Reasons include: politically charged title (ICE), unfamiliar/controversial figure (PewDiePie), sweeping pessimistic claim ("decentralized OS death"), heavy license debate, or a product positioned slightly off the community's expectations (Common Ground — community felt the crypto integration was off-topic).
• Below 0.85: Controversial or community-hostile. Almost all sit either in overtly political territory (ICE, Trump) or in promotional long-tail with AI-generated markers.

Named anti-patterns (community-specific)

1. "AI-assisted but still legit" defense posture — Posts that mention AI-assistance in the body with phrases like "I'm in IT but not in development" or "this was my first ever project where I let AI handle a lot of the initial code" (FluentTaskScheduler — 5, ratio 0.63). The community reads these as admissions of vibe-coding and downvotes aggressively. Rule 3 ("All AI-generated content is low-effort and ban worthy") gives them cover.
2. Fauxpen source mislabeling — Calling a non-OSI license or source-available project "open source" in the title. Mods remove per Rule 4. Before removal, comments aggressively correct: "that's not open source, that's source-available."
3. Political bait disguised as tech question — "Any developer work I can do against ICE" (630, ratio 0.81) is net positive but friction-heavy. The community dislikes being drawn into partisan US politics.
4. Drive-by project announcements — Accounts with no history on the sub dropping a link. Removed per Rule 6. Visible in the long tail of week posts scoring 0-3.
5. Feedback-wanted / beta-tester requests — "Feedback wanted for local-first study app" (0), "How do I do open source projects correctly?" (19, ratio 0.75). The community reads "feedback" as "come look at my unfinished thing."
6. Scope overclaiming in title — "the most powerful data table on the market" (49, ratio 0.80), "Building Harvey-style tabular review from scratch, but better" (9, ratio 0.80). Grandiose claims are punished.
7. Title rewriting of news articles — Violates Rule 5. Usually removed before they can be downvoted, but when they slip through they sit at low scores.
8. Multiple launches of the same project by the same account in a short time window — "Chronex - an open source platform" posted twice (once 7, once 2 with 0.56 ratio). Reposting is punished.

Public astroturfing / watchdog behavior

Unlike r/selfhosted (which has published blacklists and the Huntarr exposé) and r/macapps (which has a visible blacklist culture), r/opensource does not have a named blacklist. But it DOES have:

• The curl/cURL community as a folk hero whose grievances (AI slop, Fortune 500 bad-faith questions) become canonical.
• Named corporate villains: Microsoft (VeraCrypt, LibreOffice developer, Open WebUI pipeline), Google (Android sideloading), Apple (Lisa OS fauxpen), MinIO, Airdata UAV, FAKKU, Open WebUI, MongoDB/SSPL, HashiCorp/BSL.
• Star-count manipulation detection: "the Puter competitor is buying stars" (1,156) post led to a Reddit account being suspended. The community actively inspects stargazer histories on GitHub.
• License auditing: Commenters will check if your repo has a LICENSE file and whether it's OSI-approved before upvoting.

11. The Distribution Playbook

Phase 1: Pre-launch (2-6 weeks before your post)

1. Read Rules 1–8 in full. Especially Rule 2 (self-promotion), Rule 3 (AI content), Rule 4 (must have OSI license), Rule 5 (no sensationalized titles), and Rule 8 (correct flairs). Do not skim.
2. Pick an OSI-approved license and add a LICENSE file at your repo root. If you're debating MIT vs. GPL vs. AGPL, choose AGPL-3.0 unless you have a specific reason not to. This community values AGPL highest and will tell you why if you pick MIT.
3. Build comment karma on this sub before posting a launch. The lowest-friction way: answer every "What's an open-source tool you discovered" or "alternative to X" thread that comes up. Be helpful. Mention your project only if it genuinely answers the question, and always disclose "I'm the maintainer of X." Aim for at least 5 substantive comments before your first launch post.
4. Write a first-person Discussion post before a Promotional post. "Help! how do I handle [specific maintainer problem]" establishes you as a real maintainer, not a vibe-coder. "Trademark notice for my 1.5 year old OSS project - superfile" (165) is an example of how a solo dev got community sympathy and brand awareness without a Promotional flair.
5. Strip every sign of AI generation from your README and post drafts. No em-dashes in prose. No "Delve into", "tapestry", "In today's fast-paced world". No emojis in headings. No "absolutely!" openings. No bullet points where every item starts with the same bold phrase. The community reads these as tells.
6. Check your stargazer history on GitHub. If you have any suspicious star spikes or obviously-bot stargazers, clean it up. Commenters check.

Phase 2: Launch day

1. Pick your archetype. Almost certainly Archetype 6 (Launch That Actually Worked). Your title should follow the humble-builder or proprietary-alternative formula. Before publishing, ask yourself if your title hits three of these five: (a) explicit alternative framing, (b) privacy/offline value, (c) AGPL/GPL mention, (d) author humility, (e) specific technical claim.
2. Use the Promotional flair. Any other flair for a project launch will trigger the mod queue.
3. Structure the body in this order:
   • One-line value prop (problem → solution)
   • TL;DR + TL stack
   • "Why I built this" personal story (2-4 paragraphs, first person, conversational)
   • Key features (bulleted, short, no jargon)
   • Tech stack (language, framework, notable dependencies)
   • License statement with rationale (e.g., "AGPL-3.0 to ensure any fork has to share back")
   • Self-host instructions (docker-compose preferred)
   • Links: GitHub, docs, demo (in that order)
   • Explicit invitation for contributions and feedback
4. No screenshots or video in the post body unless the app is inherently visual (photo editor, game, UI tool). Even then, host them externally and link, don't embed.
5. Post in the afternoon UTC window. Top posts skew toward 13:00-18:00 UTC creation. Avoid late US evening.
6. Do NOT mention AI assistance in the title. If you used AI heavily in development, address it honestly in the BODY near the bottom with a one-paragraph disclosure that specifies what AI did (e.g., "I used Claude for frontend scaffolding; the backend architecture, security model, and data layer are hand-written"). Skipping this and getting caught later is far worse than disclosing upfront.

Phase 3: First 24-48 hours

1. Respond to every top-level comment within 2 hours for the first 6 hours. The community rewards maintainer presence.
2. When attacked on license choice (especially "why MIT, you'll get ripped off"), respond with the same answer every time: "Here's my reasoning — [specific tradeoff]. I'm open to reconsidering." Do not get defensive.
3. When asked "is this vibe-coded?" answer directly and specifically. "No — I've been writing [language] for [years]. I used [specific AI tool] for [specific narrow task]. Here's the PR history showing me iterating on architecture decisions: [link]."
4. When asked "what's the business model?" the safe answer is: "It's AGPL. There is no paid tier. If I offer paid hosting in the future, the self-host will always remain free and fully featured. I take donations via [GitHub Sponsors / Open Collective]."
5. Upvote every commenter who asks a good-faith question. This is a small community; relationships compound.
6. Do NOT cross-post to other subs within the first 24 hours. Mods and community members can see cross-posts and read them as spam.
7. If your post is downvoted below 0.80 ratio in the first 2 hours, delete and rewrite. Reddit's algorithm will kill it; there is no recovery. Identify what went wrong (title framing, flair, apparent vibe-coding) and try again in 2-3 weeks from the same account.

Phase 4: Ongoing presence (weeks to months after launch)

1. Post a follow-up update at a milestone — "6 months later", "1.0 released", "10k users" — but frame the post as gratitude or lessons learned, not as a second launch. See mitousa's "Thank you! Open-sourcing my project was one of the best decisions" (468) pattern.
2. If you get wronged, document it immediately. Drama narratives (Archetype 1) are the top-scoring posts on the sub. If a company steals your code, DMCAs you, sends a cease-and-desist, or files a trademark notice, write the post the same day and include specifics, screenshots, timeline. Link your repo naturally. This is the one path to a 1,500+ post.
3. Subscribe to "What open source tool do you use?" alerts. Comment on every one with a genuinely helpful answer that mentions your project only if it fits. Over time, you'll generate more stars from comments than from your launch post.
4. Maintain a regular news-commentary presence. Reply to corporate-enclosure stories with informed takes. This builds reputation.
5. Answer license questions. The sub has frequent "which license should I pick" threads. Thoughtful answers build trust.

Community-specific comment reply templates

• "Is this vibe-coded?" → "No. I wrote the architecture, data model, and core logic myself. I used [AI tool] for [specific narrow task, e.g., 'boilerplate React components' or 'unit test scaffolding']. My commit history shows [link to commits]. Happy to walk through any specific file you want to audit."
• "Why not GPL?" → "Good question. I chose [license] because [specific reason tied to how you want derivative work handled]. I've been rethinking whether AGPL would be better for [specific concern]. If you have a strong argument for switching, I'm genuinely listening."
• "What's the business model?" → "AGPL-3.0. There is no paid tier today. If I add one, the self-host will remain fully featured. I take donations at [link]."
• "Why not just use [existing tool]?" → "[Existing tool] is great; I use it myself for [use case]. This project exists because [specific gap: performance, privacy model, UX, missing feature]. If [existing tool] adds [feature X], I'd honestly recommend people use it instead."
• "Does this have [feature]?" → "Not yet. It's in the roadmap at [link]. If you want to help implement it, I've marked it as a good-first-issue."

Stealth distribution tactics

1. Comment farming on Q&A threads — by far the highest-ROI activity on this sub. Requires ZERO launch-post risk.
2. License question replies — build reputation as a trusted licensing authority, then launch 3 months later.
3. Cross-post to r/selfhosted only if you truly are self-hostable, and only after your r/opensource post has settled. Different mod rules; different archetypes.
4. Submit your project to alternativeto.net. The post "Alternatives to... alternativeto.net?" (171) reports persistent traffic spikes months after being reviewed there. r/opensource readers find you via alternativeto.net more than they find you via direct browsing.
5. Write a long blog post about a specific FOSS-political topic (license analysis, maintainer sustainability, corporate enclosure story) and submit it as a LINK post. Title-matches the article (Rule 5). This is technically a news post, not a promotional post, and bypasses the Promotional flair ceiling.

Score-tier calibration

• Tool launches on r/opensource rarely exceed 500. A realistic expectation for a well-executed first launch is 100-300 upvotes and 20-50 comments. Only five launches in the all-time top 25 exceeded 700 (Timeful at 1,437, Puter at 1,148, install-nothing at 739, and two drama-wrapped launches).
• Drama narratives can hit 1,500-2,200, which is the effective ceiling of the entire sub.
• Corporate enclosure news links can hit 1,000-2,000 if posted within the first 12 hours of the story breaking.
• Community Q&A posts top out around 1,100 but generate the most comments (400-700).
• If you need 3,000+ visibility for a launch, this is not your sub. Try r/selfhosted (ceiling ~9,500), r/programming, or r/LocalLLaMA.

Post-publication measurement

• First 30 minutes: If ratio drops below 0.85, the post is failing. Check the top comment — if it's a license concern, AI accusation, or "why not just use X", consider editing the body to address it proactively.
• First 2 hours: A score of 20+ with ratio >0.90 means it's on the right trajectory. Score of <5 means dead on arrival.
• First 12 hours: Most of your final score is accumulated here. If you're at 100+ upvotes by hour 12, you'll likely finish in the 200-500 range.
• 24 hours: Anything over 300 is a real success. Anything over 800 is a hit. Over 1,500 is an all-time canon candidate.
• Ratio signals: >0.94 is a win regardless of score; 0.85-0.94 means friction that needs addressing in comments; <0.85 means delete or leave as lesson.
• No traction in first 4 hours? Do not repost the same content. Write a Discussion post first to build credibility, then re-launch in 2-3 weeks.

12. Applying This to Any Project

Pre-post checklist

1. Your repo has a LICENSE file with an OSI-approved license at the root
2. Your license is AGPL-3.0, GPL-3.0, or a good-faith permissive license (not BSL, SSPL, or Commons Clause)
3. Your README has a "Why open source?" section explaining your rationale
4. You have a docker-compose.yml or one-liner install
5. Your title follows the "alternative to X" or "I built X" humble-builder formula
6. Your flair is Promotional (not Discussion, not Community)
7. You have commented on at least 5 other posts in this sub in the past month
8. You have addressed any possible AI-generation concerns in the body
9. You have NO mention of star counts, user counts, or growth metrics in the title
10. You are posting between 13:00-18:00 UTC
11. You can respond to comments for the first 6 hours after posting
12. Your stargazer history looks organic (no bot spikes)

Scenario-based launch guides

Scenario A: Your product is free and AGPL/GPL

Optimal formula: Title = "I built [proprietary-tool] alternative: [name]" or "[name] — a [license] [category] that runs [offline/self-hosted/locally]". Body leads with Problem → Solution → License rationale → Stack → Links. Emphasize privacy, offline-first, and no-telemetry claims. Explicitly state your business model is "donations only" or "AGPL with no paid tier." Key risk: License concerns. Be ready to defend your choice of AGPL vs GPL vs Apache. Realistic ceiling: 500-800 upvotes

Scenario B: Your product is open-source + paid cloud hosting

Optimal formula: Title mentions the open-source nature and the alternative framing. Body must clearly disclose: "There's a paid hosted version at [link] but the self-hosted version has [every feature / exactly these features]. Hosted revenue funds development of the open core." Key risk: "This is just freemium in disguise." Be ready to show a docker-compose that actually works and list every feature that is free vs. paid. Realistic ceiling: 200-400 upvotes

Scenario C: Your product uses subscription pricing with a source-available core

DO NOT POST HERE. This is a Rule 4 violation if your license is not OSI-approved. Even if technically approved, the community will mislabel you as "fauxpen source." Score ceiling is near zero and the post will likely be removed. Try r/SaaS, r/sideproject, or r/entrepreneur instead. Key risk: Existential. You don't belong here.

Scenario D: Your product was built with AI assistance

Optimal formula: Post a Discussion flair post FIRST about a specific technical problem you're solving, establishing yourself as a real maintainer. 2-4 weeks later, post a Promotional launch with honest upfront AI disclosure: "Full transparency: I used [tool] for [narrow task]. I wrote [X, Y, Z] myself. Here's my commit history showing iteration on architecture: [link]." Key risk: Downvote spiral from Rule 3 reflex. Hide any em-dashes, AI-flavored phrasings, and generic polished README structure. Disclosure in the body is tolerated; disclosure in the title is suicide. Realistic ceiling: 100-300 if disclosed well, near zero if detected post-launch

Scenario E: Your project was wronged (license stolen, cease-and-desist, fork, corporate copy)

Optimal formula: Follow Archetype 1. Title: "[Specific wrong] happened to my [FOSS category] project". Body: TL;DR at top, timeline with specifics, screenshots/receipts, a call to action (legal help, community support, awareness). Link your repo naturally once, near the bottom. Post within 24-48 hours of the wrong occurring. Key risk: None — this is the highest-reward archetype. Biggest trap is making it look exaggerated or manufactured. Realistic ceiling: 1,500-2,259 upvotes (the all-time #1 slot)

Cross-posting guidance

The same product repositioned for different subs:

• On r/opensource, frame as: "I built [proprietary-tool] alternative under AGPL because [enclosure story]."
• On r/selfhosted, frame as: "I built [self-hostable tool]. Here's the docker-compose. Not vibe-coded, repo is older than 3 months." (Mind Rule 6 and Vibe Code Friday.)
• On r/sideproject, frame as: "I built this on weekends over 6 months. Lessons learned:"
• On r/programming, frame as: "[Technical deep dive on how I solved X in this project]"
• On r/LocalLLaMA, frame as: "[Only if your project runs local models] I built this to make [workflow] work fully offline."
• On r/SaaS, frame as: "I bootstrapped [project]. Open core + paid hosting. Here's my pricing funnel."

The r/opensource framing is the most ideologically specific: the product needs to be positioned as an anti-enclosure act, not as a new product. If you cannot position it that way, pick a different sub.

Quick reference: what to do if you have 60 seconds to decide

• News/drama on a FOSS project you love? LINK post, title matches article, no flair needed.
• Something bad happened to your project? TEXT post, Discussion or Community flair, tell the story.
• Launching a product? TEXT post, Promotional flair, follow Archetype 6 checklist. Expect 100-300 upvotes.
• Need users urgently? Comment on the next "what open source tool do you use" thread, not a launch post.
• Asking for alternatives? TEXT post, Alternatives flair, specific requirements.
• Anything AI-assisted? Disclose in body, not title. Build Discussion credibility first.
• Meme, screenshot, gif? Wrong sub.