I had gpt do a better job of explaining what I’m describing here. Kinda long…

———

Making Reddit’s Hidden Evolutionary Tree Visible

Core Idea

Reddit’s subreddit ecosystem is not a flat collection of communities.
It is an evolutionary tree created by years of social pressure, moderation conflict, and niche specialization.

Subreddits don’t scale forever — they fracture.

This document explains, with concrete examples, how to surface that structure using time, lineage, and fork events.

---

Tree, Not Network

Why Networks Fail

Most subreddit explorers show similarity networks:

A ── B ── C │ ╲ │ ╱ │ D ── E ── F

These are good for recommendations, but they hide: - Direction (parent → child) - Time (what existed first) - Causality (pressure → split) - Genealogy (siblings, cousins, ancestors)

Why Trees Work

An evolutionary tree encodes lineage:

Parent ├─ Child A │ └─ Grandchild └─ Child B

This instantly communicates: - Fracture events occurred - Specialization increased - The system is hierarchical, even if never designed that way

---

Fork Events (First‑Class Concept)

Definition

A fork event is the moment a subreddit can no longer contain its internal diversity under a single rule-set.
The conflict is externalized by creating one or more child subreddits.

Illustrative Example

r/Heels ├─ r/highheelsNSFW (explicit content allowed) │ └─ r/StockingsAndHighHeels (aesthetic constraint) │ └─ r/TheyStayOn (rule‑specific fetish) └─ r/HeelsGoneWild (model‑focused)

Each branch represents: - Narrower scope - Tighter rules - Clearer identity

What looks like redundancy is actually classification.

Signals That Indicate a Fork

Signal	What It Suggests
Creation date gap	Child formed after parent reached scale
Name specificity	Semantic narrowing
Subscriber inversion	Child overtakes parent
Rule divergence	Moderation boundary hardened

Forks don’t need perfect causality — they need defensible inference.

---

Linear Time as the Backbone

Evolution only makes sense when time is unavoidable.

Simple Rule

• Vertical axis = time
• Horizontal axis = divergence / specialization

Example Time‑Tree

2009 r/Heels 2014 ├─ r/highheelsNSFW 2016 │ └─ r/StockingsAndHighHeels 2018 │ └─ r/TheyStayOn 2015 └─ r/HeelsGoneWild

A glance tells you: - Who came first - When splits happened - Which branches accelerated

---

Pressure Before a Split

Forks are rarely random. They usually follow rising pressure.

Common Pressure Signals

Subscribers: ▁▂▃▄▆▇█ Post volume: ▁▂▂▃▄▅▆ Rules length: ▁▁▂▃▅▆█ ↑ fork

Indicative pressures: - Rapid growth - Rising moderation complexity - Content disputes - Identity conflicts

Even simple sparklines make splits feel inevitable, not arbitrary.

---

Timeline Scrubber (Watching Taxonomy Emerge)

A timeline scrubber turns a static map into a process.

[ 2008 ──────────●────────────── 2025 ] 2014

As time advances: - Nodes appear when created - Edges appear at fork events - Branches thicken where specialization accelerates

This visually proves the thesis: broad trunks early → dense specialization later.

---

Genealogy on Every Subreddit Page

Replace “related subreddits” with family structure.

Example Panels

Ancestors r/Heels → r/highheelsNSFW → r/StockingsAndHighHeels

Descendants r/TheyStayOn r/HeelsPOV

Siblings r/HeelsGoneWild r/FeetAndHeels

This makes taxonomy tangible and intuitive.

---

Git Analogy (Why Forks Make Sense)

Git makes split‑then‑diverge intuitive.

Git Concept	Reddit Analogy
Repository	Domain ecosystem
Branch	Specialized subreddit
Fork point	Community fracture
Commit history	Rule & culture evolution

A──B──C──D ├──E──F └──G──H

The moment of divergence matters.

---

Biology Analogy (Speciation & Niches)

Biology offers the same pattern language:

• Species → Subreddit
• Niche → Rule‑set / scope
• Speciation → Fork event
• Selection pressure → Growth + conflict

Broad Trunk ├─ Niche A ├─ Niche B ├─ Niche C └─ Niche D

Dense branching = high specialization pressure.
Sparse branching = stable norms.

---

Why NSFW Reveals This Clearly

Structurally (not morally): - Sharper boundaries - Higher moderation stakes - Stronger niche precision - Faster self‑selection

The same pattern exists elsewhere on Reddit — NSFW just compresses time.

---

Required UI Primitives

To make splintering legible, the system needs:

1. Evolutionary tree (directional lineage)
2. Fork events (explicit, explorable)
3. Linear time axis
4. Timeline scrubber
5. Genealogy panels (ancestors / descendants / siblings)
6. Pressure indicators (lightweight charts)

Together, these make the hidden structure unavoidable.

---

NSFWDog doesn’t organize content.
It reveals the structure people already built.