microblog
-
unless you’re actually a bot, scraping my voice to make scam adverts to send to my friends and family – in which case, my respect will be commensurately diminished. ↩︎
- I need a simpler system for online writing. It’s been clear for some time that Wordpress was holding me back. I know: “poor workers blame their tools”, and obviously there’s something wrong with me if I can’t just log in to Wordpress and write a line or two from time to time. But really, it felt as though the user interface was presenting a psychological barrier. Every time I logged in it seemed the WordPress UX had got more complex. Anyway, that’s my excuse. I’m hoping that a switch entirely to micro.blog hosting will help the writing to flow a bit better.
- I like the IndieWeb. Although I had some Indieweb plug-ins set up on my Wordpress site, it didn’t feel as though they were getting much use. The Musky shenanigans at Twitter have made it even clearer that independence on the web is essential and that the true social network is the web itself. Switching to micro.blog will hopefully connect me better, and if I ever change my mind, there’s no lock-in.
- Updating the app feels like a chore. When I checked my hosting dashboard it was clear that there were several insecurities caused by a lack of updating. I just hadn’t gotten around to it for ages. But really, I don’t have much interest in which version of PHP I’m supposed to be using, or what version the plug-ins are - so I’d rather not think about this side of things. If micro.blog can do this for me, I’m not complaining.
- I also quite like Mastodon. Micro.blog has a certain amount of compatability with Mastodon, through the activitypub protocol. So I plan to try that out.
- Writing in Markdown syntax has become more and more intuitive to me, despite its limitations, and I like the relative simplicity of static sites. Micro.blog uses Hugo as its site generator, so now I’m now using Markdown to create static pages.
- for motivation, and
- to leave a record, sharing what I know and
- to encourage you, dear reader, to stop scrolling and go read a good book.
Built-in support for the ‘Web of Markdown’?
A Feature Request: Support for Static .md Outputs & Discovery
Motivation: A Simpler, Less Exploitative Web
I’ve been interested in a simpler, less exploitative web for a long time. It feels like the modern web is increasingly dominated by ads, intrusive surveillance, tracking scripts, and bloated layouts that mock our control over our own reading decisions.
I’ve explored simpler alternative networks like Gopher and the Gemini protocol to find a quieter reading experience. But separate protocols don’t fit smoothly into my existing publishing workflow. They require running parallel infrastructure, managing new server software, and creating extra publishing overhead.
At the same time, recent developments in AI have rapidly turned Markdown into the default lingua franca of the web. Micro.blog users already author their posts in native Markdown, as does everyone using a static site, so converting that source into HTML only to have tools and readers parse it back into text feels a bit redundant. Why not cut out the middleman and directly serve the original Markdown to anyone, human or software agent, who chooses to read it?
The Web of Markdown ‘movement’ (maybe that’s a bit premature) feels like a practical way forward.
Now you can listen to Writing Slowly
As attentive readers of this website will know, I’m happily using micro.blog as the site’s hosting platform. Micro.blog has a surprisingly wide range of features and it comes with several associated mini-apps, which provide easy access to those features. One of the apps is called Wavelength, and it has just been updated. This has inspired me, finally, to actually make use of it.
Wavelength makes it easy to edit and publish voice recordings and now with Wavelength I’ve been recording my voice, reading aloud a number of the longer articles on this site. So if you navigate to one of these posts (nearly twenty of them so far) you might find there’s now a little ’listen’ button, which will enable you to hear me speaking my own written words.
Why bother doing this? Well, so far it’s been quite fun, and you might just enjoy the opportunity to hear the person behind the writing.
I feel these days it’s more important than ever to lean into our own humanity. Sure, you can get a better, more professional experience elsewhere, enabled no doubt by AI automation and by the mimicking of human experience rather than the real thing. But as I’ve pointed out before, my range is me.
There’s an increasing amount of slop online and this is one small way to show my words are handmade and originated from a real person.
I’m celebrating the human touch and trying to respect you, dear reader, as a real person too.1
You’ll be relieved to know that while I might still insist on writing slowly, I speak at a reasonable speed.
So do let me know what you think, and whether I sound like you imagined I would. And if you’d like to subscribe to the weekly e-mail digest, there’s never been a better time to do so.
Talking of which, now would also be a pretty good time to check out my book, Shu Ha RI. The Japanese Way of Learning, for Artists and Fighters.
Simon Willison says:
💬 “I’m effectively using Substack as a lightweight way to allow people to subscribe to my blog via email.”
I already do this easily via micro.blog and it’s a lot less convoluted. I guess he has complete control of the output though, provided he’s happy to tinker like this.
How to get Strata for micro.blog up and running
I’ve decided to make use of the ‘notes’ feature in micro.blog.
This is like making private posts in a blog. But my main use case is brainstorming future blog posts. I want to take notes of half-formed ideas, which may or may not end up as blog posts. They’re not quite draft quality, but I have a hunch they’ll end up as public posts, not just remain as private notes.
The Notes feature is very easy to use. You make notes from the main page by clicking on the ‘Notes’ menu item.
And you can set up multiple ’notebooks’, which you can rename at will.
But there’s also an iOS app called Strata to make the experience easy and fun. That’s what I wanted to try.
📷 Day 26: beverage (@Annie) #mbsept
Art at The National Gallery of Victoria: 100 glasses (1991-92).
glassblower: Michael Hook
engraver: Perry Fletcher.
Can AI give me ham off a knee?
Last night I lay awake thinking about how AI-automated writing is about to change our entire language.
Since AI can easily write everything correctly with perfect spelling and punctuation, one way to show you’re human is to do the opposite. At the time of Shakespeare, spelling was wildly idiosyncratic and people just made it up as they went along. I think this free-for-all might return soon, since it’s a neat way of showing you’re not made of silicon.
But there’s another way we might change our speech and writing to subvert our digital overlords. Ladies and gentlemen, I give you: ham off a knee! It’s something chatbots can’t provide, but that we humans can understand quite easily.
I lay awake last night thinking about cryptic crossword clues (I never do crosswords, but still, that’s rumination for you!). Here’s a clue I thought up. Not a very good clue, since I don’t know what I’m doing:
“For Joyce, recovery leads to pain, we hear (15).”
The answer? “Fine again so ache”.
Doesn’t make sense to you? Well, Finnegans Wake was James Joyce’s fourth and last major work of fiction. I was thinking of it because it’s packed full of homophony (ham off a knee - get it?).
So what’s homophony? Glad you asked. Homophony is simply when you use a word that sounds like another word. But Joyce used homophones in a complex way. His sentences read one way on the page, but when spoken out loud they often mean something else, subverting the original meaning. That’s why he was a genius and I’m not.
But it also struck me that we could start doing this and AI wouldn’t be able to keep up. Admittedly it took Joyce years to finish Finnegans Wake. It’s certainly complicated to come up with whole paragraphs of homophonic writing or speech. But I suspect young people, who are always the instigators of new slang, will be quite up to the challenge.
Alternatively, it’s the new AI frontier. Imagine if you could command something like: “ChatGPT: give me a written account of a 16th Century tourist visit to Venice, which warns of impending alien attack when read out loud.”
Now that would impress me.
Big changes at writingslowly.com
New year, new website (backend)
It’s a new year, so it must be time for new web connections! Well, I finally decided to shift from a hosted Wordpress site to go all in on micro.blog.
It was fairly easy to migrate, just following the instructions. Things already feel easier and less complicated.
Why did I decide to make this change?
Look, I’m not really complaining about WordPress. I like it, and Automattic isn’t Apple/Facebook/Google/Twitter/Amazon, so there’s that. If I had to choose a dictator to rule the world, Matt Mullenweg would be on my shortlist. It’s not Wordpress, it’s me. I’m ready for a change.
Writing about reading
Also, I’m making a commitment to writing about my reading in 2023.
I love reading. Each year I read about 30-40 books and this year I’ll be writing about it here. There’ll soon be a ‘reading’ category at the top of the webpage. Why am I doing this?
Micro.blog has a series of companion apps, one of which is Epilogue. You can set an annual reading goal and every time you blog about a title you’ve finished, your goal moves one step closer to completion.
Micro.blog also has some other great book-related features, including a handly bookshelf, and this is one of the things that made me want to switch.
I keep a private TiddlyWiki Zettelkasten in which I already reflect on my reading, so the only real change is in making it public.
Don’t panic
So that’s what’s new. But don’t worry, whatever happens I’ll still be writing slowly.
Not thinking of writing a novel in November
Well, I didn't sign up to NaNoWriMo, where you undertake to write 50,000 words in a month. Partly, it's just not my way of doing things. I have recently completed a novel manuscript, which took longer than a month. But then again I also wrote a lot of other stuff while I was doing it. As previously mentioned, you can get a lot done while writing slowly.
When I publish a post with no title, where does it go and who gets to see it?
Thanks to Tom Critchlow, I now know a simple JS trick for including the micro.blog feed into a website: