Glitch

Glitch
I G · CC BY 2.0 · source
Title	Glitch
Developer	Fog Creek Software
Publisher	Fog Creek Software
Platforms	Microsoft Windows, macOS
Released	2011
Genre	Massively multiplayer online game
Mode	Multiplayer

Glitch was a browser-based massively multiplayer online game developed and published by Fog Creek Software that combined social interaction, crafting, and exploration in a persistent world. Launched in 2011 and shuttered in 2012, the project drew attention for its unique design, funding model, community engagement, and the subsequent archival and open-source efforts that preserved assets and code. The title intersected with notable figures and institutions in technology, game development, and digital preservation.

Definition and Types

In the context of interactive entertainment, Glitch refers to a specific browser-based MMO created by Fog Creek Software that embodied mechanics common to social virtual worlds and sandbox games. Variants and related types include indie MMOs such as FarmVille, Club Penguin, Second Life, Habbo Hotel, and RuneScape which share elements of social systems, crafting economies, and avatar customization. Comparisons are often drawn with experimental projects by studios like Thatgamecompany, Zynga, Mojang, Telltale Games, and Kongregate that explored microtransactions, community-driven content, and cross-platform play. Academic and industry taxonomies from institutions such as MIT Media Lab, Carnegie Mellon University, Stanford University, University of California, Berkeley, and NYU Game Center classify such projects under social MMOs, casual games, and cloud-based games.

Causes and Mechanisms

The development and lifecycle dynamics of Glitch were shaped by technological, economic, and organizational mechanisms. Technical foundations drew on web technologies contemporaneous with platforms like Google Chrome, Mozilla Firefox, Adobe Flash Player, HTML5, and services such as Amazon Web Services and Heroku. Funding and business mechanisms involved venture and startup practices similar to those of Y Combinator, Andreessen Horowitz, Sequoia Capital, and corporate strategy seen at Electronic Arts and Activision Blizzard. Community momentum and retention mechanisms paralleled social network effects characterized in studies from Facebook, Twitter, Reddit, and GitHub. Legal and intellectual property mechanisms invoked practices established by entities like Creative Commons, Electronic Frontier Foundation, and United States Patent and Trademark Office regarding licensing, archival, and code release.

Detection and Diagnosis

Diagnosing issues in live online services like Glitch employed monitoring, analytics, and community feedback channels comparable to those used by Google, Amazon, Microsoft, IBM, and New Relic. Performance anomalies were tracked using tooling and methodologies influenced by projects from Datadog, Splunk, PagerDuty, Nagios, and Prometheus. User experience and retention diagnostics leveraged metrics and A/B testing approaches popularized by Optimizely, Mixpanel, and Chartbeat, while social sentiment and bug reports were gathered through platforms akin to Twitter, Reddit, Stack Overflow, and Hacker News. Post-mortem analyses referenced case studies from Valve Corporation, Blizzard Entertainment, BioWare, and academic reviews from ACM SIGGRAPH and IEEE conferences.

Impacts and Consequences

The closure and afterlife of Glitch produced consequences across communities, preservation practices, and indie development discourse. Cultural impacts resonated with communities documented at Internet Archive, Library of Congress, Smithsonian Institution, and preservation initiatives by The Video Game History Foundation. Economic and career consequences affected developers who later contributed to studios such as Twitch, Etsy, Dropbox, Basecamp, and GitHub. The open-sourcing and archival actions paralleled precedents set by projects involving WWF, NASA, MIT OpenCourseWare, and release practices advocated by Free Software Foundation. Discussions of sustainability echoed policy and funding debates involving National Endowment for the Arts, National Science Foundation, and industry bodies like International Game Developers Association.

Prevention and Mitigation

Strategies to prevent sudden shutdowns and mitigate loss in online projects reflect best practices used by major platforms and institutions. Diversified revenue and governance models draw from frameworks employed by Kickstarter, Patreon, Steam, iTunes, and Google Play Store. Technical mitigation and redundancy rely on architectures popularized by Amazon Web Services, Google Cloud Platform, Microsoft Azure, and data preservation standards promoted by Internet Archive and LOCKSS. Community-driven mitigation strategies mirror methods used by Wikipedia, OpenStreetMap, GitHub, and archival collaborations with The Library of Congress and university libraries. Legal safeguards and licensing strategies are informed by Creative Commons and guidance from Electronic Frontier Foundation.

Notable Examples and Case Studies

Key case studies related to Glitch include the game's own shutdown and subsequent archival events, examined alongside analogous histories like the lifecycle of Club Penguin pre- and post-acquisition by Disney Interactive, FarmVille under Zynga, and Second Life’s long-term community resilience. Open-source and preservation case studies reference releases hosted on platforms such as GitHub and initiatives by The Video Game History Foundation, Internet Archive, and university special collections at MIT, Stanford, and NYU. Developer narratives and oral histories feature interviews and writings connected to individuals and companies such as Joel Spolsky, Fog Creek Software, Stack Overflow, Trello, and subsequent teams at studios like Inkle Studios and Thatgamecompany.

Category:Video games