On Substack and AI

This morning, Substack announced that it would be integrating Pangram scans to detect AI content in its posts. I wanted to spend my day revising a chapter of my next book, and later this week, I was thinking of writing a post on the “Memex” I have created using plugins for Zotero and Obsidian that I have coded using AIs to help me in my scholarly work. But instead, I have had to do some serious thinking about the future of my place on the Substack platform.

Now there were plenty of issues with Substack before: it has monetized Nazis, it prioritizes itself over its authors, and—although it billed itself as supporting discovery of small voices
it has recently followed the way of all social media corporations, shoveling large accounts down our throats through its crappy discovery mechanism and creating a social media platform (Notes) that nobody wanted.

The problem is what to do instead—Ghost or a WordPress-based newsletter? Patreon? what? (I would absolutely love your suggestions here)—as hardly anybody uses RSS readers anymore and the old days of sites like Archinect or Things Magazine driving new visitors to my site are over. I just don’t know. So in the meantime, I will be using this feed to announce my articles, but from now on, I will be hosting them where they belong—on varnelis.net, a site that I have owned and built over 25 years.

Now on to my deep, abiding hatred for Pangram and why you should hate it too.

Pangram is an AI for the AI haters. Pangram’s very young CEO, Max Spero, failed to sell his product to universities. At this point, dozens of universities, including MIT, NYU, Georgetown, the University of California, Berkeley, and Yale, have banned the use of AI detectors. The reasons are rather obvious. Much as Luddites on both the far left and far right would hope, we are not going to stuff the AI genie back in the bottle. AI, like Google and the Web, spelling and grammar check, Wikipedia, printed books, or writing itself, is a tool. What matters is whether we choose to use it intelligently. AI detection is notorious for false positives, and universities have wisely understood that calling out a student for using too many em-dashes, negative constructions, or triads is a ticket to a lawsuit. That AI detectors are especially prone to flagging neurodivergent students and students for whom English is a second language only makes it worse. So what was young Mr. Spero’s response? To shame journalists—especially those critical of him—instead. Calling himself a “slop janitor” on X, Spero has accused journalists of using AI in their writing, most notably a journalist for the Guardian.

Clearly, Pangram is trying to exploit the rampant fear of AI in the US, which is, frankly, a bit off the deep end these days. Death threats against people who use AI (even those who acknowledge using it) are not uncommon on left-leaning social media platforms such as Threads and Bluesky. The pathological fear of this technology by many deserves a deep dive of its own, and the Generative Unconscious takes that fear seriously, excavating its origins through a historical narrative; but one also has to ask: cui bono? Pangram uses AI to profit from such fear, a deeply cynical project.

Using AI—even to write an article—isn’t a guarantee of slop, nor is it required to produce slop. On the contrary, Substack’s own On Substack newsletter is full of slop, like “A Business Model That Works for Creators” or “The Global Ideas Exchange,” both of which are proof that you don’t need an AI to write like one. Substack also encourages low-effort use of AI through an image generation tool it offers writers. It even offers AI-generated “podcasts” to authors. So AI-generated images and sound are ok at Substack, but the use of AI in writing is not. Or at least for now. It’s all too easy to imagine that Pangram or Substack will offer an AI humanizer, as Grammarly does, to dodge the AI detectors, for a fee, of course.

Do I use AI? Of course. I am writing two books on AI in contemporary culture and, frankly, if I did not use AI, you should deeply mistrust anything I write. As anyone who has looked at my artwork can see, I have worked extensively with technology for two decades now—from photography to print to code to AI. I have also written pieces such as “Fables of Accelerationism” in express collaboration with AI. Did I use AI to write this article? No, I wrote every word, although I did have Claude Opus look for and correct grammatical and spelling mistakes. But what’s the next step? If we don’t get outright attempts to shame writers or death threats from the wingnuts, I imagine this corporation, valued at over $1 billion, will start evaluating its creators on the basis of whether or not they used AI in their writing even as it encourages us to use AI in our posts. It’s all a bit rich.

Like all tech hysteria, this too will pass. AI writing will get better (Anthropic’s Fable, for example, is much better at writing than any other model) and doubtless someone will come up with a way to post-train AIs to emulate any given author’s work. The war against the AI detectors will come to an end, and these scammy startups will end where they belong, in Chapter 11 bankruptcy protection.

I had other things to do today, and those all got derailed by this nonsense, but between the platform’s support of Nazis and its desire to shovel large accounts down my throat (and yours if you are reading this there), I’m done. It’s been a colossal pain dealing with Substack’s restrictions on length, the way it butchers HTML code, and how it deals with images. You will hear from me soon—assuming there are no more major home appliances breaking down (thanks, Miele), insane thunderstorms spawning tornadoes in town, or other disasters in my life. And if you are on Substack, you will still be able to follow when I publish something. But Substack doesn’t get my content anymore. It cost me a day of research and writing, but thanks to the billion-dollar corporation for making it easy for me to finally take a step I have been pondering for a while.

I am trying to break the Internet

I don’t see how we can remain enthusiastic about network culture. In the decade since the release of the iPhone, the Internet has gone from being a playpen for geeks and outsiders to the primary theater for politics and culture. Even three years ago the thought that a major global leader would use Twitter to announce major policy initiatives would have seemed futuristic and a little naïve. Now we have it and it’s the darkest time most America has collectively experienced in memory. We lurch headlong into a future, but it’s a new bad future.

And, as we seem to be drowning in information, we seem to have lost our ability to communicate and absorb knowledge. Almost nobody reads and writes blogs anymore (please don’t get me started about Medium and the final, thorough destruction of independent content its startup model is premised on). Magazines and journals are well and truly dead. Most books by theorists and academics are soundly ignored too, which is probably a good thing given that theory has become permeated by a neo-fascist identity politics. Outside of the telecocoon of our partners, children, closest friend or two, and immediate work associates, we no longer call each other, we no longer e-mail each other, and we ghost each other as much as we text each other. Earlier forms of Internet culture are also on the rocks: listservs have become replaced by Facebook groups that produce no thought or discussion of any substance whatsoever, and most online forums have died as well. The aforementioned Twitter should be dead, but is kept alive by our desire to see what the lunatic in the White House will say next, and otherwise serves as home to a few misfits and general oddballs. Facebook absorbs everything, reducing all human communication to nothing and algorithmically directs us to only see those posts that give us a fleeting satisfaction. It’s more imagistic spawn, Instagram, is the model of the new Internet, driving us to constantly one up each other with a lifestyle pornography. There are, of course, exceptions—I actually like Reddit and there are some niche online forums that have moments of productivity—but it’s bad out there. I have played my own part in migrating to these awful commercial platforms and regret it. Something must be done. Endless promises and little delivery.

In the case of this site, I’ve resolved to fix matters over and over again, but each time was undone by the content management system, Drupal. Drupal is awful. Way back in 2005, Drupal seemed like a good choice, with its module-based open architecture, and the promise of a content management system that could go far beyond a blog. At the time, I was fascinated with the idea of the networked book and Drupal seemed to offer such functionality built in. Unfortunately, Drupal long ago began to resemble a 1980s American car company, suffering from over-complexity, putting design and user interface last, and unable to got basic features working. A critical flaw is that the development team long ago decided that “the drop is always moving”: each major version of Drupal breaks all the existing plug-ins and themes without which a site is ugly and limited. And therein lies the rub. I should have updated my site eight years ago when Drupal 7 was released, but the horribly botched release of that version would have broken my site thoroughly if it had been possible to update it at all (I am now forgetting if it was Drupal 7 or 8 that did not have upgrade capabilities when first released and the upgrade cycle to Drupal 6 cost me over a month of work). Add to that constant trouble with excessive memory overhead, the obliteration of comments by spambots, together with a general feeling that the whole creaking mess was going to explode like a steam-powered Soviet tractor meant that I knew I’d never be upgrading Drupal. But where to go?

A New Year’s resolution for 2017 had been to redo my site in a new content management system and I upgraded the front end of my site to Kirby. Kirby is fantastic. It took me an afternoon to build the site (I am still running Kirby over at the network architecture lab. In Drupal it would have taken a week. Still, although now I had a decent portfolio together, the blog languished and I made a handful in 2017 and only one post in 2018. In part, this was due to life: I am still cleaning up after the decades of neglect that our house suffered before we bought it, I am spend more time with my family, and I am working on my conceptual art and sound practices. Still, doing anything in Drupal was a nightmare and I stayed away from any substantive blogging.

So it happens that we were away skiing at Smuggler’s Notch in Vermont this week and, as so often happens, we had freezing rain all day. So I decided to finally upgrade this blog and move it to WordPress. I had used WordPress before in Jo-Anne Green’s Networked book project and that had pushed the platform beyond what it was capable of at that time, leaving me with a bad opinion of the platform, but during the intervening years, WordPress has matured into a capable platform (even with the recent growing pains caused by the Gutenberg blogging interface).

Frédéric Gilles’s amazing Drupal to WordPress plugin imported all of the data from Drupal—even comments!—better than I had ever dreamed was possible, better than I would have expected from an upgrade within Drupal. I’ve long loved Indexhibit and use it on AUDC’s site so I was glad to base the new site on Leanda Ryan’s Inxhibit theme (much as I love Indexhibit, it simply isn’t designed for blogging). A day of work later and, although there are some bugs here and there, I am confident enough to replace Varnelis.net with WordPress.

One of the major impediments to blogging that I faced with Drupal is that inputting text on the Web is a nightmare (I can’t tell you how many posts I’ve lost by accidentally hitting the wrong key on Drupal) and uploading text inevitably seemed to introduce formatting issues, no matter how hard I tried. In the case of WordPress, I knew that there were many more tools available at my disposal so I decided to try iAWriter and found it worked flawlessly. I started writing this post on my Mac, seamlessly picked it to my iPad Pro and posted this entry. This is simple, the way Content Management Systems were supposed to be, without losing the independence that blogs make possible.

I’ve also put Feedly front and center for daily reading on my iPad. There are plenty of great blogs out there are acting as a resistance to the managed content of Facebook, Twitter, and Medium and I am setting out to rediscover them. With these changes to my blog, maybe, just maybe, I may once again join them as well.

 

rss frustration or, spoken into the void

Apparently, an undocumented "feature" of upgrading to Drupal 6 is that the path for RSS feeds changed, so those of you who were reading the site through RSS (which is likely most of you) have been are quite behind and have missed a couple of dozen classic posts.

The easiest way to do this is going to be through classic blog view, e.g. https://varnelis.net/blog.

Many apologies on the part of my content management system.

Thanks to Nicholas Nova for pointing this out.