index.md 13KB
title: Discord, or the Death of Lore « ASCII by Jason Scott
url: http://ascii.textfiles.com/archives/5509
hash_url: f6e269f9a6
I chose the life, it didn’t choose me. I could have walked away from it a long time ago, and I’ve certainly shifted my focus over the years. But I still hold the heft and halter, the one standing at the death of all things, and while it means a lot of moments of rescue and recovery, it also means knowing, looking across at that which thrives and bustles, the desiccation and destruction to come. The only part of the fog of the future that’s guaranteed is the moment it switches from theory to a wall of iron and then darkness.
All this to say: Discord.
Twitter, in its own death throes, its own misery, will always stand in its later years as a fantastic tool for raining down misery and pain on others with a simple “quote tweet”, and I’ve been guilty of such on the absolute regular. Few of my tweets maneuvered past 100,000 “impressions”, but this one most definitely did:
The last I checked, that tweet got the attention of over a quarter-million individuals and/or machines, and the next two follow-ups got a smaller amount, but are still worth noting:
There is absolutely nothing new about Discord, say people with experience of IRC. Of course, they’re wrong: Discord has speed, ease of use, and (at this point in time) general societal acceptance far beyond IRC. IRC is a bouncer looking you up and down and asking you to do a small dance of proof of worth before entering a text-only cave of obscurity; Discord added skylights, pretty lights, cross-platform access and verification, and centralization, not all of them great additions but very welcome for their intended audience…. who is now everyone.
I’ve been on well over 100 discords, and I’ve run or in some way moderated a half-dozen. They’re good for fast spinning-up of projects, to glom a bunch of humans into a channel system, and not have to deal with Slack’s oddities, or the ridiculous on-ramp for IRC. At one point I asked for people to send me invites to the weirdest Discords they were members of, and I can assure you, there’s weird ones indeed. And the capacity is notable – walking through the halls of particularly “hot” Discords with literally hundreds of thousands of members, especially when active, is to walk through a space station hosting an all-star concert as it blasts through the darkness.
I have no disputes as the popularity of the places, the things that happen there, and the unquestioned vivaciousness of being the party that never seems to end and everyone wants to join.
I just happen to be the sort of person who notices there’s no decent fire exits and most of the structure is wood and there’s an… awful lot of pyrotechnics being set off.
Discord’s official birthday is 2012, but it’s really 2009, when OpenFeint was created.
OpenFeint is the pile of bones worn into the foundation of Discord telling us it was built on land that will very occasionally flood to great catastrophe. It was founded in 2009, was given a huge ecosystem of plugins and support, gained ten million followers, took in roughly $12 million of known VC investment, was sold to a Japanese company in 2011 for $104 million, and was fucking dead in the ground by 2012. By the flickering light of its Viking funeral, Discord was founded and the cycle began anew.
Spare me the “they learned their lesson speech”, and please store it in this garbage can I’ve already stuffed with the “it won’t happen again” and “you don’t know what you’re talking about” bags I tend to get. It will happen again; it’s just a matter of when.
The main considerations I have are what will be lost.
When the free image-hosting site ImageShack made the realization that they were losing buckets of money hosting images for free, and shifted over to a subscription model that also cut off legacy accounts, deleting them in fact, the question was who would care. Perhaps the original uploaders of the images, too cheap to pay the additional fees of a few bucks per month, or maybe someone who took amusement from this image or that, but probably had downloaded it anyway?
No, what this did was decimate warehouses of lore.
It turns out, in the breadth of time, ImageShack was the unofficial official clearinghouse of diagrams and illustrations of web discussion boards that had limits (or difficulties) hosting images. Sure, most of the boards had software that allowed you to upload to them, but ImageShack was very easy to host with, and the results were fast and simple and could be rather large when needed. This was very helpful for technical diagrams and explanations that would cover (at the time) larger resolutions of graphic information.
So, when ImageShack killed what had been 13 years of these illustrations, they definitely probably saved the business, and they ensured everyone who was hosting with them was truly engaged, but they also lobotomized hundreds, possibly thousands of forums and discussion groups and absolutely wiped an entire collection of reference documents from the web at the same time. Walking through some of them (before they, themselves, died) was walking through a bombed city, its institutional and cultural memory pockmarked with “pay us to see this stuff” placeholders.
Documents are documents. Books are books, recordings are recordings, and so on. As time has gone on, though, I’ve observed the probably obvious-to-others fact that Lore is the grease between the concrete blocks of knowledge, the carved step in an otherwise impossible-to-scale mountain, the small bit of powder sprinkled through a workspace to ensure sparks don’t fly and things don’t burn. Inconceivably odd to the outsider, but vital to the dedicated or intense practice of the craft.
Certainly, the ideal situation is lore is inlaid into a framework of knowledge. As the joke goes, there’s no real conflict between herbs and medicine – we took herbs and the ones that worked became medicine. In the same way, the lore of knots became the rules of the sea and the lore of practiced building that was vital to share across long distances of time and space became engineering. This is an overly simplistic view, but it holds true that “lore” joins “knowledge” in a very haphazard fashion, usually relying on someone so driven to push the process that they create a 400 page behemoth of writing that is gleaned by social calls and favors into the story of How It Has Been Done.
The danger in this process, the potential lost ballast in the rise to the skies, is that the lore-to-knowledge transfer is lossy, messy, and arbitrary. Maybe those in the know want to keep the information to themselves, so it won’t be given to whoever the person or persons are who are laying down the written form. Maybe the chronicler of information has blind spots they don’t know about and not enough people to correct them. Or, more likely, you have to set the “noise filter” of the information to not go down the rabbit and rat holes of contingencies that maybe a dozen or two people will even want to know about, to the favor of that which everyone will need. The outcome is always the same: Lore loses in the long run.
I’ll take a quick diversion to say that we do see attempts to whip lore into shape on a shared basis, be it Quora, Yahoo! Answers, Reddit and Stack Overflow – all of them centralized entities, some of them better than others, and all of them fundamentally unstructured compared to a “book” form factor but infinitely searchable and fungible to the needs of whoever is wandering in, even if they must know three-quarters of the solution to get the actual final part.
Discord, in the decade and change it has lived, and especially once it took off beyond its initial social and classification groups, has exploded exponentially in all the parts it plays on the remnants of the Web. Time and again, we see a Discord rise that represents a subject general or specific, a grouping of dozens or hundreds of folks interested or entangled in the subject, and then a massive growth of channels and direct messages rising from that clumped “community”. Some of the results are droll mostly-silent channels with occasional flares of conversations, while others are waterfalls of discussion and write-once read-never rants and dumb questions, punctuated with someone asking a question for the hundredth time and someone answering a different way.
There are more Discords than you realize, and more lore pouring into them than anyone can truly comprehend. They are not the exclusive spigots of lore but they’re a major pipeline, a notable artery on Knowledge’s Heart that we would definitely notice if, for whatever reason, it was clogged with Mission Shift or New Opportunities cutting it off.
The two-line discussion at the center of my first public lambasting of Discord’s nature is telling, not because of the individual who responded as they did, but the situation they were unintentionally highlighting:
EmoSaru is not evil or a paragon of Knowledge’s Destruction; they’re a shopkeeper noticing that fresh tomatoes aren’t selling as well as ketchup and ketchup is cheaper to keep on the shelves and lasts longer, and everyone who might come along and complain about losing fresh tomatoes aren’t buying said beloved tomatoes. They’re following the wind. Only fools stay in the field when the herd has gone in from the rain. I highlighted them just because the exchange was, as they say, el perfecto.
My grandmother would always scold me, lightly of course, about my cartoons I’d draw on paper because I wouldn’t use both sides of the page; my personal belief that it would bleed into each other wasn’t part of the argument, just that she had long memories of doing without and making do with little and she wanted me to not waste the (temporary) bounty before the next (inevitable) hardship.
To that end, I am, again, the angel-winged herald of the Death of Discord and I only wish to highlight what might blunt the pain of the inevitable decay and destruction of what it is.
In the unlikely event that Discord sits across from me at a table and asks What Exactly Do You Want To Leave Us Alone, my list of demands is both logical and impossible:
- Right now every channel is meant to be both transient and permanent. I know that’ll never change, so create a new “Lore” or “Archive” channel where the moderators tap on wisdom and preserve-forever statements or threads, and they get added over there. Think of it as “Pinning” but they’re pinned forever and there’s a bunch of them.
- Make it possible to export this Lore/Archive channel to a reasonable file, like JSON or any other text format. Hell, make it a feature for “Discord Nitro“, which is obviously a part of the “oh crap, we need to prove we can make money with this thing” phase of the cycle you’re now entering.
- At the very least, consider some sort of “FAQ” feature/contingency that does a similar function to the old-style FAQs, so people can contribute sets of knowledge in a structured manual instead of an endless search for terms from everyone who ever touched a server.
The unlikely event of them sitting with me across a table is doubly joined by the unlikely event they would implement anything like I’m asking for.
Consider this me walking through and pointing out the wood structure and lack of fire exits, and if someone did the work, even if it cost a little extra, a lot of people will be a little less sad down the line.
And when the inevitable does its inevitable thing, maybe we can all sit down and talk about what could have been.
…just not on Discord.