Reddit Community Analysis: r/algotrading

1. Data Sources & Methodology

• 313 unique posts after deduplication across 4 time periods (all-time, year, month, week), 4 pages each (15 raw JSON files — top_week had only 3 pages)
• Date collected: April 10, 2026
• Subreddit subscribers: 1,849,657
• Score range: 0 to 2,969
• Median score: ~60 (heavy long tail — most posts in the dataset are recent month/week posts with double-digit scores)
• Top 10 threshold: ~1,096
• Top 25 threshold: ~722
• Top 50 threshold: ~491
• Top 100 threshold: ~174

This is a content strategy guide for understanding what resonates on r/algotrading, not a sociological study. The dataset skews toward top-sorted content, so routine daily discussion threads and the (removed) "how do I get started" questions that the mods delete are underrepresented. Only one post in the dataset scored above 2,500, and only seven scored above 1,200 — the long tail is steeper here than on comparable finance subs.

Cross-subreddit calibration: r/algotrading peaks at ~2,969 vs r/Daytrading's ~9,563, r/Forex's ~2,136, r/stocks' ~102,431, r/investing's ~15,106, r/ChatGPT's ~84,058, r/macapps's ~2,029, and r/learnmachinelearning's ~7,000+. With 1.85M subscribers, r/algotrading has roughly 3.5x the subscriber count of r/Forex but generates nearly identical peak scores. Engagement per subscriber is very low — this is a niche technical community where the vast majority lurk, and where the content bar is high enough that viral outbursts are rare. A score of 200 is a genuine hit; 500+ is strong; 1,000+ is canonical. Unlike r/Daytrading (which rewards emotional P&L porn) or r/Forex (which rewards memes), r/algotrading rewards demonstrated engineering competence, brutal self-awareness, and open-source contribution.

2. Subreddit Character

r/algotrading is an engineering-first self-help group for people who want to believe retail quant trading is possible, policed by moderators who treat the subreddit like a hostile environment under constant bot and promoter siege. It is not a strategy-sharing community — the sidebar and rules make clear that asking for strategies will get you removed, and the top posts explicitly acknowledge that "successful algo traders don't exist" publicly because any real edge is never shared. The emotional engine is the tension between the community's shared fantasy (making money with code) and the data-literate acknowledgment that almost nobody in the retail space actually does.

Product launches and self-promotion are explicitly hostile territory. Rule 1 ("No Promotional Activity") is a zero-tolerance policy: no blog/YouTube/affiliate links, no "PM me for details," no low-quality promo. Rule 2 ("High Quality Questions Only") removes beginner posts. Rule 3 ("Do Not Ask for Strategies") removes shortcut-seekers. Rule 5 ("No Gain/Loss Porn") requires any P&L post to include a thorough write-up. Rule 6 asks users to report bot accounts. The community self-polices aggressively: the #11 all-time post (890 score) is literally titled "PM me for code" posts should be banned. Put up the code to everyone or STFU. These are all scams. This is a community that has been burned repeatedly by crypto shills, course sellers, and low-effort AI slop, and it has developed antibodies accordingly.

Core cultural values, ranked by intensity:

1. Anti-promotion / anti-affiliate / anti-course — The most ferocious antibody. Two moderator ANNOUNCEMENT posts in the top 25 (NEW RULE: Anyone found pumping stocks..., 2,862; r/algotrading is currently being swarmed by stock pumping bots, 808) reveal an environment under constant manipulation attempts. "Rocket emojis are not DD" is the mod voice. Any whiff of a Discord, Telegram, YouTube channel, or paid indicator triggers immediate hostility and often bans.
2. Open-source-or-GTFO — Tools that succeed here are open-source with GitHub links in the body. Top tool launches all cite repos: tda-api (601), Blankly Python framework (640), Gamestonk Terminal (888), Tickerrain (922), pmxt orderbook dumps (732), D-Tale visualizer (641), stonkr R package (494), IB Gateway in Rust (216). Sidebar rule: "Submit software that is proprietary and not open source" is explicitly a "Don't."
3. Brutal self-awareness about failure — "Truth about successful algo traders. They don't exist" (905), "I'm Leaving Algo Trading. Thank You" (831), "My reality of trading and how i wish i had never started" (823), "Why I gave up algo trading" (446), "Why I'm over my algo-trading journey - 11 months" (145), "I ADMIT IT. I OVERFIT. I HAVE SELECTION BIAS." (524). Capitulation posts reliably outperform success posts. The community rewards people who admit they failed.
4. Anti-AI-slop / anti-LLM — A major 2025-2026 shift. "LLMs are not the right tool for algo trading" (138), "They nearly all burned the money they gave to the LLMs" (185), "All LLMs are losing money in a trading competition" (257), "Dead Internet Theory in r/algotrading" (593), "They just stuffed the models with raw price and indicator data 😭😭" (156). Anyone posting AI-generated or "I asked ChatGPT to build me a bot" content gets mocked. The exception: Meta Labeling (618) — ML applied correctly, as a filter on an existing edge, not as a strategy generator — is the community's accepted ML path.
5. Methodology rigor — Backtest integrity matters. "This is what happens when you DO NOT include Fees in your backtests" (821), "Look-ahead bias is a hell of a drug!" (134), "Ah, that sweet moment of bliss before you realise you've coded in epic look-ahead bias" (382), "Why your massive gains in backtesting aren't real" (149). Overfitting, look-ahead bias, fees, slippage, and walk-forward validation are the gospel.
6. Python-normative, with Rust and C++ niche — Sidebar and code examples are Python-first. Top posts reference quantstrat (R), but modern Python is the lingua franca. Rust/C++ infra posts (IB Gateway in Rust, 216; Rust pipeline 442 tests, 37) are respected but rare.

Enforcement mechanisms are aggressive and visible. The mods distinguish posts with the ANNOUNCEMENT flair. Two top-25 posts are mod meta announcements. Beginner "how do I start" questions are removed per Rule 2 — the sidebar redirects them to the wiki. Promotional posts are removed per Rule 1. The community's wiki has a "Hall of Fame Threads" section and a "rules_of_engagement" page for presenting projects. One top-performing post (I wrote a Python wrapper around TD Ameritrade's streaming data API, 601) explicitly notes "This post was removed (presumably by mods) without an explanation after it had become the fourth most-upvoted post of all time" — mods will remove even popular content if it trips promo rules.

Humor works, but only as insider meme. "The tax guy at H&R Block when I show up with 40 binders of paperwork..." (#1 all-time, 2,969) is the archetype: a relatable loss framed as a setup/punchline. "My little bot has really mastered the 'Buy High, Sell Low' strategy" (1,020), "Funny Story About my Trading Bot" (1,559, where the bug was "doing the opposite"), "Most Sane Algo Trader" (614), "It do be like that" (977). Memes must be clearly in-group — about look-ahead bias, overfitting, blown accounts, or the retail-vs-quant gap. Generic market memes get removed.

Technical level is high. Users discuss Lopez de Prado meta labeling, combinatorial purged cross-validation, volatility regime filters, Sharpe ratios, walk-forward analysis, CAGR, max drawdown, Level II/L2/L3 market data, order book microstructure, delta-one strategies, and the Jane Street/SIG/Optiver/IMC trading culture fluently. Posts with rigorous methodology outperform posts with flashy equity curves.

How this sub differs from similar subs: r/algotrading is far more engineering-oriented than r/daytrading (which is psychology-focused), far less meme-friendly than r/forex, far less consumer-focused than r/stocks, and far more skeptical than r/machinelearning or r/LocalLLaMA when it comes to ML claims. It is the only major finance sub where "I built an open-source thing with GitHub link" is consistently more upvoted than "I made money."

3. The All-Time Leaderboard

Dataset median: ~60 (heavily skewed by recent posts). Top-25 threshold: ~722. Top-25 represents the canonical "best of r/algotrading."

Observations on the leaderboard:

• 9 of top 25 are Other/Meta (memes, jokes, meta-commentary). The #1 spot is a meme.
• 7 of top 25 have no flair at all — older posts from before flairs were standardized.
• Only 5 of top 25 are Strategy flair (and 2 of those are meta-commentary, not actual strategy reveals).
• Only 1 post exceeds 2,500 (the tax guy meme). The gap between #1 and #4 is nearly 2x — this community has a very flat peak.
• Post #11 "Options trading with automated TA" is the ONLY top-25 post with 400+ comments from a Strategy flair — but the post itself is an image of what looks like a legit P&L chart, which generated skepticism-driven discussion.
• Post #14 "Finally created my own algo (using AI)" at 1,140 is the highest-scoring AI-built post and shows the community will upvote AI-assisted work IF it's humble, forward-tested, and shows brutal honesty.
• No flair is used ironically here — the Strategy flair is used consistently for strategies, even when those strategies failed.

4. Content Type Dominance at Scale

Most surprising finding: The "no flair" category has the highest average score (~680) in the full dataset because it's dominated by old, pre-flair-system classics from 2019-2020. If you're submitting today, you MUST pick a flair — unflaired modern posts get nothing.

Second surprising finding: Strategy flair has the LOWEST average ratio (0.93) and the second-lowest average score among non-meta flairs — because Strategy posts get hit with "prove it" skepticism and downvotes when users suspect overfitting, look-ahead bias, or vague claims. Strategy is the most-used flair but it is NOT a safe harbor.

Third surprising finding: Other/Meta is simultaneously the most viral category (3 of the top 10, dominated by memes and joke bots) AND it is the catch-all for "I quit algo trading" capitulation posts. It's the widest-aperture flair.

Data flair has been rising fast in 2025-2026 — the PMXT Polymarket post (732, GALLERY) is the first Data flair post to crack top 25, and it did so by combining open-source + free data + skeptical-of-scam framing.

5. Content Archetypes That Work

Seven distinct archetypes emerge from the data, ranked by score ceiling:

Archetype 1: The Self-Deprecating Failure Meme

Score range: 679–2,969 (ceiling: highest in dataset) Examples:

• "The tax guy at H&R Block when I show up with 40 binders..." (2,969, IMAGE)
• "Don't know if memes are allowed here but here it is" (2,308, IMAGE)
• "My little bot has really mastered the 'Buy High, Sell Low' strategy" (1,020, IMAGE)
• "Funny Story About my Trading Bot" — bug made it do opposite (1,559, TEXT)
• "It do be like that" (977, LINK)

The pattern: The joke is always on the author. The punchline is always loss, futility, or the ironic gap between engineering effort and financial result. It must be clearly in-group — references to backtests, look-ahead bias, overfitting, fees, blown accounts, or the retail-vs-quant gap. Generic market memes get removed.

Why it matters: This is the single highest score ceiling in the entire community. If you want virality, you need a meme. But memes are not a distribution vehicle for products — they're the hazing ritual that earns you credibility for future substantive posts. Post a meme first, then post your tool.

Archetype 2: The Moderator / Community Meta Announcement

Score range: 593–2,862 Examples:

• "NEW RULE: Stock pumpers perma-banned" (2,862, TEXT)
• "/r/algotrading is being swarmed by stock pumping bots" (808, TEXT)
• "'PM me for code' posts should be banned. These are all scams." (890, TEXT)
• "For Your Own Sake, Don't Lie on This Sub" (551, TEXT)
• "Dead Internet Theory in r/algotrading" (593, TEXT)

The pattern: A member (or mod) calls out a perceived threat to community integrity — scams, bots, liars, pumpers, AI slop. The vote is ratification of shared cultural values.

Why it matters: Only mods and long-tenured users can pull this off. Don't attempt this as a new poster — but DO participate in the comments to signal alignment with community values.

Archetype 3: The Brutal Capitulation / "I Quit" Post

Score range: 145–831 Examples:

• "I'm Leaving Algo Trading. Thank You" (831, TEXT, 306 comments)
• "My reality of trading and how i wish i had never started" (823, TEXT, 560 comments)
• "Why I gave up algo trading" (446, TEXT, 159 comments)
• "Why I'm over my algo-trading journey - 11 months on HFT Solana" (145)
• "Truth about successful algo traders. They don't exist" (905)
• "I ADMIT IT. I OVERFIT. I HAVE SELECTION BIAS." (524)

The pattern: Long-form text post. Author shares total honest accounting of time and money spent, acknowledges they failed, lists specific things they tried, and thanks the community. The highest-comment post in the dataset (My reality of trading, 560 comments) is this archetype.

Why it matters: Capitulation posts generate MORE discussion than success posts. The community processes its own fears through these posts. This is where you build genuine relationships if your eventual goal is distribution — but you need to actually have tried and failed. Don't fake capitulation.

Archetype 4: The Open-Source Tool Launch (with GitHub link)

Score range: 216–922 Examples:

• "Tickerrain — open source real-time sentiment analysis" (922, TEXT)
• "Gamestonk Terminal: next best thing after Bloomberg" (888, TEXT, linked GitHub)
• "Stop paying for Polymarket data. PMXT just open-sourced orderbooks" (732, GALLERY)
• "Algo trading lectures, notebooks and strategy code" (721, TEXT)
• "An awesome list about crypto trading bots" (723, TEXT)
• "I created a Python trading framework for trading stocks & crypto [Blankly]" (640, TEXT)
• "TD Ameritrade Python wrapper with Level II" (601, TEXT)
• "D-Tale UI updates" (641, VIDEO)
• "I reverse-engineered the IB Gateway and rebuilt it in Rust" (216, TEXT)
• "stonkr R package for stock price prediction" (494, TEXT)

The pattern: TEXT post (not link post). GitHub URL is in the body, near the top. The post title describes the tool's function plainly and honestly — no marketing language, no "check this out," no emojis. The body explains what the tool does, what the user built instead of using it, acknowledges existing alternatives (e.g., Blankly post calls out Freqtrade and CCXT), and explicitly offers it as free and open-source with "do whatever you want with this, fork it" language. The author reads like a developer who wrote the tool to scratch their own itch.

Why it matters: This is the one reliable archetype for product distribution on r/algotrading. Every successful tool launch in the dataset follows this formula. The ceiling is ~900, and hitting it requires a genuinely useful tool — but 300-500 is achievable for any well-positioned open-source release.

Archetype 5: The Methodological Education / "Advances in Financial ML"-Style Deep Dive

Score range: 156–1,096 Examples:

• "High-level overview of how to get started" (1,096, IMAGE — essentially a flowchart)
• "Lesson from a quant on testing trading strategies" (977, IMAGE)
• "5 Strategies in Quant Trading Algorithms" (853, TEXT, ex-Wall Street trader)
• "Advice for aspiring algo-traders" (769, TEXT — 25 numbered rules)
• "Meta Labeling for Algorithmic Trading: How to Amplify a Real Edge" (618, GALLERY, Lopez de Prado applied)
• "Brief guide on researching strategies and generating alpha" (593, TEXT)
• "What have been your breakthrough/aha moments in algotrading?" (657, TEXT)
• "This is what happens when you DO NOT include Fees in your backtests" (821, IMAGE)
• "Profitable Trading is often Boring Trading" (549, GALLERY)
• "How to develop, test and optimize a trading strategy — complete guide" (484, LINK)

The pattern: Long-form educational content from a credible voice. Either a numbered list of battle-tested rules, a single methodological insight demonstrated with plots, or a cited concept from Lopez de Prado / Chan / Kaufman. Must include specific, actionable detail — "don't overfit" is useless, "be skeptical of test results with less than 1000 trades" is viral. Credibility markers help: "I'm a former Wall Street quant" (post #823), "At Morgan Stanley we found..." (post #735).

Why it matters: This is the second-most-reliable archetype. It's harder than tool launches because it requires you to teach something non-obvious — but the ceiling is higher (1,000+) and it earns long-term credibility.

Archetype 6: The Live Results Post with Rigorous Write-Up

Score range: 186–1,140 Examples:

• "Finally created my own algo (using AI) — first 10 days real money" (1,140, IMAGE)
• "6 year algo trading model delivering the goods" (710, IMAGE, £10k→£550k)
• "Backtest results for a simple 'Buy the Dip' strategy" (670, TEXT)
• "How I made 74% YTD retail algotrading" (611, TEXT)
• "6 Week Results on my First Crypto Algo" (781, IMAGE)
• "Performance of my DipBot during the first hour" (757, IMAGE)
• "3 months of live trading with proof" (446, IMAGE)
• "My life's pride and joy is completed. 5 years non-lookahead" (605, IMAGE)
• "Built a Regime-Based Overnight Mean Reversion Model..." (186, GALLERY, includes WR+Sharpe)

The pattern: Title states the duration and a specific metric (days, win rate, CAGR, Sharpe). Selftext MUST explain methodology — what you trade, on what broker, with what leverage, what the entry signal is. Rule 5 requires this. A bare P&L screenshot with no write-up will be removed. The community's favorite phrase in response: "nice, but what's your Sharpe? Max DD? Did you include fees? Walk-forward?"

Why it matters: Live-results posts generate the highest comment counts after capitulation posts. They're relationship-building, not viral, but they establish you as a serious practitioner. Expect aggressive questioning — it's how the community vets claims.

Archetype 7: The AI / LLM Skepticism Post (2025-2026 emergent)

Score range: 138–618 Examples:

• "Meta Labeling for Algorithmic Trading: How to Amplify a Real Edge" (618, GALLERY) — "ML will not find patterns by itself"
• "Dead Internet Theory in r/algotrading" (593, TEXT)
• "All LLMs are losing money in a trading competition" (257, LINK)
• "They nearly all burned the money they gave to the LLMs" (185, IMAGE)
• "LLMs are not the right tool for algo trading" (138, TEXT)
• "They just stuffed the models with raw price and indicator data 😭😭" (156, IMAGE)
• "The slop is strong with this one" (111, IMAGE)

The pattern: Position yourself against the naive "I asked ChatGPT to make me a bot" crowd. Explain what ML/LLMs CAN do correctly (Meta Labeling as a filter on an existing edge, signal amplification) vs. what they CAN'T (predict price from raw candles, find edges from nothing). This archetype did not exist before 2024 — it's a direct response to the wave of AI slop that flooded the sub.

Why it matters: If your product uses AI/LLMs, you MUST address this archetype head-on. Don't pretend LLMs are magic. Acknowledge their limits. Position your tool as a filter, a research accelerator, or a feature-engineering helper — never as a "tell GPT to trade for you."

No Giveaway Archetype

Unlike r/macapps, r/ClaudeAI, or r/cursor, there are zero giveaway posts in the r/algotrading dataset. Giveaways don't exist here. Don't attempt one — the community would interpret it as a promotional stunt and flag it under Rule 1.

6. Format Analysis

Key finding: IMAGE dominates the top 25 at 52%, but TEXT dominates the overall dataset at 42% (because text is the default for technical deep dives and questions). VIDEO is punchy — only 3.5% of all posts but 16% of the top 25, meaning a good video is 4.5x more likely to crack the top tier than a random post format. GALLERY is the newcomer — fast-growing in 2025-2026 but still zero in the historical top 25.

What Format to Use For What

• Tool/framework launches → TEXT with GitHub URL in body. Every top tool launch in the dataset is TEXT format. Don't post a LINK directly to GitHub — it looks promotional. Write a selftext that explains what, why, and how, and put the GitHub URL inline.
• Strategy / methodology education → TEXT (if 500+ words) or IMAGE (if it's a single chart that makes the point). Lopez de Prado meta-labeling posts use GALLERY for calibration plots. "High-level overview of how to get started" (1,096) is a single IMAGE of a flowchart.
• Live results / P&L → IMAGE or GALLERY with rigorous selftext write-up. Bare P&L screenshots get removed. 2-4 images showing equity curve + drawdown + stats table is the sweet spot.
• Memes / jokes → IMAGE. Never TEXT for memes. Never LINK to imgur if you can avoid it (use i.redd.it).
• Capitulation / "I quit" → TEXT. Long-form, no images. The whole point is the honest narrative.
• Demo videos for tools or algo runs → VIDEO (v.redd.it, native upload). 16% of top-25 is video despite being only 3.5% of dataset.

What Makes a Good Demo Video (rare but punchy)

From the 4 VIDEO posts in the top 25:

1. Short (15-60 seconds). "Algo for ETH based on GPU prices" (1,603), "WSB ML algo" (1,285), "Buys WSB comments" (983), and "FX Spot arbitrage circa 2005" (926) all read as short, focused clips.
2. Show the absurd premise in the first 5 seconds. The titles tell you the hook (GPU prices → ETH; WSB → alpha; arbing FX in 2005). The video confirms it.
3. Let the joke land — don't narrate. The videos work because the concept is self-evidently hilarious (or historically fascinating).
4. Native upload to Reddit (v.redd.it), never YouTube embeds. YouTube videos are treated as promotion.
5. Put source code link in comments, not in the video. The "[Source code in the comments]" convention is explicit in the title.

Galleries

Gallery posts average 3-5 images. The PMXT Polymarket post (732) uses gallery for screenshots of the data dump. The Meta Labeling post (618) uses gallery for the equity curve, the calibration plot, and the expected-value confidence plot. Galleries work for multi-panel results posts — equity curve + drawdown + stats table is a standard layout.

7. Flair/Category Strategy

Raw performance ranking (avg score across all posts)

1. ANNOUNCEMENT (avg ~1,835) — only available to mods
2. (no flair) (avg ~680) — only works on legacy content; new posts with no flair get auto-removed or ignored
3. Other/Meta (avg ~280) — memes, jokes, meta-commentary; highest ceiling
4. Career (avg ~230) — capitulation / "I quit" posts
5. Business (avg ~230) — institutional insight posts, e.g. Morgan Stanley
6. Education (avg ~195) — methodology deep dives
7. Strategy (avg ~185) — risky; hit with skepticism
8. News (avg ~200) — rare, works when big quant fund news drops
9. Infrastructure (avg ~140) — tool launches, dev posts
10. Data (avg ~125) — datasets, data sources, backtests
11. Research Papers (avg ~156, n=1) — too small to judge

Distribution utility ranking (if you're trying to distribute a product)

This is different from raw performance. For promoting a tool or strategy:

1. Infrastructure — best fit for open-source tool launches. Lower avg score but aligned with the content, less likely to be removed.
2. Education — best for methodology posts and "here's how I think about X" content. Builds credibility.
3. Data — best for datasets and data-source launches (PMXT is the #1 Data post, 732).
4. Strategy — USE WITH CAUTION. Only if you can handle the skepticism. Be honest about backtest vs. live.
5. Other/Meta — USE FOR MEMES ONLY. Don't disguise product posts as meta.
6. Business — use for "I'm a founder / quant" insight posts without promoting the company.
7. Career — use only for capitulation or career-pivot posts.
8. News — if you're genuinely sharing industry news, not promoting.

No [tag] title convention

Unlike r/macapps ([FREE], [OS], [Subscription]) or r/indiedev ([DEVLOG]), r/algotrading does not use bracket tags in titles. The closest thing is the convention of including "[Source code in the comments]" or "[Update]" in the title when linking to follow-up posts — but these are rare and not required. Don't invent bracket tags. Use the flair system.

Pricing model hierarchy

r/algotrading does not engage with consumer pricing discussions the way r/macapps does — most content is software by devs for devs. That said, a clear hierarchy exists:

1. Open-source, free — highest acceptance. Every successful tool launch is OSS.
2. Free API / free data — highly accepted (PMXT data dump, SEC EDGAR scraper, stock news datasets).
3. Free but closed-source — tolerated for data providers only, never for strategies.
4. Paid indicators, courses, signals, Discords, paywalls — immediate ban under Rule 1.
5. Affiliate links — immediate ban under Rule 1.

There is no viable path to distributing a paid product through r/algotrading directly. Your only plays are: (a) open-source the thing, (b) use the sub to build reputation and drive traffic to your paid product through your author profile, not posts, or (c) share methodology publicly and let people come to you.

8. Title Engineering

Deconstruction of the top 10 titles

1. "The tax guy at H&R Block when I show up with 40 binders of paperwork because I ran a set of servers with 40 simultaneous scalping algos to execute 45.4 million trades in a year for a net profit of $100.27" — Technique: specificity + absurd juxtaposition. Every detail is concrete (40 binders, 40 servers, 45.4M trades, $100.27). The humor comes from the disproportion. LESSON: exact numbers are funnier than round numbers.

2. "NEW RULE: Anyone found pumping stocks or bringing attention to individual tickers will be perma-banned. We are not WSB. This is an algo trading subreddit." — Technique: in-group boundary-setting + identity assertion. LESSON: mod voice is its own format.

3. "Don't know if memes are allowed here but here it is" — Technique: pre-apologetic humility. LESSON: asking permission deflates gatekeeping.

4. "Would anyone be interested in a beginner series of posts?" — Technique: interest check, not a claim. LESSON: offering value invites buy-in before you deliver.

5. "I made an algorithm to buy and sell ethereum based on graphics card prices throughout the day and it worked as well as you would expect it to." — Technique: absurd premise + telegraphed punchline. "Worked as well as you'd expect" is the universal r/algotrading tell for "it failed." LESSON: self-deprecation in the title is rewarded.

6. "Funny Story About my Trading Bot" — Technique: understatement. LESSON: restraint wins — the word "funny" sets up the story without overselling.

7. "Are you new here? Want to know where to start? Looking for resources? START HERE!" — Mod sticky. LESSON: not replicable.

8. "Some of my algotrading/trading book collection" — Technique: humble flex. LESSON: showing genuine effort (book photos) works without claiming expertise.

9. "I created an algorithm that collected wallstreetbets posts and market data, and then utilized a machine learning model to try and calculate an edge of of WSB posts. It worked exactly how you expect it would..." — Technique: absurd premise + "worked exactly how you expect." SAME formula as #5. LESSON: this formula is so reliable it works twice.

10. "The Good Money Management" — Technique: declarative short title. LESSON: sometimes the chart is the content and the title is just a label.

Title formulas that work

1. "X worked exactly how you'd expect it to" — self-deprecating failure telegraph.

   • "I made an algo based on GPU prices and it worked as well as you would expect" (1,603)
   • "ML model on WSB posts. It worked exactly how you expect it would" (1,285)

2. "[Number] of [Thing]: [Result]" — concrete results with specific metrics.

   • "6 year algo trading model delivering the goods" (710)
   • "6 Week Results on my First Crypto Algo" (781)
   • "3 months of live trading with proof" (446)
   • "How I made 74% YTD retail algotrading" (611)

3. "Truth about X" / "Don't lie on this sub" — community-policing declarative.

   • "Truth about successful algo traders. They don't exist" (905)
   • "For Your Own Sake, Don't Lie on This Sub" (551)
   • "No person/company will EVER sell you a strategy with a real edge!" (135)

4. "I [did hard thing] and [result]" — humble achievement.

   • "I wrote a Python wrapper around TD Ameritrade's streaming data API" (601)
   • "I reverse-engineered the IB Gateway and rebuilt it in Rust" (216)
   • "I scraped ~12 years of Financials Data from SEC EDGAR" (516)

5. "This is what happens when you [common mistake]" — methodology warning.

   • "This is what happens when you DO NOT include Fees in your backtests" (821)

6. Capitulation title: "I'm leaving / gave up / my reality of X"

   • "I'm Leaving Algo Trading. Thank You" (831)
   • "My reality of trading and how i wish i had never started" (823)
   • "Why I gave up algo trading" (446)

Community-specific title anti-patterns

• No "🚀" emojis, no all-caps marketing. "# 🚀 [RELEASE] pandas-ta-classic..." scored 143 — fine, but the emoji didn't help. The word "RELEASE" signals promotion.
• No stock ticker mentions in titles. The community treats individual ticker mentions as WSB-adjacent; mods perma-ban for pumping. Zero top posts include ticker symbols in titles (beyond abstract references to SPY, BTC, XAUUSD used as instruments).
• No "guys" / "fellas" / "y'all" in technical posts. The community is formal. The one top-50 post that says "Yall be posting some wack shit so ill share what I have so I can get roasted" (174) is a deliberately casual outlier.
• No "INSANE RESULTS" / "PROFITABLE" / "100% WIN RATE". These read as either AI slop or course-seller hype. The one post that tried this (Algo Update - 81.6% Win Rate, 16.8% Gain in 30 days. On track for 240% in 12 Months, 296) scored well but got ratio-hit (0.92) and dismissed in comments as overfitting.
• No titles that only state the tool name. "D20" (142), "NT8" (4), "New algos" (0) — tool-name-only titles underperform. You need to describe what it does.
• No questions without homework. Rule 2 removes low-effort questions. "How do I get started?" gets deleted.

9. Engagement Patterns

Highest-comment post in dataset: "My reality of trading and how i wish i had never started" — 560 comments on 823 upvotes. C/U = 0.68. Capitulation generates more discussion than anything else on the sub.

Conditional recommendation:

• If your goal is VISIBILITY, post a self-deprecating failure meme (IMAGE format, Other/Meta flair). Ceiling ~3,000.
• If your goal is CREDIBILITY, post an open-source tool launch (TEXT with GitHub link, Infrastructure flair). Ceiling ~900.
• If your goal is RELATIONSHIPS and discussion, post a capitulation or a Strategy post with honest methodology. Comment counts will be 100-560 even at modest score. This is where you build DM-level connections with serious practitioners.
• If your goal is LONG-TERM REPUTATION, post methodological education (Lopez de Prado, Meta Labeling, regime filters). Lower ceiling than memes but you become a name people recognize.

Highest-discussion topics (regardless of score):

1. Overfitting / look-ahead bias / backtest integrity
2. Fees, slippage, and realistic transaction costs
3. LLMs in trading (almost always contrarian / skeptical)
4. Whether algo trading is actually profitable at retail scale
5. Broker API comparisons (IBKR, TD Ameritrade, Alpaca, MT4/MT5)

10. What Gets Downvoted

Notable posts with ratios below 0.85

Ratio tier interpretation

• Above 0.94: Universally well-received. 85%+ of top-50 posts clear this.
• 0.85-0.94: Net positive but with friction. Usually indicates some community disagreement on methodology, or a divisive opinion. Survivable.
• Below 0.85: Controversial or community-hostile. Most below-0.85 posts in the dataset are either (a) grandiose claims, (b) AI hype, (c) beta-tester/user recruitment, (d) vague philosophical content, or (e) low-effort questions that violate Rule 2.

Anti-patterns (named)

1. The Grandiose Claim Trap — "SENTINEL - destroying every known theorized quant law" (0 score, 0.24 ratio), "Just found alpha" (208, 0.84). Titles that claim you've broken markets get ratio'd immediately. Always hedge claims.

2. The AI Slop Accusation — Any post that reads as AI-generated or that credulously promotes AI tools without acknowledging limits gets dogpiled. "ChatGPT is a GAME CHANGER!" (491, 0.92) — survived but controversial. "Real-time AI analysis on key levels" (0, 0.14) — annihilated. "The slop is strong with this one" (111) mocks this pattern.

3. The Beta Tester Recruitment Scam Flag — "I built a strategy... Seeking Beta Testers" (0, 0.50). The community reads "beta tester" as "wants free users for a paid product." Don't use this phrase. If you need testers, ask in the weekly discussion thread.

4. The Validation-Seeker — "Building a data-driven 'market conditions' tool. Would this be useful?" (0, 0.25). Don't ask if your idea is useful. Build it, ship it, open-source it, show your work. The community hates idea-validation posts.

5. The Low-Effort Question — "How often do your trading bots break?" (0, 0.46), "Where can I begin making an algo/bot?" (33, 0.85). Violates Rule 2. Shows no prior research. Gets removed or ratioed.

6. The Paywall Tease — "PM me for code" / "Details in DM" (called out in the 890-score meta post). Any solicitation of private contact triggers instant suspicion. Always put the code in the post or in a public GitHub link.

7. The Course Seller Ghost — Any title that reads as "I'll teach you trading" or "Here's my system that made me $X" without code or methodology. The community can smell this from miles away. The one 14-year-old TradeAlgo post at 448/0.86 is the classic borderline case.

Hall of Shame / Blacklist

r/algotrading does not maintain a public blacklist the way r/macapps does, but the wiki contains a "Hall of Fame Threads" (promoting the best content) and a "rules_of_engagement" page that you must follow to promote any project. Repeat promotional offenders are quietly shadowbanned. The mods make periodic meta-posts about bot farms and stock pumpers, and the community is encouraged to report via Rule 6.

11. The Distribution Playbook

Phase 1: Pre-Launch (4-8 weeks)

Build genuine presence first. Most failed launches here come from first-time posters.

1. Create an account with real karma. Post in the weekly discussion thread. Comment substantively on 5-10 Strategy or Education posts. Share methodology opinions. Demonstrate competence.
2. Read the wiki's rules_of_engagement page. It literally tells you how to post about your project. Follow it.
3. Read "Are you new here? Want to know where to start?" (the sticky). The community has pre-decided what it values. Align with it.
4. Find your archetype. Is your tool open-source? Archetype 4. Is it methodology? Archetype 5. Is it a paid product with no OSS path? You have no archetype. Reconsider the plan.
5. Prepare the GitHub repo before posting. README must be clear. License must be open (MIT, Apache, GPL). No marketing language. No "buy now" links. Include setup instructions and at least one working example.
6. Capture a short demo if your tool produces visual output. Native Reddit video upload, 15-60 seconds.

Phase 2: Launch Day

1. Day: Tuesday-Thursday. Weekend posts get buried by the weekly discussion thread and casual scrollers. Friday posts get lost in weekend-mode drift.
2. Time: Post between 13:00-17:00 UTC (9am-1pm ET) to hit US business-hours algo devs. Several top posts confirm this window.
3. Format: TEXT post (self.algotrading), not a link post, EVEN if linking to GitHub. Link posts read as promotional.
4. Flair: Infrastructure (for tools), Education (for methodology), or Data (for datasets). NEVER Strategy for a tool launch — Strategy invites skepticism you don't need.
5. Title formula: "[I built/wrote/released] X for Y" — plain, descriptive, no hype. See Archetype 4 examples.
6. Body structure:
   • Paragraph 1: What it is, 1-2 sentences.
   • Paragraph 2: Why you built it (your specific problem).
   • Paragraph 3: What it does (bullet points of features).
   • Paragraph 4: What it does NOT do / known limitations / acknowledged alternatives (Blankly's post explicitly calls out Freqtrade and CCXT).
   • Paragraph 5: GitHub link + "do whatever you want with this, fork it" license language.
   • Optional: one code example inline (like Blankly's post).
7. Never include: affiliate links, Discord invites (unless the sub's own Discord), Telegram, Patreon, Substack, Twitter CTAs, "PM me."

Phase 3: First 24-48 Hours

1. Reply to EVERY comment within 30 minutes for the first 4 hours. This is the highest-leverage behavior. The top tool-launch posts all have authors who replied substantively in the first hour.
2. Expect aggressive methodology questions. "How is this different from Backtrader?" "Does it handle corporate actions?" "What about look-ahead bias?" "How are fees modeled?" Answer technically and honestly. Never defensive.
3. Expect skepticism comments. "Another crypto bot" / "Yet another backtester." Respond with a specific differentiator, not a generic "mine is different" — e.g. "Blankly enforces exchange order filters in backtest to match live, Freqtrade doesn't."
4. Do not delete negative comments. The community notices and downvotes.
5. If the post is going to get removed by mods for promotion, message the mods proactively. The Quantopian Lectures post author (721) explicitly thanks mods for working with them to unblock.

Phase 4: Ongoing Presence

1. Return with updates. "[ Update ]" titles work — "[ Update ] To my last post in here reddit users told me to flip my algorithm around and it worked" (811). Frame updates as "the community told me X, here's what happened."
2. Post once per month maximum. More frequent posting will get flagged as self-promotion.
3. Build a posting cadence: meme → educational → tool update → capitulation → educational → tool update. Vary archetypes.
4. Answer questions in other people's posts. Be the person who replies to "How do I handle fees?" with a link to your tool's fees module. This is stealth distribution.
5. Participate in the weekly discussion thread. Mods pin it every week. It's under-trafficked but rewards persistence.

Community-specific comment-reply templates

For the 5 most common objections you'll face:

Q: "Is this vibe-coded / AI slop?"

"I wrote the architecture and the core pipeline by hand. I used [Claude/GPT] for [specific thing, e.g. docstrings, test scaffolding, a specific hash function]. Here's the commit history so you can see the progression: [link]. The ML parts don't touch LLMs — [explain your actual model]."

Q: "Why not just use [Backtrader/Freqtrade/Zipline/QuantConnect]?"

"I evaluated [the specific tool] and it does [X] well. I built [yours] because [specific gap: e.g. it was slow for my use case / didn't support the exchange / required wrapping every strategy in a class]. Not saying it's better — saying it solves a different problem. If [their use case] fits the existing tool, use that."

Q: "Did you include fees and slippage? Is this walk-forward?"

"Yes — fees are modeled as [fixed bps / per-share / exchange-specific]. Slippage is [not modeled / modeled as X]. I did walk-forward with [N] years train / [M] year test. Here's the full backtest config: [link]. Happy to share the full dataset if helpful."

Q: "Aren't you just overfitting?"

"Possibly. That's why I'm only showing results, not claiming an edge. The reason I think it's not pure overfit is [specific reason: stable parameters across markets, OOS test on different instrument, etc]. If you have a way to stress-test it harder, I'd love suggestions."

Q: "What's your pricing model?"

"MIT-licensed, free forever, nothing to buy. If you like it, star the repo. If it breaks, file an issue. I'm not monetizing this." [If you DO plan to monetize: "Currently free and open source. I may offer a hosted version down the road for people who don't want to manage infra, but the core library will stay OSS."]

Stealth distribution tactics

1. Answer "what tool should I use" threads (they appear in the weekly discussion thread frequently) with one-line recommendations that include your tool as one of several options.
2. Post a methodology deep-dive (Archetype 5) that happens to use your tool in the examples, without making the post about the tool.
3. Share a dataset your tool produced. Data posts work if the data is free and the tool is implied but not hard-sold.
4. Reply to capitulation posts with "I've been there — one thing that helped me was [Y]." If Y is an approach your tool supports, great.

Score-tier calibration

Be realistic about what's achievable:

• Memes: 500-2,900 ceiling. Unpredictable. Don't plan on this.
• Tool launches (open-source, well-executed): 200-900 ceiling. Realistic target 300-500.
• Methodology education: 200-1,100 ceiling. Realistic target 300-600.
• Live results with rigorous writeup: 150-1,100 ceiling. Realistic target 200-500, but with high comment count.
• Capitulation posts: 150-830 ceiling. High C/U ratio, lots of DMs.
• Data/dataset posts: 100-730 ceiling. Realistic target 150-400.

Anything tool-related above 1,000 is exceptional. Most successful product distributions on this sub will peak in the 300-700 range and drive 200-1,000 GitHub stars rather than direct sales.

Post-publication measurement

• First 4 hours critical. If you're below 30 upvotes after 4 hours, the post will cap out at 100-150. If you're above 80 upvotes at 4 hours, you have a shot at 500+.
• Ratio < 0.90 in first hour = concerning. Some methodology skeptic is triggering others. Jump into comments.
• Ratio < 0.85 at any point = hostile reception. Consider editing the post with a clarification — don't delete.
• Comment count > 2x upvote count = high engagement. You're building relationships even if the score is modest.
• If you get zero traction in the first hour, the post is probably caught in the spam filter. Message mods and ask for review — this happens more on r/algotrading than most subs due to aggressive automoderation.

12. Applying This to Any Project

Quick-reference checklist

1. Is my product open-source? If no, I have no primary archetype on this sub.
2. Do I have a public GitHub repo with a clear README?
3. Have I read the wiki rules_of_engagement page?
4. Does my post body explain WHY I built this (my specific problem)?
5. Does my post body acknowledge existing alternatives and explain differentiation?
6. Have I chosen Infrastructure / Education / Data flair (not Strategy)?
7. Is my title plain descriptive, with no emojis, hype language, or ticker symbols?
8. Am I prepared to reply to every comment in the first 4 hours?
9. Have I removed all affiliate links, Discord invites, and "PM me" language?
10. Am I posting Tuesday-Thursday, 13:00-17:00 UTC?
11. Do I have a pre-written response for the "is this vibe-coded?" question?
12. Am I prepared for the post to be removed by mods, and do I know how to message them?

Scenario-based launch guides

Scenario A: Free, open-source tool (Python backtesting library, data scraper, broker wrapper)

• Optimal formula: TEXT post, Infrastructure flair, title format "I built/wrote/released [tool] for [purpose]", body paragraphs on what/why/features/limitations/GitHub link, single code example inline.
• Key risk: Being dismissed as "yet another Backtrader." Pre-empt by calling out existing tools in the post and explaining your specific differentiation.
• Score target: 300-600.

Scenario B: Paid product with no OSS core

• Optimal formula: Do not post a launch. Instead: (1) write a methodology education post (Archetype 5) that demonstrates competence without mentioning your product; (2) use your author profile to drive traffic to the product; (3) participate in strategy discussions for 2-3 months; (4) only post about your product if the product page is substantive (weekly discussion thread only, never as a standalone post).
• Key risk: Instant ban under Rule 1. Do not attempt a direct launch.
• Score target: 0 (don't post). Use the sub for credibility only.

Scenario C: Product built with AI assistance (Claude, Cursor, ChatGPT)

• Optimal formula: Lead with the "I used AI for X, not for the edge" framing. Meta Labeling post is your reference (618 score) — it explicitly says "ML will not find patterns by itself" before introducing a valid use case. Acknowledge AI limits. Show your commit history. Include a brutal honest section: "Here's what AI got wrong and I had to fix."
• Key risk: Being lumped with the "I asked ChatGPT to build a bot" crowd. The "Finally created my own algo (using AI)" post (1,140) worked because the author stressed "Claude AI gave me working code, ChatGPT didn't" (specific), 10 days forward-tested (empirical), humble wording ("I am very happy with the result. Will keep forward testing").
• Score target: 200-800 if framed correctly.

Scenario D: Trading strategy / backtested results

• Optimal formula: Title states specific metric + duration. Body MUST include methodology (what you trade, on what broker, with what leverage, entry/exit rules, fee assumptions). IMAGE or GALLERY format with equity curve + drawdown + stats table. Call out possible overfitting / selection bias before anyone else does. Do not hype.
• Key risk: Being destroyed on methodology. The community will ask for Sharpe, max DD, walk-forward validation, OOS testing. If you don't have answers, don't post.
• Score target: 200-700.

Scenario E: Dataset / data source release

• Optimal formula: Data flair. Title: "Stop paying for X. [Name] just open-sourced the Y." (see PMXT post at 732). Body: what the data is, how much of it exists, how to access it, GitHub / archive link, explicit "it's free because [reason]" framing. Bonus for direct shots at expensive data providers — the community loves anti-gatekeeping framing.
• Key risk: Being accused of data quality issues. Include a sample, describe the pipeline, stress-test claim.
• Score target: 200-800.

Cross-posting guidance

If you're cross-posting between finance subs, reframe for each community's values:

• On r/algotrading: Frame as "I built X in Python/Rust. It's open source. Here's the GitHub. Here are the methodology notes. Here's what I acknowledge I got wrong." Engineering-first.
• On r/daytrading: Reframe as "Here's how this tool helped me stop sabotaging myself" (psychology-first) or "Here's a demo of what a full session looks like" (voyeurism-first). Verification via Kinfo matters there.
• On r/forex: Reframe as a meme first, a tool second. Or post on a weekend when memes are allowed. The community is more casual and meme-friendly.
• On r/stocks / r/investing: Don't post tool launches. These subs are consumer-focused. Use them only for macro / research content.
• On r/wallstreetbets: Do not cross-post. Any r/algotrading content will get dismissed as "nerd shit."
• On r/MachineLearning: Reframe the ML post as a methodology contribution to financial time series. Emphasize the ML novelty, not the trading outcome.
• On r/LocalLLaMA / r/ClaudeAI: Reframe as "I used [LLM] to build X — here's my prompt engineering + workflow." Product-of-LLM framing works there; methodology framing works here. Do not use the same post.

Final word: r/algotrading is one of the hardest subreddits on Reddit to distribute through, because it has explicit anti-promotion rules, vigilant moderators, a skeptical community, and a niche technical audience that rewards demonstrated competence over marketing. But the payoff for doing it right is outsized: a successful open-source tool launch here reaches a concentrated audience of serious practitioners, drives high-quality GitHub stars, and builds long-term reputation in the retail quant community. The cost is honesty — you cannot fake your way in. Build something real, show your work, open-source the core, admit what you got wrong, and let the community's own credibility-granting mechanisms do the distribution for you.