#a writer in theory but not in practice

[nite-puff]

The danganronpa writers really created a character who was the complete antithesis to hope’s peak and some major characters in later games only to pretty much play him for laughs and then kill him off early.

silly little man. representing the very thing the evil organization stood against and actively tried to prove wrong. and yet was still invited to be a part of their school. only to die. silly taka.

[ejunkiet]

okay I need to leave, but I've been poking at wips, and after a month in the trenches trying to find romance authors I like, it's crazy to return back to fanfic and just be like oh. shit. this is good. why can't I find stuff like this published??

[sure-thing-casey]

Exception

the macrofeminism of my twenties but in the small of your Subaru the patriarchy thrived you told me I was asking, asking too much and no question I believed you heard it in my own voice

my fist in the air at the capitol at all the glass above my head but my fist making little crescent red moons in my palms in your bed that I made with sheets that I bought because I thought your skin deserved softness and the sheets would be so lucky

Casey O’Brien, 2024

[mooshkat]

glaring at gdocs as if it's gonna make the words happen any easier

[writeouswriter]

Me: *Has written plenty of great opening scenes that I'm actually quite fond of*

Also me when trying to write a new opening scene for a new project: I have never written an opening scene in my life, what's an opening scene any more, has there ever truly been an opening scene to anything, there is no beginning, so there is no end, there is no one out there watching over this monstrosity, I am in the void, my mind is adrift, how do I open this scene without a key, where did I leave my keys??

[that-one-loz-nerd]

Not being good at art is the most frustrating thing in the world

[lottiecrabie]

need a new part to literally any of the stories you’ve been working on. they’re so good 😭 fave writer frrrrr

i have the parts of my two current stories all planned out as well as other extracurricular (lol) ideas. i just struggle with actually writing things sooo bad

also thank you so much for saying fave writer i’m literally crying🤧🤧

[brujahinaskirt]

remind me not to hire any more 50 year old cishet men onto my feminist thriller publishing house staff no matter how impressive their professional accolades

[aclosetfan]

I don’t understand why Buttercup and Blososm not getting along in fan contents is rare, does it have something to do with a lot of people lack of understanding for these characters? (Seriously most of the time I feel that a lot of ppg fans don’t even watch the show/or actually hated some parts of the show that its actually good) They do seem to clash the most out of all the sisters, but its not all the time. They do seem to team up whenever they’re teasing Bubbles or when Bubbles does/say something dumb

hmm, i really don't know why this happens! I'm assuming people are just projecting their own feelings onto the characters, resulting in conflict between Blossom and Buttercup because those two are the most relatable of the three sisters (in my opinion).

People also like it when leaders and second-in-commands argue, and most people make Buttercup the second-in-command.

Or maybe it's just a "I liked how this one fic did, but I can do it better" situation, so we end up with the same thing over and over and over again.

Also, like I've ranted about before, Bubbles is a hard character to write, so I bet there are some people who don't know what to do with her, and they have to fall back on the other two girls.

[elrondsscribe]

💬

Omg stop making me say positive things about my writing!! Okay well, here’s this bit from chapter 50 of my modern AU, In Theory and Practice, right after Isildur and Valandil have made love in the morning:

“Restful night?” [Elendil] asked.

Val flushed, and kept silent.

“Yeah,” Isil said lightly, moving around his father for mugs.

“And an active morning,” Elendil continued, arching an eyebrow.

Val briefly perished on the spot.

“Dad, oh my God,” Isil groaned, turning scarlet .

The gentle Dad prodding, the awkwardness — I love it so much!!

[martyrbat]

forming parosocial relationships with the people in the medical book </3

[power-chords]

Can you please explain your dialogue theory of fanfiction?

In short, that dialogue, more than anything, makes or breaks a fanfic. What do posts like "He would not fucking say that" and "They would NOT have communication skills that good" have in common? Talk. Characters expressing themselves to one another. The faithful recreation of identifiable speech patterns is weighted heavily in the evaluation of a fic's quality. By "speech patterns" I do not just mean the semantic content of a given character's expression, but idiosyncrasies of style and slang, vocabulary and idiom, even gesture, musicality, and rhythm.

Of course believable dialogue is far from the only thing that makes a good fanfic Good. And there are forms of fic writing, particularly highly abbreviated ones like drabbles and ficlets, that in practice tend to de-emphasize its significance. But if we are talking about the romantic, erotic shippy stuff that is the meat and potatoes of online fandom, dialogue does the heaviest lifting short of the consummation itself. Arguably more so! It's the real keystone to the catharsis, and often the catalyst for it. Is there a confession occurring? A provocation? An evasion or ultimatum? Zoom out, big picture: What is the most potent and fundamental mechanic for developing complexity, tension, and transformation within a relationship, getting it to go from one thing to another? Making these two idiots talk to each other! Often clumsily and indirectly and maladaptively, at the worst possible time and in the worst possible situation, about anything or everything but what they should be — but talk they usually do.

What makes fanfic specifically so challenging and rewarding in this regard is that the talking is as much a feat of translation as invention, because both reader and writer are working off an existing model. Liberties taken with plot, form, and even narrative voice have wider buffer zones; you can get creative with circumventing the events of canon while still conforming to its emotional and substantive essence.

But the training wheels come off the moment you open your mouth to speak in another character's voice. And man, nothing will break a reader's immersion quite like he would not fucking say that.

[headspace-hotel]

okay. so.

i'm reading this book The Origins of the Modern World by Robert Marks

and even from the beginning i was getting this weird feeling from it. I'm always really wary of books that are broad overviews of history that claim to explore big theory-of-everything explanations for very broad phenomena, because history is unbelievably complex and there is so much disagreement between historians about everything.

But anyway I come to this section (in the first chapter)

This writer's opinion is that the Americas seemed so abundant when English settlers first arrived because the Native Americans had been mostly killed, and as a result, the wildlife increased greatly in numbers and forests overtook the farms, creating what appeared to be a natural paradise.

I'm immediately suspicious of this paragraph because arguing that the mass death of Native Americans was good for nature seems really contradictory to the research I've explored, on top of being just...disgusting.

But it doesn't sound right in regards to how ecosystems work either. If populations of animals had recently exploded after millennia of being limited by a major predator, it would cause the plants to be overwhelmed by the herbivore populations. The land would be stripped barren and eroded, and soon the animals would be weak and starving.

So I thought to myself, huh, a citation. I will look at the citation and see what it says.

It's a book called Changes in the Land by William Cronon, who seems to be one of the most important and respected guys in his field. I thought, I have to find this book. So I did, I found the book, and spent like an hour reading through it.

And what I discovered, is that Cronon's book directly contradicts what Marks says in the paragraph that cites Cronon?!

So basically this entire book, Changes in the Land, is a detailed exploration of how the arrival of English settlers, the decline of Native American populations, and the slow transition to European farming and land use practices caused increasing degradation to the ecosystem, beginning very early on in colonization.

Changes in the Land quotes a great array of documents from the colonial period where settlers observed the soil becoming depleted, animals disappearing, and the climate itself becoming more hostile even in the 1600's. It's actually a really fascinating book.

Cronon tells us that Native Americans created lush and abundant conditions for wild animals by causing a "mosaic" of habitats, with different areas representing various stages of ecological succession. With this great diversity in habitats, and lots of transitional "edges" between them, the prosperity of the animal life was maximized. This was intentional, and really a type of farming.

The book essentially explains how European settlers couldn't recognize Native American life ways as "agriculture," they thought the land was just supernaturally abundant all by itself because of its inherent nature, and yet almost immediately after settlers came, the abundance of the land degraded and vanished. The settlers cut down vast amounts of trees, which caused erosion, which destroyed the river and stream ecosystems and starved the soil of nutrients. Destruction of forest caused less rain, and more extreme temperatures. It became a vicious cycle where the settlers had to abuse the land more and more just to survive.

The spiral pulled in Native American communities too, forcing them to turn to more exploitative means of survival like the fur trade, (which depleted the beaver population, which caused the decline of beaver ponds, which harmed the whole forest). It describes how the changing ecosystems left Native Americans with no choice but to turn to European practices for survival, which in turn depleted the land even further.

Even I was surprised to learn just how early on environmental disaster set in, and the incredible extent of it. English farming practices literally reshaped the map of New Haven between the 17th and 18th centuries:

To return to Marks, though...Marks' statement in the excerpt, where he says the "abundance" of animals continued throughout the 19th century, is blatantly false according to the source HE CITES.

Deer were becoming scarce in New England by the 1690's. It was so bad by 1718 that deer hunting was forbidden for 3 years at that time, and by 1800, deer were almost extirpated from New England. The book explains on another page that wild turkeys became so rare that a farmer's manual from the time said their domesticated turkeys were from Turkey—settlers had no opportunity to see a wild turkey and no idea they existed.

Marks is supporting his statement using a source entirely dedicated to contradicting the exact thing he's saying! It's unbelievable.

How does this happen? Did Marks just have his own opinion and insert a famous book that seemed to be on the subject as support, without reading it?

I'm thinking now of all the times I've read a book and seen a citation on a statement and unconsciously thought "oh, well it seems there is evidence, so it must be reliable" when actually, something like this was happening. The array of ways misinformation can be propagated and never be found out is terrifying.

[topazadine]

Writing Post Masterlist

All my posts about writing - plus some I absolutely loved by other writers.

Masterlists by Other People (all good)

"Writing Tips Masterpost" by @deception-united - Deception-United has an incredibly wealth of resources available, far more comprehensive and detailed than mine. Go check it out!

"WQA Post Master Lists" by @writingquestionsanswered - Another fantastic and wonderfully comprehensive resource that covers damn near everything you need to know about writing. Genuinely one of the best free resources on writing that you could find on the internet.

General Advice for a Happy Writing Life

"The Myth of the Martyr Artist" - An incredibly important post, perhaps my most important one ever, that discusses why mental illness is a burden, not a benefit. I have no idea why this even needs to be said, but it does, apparently.

"Advice to Beginner Writers: The Good, the Bad, and the Unpleasant" - How long it takes to become a good writer, what to focus on when learning, and why fanfic is such a useful tool.

"Mindset Shifts: Fanfiction -> Original Fiction" - What fanfic writers should know about deciding to take on original characters and stories.

"Defeating Protracted Writer's Block" - What to do when you find it impossible to write for days, weeks, or months at a time.

"Five Common Anxieties of Newbie Writers, Demystified" - Explorations of five mindsets that can set younger writers back as they learn their craft, including overcompetitiveness, overdescribing, and fearing they're "too old."

"Good Motivations for Continuing to Write" - Why it is crucial to have a passion for writing beyond fame and fortune.

"Extremely controversial writing opinions that will make you mad (but I'm going to say them anyway)" - Things you really don't want to hear, but need to be said. A bit of tough love, including the insignificance of ideas, the cold hard truth about how non-writers react to your writing, and the essentiality of having a well-rounded life.

"Why Mindfulness Is a Key Practice for Writers" - On the need to slow down and let our brain rest - plus some options that are categorically not sitting there in dead silence (boring).

"Writing When Happy" - Wherein I hijack someone's question to discuss the Myth of the Martyr Artist, why we might self-limit because of it, and how to do the impossible: write when we're happy.

"The Neurodivergent Writer’s Guide to Fun and Productivity" by @bookishdiplodocus - Excellent advice on how enjoying the process and reminding yourself that writing is supposed to be fun can help you stay motivated and productive, even when your brain is not cooperating.

"The Glorification of Self-Deprecation in Art/Writing Spaces" by @nicolkoutoulakiauthor - I've discussed before how crucial it is to have a healthy self-esteem when writing, but Nicol does it even better here. Nicol also includes some excellent reframing tactics so you can stay motivated.

Generalish Writing Advice (multifactorial)

"'How Do I Start Writing?'" (Or; A Psychoanalysis of Newbie Writer Fears) - Inspired by the dozens of Reddit posts that ask this exact same thing, often with useless responses. So why do people ask this? I offer my theory.

"How to improve your writing style : a 5-steps guide" by @writer-logbook - Especially great information on why reading widely is so helpful for your craft!

"Some Writing Advice" by @whispers-whump - Especially great discussion of why you shouldn't write what you mean.

"Practical Writing Advice Part 2" by @so-many-ocs - Does what it says on the tin. Simple, easy-to-follow advice that can break you out of writer's block.

"25 Prose Tips for Writers" by @thewriteadviceforwriters - I absolutely love the emphasis on sound and harmony here. As someone whose entire book series revolves around the magic of poetry, of course I think this is incredibly important advice!

"Pacing and Show Don't Tell" by @mylordshesacactus - Two for one deal! First, learn more about why pacing is important; then, look at some examples of the classic advice "show, don't tell." The post does a great job on breaking down what show don't tell actually means and what is not a violation of this guideline so that newer writers aren't confused.

Writing tools

"How to Build a Sustainable Writing Habit Through SCIENCE (Fuck Off, NaNoWriMo)" - Why NaNoWriMo doesn't actually motivate young writers and how to do better through a spreadsheet (yes, really, a spreadsheet). It also explains the importance of intrinsic motivation!

"'I've Outlined Too Much and Now I Can't Write!' (Or: the Double Outline Method for Overanxious Plotters)" - Some of us tend to go absolutely ham on our outlines, to the point where they're practically their own books. But then we also tend to not actually do the writing attached to said outline. Does this mean outlining is useless? Of course not. My method lets you have your outline and eat it too. (.... Wait.)

Worldbuilding

"Stop Making Everything So Damn Complicated!" - Why fantasy (and scifi) does not need to be dizzyingly intricate to be enjoyable.

"Grounded vs. Airy Fantasy" by @aethersea - Excellent breakdown of different levels of groundedness in fantasy and why it's important to understand your own approach.

"Fantasy Guide to Building a Culture" by @inky-duchess - Thorough and methodical analysis of what can create a compelling fantasy culture, including those things that many fail to think about when writing.

"Writing tip - Research" by @pygmi-cygni - Fantastic assessment of the importance of research, including for fantasy stories. As Pygmi-Cygni said, a lot of people claim that they don't need to do any research for fantasy novels, which isn't true! Any parallels to IRL need to be realistic, or you will lose credibility.

Plotting

"How to Find a Plot When All You Have is Characters and Setting" by @rheas-chaos-motivation - This is a common problem for many writers, when you have cool characters or an intriguing setting. This short post can help you kickstart your ideas for how to create an intriguing plot that has built-in tension.

Description

"Remembering Perspective When Writing Descriptions" - Key factors to think about when describing other characters or settings from your POV.

"Description, Momentum, and Tension; Or, How Not to Bore a Reader" - Why, when, and where to put description so that people don't skip over it. Hopefully.

"Writing Notes: Seasons" - Each season has both benefits and downsides. In this post, we look at the negatives and positive aspects of each so you can decide how a particular season may strengthen your themes - plus some descriptions to help inspire you.

"How to Write Smut?" by @unfriendlywriter - Wonderful examples of how to write heartstopping smut.

"How to pull off descriptions" by @fictionstudent - Fictionstudent has a ton of great posts, both about film analysis and about the art of writing. I especially liked this one because it discusses how important perspective is for descriptions and the importance of filling in the details as a character would rather than just throwing it all at the reader at one time.

"How to avoid White Room Syndrome" by @writerthreads - Fantastic and focused advice on how to ensure you're offering readers just enough setting to help them envision the world.

Characterization

"Writing Relatable Characters; Or, Using Human Failures to Your Advantage" - Explaining how you can use character flaws and human needs to create a relatable character. Also explains the basic development of a plot, which is about equilibrium.

"How NOT to Write a Character" - Wherein I give you some examples of annoying characters we want to punt off a cliff so you can watch yourself.

"Writing Strong Female Characters" - Why you should give your female characters a secret goal, as well as how to avoid common 'strong female' stereotypes.

"Writing Compelling Trauma in Fiction: Dos and Don'ts" - How to avoid melodrama and create intriguing emotional wounds for characters.

"Quality Assurance Checks for Character Development" - Thought exercises that can help you differentiate characters, prune down unnecessary characters, develop true chemistry between LI and MC, and avoid having too many POVs.

"Developing Character Agency (Or; Cutting the Plot Strings)" - A discussion of character agency and how to ensure your characters are not bound by the narrative.

"Writing Notes: Thought Distortions" by @literaryvein-reblogs - Some psychological concepts you can use in your writing to add depth to characters.

"Questions about your character’s perspective on love and relationships" by @luna-azzurra - Excellent questions that can help you delve into your character's attachment style, what baggage they may bring to a current relationship, and how to create conflict through mentality.

"How to Write a Confession of Love," also by luna-azzurra - Perfect discussion of how to create tension, the utility of setting, not making it perfect, and including the other character's response.

Revisions

"Common Writing Issues that Reduce Readability" - Examples of fixes for four common issues: double describing, long sentences, overexplaining, and head hopping.

"Differential Diagnosis When Your Writing Is Getting Worse" by @ariaste - Fantastic explanation by a professional writer about why you might feel like your writing is getting worse and what to do about it.

"How to Make Your Writing Less Stiff Part 3" by @physalian - Physalian's whole blog has some excellent advice, so definitely give it a look!

"How to Improve Your Writing" - Also by literaryvein-reblogs, this offers some excellent exercises to help with sentence-level issues, such as modifiers, parallelism, and details.

Publishing

"How to promote your book online : a discussion about social media (and few tips)" by writer-logbook - Great tips about how to get more interest in your book. I especially enjoyed the emphasis on patience and consistency. Writer-logbook has some excellent info overall about the nitty-gritty of writing, so I definitely recommend poring through their blog in general. (That's why they're included here twice!)

Specific Research Advice

"Assassination Methods Through the Decades: A Writer’s Handbook" by @hayatheauthor - A thorough review of different assassination methods, including a section discussing common assassination methods by region!

"How to Write Someone in a Wheelchair" - A group effort! This is a reblog chain discussing body language in manual wheelchairs, the mechanics of power wheelchairs, wheelchair propulsion methods, and a reminder that just because someone is in a wheelchair doesn't mean they can't walk short distances.

"Writing Research Notes: Caves" - Oh caves how I love them. Caves. Let me tell you about them if you want to write about caves. Blessed.

"Writing Research Notes: Horses" - A beginner's guide to horse mindsets, whether horses like working, approaching horses, how to ride, and tips on training.

"Writing Research Notes: Bipolar Disorder" - Written by me, a writer with bipolar disorder! This shares basic facts about bipolar, offers a list of symptoms you can use, and cautions you against spreading misinformation through poor characterization or myths.

"Stop Doing This in Injury Fics!" by @pygmi-says-hi - Discusses some common errors when writing whump/angst. The fever part was especially helpful for me!

"Writing US Military Characters" by @lookbluesoup - An explanation of the habits and mentality of US military characters. Many of these were quite helpful for my fantasy military characters, so you can get a lot of mileage out of these for soldiers in other militaries too!

Little Funsies

"What Painting Style Is Your Writing?" - A short exploration of different writing styles to help you better understand your own approach.

I'll be adding onto this as I continue to scroll through my old likes and, of course, as I find more resources.

[mostlysignssomeportents]

Unpersoned

Support me this summer on the Clarion Write-A-Thon and help raise money for the Clarion Science Fiction and Fantasy Writers' Workshop!

My latest Locus Magazine column is "Unpersoned." It's about the implications of putting critical infrastructure into the private, unaccountable hands of tech giants:

https://locusmag.com/2024/07/cory-doctorow-unpersoned/

The column opens with the story of romance writer K Renee, as reported by Madeline Ashby for Wired:

https://www.wired.com/story/what-happens-when-a-romance-author-gets-locked-out-of-google-docs/

Renee is a prolific writer who used Google Docs to compose her books, and share them among early readers for feedback and revisions. Last March, Renee's Google account was locked, and she was no longer able to access ten manuscripts for her unfinished books, totaling over 220,000 words. Google's famously opaque customer service – a mix of indifferently monitored forums, AI chatbots, and buck-passing subcontractors – would not explain to her what rule she had violated, merely that her work had been deemed "inappropriate."

Renee discovered that she wasn't being singled out. Many of her peers had also seen their accounts frozen and their documents locked, and none of them were able to get an explanation out of Google. Renee and her similarly situated victims of Google lockouts were reduced to developing folk-theories of what they had done to be expelled from Google's walled garden; Renee came to believe that she had tripped an anti-spam system by inviting her community of early readers to access the books she was working on.

There's a normal way that these stories resolve themselves: a reporter like Ashby, writing for a widely read publication like Wired, contacts the company and triggers a review by one of the vanishingly small number of people with the authority to undo the determinations of the Kafka-as-a-service systems that underpin the big platforms. The system's victim gets their data back and the company mouths a few empty phrases about how they take something-or-other "very seriously" and so forth.

But in this case, Google broke the script. When Ashby contacted Google about Renee's situation, Google spokesperson Jenny Thomson insisted that the policies for Google accounts were "clear": "we may review and take action on any content that violates our policies." If Renee believed that she'd been wrongly flagged, she could "request an appeal."

But Renee didn't even know what policy she was meant to have broken, and the "appeals" went nowhere.

This is an underappreciated aspect of "software as a service" and "the cloud." As companies from Microsoft to Adobe to Google withdraw the option to use software that runs on your own computer to create files that live on that computer, control over our own lives is quietly slipping away. Sure, it's great to have all your legal documents scanned, encrypted and hosted on GDrive, where they can't be burned up in a house-fire. But if a Google subcontractor decides you've broken some unwritten rule, you can lose access to those docs forever, without appeal or recourse.

That's what happened to "Mark," a San Francisco tech workers whose toddler developed a UTI during the early covid lockdowns. The pediatrician's office told Mark to take a picture of his son's infected penis and transmit it to the practice using a secure medical app. However, Mark's phone was also set up to synch all his pictures to Google Photos (this is a default setting), and when the picture of Mark's son's penis hit Google's cloud, it was automatically scanned and flagged as Child Sex Abuse Material (CSAM, better known as "child porn"):

https://pluralistic.net/2022/08/22/allopathic-risk/#snitches-get-stitches

Without contacting Mark, Google sent a copy of all of his data – searches, emails, photos, cloud files, location history and more – to the SFPD, and then terminated his account. Mark lost his phone number (he was a Google Fi customer), his email archives, all the household and professional files he kept on GDrive, his stored passwords, his two-factor authentication via Google Authenticator, and every photo he'd ever taken of his young son.

The SFPD concluded that Mark hadn't done anything wrong, but it was too late. Google had permanently deleted all of Mark's data. The SFPD had to mail a physical letter to Mark telling him he wasn't in trouble, because he had no email and no phone.

Mark's not the only person this happened to. Writing about Mark for the New York Times, Kashmir Hill described other parents, like a Houston father identified as "Cassio," who also lost their accounts and found themselves blocked from fundamental participation in modern life:

https://www.nytimes.com/2022/08/21/technology/google-surveillance-toddler-photo.html

Note that in none of these cases did the problem arise from the fact that Google services are advertising-supported, and because these people weren't paying for the product, they were the product. Buying a $800 Pixel phone or paying more than $100/year for a Google Drive account means that you're definitely paying for the product, and you're still the product.

What do we do about this? One answer would be to force the platforms to provide service to users who, in their judgment, might be engaged in fraud, or trafficking in CSAM, or arranging terrorist attacks. This is not my preferred solution, for reasons that I hope are obvious!

We can try to improve the decision-making processes at these giant platforms so that they catch fewer dolphins in their tuna-nets. The "first wave" of content moderation appeals focused on the establishment of oversight and review boards that wronged users could appeal their cases to. The idea was to establish these "paradigm cases" that would clarify the tricky aspects of content moderation decisions, like whether uploading a Nazi atrocity video in order to criticize it violated a rule against showing gore, Nazi paraphernalia, etc.

This hasn't worked very well. A proposal for "second wave" moderation oversight based on arms-length semi-employees at the platforms who gather and report statistics on moderation calls and complaints hasn't gelled either:

https://pluralistic.net/2022/03/12/move-slow-and-fix-things/#second-wave

Both the EU and California have privacy rules that allow users to demand their data back from platforms, but neither has proven very useful (yet) in situations where users have their accounts terminated because they are accused of committing gross violations of platform policy. You can see why this would be: if someone is accused of trafficking in child porn or running a pig-butchering scam, it would be perverse to shut down their account but give them all the data they need to go one committing these crimes elsewhere.

But even where you can invoke the EU's GDPR or California's CCPA to get your data, the platforms deliver that data in the most useless, complex blobs imaginable. For example, I recently used the CCPA to force Mailchimp to give me all the data they held on me. Mailchimp – a division of the monopolist and serial fraudster Intuit – is a favored platform for spammers, and I have been added to thousands of Mailchimp lists that bombard me with unsolicited press pitches and come-ons for scam products.

Mailchimp has spent a decade ignoring calls to allow users to see what mailing lists they've been added to, as a prelude to mass unsubscribing from those lists (for Mailchimp, the fact that spammers can pay it to send spam that users can't easily opt out of is a feature, not a bug). I thought that the CCPA might finally let me see the lists I'm on, but instead, Mailchimp sent me more than 5900 files, scattered through which were the internal serial numbers of the lists my name had been added to – but without the names of those lists any contact information for their owners. I can see that I'm on more than 1,000 mailing lists, but I can't do anything about it.

Mailchimp shows how a rule requiring platforms to furnish data-dumps can be easily subverted, and its conduct goes a long way to explaining why a decade of EU policy requiring these dumps has failed to make a dent in the market power of the Big Tech platforms.

The EU has a new solution to this problem. With its 2024 Digital Markets Act, the EU is requiring platforms to furnish APIs – programmatic ways for rivals to connect to their services. With the DMA, we might finally get something parallel to the cellular industry's "number portability" for other kinds of platforms.

If you've ever changed cellular platforms, you know how smooth this can be. When you get sick of your carrier, you set up an account with a new one and get a one-time code. Then you call your old carrier, endure their pathetic begging not to switch, give them that number and within a short time (sometimes only minutes), your phone is now on the new carrier's network, with your old phone-number intact.

This is a much better answer than forcing platforms to provide service to users whom they judge to be criminals or otherwise undesirable, but the platforms hate it. They say they hate it because it makes them complicit in crimes ("if we have to let an accused fraudster transfer their address book to a rival service, we abet the fraud"), but it's obvious that their objection is really about being forced to reduce the pain of switching to a rival.

There's a superficial reasonableness to the platforms' position, but only until you think about Mark, or K Renee, or the other people who've been "unpersonned" by the platforms with no explanation or appeal.

The platforms have rigged things so that you must have an account with them in order to function, but they also want to have the unilateral right to kick people off their systems. The combination of these demands represents more power than any company should have, and Big Tech has repeatedly demonstrated its unfitness to wield this kind of power.

This week, I lost an argument with my accountants about this. They provide me with my tax forms as links to a Microsoft Cloud file, and I need to have a Microsoft login in order to retrieve these files. This policy – and a prohibition on sending customer files as email attachments – came from their IT team, and it was in response to a requirement imposed by their insurer.

The problem here isn't merely that I must now enter into a contractual arrangement with Microsoft in order to do my taxes. It isn't just that Microsoft's terms of service are ghastly. It's not even that they could change those terms at any time, for example, to ingest my sensitive tax documents in order to train a large language model.

It's that Microsoft – like Google, Apple, Facebook and the other giants – routinely disconnects users for reasons it refuses to explain, and offers no meaningful appeal. Microsoft tells its business customers, "force your clients to get a Microsoft account in order to maintain communications security" but also reserves the right to unilaterally ban those clients from having a Microsoft account.

There are examples of this all over. Google recently flipped a switch so that you can't complete a Google Form without being logged into a Google account. Now, my ability to purse all kinds of matters both consequential and trivial turn on Google's good graces, which can change suddenly and arbitrarily. If I was like Mark, permanently banned from Google, I wouldn't have been able to complete Google Forms this week telling a conference organizer what sized t-shirt I wear, but also telling a friend that I could attend their wedding.

Now, perhaps some people really should be locked out of digital life. Maybe people who traffick in CSAM should be locked out of the cloud. But the entity that should make that determination is a court, not a Big Tech content moderator. It's fine for a platform to decide it doesn't want your business – but it shouldn't be up to the platform to decide that no one should be able to provide you with service.

This is especially salient in light of the chaos caused by Crowdstrike's catastrophic software update last week. Crowdstrike demonstrated what happens to users when a cloud provider accidentally terminates their account, but while we're thinking about reducing the likelihood of such accidents, we should really be thinking about what happens when you get Crowdstruck on purpose.

The wholesale chaos that Windows users and their clients, employees, users and stakeholders underwent last week could have been pieced out retail. It could have come as a court order (either by a US court or a foreign court) to disconnect a user and/or brick their computer. It could have come as an insider attack, undertaken by a vengeful employee, or one who was on the take from criminals or a foreign government. The ability to give anyone in the world a Blue Screen of Death could be a feature and not a bug.

It's not that companies are sadistic. When they mistreat us, it's nothing personal. They've just calculated that it would cost them more to run a good process than our business is worth to them. If they know we can't leave for a competitor, if they know we can't sue them, if they know that a tech rival can't give us a tool to get our data out of their silos, then the expected cost of mistreating us goes down. That makes it economically rational to seek out ever-more trivial sources of income that impose ever-more miserable conditions on us. When we can't leave without paying a very steep price, there's practically a fiduciary duty to find ways to upcharge, downgrade, scam, screw and enshittify us, right up to the point where we're so pissed that we quit.

Google could pay competent decision-makers to review every complaint about an account disconnection, but the cost of employing that large, skilled workforce vastly exceeds their expected lifetime revenue from a user like Mark. The fact that this results in the ruination of Mark's life isn't Google's problem – it's Mark's problem.

The cloud is many things, but most of all, it's a trap. When software is delivered as a service, when your data and the programs you use to read and write it live on computers that you don't control, your switching costs skyrocket. Think of Adobe, which no longer lets you buy programs at all, but instead insists that you run its software via the cloud. Adobe used the fact that you no longer own the tools you rely upon to cancel its Pantone color-matching license. One day, every Adobe customer in the world woke up to discover that the colors in their career-spanning file collections had all turned black, and would remain black until they paid an upcharge:

https://pluralistic.net/2022/10/28/fade-to-black/#trust-the-process

The cloud allows the companies whose products you rely on to alter the functioning and cost of those products unilaterally. Like mobile apps – which can't be reverse-engineered and modified without risking legal liability – cloud apps are built for enshittification. They are designed to shift power away from users to software companies. An app is just a web-page wrapped in enough IP to make it a felony to add an ad-blocker to it. A cloud app is some Javascript wrapped in enough terms of service clickthroughs to make it a felony to restore old features that the company now wants to upcharge you for.

Google's defenstration of K Renee, Mark and Cassio may have been accidental, but Google's capacity to defenstrate all of us, and the enormous cost we all bear if Google does so, has been carefully engineered into the system. Same goes for Apple, Microsoft, Adobe and anyone else who traps us in their silos. The lesson of the Crowdstrike catastrophe isn't merely that our IT systems are brittle and riddled with single points of failure: it's that these failure-points can be tripped deliberately, and that doing so could be in a company's best interests, no matter how devastating it would be to you or me.

If you'd like an e ssay-formatted version of this post to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:

https://pluralistic.net/2024/07/22/degoogled/#kafka-as-a-service

Image: Cryteria (modified) https://commons.wikimedia.org/wiki/File:HAL9000.svg

CC BY 3.0 https://creativecommons.org/licenses/by/3.0/deed.en

[dcxdpdabbles]

DC x DP fic idea: Love Among Fans

Damian Wayne would be the first to admit he had difficulty connecting to others his age. The only thing he knew well was the unforgiving bloodlust of battle and while that helped him fight as Robin it didn't mean it made a well liked Robin.

Civilians flinched away from him, and Police officers stood weary around him. He cares not for the crooks' opinion of him, but he knew it is low.

Worse, other teenage heroes didn't like him around. The Teen Titans had rejected his membership after the three months trial run. Young Justice made excuses after the first two. Even the Outlaws said he was too much to be around, and Todd ran that one.

Of course, his brothers did their best to let him down gently but they could not force the rest of their teams to accept him.

That's why Jon meant so much to him. His best friend had been displeased initially with Damian's behavior, but he had been willing to still get to know him.

Jon had the patience of a Saint. He discovered what worked for Damian and how to help him breach the gaps between them. Damian knew little of what he had missed as a kid, but Jon never made him feel less for it. He carefully explained, opening his world to wondrous new things and Damian tried them all because Jon asked him to.

There was very little he wouldn't do for Jon.

"Have you ever read fanfiction?'" Jon asked one afternoon in the Kryptonian's room.

"No." He grunts, knowing the other wouldn't take offense to the short reply.

Jon smiles, pushing the tablet he had been scrolling on. "You should! This is my current favorite. It's about the show Space Ninjas, you like."

Damian appreciated the show's art and animation, so he took the tablet and clicked on the first chapter. Jon pulled out his phone, and got comfortable on his bed as Damian read.

And read and read and read.

Three days later, he lay on his bed staring at the ceiling, unsure how to deal with real life until the author posted another chapter. He been texting Jon about the story and hosting over amazing character interpretation, theories on what the upcoming twist would be and just about how amazing this piece of art is.

Jon sent back multiple reaction gifs and links to the author's blog, where fans had posted art of the fic. Damian scrolled through them, amazed by how well every piece was, and his eyes caught the drawing Tabet Drake given him a year ago that he had ignored for his paints.

After a moment of thinking, he picked it up, hooked up his computer, and tried to draw the one scene that made the whole fic his newest obsession.

It took three days before he was satisfied with the results. He showed Jon who gushed over it for hours. He convinced him to open a blog to post it and when Damian couldn't bring himself to, Jon tagged the writer in it.

The writer sent him a heartfelt message equally moved by his drawings as Damian was by his writing.

It was the start of his second friendship.

Over time Damian drew more and more. His fanart blog grew in followers as his skills sharpened with practice. He made more pieces of other fanfiction he read, but he always fell back to making unique fan art for GlaxeyAstronaut.

He and GlaxeyAstronaut chatted for years. He didn't know his real name- he could find it easily enough with the Batcomputer but felt it would ruin things if he did- but he knew about him. His online friend was the same age as, Damian, who identified as male, had an older sister and two scientist parents, lived Minnesota and dreamed of being a astronaut.

Damian likewise told him things about himself, mindful never of revealing anything that could pinpoint him a Wayne. And that's how their relationship was for two years.

The writer and his artist.

At one point, Jon had pointed out that Damian messaged GlaxeyAstronaut daily and talked about him just as much. He pointed out how Damian's heart beat raised whenever he saw that silly icon on his notification. He pointed out how flustered he became when he read GlaxeyAstronaut's messages.

But Damian ignored him beacuse surely he was only excited to have two whole friends now.

When they turned fourteen, things changed. GlaxeyAstronaut stopped replying to his message for a week, nearly causing Damian to go find him as Robin until his friend returned to the chat room with a short "I had an accident in my parent's lab. Electric accident. It was bad. It is bad. I may not be able to get on here as much"

His friend became somewhat distant after that, replying three or four days after. Damian figured it was because he was recovering from his accident. Still he tried to be there for him and one day, almost a year after GlaxeyAstronaut's accident he received the message.

"I can't be an Astronaut. My heart will always be too slow to apply"

Damian stared at the words feeling ice cold. Being an Astronaut had always been his friend's dream since he was five, and he could point at the glowing dots to his parents on a camping trip. The fact a medical condition acquired from a lab accident ruined it just left Damain feeling cheated.

He had no idea what GlaxeyAstronaut must feel but he guess far worst.

He had sent a message asking GlaxeyAstronaut if he wanted to call him and talk about it without much thought . They had never done a voice call before, never wanting to breach that uncharted area of online and real life friendship.

But GlaxeyAstronaut agreed, and hesitantly, Damian sent him a link to a chat room with a call option.

The call connected, and the two spoke about the writer's condition how the electricity had run amok in his body, slowing his heart and killing him for a few seconds until his friends were able to bring him back using CPR.

When that became too heavy, they switched to their favorite shows, then brainstormed ideas for collaboration and everything else under the sun.

Damian felt like no time had passed when Father came to warn him to get ready to head out soon, and GlaxeyAstronaut told him he should get started on his homework anyway.

"My name is Danny, by the way," the voice from his speaker said softly. "You don't have to tell me your name. I just....thank you for listening. My best friends and sister hear me but they don't listen to what I saw about.....the accident. It means a lot to me."

"You are most welcome" He pauses for a few seconds before he tacks on "My name is Damian. It is a honor to meet you Danny"

He heard the other boy laugh before the call disconnected any Damian was left staring at his ceiling like he did three years ago.

Back then, Damian's life had changed upon discovering fanfiction and fandoms. Today his life changed upon the startling discovery that Jon had been trying to tell him since he was twelve.

He had a crush on Danny.

How would ge deal with this?