So I’m taking live notes at Blockchain in Journalism: Promise and Practice, happening at the Brown Institute for Media Innovation, in the Tow Center for Digital Journalism at the Columbia School of Journalism, to name the four Russian dolls whose innards I’m inhabiting here.
In advance of this gathering, Linux Journal, which I serve as editor-in-chief (but which I can’t use as a blog, meaning editing it live is maybe do-able but not easy), published When the problem is the story. I wanted it up, on the outside chance that stories themselves, as journalism’s stock-in-trade, might get discussed. Because stories are a Hard Problem: maybe one we can’t solve.
The panels are interesting but so far tell me nothing I didn’t already know, though some of it is interesting at the jargon level.
Okay, here comes a new one: “Token curated registratries, aka TCRs. Mike Goldin of AdChain is talking about those now. Looking him up. Links: Token Curated Registries 1.0, #18 Mike Goldin, AdChain: Token-Curated Registries, An Emerging Cryptoeconomic Primitive.
Observation: blockchain is conceptually opaque, in ways the Internet (the way everything is connected) and the Web (a way to publish on the Internet) are not.
Not quite technically speaking, a blockchain is a distributed way of recording data in duplicate. Or something close enough to that. (Let’s not argue it.) What makes blockchain hard to grok is the “distributed” part. What it means is an ever-expanding copy of the same record accumulates on many different computers distributed everywhere. Including yours. Your computer is going to have a copy of a blockchain, or many blockchains, for the good of the world—or the parts of the world that could use a distributed way of keeping an immutable record of whatever. See what I mean? (Yes and no are equally good answers to that question.)
Mike Goldin just said that understanding blockchain is as big a cognitive leap as it took to grok the Internet way back when. Not so. Understanding blockchain is a shit-ton harder than understanding the Internet.
“Identity procreator type tool” just got uttered. My wife, who is not very technical but knows blockchain better than I, just made two fists and whispered “Yes!” I believe @JarrodDicker of Po.et just uttered it.
So let’s get to the title of this post.
Normally I’d be tweeting this, but right now I can’t. Nor can I write about it in Medium. Both are closed to me, because Twitter hates my @dsearls login, for reasons unknown, and my login to Medium uses my Twitter handle.
When I tried to trouble-shoot my eviction from Twitter this morning, I went to the trouble of creating a new password, alas without help from Dashlane, my password manager, which for some reason wasn’t able to help by generating me a new one. Dunno why.
Deeper background: I’m active on four different Twitter accounts, spread across four browsers. I tweet as myself on Chrome, and as @VRM, @CustomerCommons and @Cluetrain on the three other browsers. The latter three are ones where multiple people can also post.
(Yes, I know there are ways to post as different entities on single browsers or apps, but being different entities on different browsers is easier for me. Or was until this morning.)
So I decided to try getting onto Twitter on one of the other browsers. So I logged out @VRM on Firefox, failed to log in as myself, created the new password through Twitter’s password creating routine, made up a new password (because Dashlane couldn’t help on Firefox either), and wrote the new password down on a sticky.
Then, once I got @dsearls working on Firefox, I logged out, and tried to log in again as @vrm there. Twitter didn’t like that login and made me create a new password for that account too, again without Dashlane’s help. Now I had two passwords, for two accounts, on one sticky.
Then I got in the subway and came down to Columbia, ready to tweet about the #BlockchainJournalism from the audience at the Tow Center. But Twitter on Chrome wouldn’t let me in. Meanwhile, the new password was still on a sticky back at my apartment, and not remembered by Firefox. So I thought, hey, I’ll just create a new password again, now with Dashlane’s help. But I got stopped part way with this response from Twitter when I clicked on the new password making link: https://twitter.com/login/error?redirect… .
This kind of experience is why I posted Please let’s kill logins and passwords back in August, and the sentiment stands.
So now that I’m experiencing life without Twitter, on which much of journalism utterly depends, I’m beginning to think about how we’ll all work once Twitter is gone—either completely or just to hell. Also about my own dependence on it. And about how having Twitter as a constant steam valve has bled off energies I once devoted to doing full-force journalism. Or just to blogging. Such as now, here, when I can’t use Twitter.
A difference: tweets may persist somewhere, but they’re the journalistic equivalent of snow falling on water. Blog posts tend to persist in a findable form for as long as their publisher maintains their archive.
Interesting fact: back in the early ’00s, when I was kinda big in the (admittedly small) blogging world, I had many thousands of readers every day. Most of those subscribed to my RSS feed. Then, in ’06, Twitter and Facebook started getting big, most bloggers moved to those platforms, and readership of my own blog dropped eventually to dozens per day. So I got active on Twitter, where I now have 24.4k followers. But hey, so does the average parking space.
I guess where I’m going is toward where Hossein Derakhshan (@h0d3r)has been for some time, with The Web We Have to Save. That Web is ours, not Twitter’s or Facebook’s or any platform’s. (This is also what @DWeinberger and I said in the #NewClues addendum to The Cluetrain Manifesto back in ’15.) Journalism, or whatever it’s becoming, is far more at home there than in any silo, no matter how useful it may be.