OverClocked ReMix (OCR) — polarization, privatization, and controlled-opposition pattern language (open)
TL;DR: VGM fan community routed through OverClocked ReMix, LLC submission licenses and (from 2016) Game Music Initiative, Inc. 501(c)(3) umbrella; 2007 content policy formalized broad site licenses shortly before Capcom Street Fighter II HD Remix used community soundtrack work; later Capcom-licensed commercial albums (MM25) and OverClocked Records (2014). No public record in this dossier proves embezzlement or withheld artist payouts — the pattern under study is central routing of fan labor toward industry deals. Author read — §4.1: HD Remix narrative treated as dubious (Capcom for-profit use of free scene work ; alleged forum moderation / pro-industry face ; narrowing of tolerated opinion). Parallel lanes: Homestuck / Hussie (IP / canon); SDA / GDQ / MSF (charity / forums — OCR appears there as a lite rhyme only).
Status: Open — §1 preserves third-party seed text (mixed assistant / LLM draft not in the repo author’s voice); §2–§10 add citations and pattern framing.
Guide
Reader-facing synthesis: Success — by any means necessary — Protricity / Ari voice; cross-investigation essay (links §8 firsthand + Limits discipline).
Reader essay alignment: Same file — NDA / paycheck silence , black-box economics vis-à-vis paying audiences , leader responsibility **(potential suicide where support was absent ) , active conflict resolution , no one is ever banned **(author moral standard — not a claim every host can lawfully run literal zero enforcement everywhere ) . Moral ledger only unless sourced as law ; see essay Honesty cap.
- Seed spine (third-party draft + disclaimer)
- Entity stack — LLC, “not-for-profit” site language, GMI
- 2007 policy + Street Fighter timeline
- Interviews — Capcom contact, coordination through OCR 4.1 Author read — HD Remix (ethics, forums) 4.2 Forum-primary — topic 9050 (Oct 2007) + djpretzel as Capcom contact 4.3 Press — Ars, GeekDad / Wired network, Wikipedia (framing) 4.4 ChatGPT thread digest (verify pages 2–5)
- Commercial lane — MM25, OverClocked Records
- Forum ethics examples + §6.1 (Chrono/CIA test thread ) + §6.1.1 **(post-Exodus repair , Liontamer , judge removal — firsthand ) + §6.2 **(paid-guardian / silver-platter universality — author working model )
- Cross-theme bridge (Homestuck, SDA/GDQ) + §7.1 / §7.2 / §7.4 / §7.5 (fan edit lane + Morrowind OpenMW vs MWSE / engine fork — legal chill, Reddit / industry monitoring cites, author firsthand)** + Discord / macro privatization thesis
- VGMix fork & exodus lane (sources + firsthand Protricity; §8.4 LLM digest + anchors; §8.5 VGMix 2 collapse; §8.6 CO typology — Lloyd vs Kaufman)
- Unmod compact, removal, and 2007 cadence (policy / HD Remix window; §9.3 UnMod shutdown digest)
- Hooks
1. Seed content (third-party draft — not repo author)
The following synthesis was supplied as starting material (mixed editor / LLM voice). It is kept as a working spine; treat every factual clause as needing confirmation against primaries in §2–§6.
A. “Not-for-profit” + LLC
- Public face: FAQ describes a not-for-profit mission; ads, merchandise, donations → bandwidth, hosting, promotion, admin; staff described as unpaid volunteers — OverClocked ReMix — FAQ.
- Contract counterparty: Submission Agreement names “OverClocked ReMix, LLC” — Content Policy — Submission Agreement.
- 501(c)(3) umbrella (from 2016): Site copy places OCR under Game Music Initiative, Inc., EIN 81-4140676 — same FAQ; chronology Site History (Nov. 26, 2016 — GMI founded; assumes management / sponsorship).
- Transparency: ProPublica Nonprofit Explorer — Game Music Initiative lists tax-exempt since Nov. 2016, no Form 990 financial data in its dataset — explanation on-page matches small filers / 990-N not fully exposed in Explorer.
B. 2007 content policy
- Forum enactment (final 6/12/2007): OverClocked ReMix Content Policy — Final Enacted 6/12/2007 links to wiki policy; OP cites “over three weeks of continuous discussion.”
- Current policy text (non-exclusive license to OCR, ad revenue clause, OCR may not distribute submissions for for-profit endeavors) — Content Policy.
- LLC context: 2007 State of the ReMix Address mentions registering OCR as an LLC for legal protection.
C. Street Fighter II HD Remix
- Interview spine: Capcom associate producer Rey Jimenez contacted Shael Riley after Blood on the Asphalt; Riley needed ~20 other artists’ permission and emailed Dave (djpretzel) to coordinate; Riley describes OCR as due entity-level credit and community ownership of the album — Street Fighter Devotion interview; parallel reporting — Ars Technica — “Fans go pro” (Larry Oji, Andrew “zircon” Aversa named).
- Additional primary: Retro Garden — OC Remix interview Part 4 (HD Remix) (djpretzel + Larry Oji on how Capcom found the album and scope of community involvement).
- Forum (Oct 2007): IS Blood on the Asphalt the soundtrack for SF2HD? — djpretzel states he is “the single point of contact with Capcom” and asks users not to contact Capcom (§4.2).
D. Commercial releases
- For Everlasting Peace: 25 Years of Mega Man (2013) — album site frames first commercial fully licensed OCR album with Capcom — mm25.ocremix.org; Capcom USA — MM25 / For Everlasting Peace OUT NOW (Oct 29, 2013).
- OverClocked Records (2014) — OC ReMix forum announcement; press quoting ~80% to artists / remainder to operations — Destructoid, Last Minute Continue (secondary; cites OverClocked ReMix, LLC in revenue split language).
E. Ethics / “selling remixes”
- Example thread with royalties / Kickstarter / rights-holder discussion — FF6 Balance & Ruin Kickstarter RELAUNCHED (Sept. 2012) — illustrates public negotiation of money + licensing, not a leadership accusation thread by itself.
Seed conclusion: Public material reads less like charity withholding and more like fan labor aggregated under one legal interface that could negotiate with publishers — audit as privatization / gatekeeping, not presumed fraud.
2. Entity stack — documented
| Layer | What sources say | Primary links |
| OverClocked ReMix, LLC | Named in Submission Agreement | Content Policy |
| Public mission / revenue | Not-for-profit framing; revenue → operations; volunteer staff | FAQ |
| Game Music Initiative, Inc. | 501(c)(3); Nov. 2016 assumes OCR sponsorship | Site History; FAQ; gamemusic.org |
| 990 visibility | ProPublica: no 990 financials in Explorer for GMI (990-N / small-filer explanation) | ProPublica — GMI |
Pattern note: LLC + “not-for-profit” site language + later 501(c)(3) is the kind of stack contributors may scrutinize — without implying misuse was demonstrated here.
3. Timeline — policy vs Capcom (hypothesis hygiene)
- January 7, 2007 — Forum thread What happened to Unmod? — community unease about Unmod in the same run-up as formal policy (§9); MAGFest 5 (Jan 4–7, 2007) overlaps per common recollection (§9.3).
- June 12, 2007 — Content Policy enacted (forum thread).
- 2007 — Capcom outreach re Blood on the Asphalt / HD Remix (interviews, §4).
- 2008 — Super Street Fighter II Turbo HD Remix ships with OCR-coordinated soundtrack (Ars, §4).
Hypothesis only: The policy is not proven here to have been written for Capcom; it is the first document to read if asking how centralized permission could work at scale.
4. Interviews — centralized coordination vs community narrative
- Shael Riley (Street Fighter Devotion): Jimenez email after Capcom used Blood on the Asphalt at trade shows; Riley could only approve his tracks; contacted Dave to coordinate ~20 artists; “ownership lay with the community” while OCR needed entity-level involvement.
- Ars Technica (July 2008): Same chain; notes EULA / policy as possible framework for Capcom to work with many artists.
- djpretzel / Larry Oji (Retro Garden): Capcom found Blood on the Asphalt; community effort; coordination realities.
Unpack: Publisher needs a single counterpoint; community narrates collective ownership; OCR leadership becomes the routing layer — documented tension, not proof of secret payments.
4.1 Author read — Super Street Fighter II Turbo HD Remix (supplied)
Author thesis (supplied): I find the whole Capcom / OCR / HD Remix story extremely dubious, including Shael Riley’s public posture that waves off controversy — it reads like reputation management, not a straight account of ethical cost.
First problem: A private corporation with the IP, money, and distribution power still showed up to use free community music in a for-profit game — major ethical blur. They shouldn’t need to “borrow” that way from a volunteer scene to extract more profit on top of what they already own.
Second problem: OCR went along with it — not only without pushback in public, but (in my memory) staff moderated hard against “excess” complaining so the site could wear a pro-corporate face: come pillage us, tell us how to behave on the forums, expect the next release without griping about the industry itself — you’re allowed to nitpick games but you’re still expected to keep paying for the next version forever. OCR used to have forums with their own soul and a myriad of opinions; after this turn toward industry politeness, that breadth of opinion stopped being tolerated.
Unpack (assistant): Interviews (Ars Technica, Street Fighter Devotion) are participant-authored publicity — treating low-controversy framing as neutral truth would be a mistake. Capcom shipped a commercial title incorporating fan arrangements; whether that equals “sold free songs” depends on licensing and who was compensated — this dossier has not found a public revenue split for HD Remix. Forum moderation and culture claims in the blockquote are author memory — verify or falsify with Wayback, mod posts, and dated threads (§10).
4.2 Forum-primary — topic 9050 (October 2007)
Thread: IS Blood on the Asphalt the soundtrack for SF2HD? — opened Oct 23, 2007 (OP: dsx100, speculation from trailers).
djpretzel (Oct 24, 2007, administrator), same thread — verified pull (forum body is not bold in source; emphasis added):
Please don’t contact Capcom regarding this; their usage on the blog is legitimate, if a little premature. […] At this moment, we’re coordinating things and I’m the single point of contact with Capcom, with Shael and Malcos remaining informed every step of the way. We planned to fully inform involved mixers of the potential once we had something more definite in terms of contracts, but the cat’s at least partially out of the bag now. […] Please don’t contact Capcom; my contact there, who is the decision maker, will simply refer you to me.
Unpack: Strong forum-primary evidence that coordination centralized through Dave / OCR (not Shael alone) once Capcom was in play — not proof Shael was “pushed out,” but consistent with interviews where Riley sends Jimenez to Dave.
4.3 Press — commercial framing, “free” soundtrack, big-business pattern
- Ars Technica — Fans go pro (July 2008) — David W. Lloyd: “we adapted to working with Capcom, not the other way around”; “It wasn’t always a particularly democratic process”; frames the project as a “prototype” for publishers working with fan communities. Same interview: “Ultimately, everyone wins… Capcom gets what we think is a pretty badass soundtrack for free.”
- GeekDad — Capcom Uses Fan-made Re-mixes… (July 23, 2008) (Wired.com network) — mainstream notice that Capcom drew on OverClocked ReMix after Blood on the Asphalt; Jimenez → Riley → site founder chain in prose. Listed on OCR Press/2008.
- Wikipedia — Super Street Fighter II Turbo HD Remix (secondary) — summarizes Jimenez discovering Blood on the Asphalt and Lloyd directing the soundtrack / acting as Capcom liaison so a large community could function “as close as possible … to working with a single composer.”
4.4 Third-party research digest (ChatGPT) — forum friction + spot-check
Another LLM pass flagged disagreement, secrecy, and ethics inside topic 9050 (and possibly OCRA-0007 album discussion). Pages 2–5 were not transcribed here — confirm quotes on the live thread or Wayback before relying on them.
| Claim | Status in this dossier |
| Shael initial Capcom contact → Dave/OCR became coordination layer | Supported by interviews + §4.2 |
| No public Shael post: project “taken away” / distress | Not found in third-party pass; not exhaustive |
| Infinity’s End — posting restrictions; Liontamer — deleted post / “jig was up” | Needs pagination verify (9050 or 3890) |
| Dhsu — distribution / artist rights | Page 1 shows Dhsu supportive / offering email — rights wording may be later pages — confirm |
| The Pezman — outsourcing / fan-labor critique | Conflict: Pezman’s Oct 24, 2007 post on page 1 is a Phoenix Wright joke, not an outsourcing essay — ChatGPT may have merged users, pages, or threads |
| big giant circles, MkVaff, Urban Xperience — ethics / leverage / “cash money” | ChatGPT cites same discussion vein — verify pages 2–5 |
| José the Bronx Rican — defense of Dave / LLC looking out for artists | Plausible — locate exact post ID |
Negative finding (ChatGPT): No located post where Shael says outright “they took the project from me.”
Parallel digest: §8.4 — VGMix exodus / OCR–VGMix split extended LLM pass + OCR03049 / 6976 anchors.
Longform: David “Dhsu” Hsu — “From Blood To Sweat: How OverClocked ReMix Scored Its First Gig” (Dec. 2008) indexed on Press/2008 — resolve canonical outlet URL when convenient.
5. Commercial lane — Mega Man MM25, OverClocked Records
- For Everlasting Peace — Oct 2013; Capcom-licensed; first commercial album framing on mm25.ocremix.org; Capcom USA release post.
- OverClocked Records — Jan 2014 announcement topic; Destructoid (~80% artists / rest OCR).
Assistant note: Documented monetization steps — not evidence of undisclosed diversion without contracts.
6. Community ethics threads (examples)
- Pre-policy license confusion — What license are the remixes under? (Feb 2007).
- Kickstarter / royalties — FF6 Balance & Ruin Kickstarter relaunch (Sept 2012).
- Site Issues — Chrono / CIA thread removal — topic 65360 — Chrono Trigger thread suddenly vanished… (2026; Liontamer staff reply — §6.1).
6.1 Author firsthand — Chrono Trigger × CIA Mars thread, whole-thread removal (2026)
Supplied account (repo author): I opened an OC ReMix community thread that was this repo’s Mars × Chrono Trigger article — forum trim, same spine: CIA-RDP96-00788R001900760001-9 on cia.gov beside Square’s game, pattern not proof. Part of the point was instrumental: I wanted to see how the board would behave when the anchor was an official scan rather than a pastebin chain letter.
Author judgment: not ban-worthy content by any fair read — still something I believe they do not want left up in public view. I would have preferred a notice or rule cite; I also know they have little incentive to argue with me on paper given our long history on the site **(this dossier §8 — Protricity / exodus lane).
A poster (Master Mi) steered into Israel / Palestine and vaccine-injury territory that had nothing to do with the OP. I expected that shape of derail and refused to reply in those lanes. I was surprised the vaccine thread even stayed visible long enough to attach to my topic given how tightly curated OCR’s public face usually reads.
Author read — Master Mi is not “some random user” (pattern language): Master Mi is not modeled here as a one-off drive-by . On-site (General Discussion and related forums — author eyeball only ; no scraped count in this repo) he shows up with heavy reply and topic-creation presence on many threads that sit on the community front page . Author hypothesis (metaphor , not employment accusation unless payroll is sourced) : that footprint pairs with staff mood ruling (Liontamer “wacko”) to produce the “silver platter” environment this dossier tracks elsewhere — a pre-cleaned , low-friction table for approved tone , plus fast character verdict on anything that reads as edge (“guard dog”** + knee-jerk admin bias as complementary forces , not proven conspiracy in a room)** .
Outcome: when I checked again ~a week later, the entire original thread was gone (no URL archived here for that topic).
Staff on-record (forum-primary): Master Mi opened Site Issues & Feedback — topic 65360 Friday 10:11 PM (OP) asking what happened (mentions a PM from @Protricity). Liontamer (Grand Master, Judges) Friday 10:16 PM: “It’s a wacko thread, so it’s gone.” Topic locked after that reply (same thread).
Interpretation (author — pattern language): this is the old intermediary geometry I have watched for decades: someone contaminates the bundle with third rails, then moderation nukes the whole package — sometimes with a plausible **“look at the toxic reply” cover, sometimes with a blanket label only (Liontamer’s on-record line does not name Israel/Palestine or vaccines — just “wacko”). Either way, selective deletion and named sanctions on the derail were available and were not what the public got. Collective punishment of the OP and lurkers who did nothing wrong is a choice. I read it as consistent with scene capture after years of corporate-facing branding — not a neutral “safety” outcome but a power outcome.
Generalization: the real signal is not “forums hate overlapping fringe topics.” It is whether institutions default to excising challenge while preserving in-group peace — the same schoolroom “punish the weakest link” reflex culture has sung about for generations (Pink Floyd canon as shorthand). Prospecting artists and new voices get this treatment when they brush established prestige — provoke them into a fight, then let mods pick the familiar side. No indexed petition → reasoned answer lane means the abuse stays subtle.
Repo article scan (assistant — not legal / not OCR staff): This desk re-read the parent article cia-1984-mars-chrono-trigger.md as published (not the Mars dossier) against generic forum ToS buckets (hate/harassment/dox/illegal/spam) and against “on-topic for a VGM board” (game + primary Reading Room PDF + fiction/film parallels with explicit limits). Nothing in that file presents as ban-worthy or inherently off-topic for a video-game forum that already hosts culture / analysis threads — moderators may still dislike tone or length, but that is discretionary taste, not a clear violation object visible in the markdown body.
Author opinion — staff line vs rules: Liontamer on 65360 names no Community Guidelines clause, no quoted OP violation, no per-post sanction narrative — only “wacko” . To me that reads as categorical bias / prejudice (mood verdict on a whole topic) that should jar anyone who expects rule-text moderation — you weigh that moral claim yourself.
Author opinion — OCR invariant: OverClocked ReMix has never (in my experience across decades on the site) been different from what just happened — long history of temperature control and visibility filtering (this file §8/§9**)** , so running this thread as an instrumental test was warranted .
PM exchange (author paraphrase — private, not pasted verbatim): After the removal, Protricity messaged Master Mi that his Israel/Gaza and vaccine-injury turns had raised the temperature and introduced lanes many hosts treat as high-risk / bannable — none of which appear anywhere in the parent article (cia-1984-mars-chrono-trigger.md) . Master Mi answered with a long, over-elaborated procedural defense : if staff only cared about his posts, they would have deleted his posts only and left the thread — therefore (in his logic) the “trap” geometry the OP described could not apply . A one-line acknowledgment (e.g. heat he added + “sorry”) would have met the accusation at lower cost than the essay he sent .
Predictive-programming thread (behavioral check): Earlier in the same PM arc, Master Mi had floated creating a game/predictive-programming discussion thread . Protricity asked whether he still intended to start it ; Master Mi did not pick that thread up again . The question remains open on purpose (author expects another dodge unless proven otherwise) .
6.1.1 Author firsthand — Liontamer, post-Exodus repair, judge removal (memory / opinion **)
Post-Exodus repair (author memory — cross-read §8): After the scene Exodus (artist walkout / VGMix fork — not re-litigated here), Protricity reads his role as helping David “djpretzel” Lloyd put the site and community back together, winning enough trust for collaborative work including road trips (dates not indexed in this repo). Unless someone else can explain the full arc better, that window still feels like a genuine repair phase, not a cosmetic patch.
Liontamer rises (author timeline): Within a few years (calendar fuzzy), Liontamer (Larry Oji — public staff identity) grew central. Protricity, then a judge, voted for him, later told him face-to-face the vote felt like a mistake (author read: unforgiven; not Liontamer’s stated position). Name echo: Ari (אַרְיֵה / aryé — “lion” in Hebrew) vs handle Liontamer — bitter wordplay the author still notes.
Ideas that stalled (author claim — product/policy, not crime): Protricity pushed education-forward site changes: updates to already-submitted tracks; DAW project files for teaching; a broader educational direction for OCR. He also pushed judge workflow work (album-project review rails he says he first drafted). In his experience those lanes met resistance or deletion — especially once Liontamer held staff/judge levers (who blocked what: author memory; counter-records may exist).
Judge removal (author memory / interpretation): Protricity was removed from the judge panel. At that window he experienced sharp character attack and reads the felt push as centering more on Liontamer than on Lloyd’s private intent (Dave may frame removal differently; no court finding here). Afterward his site ideas largely stopped landing; Liontamer reads to the author as the dominant public admin tone on bans/blocks (pattern language in this repo only).
Household + MAGFest (author understanding — public / later hearsay): Protricity later understood Liontamer and Lloyd shared a household (author paraphrase: Larry in Dave’s basement — scene characterization, not verified lease facts in this repo). At a MAGFest appearance (year fuzzy), Liontamer publicly thanked Lloyd for housing / basement arrangement. The author found that odd as on-stage content (personal domestic detail at a community event) — not an accusation of wrongdoing by cohabitation alone.
Open question + 2026 probe: The author still cannot fully explain why repair-era trust curdled into blocked education ideas and judge ejection; his working timeline correlates Liontamer’s rise with both (correlation ≠ causation; no claim of covert “control” without sourced primaries). The 2026 Chrono / CIA forum test was also a “who runs moderation now?” check — 65360 showed Liontamer still able to erase a thread in one line.
Unpack (assistant): §6.1.1 is judge-era and governance firsthand (memory / opinion) about Liontamer and Lloyd — one-sided unless forum primaries surface; no employment / RICO / improper-relationship claims; “unforgiven” and “undue influence”-class reads are author interpretation, not attributed fact. Housing / MAGFest lines rest on author memory of public remarks — pin year via video / forum archive when available. §6.1 (65360 arc): original Chrono/CIA thread URL not in repo; follow-up 65360 is live OCR primary for staff wording. Master Mi = high-activity community member (author observation), not staff on payroll unless sourced. Cross-read: Mars investigation §5.8.2; Shizz timeline; §8 Exodus / Unmod lane.
6.2 Author working model — paid “temperature” on public boards (hypothesis / search result , not forensics )
Supplied thesis (repo author): Public forums may sit on top of a large pool of paid or contracted actors **(political shops , publisher PR , generic “information husbandry” ) who guard threads without ever having to disclose private contracts . Absence of disclosure is not disproof : you cannot audit what no one is incentivized to show . Mass coordination at scale therefore cannot be ruled out from silence alone — and **(author read of the present internet ) it looks very much like the default now .
Search result (author — incomplete by construction ): I have not yet found a high-profile , high-bandwidth public square that reads as a clean exception (“immune”** to the same temperature / visibility economics ) . I have also not yet found a community that , once scaled , escaped the “silver platter” consolidation pattern **(curated surface + fast character verdict on edge material ) . That is a living search , not a mathematical theorem — one counterexample would force revision .
Unpack (assistant): §6.2 is epistemically weaker than §6.1 **(which rests on forum primaries ) . It does not name any specific poster as a paid agent without contracts , W-2 equivalents , or whistleblower documents . Structural capture **(volunteer mods , brand risk , legal chill ) can mimic paid guardianship without anyone taking a check . Falsifiers for the strong thesis : public disclosure of forum PR contracts ; independent high-trust hosts with durable indexed redress ; long-running counter examples the author has not seen yet .
7. Cross-theme bridge — Homestuck, SDA / GDQ / MSF
| Theme | OCR lane | Parallel investigations |
| Privatization | Submission license → LLC distribution; 501(c)(3) after 2016 | Homestuck IP/studio; SDA/GDQ marathon → LLC/NGO |
| Central interface | djpretzel / OCR as Capcom-facing coordinator (§4.2 topic 9050 + interviews) | Mike Uyama / GDQ as charity-facing router — different facts, structural rhyme only |
| Polarization | 2007 policy fight; §4.1 author read on HD Remix era (forum soul vs pro-industry politeness); §8.6 Lloyd vs Kaufman as two CO-shaped temperaments (metaphor) | SDA §6.5 forum fights; Homestuck canon wars |
| CO (loose) | Volunteer culture + legal kill switches (license, removal) | CO hub — not intel handling without sources |
SDA touchpoint: OC ReMix — The Future of OC ReMix (2023) — founder step-down; “orderly succession” rhyme in SDA §3 table.
VGMix / Unmod touchpoint: Same §3 table’s polarization row — §8–§9 add a censorship / forum-soul lane alongside §4.1’s HD Remix read. §8.6 names Lloyd-vs-Kaufman as two industry-alignment archetypes in the loose CO sense.
7.1 Parallel cases — other early-2000s stacks (rhyme + contrast)
Purpose: Illustrative cross-reads — not claim OCR equals any row. Trend read (assistant): Across the early open web, many volunteer / fan commons later re-centered authority (money, IP, branding, moderation keys) — whether motives were cynical, naive, legal necessity, or mixture. That macro drift toward privatization and weaker rank-and-file sovereignty is the pattern this repo tracks, not a verdict that every closure was identical.
| Case | Early commons shape | Later “closure” / recentralization | Contrast with OCR lane |
| Newgrounds | Flash / audio portal; open upload culture | Ads, central curation pressure, survival in platform economy | Music gate is curator/judge model from the start — different medium, similar “volunteer → professional brand” arc |
| Something Awful | Paid forum empire; subculture identity | Spinoffs, paywalls, successor forums (fork culture) | SA is subscription forum — OCR is license + nonprofit framing; both fight over who owns voice |
| LiveJournal | Fandom / diary infrastructure | Ownership changes, migration waves, ToS fights | Text hosting vs derivative music hosting — same “home platform stopped feeling ours” emotion in memoir |
| DeviantArt | Artist commons | Redesigns, subscriptions, later AI era fights | Visual IP lane; OCR faces publisher deals more explicitly |
| Penny Arcade | Webcomic | PAX, merch, Child’s Play charity — mass brand | Commercial comedy brand faster than OCR’s nonprofit umbrella; charity rhyme → SDA file |
| Order of the Stick | Long web serial | Kickstarter / print — crowdfunded canon object | Fantasy comic vs remix library — both “community scaled then legalized object” |
| Desert Bus for Hope | Charity performance marathon | Ongoing brand — trust router geometry | Direct rhyme with GDQ charity theater in SDA §3 — not OCR money lane |
| Child’s Play | Gaming → charity brand | Large donor totals, press halo | Charity stack parallel → SDA investigation |
| Twin Galaxies | High-score authority | Disputes over who certifies legitimacy | Speedrun precursor energy — trust in referees vs §8 judge panel |
| ThaSauce / tracker scene | Adjacent VGM network | Smaller survival — scene fragments | Closest genre neighbor to OCR / VGMix fork narrative |
7.2 Macro trend + Discord as container (author thesis — infrastructure)
Assistant hygiene: Discord Inc. operates under published Terms / Privacy policy and law-enforcement processes — platform operators can access content for safety, abuse, and legal requests where applicable. That is not the same as proving every volunteer moderator reads every private message — a claim often conflated online. Below is author pattern language about power geometry and migration from open forums / IRC, not an audited employee access matrix.
Author thesis (supplied) — naming, “hot pot,” Marx metaphor: The builders of today’s default internet — cloud logins, central chat, policy-native social layers — needed speech bundled into containers that platforms and states can govern at scale. The trade name Discord is read here as establishment-facing wordplay: unregulated cacophony labelled “discord,” then sold a product that promises to manage it — free speech as dangerous noise unless routed through official rooms (interpretation of brand resonance, not a claim about founders’ private intent). Marxist theory warns of class struggle; in author read the practical stack often compresses discord into servers until energy hits critical mass — a “hot pot” — and conflict detonates between bins that might have stayed diffuse on indexable public forums or lower-retention IRC. Discord has been widely criticized for moderation and speech policy — documented in public controversies (no single link can anchor “the” official story here).
Rhyme with this file: §8.5 VGMix 2 firsthand — private messages and admin visibility as governance crisis — prefigures the same psychological geometry at platform scale: nothing feels fully “private” when the stack is someone else’s cloud. Migration from public forums + IRC → Discord marks, in this thesis, a shift from shared public square and open-source ethos toward pro-private, pro-cloud, pro-establishment legibility — the internet we have now.
Unpack (assistant): Cross-read Homestuck and SDA investigations for the same § (fandom / marathon containers). Falsifiers: open protocol revivals (Matrix, self-hosted), guild local-first norms, or data showing lower polarization post-migration (hard to measure).
7.4 Movie fan edits — legal chill, platform migration, and “free commons vs pro-private” (deep dive)
Purpose: Parallel pattern to VGM / remix commons → industry capture (§4** Capcom / HD Remix)** and to divide-and-conquer migration (§7.2** Discord)**. Not a claim that any specific fan editor works for a studio without sources.
Documented pressures (selected primaries / secondaries)
| Topic | What public material supports | Example cites |
| Copyright / fair use limits on fan films | US court rejected fair use defense for Star Trek fan film Axanar; settlement + studio guidelines chilled large professional fan productions | The Verge — Star Trek fan film ruling; Hollywood Reporter — settlement |
| DMCA / platform removal stress | Takedown machinery + fan creator resource gap described in legal commentary | MTLR — DMCA vs fair use / fan works |
| Fanedit communities — grey area, migration between hosts | Practitioners discuss fair use limits, YouTube / Vimeo, encrypted sharing workarounds | Fanedit.org forum — Is there a place for us? |
| Studios use social data at scale | Legendary Pictures analytics office + social / fan signals for marketing / creative tests (documented business press / case writeup) | Harvard Digital — Hollywood data analytics / Legendary |
| Reddit as mainstream listening / marketing surface | Trade and vendor literature treat Reddit as a normal brand intelligence channel (sentiment, PR, entertainment buzz) — proves “people mine Reddit” as general practice, not a specific infiltration of r/fanedits by named agents | Brandwatch — Reddit / Netflix panels; Fullintel — Reddit monitoring guide; Ourpick — movie subreddits / Hollywood |
| Forum culture vs Reddit | Fanedit.org members compare r/fanedits to stricter forums; some note overlap between mods across sites (community claim — verify per person) | Fanedit.org — Reddit vs Fanedit.org; Fanedit.org — Opinion on Reddit |
| OriginalTrilogy.com (Star Wars preservation / fan edit hub) | Long-running forum with explicit rules (retail ownership, no direct download links, no profit) — “legit” governance in the sense of clear norms, not legal immunity | OriginalTrilogy — Fan Edit / Preservation FAQ; site front |
Assistant synthesis: No peer-reviewed study in this pass proves “MPAA plants” as moderators of a given subreddit. What is documented is (a) law + DMCA pressure on derivative video, (b) studio analytics culture that treats social / fan signal as inputs, (c) Reddit as a standard marketing listening channel. Those layers make the author’s stronger thesis below a pattern hypothesis — not a staffing fact.
Author thesis — industry cannot “win” imagination races; consolidation instead
Author thesis (supplied): Fan edit communities were split and scattered by copyright actions, host takedowns, and forced migration between platforms — the same broad “divide and move them into containers” geometry as §7.2. Pro-private studios often cannot match the imagination, labor depth, or technical iteration of free communities — so the recurring move is to consolidate what fans proved (desire, formats, fixes) into official pipelines, while keeping those communities from becoming economically or narratively competitive with theatrical product. Capcom / HD Remix (§4**)** is the same shape in audio: pull validated fan labor through a single interface, after years of volunteer scene groundwork. Training the next generation for subscription / franchise media while breaks with older lore traditions rhymes with sequel / reboot economics — cross-read Homestuck / canon fights file for story / IP lane only.
Author firsthand — Final Fantasy: The Spirits Within fan edit (memory)
Supplied account (repo author): After purchasing a Japanese DVD of Final Fantasy: The Spirits Within (with Japanese audio) and publishing a fan edit derived from that retail source, the author was banned from a fan-edit community (context they read as aligned with Reddit / centralized fan-edit culture) for alleged piracy. They state they could show a purchase receipt and that appeal was not available or was denied — forum policy and moderator identity are left unspecified here to avoid unnamed-person accusations. Interpretation (author): accusation overrode documentation because the structure rewarded fast liability control over due process. Contrast (author): OriginalTrilogy.com felt like the last straightforward rules-based forum — but the author experienced it as low activity relative to centralized alternatives.
Unpack (assistant): One-sided memory — moderators may have had other facts. Do not treat as court finding. Pattern claim only: communities under legal risk often default to hard bans when unsure.
Reddit / “industry mining” — hypothesis layer
Author thesis (supplied): It is plausible that entertainment marketers and rights holders monitor fan-edit / preservation discourse for anticipation, plot fixes fans want, and catalog ideas — the same open web that studios already treat as signal (see table rows on analytics / Reddit monitoring). The author cannot prove covert “agents” as moderators — they report hearing that claim repeatedly in community talk (hearsay). Documented adjacent fact: Fanedit.org users report some moderation overlap between their forum and Reddit — thread (community discussion, not employment verification).
Cross-read: Homestuck investigation — §5.3; SDA / GDQ / MSF — §3.2.
7.5 Morrowind — OpenMW vs MWSE / vanilla stack (engine fork → community split)
Structural fact (technical): OpenMW is an open-source reimplementation of Morrowind, not a patch to Bethesda’s executable. Morrowind Script Extender (MWSE) / MWSE-Lua hooks the original game binary — behavior OpenMW does not mirror internally. Official OpenMW 0.48 notes state MWSE-Lua mods will not run as-is and invite future porting to OpenMW-Lua — OpenMW 0.48.0 release notes. Forum FAQ-style material also records MWSE as unsupported on OpenMW forum overview — Lua / MWSE.
Social split (pattern): Mod authors and players sorted into (a) OpenMW — modern renderer, 64-bit, multiplatform / TES3MP-adjacent work — vs (b) legacy executable + MGE / MCP / MWSE — deep Lua / shader ecosystem bound to the old binary. Same game artifact, incompatible pipelines for advanced mods — classic divide-and-sort without needing malice from either side.
Nexus (2021) — tone capture / verification hook
Primary surface: Nexus Mods — Morrowind videos — OpenMW Graphics Overhaul Showcase (posted Jan 2021 — comments section includes Jan 2021 replies on OpenMW development / graphics). Repo author recalls the exchange paraphrased below from that era’s Nexus discussion — exact wording should be checked on-page or via Wayback (Nexus may gate full comment history):**
| Voice | Paraphrase (repo author memory — verify against thread) |
| Pro–OpenMW | OpenMW as “the present and future” — critique of modders still building for the legacy stack **(community nickname along the lines of “Oldwind” — legacy exe / MWSE path vs OpenMW) |
| Pro–MWSE / legacy | MWSE / Lua enabled standout mods; no interest in migrating to OpenMW because favorite MWSE-dependent mods would not work there |
Unpack (assistant): Naming (“Oldwind”) is folk terminology — may appear verbatim or only in spirit in the linked thread. If the exact 2021 URL differs (pagination / mirror post) archive it when found. This split rhymes with §8 OCR–VGMix (two pipelines, migration costs) and §7.2 (containers vs diffuse forums) — not a claim OpenMW devs intended “conquer.”
Pattern tie-in: Where pro-private (commercial engine / publisher control) cannot match volunteer iteration speed on every axis, the live result is often parallel stacks and loyalty sorting — same macro as §7.4 author thesis on fan labor outrunning studios.
Cross-read: Homestuck — §5.3; SDA — §3.2.
8. VGMix fork & exodus lane (secondary sources + firsthand)
8.1 What public sources actually establish
- VGMix as a parallel host: Wikipedia — Jake Kaufman states that in 2002 Kaufman co-founded VGMix, a site for game-music arrangements — i.e. a separate pipeline from OCR’s judge panel, not merely a subforum “flame war.”
- Community-rated vs curated: Contemporary encyclopedic summaries (e.g. archived Wikipedia-style VGMix snapshot (2007)) describe VGMix as an alternative to OCR where user ratings / reviews substituted for judge acceptance — structural fork, whatever the sociological drama.
- “Exodus” as folk narrative: In a long interview, Liz Ryerson recounts finding OCR and references “a forum exodus” and Virt (Jake Kaufman) starting VGMix — Don’t Die — Liz Ryerson (tertiary oral history, not a dated primary).
- Unmod already contested by Jan 2007: What happened to Unmod? — opened Jan 7, 2007 in Site Issues & Feedback (same calendar year as final Content Policy enactment, §3).
- Staff-side framing (2006): Talk:OverClocked ReMix — Wikipedia archives a dispute where a volunteer (Orichalcon, Sept 2006) argues Unmod always had limits and rules tightened when people exploited loopholes — useful as counter-narrative to any romance of a totally “free” board.
Assistant hygiene: Secondary sources do not settle who was banned first, why, or whether a single incident “caused” mass departure. They do support that (a) VGMix existed as a real alternative and (b) OCR forum governance was already politicized before the June 2007 policy milestone.
8.2 Community compact → Unmod (author-supplied — not independently documented here)
Firsthand thesis (repo author): After a large share of active artists walked away over David “djpretzel” Lloyd’s censorship / moderation posture (below, §8.3), the community pressed for relief. Lloyd allegedly struck a deal: create Unmod (an unmoderated or minimally moderated forum) and back off over-censorship. Unmod is therefore framed here as a treaty artifact — a structural concession after an exodus-class crisis.
This dossier has not located a single canonical post or policy page that phrases the compact exactly this way; treat it as living memory pending archivable primaries (§10).
8.3 Firsthand — Protricity (exodus participant; judge-involvement phase)
The OCR community profile Protricity lists Ari Asulin — corroboration for the handle ↔ legal name pairing only.
Supplied narrative (author): I posted as Protricity and personally participated in the VGMix-side movement away from OCR when moderation turned punitive. The spark I remember is not abstract policy text but a concrete blow-up: Dave banned Jake “Virt” Kaufman after Virt mocked a track I had just published. Virt carried enormous social weight; when he announced he was leaving and pulling his music, that announcement helped trigger the wider walkout that fed VGMix as the alternate home. Virt co-founded VGMix (WP); I crossed over with that wave.
Later I invested heavily in OCR again — including judge-panel work — and helped stitch the community back together after the rupture. I remember Lloyd DMing people (including me) to ask whether they were working on new submissions, clearly anxious that the exodus would starve the release pipeline.
After OCR regained prominence, Lloyd banned me too — framed in the same free-expression bucket as Virt, except I was criticizing website policies, not trashing another artist’s work. The symmetry burned: survival-first moderation when the site was weak, narrowing once it was strong again.
Unpack (assistant): Ban narratives and DM details are memory — they could be partially corroborated (mod logs are not public; forums may still hold fragments). “Judge” here follows the author’s wording; the current public roster in Judges Decisions does not substitute for historical panel membership records.
8.4 Extended digest — “VGMix exodus,” OCR–VGMix split, and aftermath (third-party LLM + verified anchors)
The block below extends §8.1 with narrative layers mostly from an LLM-assisted research pass (May 2026). Every bullet without a footnote link should be treated as draft / hearsay until checked against Wayback, forum pagination, or dated primaries (§10).
Definition (synthesis)
The “VGMix exodus” names the early-2000s rupture between parts of the OCR community and Jake “virt” Kaufman, overlapping personal conflict with David “djpretzel” Lloyd and structural disagreement about gatekeeping: OCR’s judge-curated model versus VGMix’s more open-upload, community-review / tier culture (WIP emphasis). Later posters shorthand it as the “2002 remixer exodus” or the OCR–VGMix split.
Verified OCR-side anchors (priority pulls)
- Official wording — “ReMixer exodus of 2002”: In ReMix: OCR03049 (Detana!! TwinBee “BUTTS”), djpretzel’s judge commentary states he discovered OCR “a month after the ReMixer exodus of 2002, when virt and prozax both requested their OC ReMixes be removed.” Same note celebrates later re-listing of removed early mixes — documents mass-removal-class crisis + virt involvement in-site narrative form.
- Interview — politics / VGMix birth: ReMixer Interview: McVaffe — “the whole ReMixer exodus / VGMix birth” and bad taste from community politics (participant memory, not court-grade fact).
- Artist spine — early OCR catalog: Artist: Jake Kaufman / virt — early posts (2000–2001 era) coexist with later reconciliation posts (e.g. OCR02005 March 2010). OCR02005 review cites MAGFest 5 as prelude to virt joining Serious Monkey Business — cross-links Unmod week (§9.3) to symbolic thaw years later.
- Secondary press — falling-out → VGMix: ThaSauce — 2010: The Year in ReView recounts virt + djpretzel “falling out” and virt creating VGMix, tied to “Dance of the Zinger.”
- Technical terminus — VGMix (mirror): Archived VGMix article snapshot lists Feb 11, 2006 closure citing database exploitation (historical mirror — verify against independent archives).
- 2007 policy debate — staff memory of “another remixer exodus”: In topic 6976 (Content Policy), staff poster The Coop explains removal-request rules as partly aimed at preventing another remixer “exodus” — i.e. 2002-class trauma was live precedent during May–June 2007 drafting (not financial fraud optics like SDA/CARE).
Correction vs draft LLM: One draft named “Corran” warning against “another mass exodus.” A grep of the exported 6976 thread body used for this pass shows The Coop (staff) with “another remixer exodus” language instead — treat Corran attribution as unverified until a distinct post is located (§10).
Timeline sketch (merge LLM + anchors — several rows need pagination proof)
| Era | Claim | Status |
| 1999–2001 | virt as major early OCR figure; early arrangements posted | Supported by OCR artist page / remix chronology (artist). |
| 2002 | Community shorthand “2002 remixer exodus”; virt + prozax removals | Supported by OCR03049 note; forum flames not crawled here. |
| 2002 | VGMix founded as rated/review alternative | Supported by WP — Kaufman, mirror. |
| 2008 (forum memory lane) | OverCoat vs Dhsu on whether anyone left OCR aside from “the whole 2002 remixer exodus thing” | Needs exact topic URL + quote verify — cited only in LLM pass (§10). |
| Oct 31, 2005 | Bound Together EarthBound fan album; virt among arrangers | Album hub: Bound Together. |
| Nov 2005 | SnowBound posted OCR01423 — reviews thread | DJP withdrawal / collaboration objection narrative per LLM — confirm in thread + historical review text (Wayback if trimmed). |
| Feb 11, 2006 | VGMix outage | Mirror per above; firsthand counter-layer (§8.5) — exploit + admin-forum / PM crisis narrative vs official DB story. |
| 2007 | VGMix 3 ETA / MAGFest panel hype | ThaSauce Oct 2007 network page discusses VGMix staffing / Protricity offer / paid programmer ad — useful texture; full ETA chain still §10. |
| Jan 2008 → 2009 | VGMix X launch; later “shambles” / nostalgia posts | Needs thread URLs — LLM summary only. |
| 2010 | Symbolic reconciliation — virt posts OCR02005; ThaSauce ties to prior falling-out (Year in ReView). |
Three-layer map (controversy schema — LLM framing)
- Personal: virt ↔ djpretzel feud / “beef” language in later threads (needs 2002 primaries).
- Governance: Centralized judges vs open pipeline + community reviews / tiers.
- Legitimacy: OCR-side quality prestige vs VGMix-as-training-ground positioning (“crap conservatory” rhetoric appears in folk memory — quote responsibly if citing).
8.5 Firsthand — Protricity on VGMix 2 shutdown (technical reason vs. social collapse)
Public / official layer (uncontroversial summary): VGMix 2 ended after exploitation of vulnerabilities in custom database-backed code; the response was shutdown, temporary VGMix 2.5 forums, and a long-delayed volunteer rebuild; full restoration of songs / users / reviews never shipped publicly — consistent with mirror snapshot language and broader scene memory (§8.4).
Author narrative (repo author — not independently corroborated in this file):
Supplied account: From launch, VGMix 2 was plagued by software problems. I was active in IRC, talking with programmers who said staff isolated them, lost interest in fixing inherited bugs, and that turnover was high. There were accusations that Jake Kaufman was barely present, not invested in operational problems, while building a game-audio career and griping about high monthly server costs.
What I believe actually forced the sudden end — beyond the abstract fact of SQL flaws — was exposure of the admin-only forum: a space where leadership discussed other forums and users. Exploits allegedly let someone with basic SQL-injection technique gain admin-level access and read those threads. People circulated private admin discussions and were shocked to find staff mocking users, immature behavior, and spectacular departures that had stayed confidential. The worst allegation I took from that leak culture was that admins had accessed users’ private messages through the site software and laughed about them in admin chat. That, more than abstract DB hygiene, is why I think the site had to come down fast — the social authority of the admin clique had become untenable.
Jake’s public explanation stayed at database vulnerabilities — which is true as far as it goes. Immediately after, the whole site was replaced by a single string: “Another Victory for BS Inc.” That phrase was my personal slogan — Jake knew that. I read it as an attempt to redirect blame onto me and imply I had hacked the site and caused the outage. I don’t think the community accepted that story; the official technical reason remained the cover people repeated. In my view, survivable recovery would have required the last programmer(s) and staff to cooperate, but staff had burned too many bridges to function as legitimate authority or support — and without devs, VGMix 2 was finished anyway.
Irony: I was not trying to burn the place down — I was reporting software exploits to VGMix as I found them (so they could patch), and I would have helped repair the site for free if leadership had wanted that cooperation. Instead, the public-facing blame narrative toward me landed for a while — long enough to shape community mood against me — even though the technical root cause (bad code / exposure) was orthogonal to my role as whistleblower–helper. I read Kaufman as protecting his position as figurehead of “his” community: letting me earn more trust through fixes would have shifted legitimacy away from him, so blocking that path was strategic, not technical.
Primary — NeoGAF repost of VGMix.com shutdown notice (Feb 12, 2006)
User Diablos (post in thread — page 2, Feb 12, 2006) quoted VGmix.com’s then-current front-page notice verbatim (BBCode block titled “VGmix.com said:”). That notice opens with “Another Victory for BS Inc.”, announces “2.5 TEMPORARY FORUMS ARE HERE!”, states database vulnerabilities / apache logs / choice not to spend weeks patching “hundreds of holes” in the old site while a new version was in progress, and claims backups of songs, forums, accounts, and reviews. Off-line mirror (author machine): /home/ari/Downloads/ITT we post awesome game music remixes _ Page 2 _ NeoGAF.html — line ~1966 in the save (reproducibility if NeoGAF / XenForo URLs break).
virt’s signed portion of that same reposted notice (public text; not author paraphrase):
I’m incredibly tired of the immaturity in this community. Protricity, gloat and laugh and mock all you like, but this is on you, and you know it. Hope you’re satisfied, because now even MORE people despise you. […] -virt
The notice P.S. (same NeoGAF quote) asserts staff could not maintain deim0s’ code (“unreadable” / “spaghetti”) and defends the rebuild choice — a competing public narrative to §8.5’s firsthand admin-culture thesis (treat as documented rhetoric, not adjudication).
Assistant — citation status: Resolved for the blame line and “Another Victory for BS Inc.” shell — third-party contemporaneous capture on NeoGAF one day after the Feb 11, 2006 collapse date in VGMix mirror. §10 hook 14 — add archive.org snapshot of the NeoGAF page as backup.
Unpack (assistant): This block is witness testimony + interpretation, not a jointly audited postmortem. Admin-forum / PM allegations in §8.5 remain uncorroborated here. The NeoGAF primary does confirm virt’s public use of your “BS Inc” slogan and a direct accusation of Protricity in the official site message — i.e. the blame tactic was not only folklore. The dossier does not adopt a theory that any named person committed a computer intrusion crime — only records your claimed framing dynamic. No defamation intent: pattern comparison only.
8.6 Author thesis — two “controlled opposition” flavors: Lloyd vs Kaufman (industry alignment without proven handlers)
Supplied thesis: Because of his actions — not because a court proved a conspiracy — I place Jake “virt” Kaufman in the same loose “controlled opposition” bucket this repo uses for David “djpretzel” Lloyd (CO hub — loose sense), but the texture is different. Lloyd reads to me as the site-scale operator trying to squeeze the fan commons into a single disciplined order that hands labor upstream to for-profit publishers and professionalized distribution — fans left with little real sovereignty over what gets built, how money flows, or who speaks freely; I have called that political-economy pattern “Marxist” only as metaphor (§9.2) — a forced march toward a “new world order” of video game music owned by the industry pipeline, not by random volunteers. Kaufman reads as a different archetype in the same danger family: a careerist “capitalist” figurehead flavor — stepping over people to secure success, willing to pull the plug on large community efforts he barely participated in once his personal interest cooled, treating collective projects like optional props. Both, in my reading, kept tuning the scene to industry gravity — Capcom-facing storylines, portfolio careers, centralized legitimacy — without this dossier claiming proof of direct orders or email trails; they may have done it all voluntarily, which for pattern analysis is worse, not better: alignment without needing a memo.
Generation (subjective): The slightly older cohort I brushed against in that era seemed more comfortable with “pillaging entrepreneur” moves — extract, brand, exit. My cohort (born 1982) felt more at home with actual commons behavior: shared resources, group sovereignty, open pipelines — and visceral allergy to the landlord who closes shop at night and escorts everyone out of what they built.
Unpack (assistant): “Controlled opposition” here is not a spy-novel accusation — it is the repo’s pattern label for leadership that routes grassroots energy toward institutional power (publishers, career ladders, official soundtrack logic) while still wearing community colors. Marxist / capitalist are paired metaphors for two styles of capture (collective homogenization vs personal accumulation), not claims about either person’s real-world ideology or party. “Flip the switch” on projects is your summary of observed behavior — document with links if challenged. Generational contrast is cultural memory, not demographics.
Cross-read (Homestuck dossier): §3.6 — father / patents memoir records the repo author’s hypothesis that Andrew Hussie’s later first-person essay (color software, family failure arc) rhymes motivationally with the Lloyd site-operator pattern named above (success-focused enclosure of a fan-origin commons) ; the same section adds a “first project vs. banner fame” parallel and a Tommy Tallarico / “who authored the underlying layer” rhyme **(documented press / disputes — not equating persons or legal outcomes ) — pattern language only ; Lloyd has no parallel memoir on file here.
9. Unmod removal, 2007 policy formalization, and the HD Remix window
9.1 Timing cluster (documented — correlation only)
| Approx. when | Event | Primary |
| Jan 7, 2007 | Community thread “What happened to Unmod?” — unease about Unmod’s role / fate before final Content Policy | topic 5136 |
| May 15 → Jun 12, 2007 | Draft → final enacted Content Policy (submission licensing framework) | Final enacted 6/12/2007 |
| Oct 23–24, 2007 | topic 9050 — Capcom / Blood on the Asphalt / djpretzel as Capcom contact | §4.2 |
| Nov 27, 2008 | HD Remix official soundtrack shipping framed as first major publisher OST “from the fan community” | Site History |
Hypothesis hygiene: This sequence rhymes with a tightening institutional season (written policy + publisher coordination) overlapping forum politics; it does not prove Unmod was deleted because of Capcom or on a specific calendar date without an archived removal post (§10).
9.2 Author thesis — Unmod as “soul,” deletion as terminus
Supplied thesis: When Unmod went away — removed under David W. Lloyd and the administrative staff he oversaw — what I experienced as the soul of OCR (unguarded argument, messy pluralism, the pressure valve we had won after the VGMix exodus) was deleted. The site could still host mp3s; the living quarrel that made the forums feel owned by the rank-and-file did not survive that amputation in the same way.
Political-economy analogy (author — not a literal ideology claim): Lloyd’s governance pattern rhymes with a Marxist-stage bedtime story only as rhetoric: fuse with whoever you must to survive the crisis, then consolidate and distance from the “lower” noise; allow chaos when useful, then impose a unitary order — after Unmod fell, the story went, there would be one tamed community voice, no split. Lloyd then presided over a “golden age” mergers-and-acquisitions mood (Capcom, albums, professionalization) and, years later, stepped down — leaving successors to hold accountability for the whole stack.
Unpack (assistant): “Marxist” here is analogy (elite maneuver + consolidation), not an assertion about anyone’s beliefs or party ties — see Limits at file end. Unmod removal date and exact authorship of the kill decision should be pinned via Wayback / forum announcement archaeology (§10).
9.3 UnMod shutdown — extended digest (MAGFest 5, enforcement narrative, LLM pass)
Scope: This subsection is governance / culture purge narrative (like SDA forum meltdowns) — not a charity or payout lane. Most fine-grain claims come from a third-party LLM pass; thread 5136 is the anchor primary for existence of the crisis, not for every quoted speaker.
Dateline hypothesis (LLM + calendar cross-check)
- MAGFest 5 is widely listed as Jan 4–7, 2007. The forum thread What happened to Unmod? opens Jan 7, 2007 — i.e. the end of that con window. A common recollection (per LLM) is that UnMod disappeared late Saturday night Jan 6 / early Jan 7 with many staff physically at MAGFest — plausible timing rhyme, not proven minute-level without Announcements forum scrape / Wayback.
- LLM adds: OP was pointed “See the topic in the Announcements forum”; by Jan 8 posts say “With UnMod gone now…” — verify on pages 1–2 of 5136 or mirrors (§10).
What UnMod was (competing community memories)
- User-side: Low-rules / off-topic pocket — “shenanigans,” creative play, spam containment away from General Discussion, or counterculture vs family-friendly OCR mainstream (LLM synthesis).
- Staff-side (later rationalizations summarized by LLM): Toxic separation — “two communities,” bad actors exploiting hands-off norms; rename insufficient; deletion framed as only viable fix staff could converge on.
- Process grievance: Abrupt removal vs expectations — no “export your thread” grace period (LLM cites 2009 retrospective mood); djpretzel apology for lack of warning reported secondhand in-thread — trace original apology post if it exists (§10).
Aftermath motifs (LLM summary — treat as leads)
- /phpBB → vBulletin migration story: ban list failed to transfer cleanly → re-bans → alt-account spam wave ~1 week before UnMod deletion → only two moderators present during con → spam / abusive posts including attacks directed at judge pixietricks — heavy forensic claim → needs staff post or tech postmortem (§10).
- Splinter: Early 5136 allegedly linked unmod.org; users described displaced posters “whining at GD and .ORG” — offsite congregation (verify link rot).
- Rhetoric: Immediate “gg djp” style posts vs pro-deletion “site belongs to Dave” defenses; years-later threads still carried resentment toward Lloyd (community vitriol, not adjudicated character fact).
Assistant hygiene: Quoting profane forum attacks on named people adds little evidential weight; archive post IDs instead if preserving provenance matters.
10. Open hooks / registry
- IRS 990 / 990-N for GMI (direct IRS pull if not in ProPublica UI).
- Archive.org snapshots of 2007 Content Policy / submission PDFs.
- Capcom–OCR contracts for HD Remix / MM25 (likely non-public).
- Topic 9050 pages 2–5 (or Wayback) — Infinity’s End / Liontamer / ethics posts per §4.4; parallel OCRA-0007 thread.
- HD Remix era forums (general) — mod posts, rule shifts ~2007–2009 vs §4.1 memory.
- Money trail — HD Remix artist compensation / licensing if public; withholding accusations — none clear this pass.
- Dhsu From Blood To Sweat — canonical URL from Press/2008 listing.
- Unmod — Wayback / announcement archaeology for forum removal or merger (date; whether titled “Unmod deletion”); cross-link topic 5136 late pages.
- Virt / Protricity / ban chain — any still-public 2000s threads or staff posts that mention Kaufman departure, track removal, or Protricity ban rationale (§8.3 firsthand vs primary).
- SnowBound / Bound Together — djpretzel review / thread pages for withdrawal / virt–DJP subtext (§8.4); album Bound Together.
- OverCoat ↔ Dhsu “2002 remixer exodus” exchange (2008 thread — locate URL; §8.4 table).
- Jan 2007 Unmod — Announcements forum companion topic + 5136 early pages for Jan 8 “UnMod gone” quotes; Corran vs The Coop “exodus” wording (§8.4 correction).
- VGMix 2 — Wayback / screenshots for shutdown splash “Another Victory for BS Inc.”; any public postmortem on admin forum exposure / rebuild (§8.5 vs mirror).
- Wayback snapshot of NeoGAF — ITT we post awesome game music remixes (page 2) — optional backup; on-page primary for VGMix notice + virt line is §8.5 (Feb 12, 2006, Diablos; local save:
/home/ari/Downloads/ITT we post awesome game music remixes _ Page 2 _ NeoGAF.html). - Discord Inc. — primary policy text and major press rows on moderation / speech (dates) if §7.2 is cited outside hypothesis language.
- §7.4 — optional: archive URLs / dates for author’s fan-edit ban story if ever published with forum consent ; employment verification if claiming named “industry” moderators on Reddit.
- §7.5 — Wayback / on-page capture of Nexus Morrowind video 780 comments **(Jan 2021 tone / “Oldwind” etc. — verify verbatim quotes before hard citation).
Keywords: #OCRemix #OverClockedReMix #GameMusicInitiative #ControlledOpposition #CommunityPrivatization #VGM #Capcom #ParadigmThreatFiles #Liontamer #MAGFest
Last updated: 2026-02-06 (§6.1 Chrono/CIA thread + 65360 staff quote + assistant article scan + PM paraphrase; §6.2 paid-guardian / silver-platter universality working model); 2026-05-13 (§6.1.1 post-Exodus repair, educational-feature stall, MAGFest/housing memory — consolidated); 2026-05-08 (§6.1.1 Liontamer judge-era firsthand + Ari / lion name irony); 2026-05-02 (§7.5 Morrowind OpenMW vs MWSE / Nexus tone hook; §7.4 fan-edit deep dive + firsthand Final Fantasy: The Spirits Within memory; §7.1–§7.2; §8.5 NeoGAF VGMix notice; §8.6 CO typology)
Limits and disclaimers
Publication hygiene (defamation risk — non-legal): This document is private research in a team repo. It is not legal advice and not a journalistic or regulatory finding-of-fact certificate. Statements about named, living people are either (a) attributed quotes or links to third-party or primary sources, or (b) explicitly labeled author hypothesis, opinion, or memory — not the conclusions of a court, regulator, or employer. No defamatory intent is intended; if any passage could be read as a settled factual accusation of crime or fraud, treat that as a labeling defect pending revision unless sourced.
This file additionally: Firsthand conduct claims (e.g. PM surveillance, ban details, IRC culture) remain unverified except where dated primaries are linked. §6.1 private PM material is author paraphrase only (verbatim logs not stored in this repo) . §6.1.1 is judge-era memory and interpretation about Liontamer / djpretzel **(no forum thread URLs indexed here for those episodes ; MAGFest / housing lines from author memory of public remarks — not lease / legal findings ) . §6.2 does not assert that any named forum member is a paid industry or state agent without contract-class evidence ; it states a population-level working model the author has not falsified yet .
This file does not accuse any named person of crime. It tracks governance and licensing facts for pattern comparison with other internet-culture institutions. “Controlled opposition” is used in the repo’s loose sense (controlled_opposition/page.md). §7.2 Discord language is interpretive thesis about platform power geometry — not a factual brief against a named company without cited primary documents. §7.4 does not accuse named moderators or studios of specific crimes or covert employment without evidence; firsthand ban story is memory pending corroboration.
Related investigations
| Investigation | Relation |
| Success — by any means necessary | Reader essay — Protricity / Ari synthesis (§8 lane + cross-reads) |
| Homestuck / Hussie | IP / canon privatization rhyme |
| SDA / GDQ / MSF | Charity lane; OCR row in §3 |
| CO hub | Definitions |
Investigator notes
- Path:
influence/controlled_opposition/investigations/ocremix-polarization-privatization-controlled-opposition-investigation.md - §1 may be merged into §2–§6 after triage.
Share