Wrapping My Head Around Micro.blog and IndieWebJason Sadler
After the Facebook / Cambridge Analytica catastrophe and recent Twitter news (and retraction) about support for 3rd party clients, I found myself wondering about Micro.blog again, after hearing about it on Kickstarter a little over a year ago.
On the surface, it’s an indie Twitter-like app, in the vein of the now-defunct App.net, but whereas App.net was a Twitter clone – a silo where all interaction took place within the App.net platform – Micro.blog is more like a bit of glue to create a social app out of the larger web. (Brent Simmons has an excellent post about the differences.) You can pay $5 a month to get them to host your microblog, but by adopting some web standards like RSS and webmentions, you can host your microblog on your own site. If you’re on WordPress you can publish to your site using the Microblog iOS and Mac apps. Replies are a bit of a bugbear, though: they’re handled entirely within Micro.blog if initiated using the app’s Reply functionality, or threaded in properly if you post from your own site with the proper webmention URL.
It sounds a lot like a social RSS reader.
At the same time I was considering all this, I came across another post by Brent Simmons talking about the “IndieWeb”.
The IndieWeb is a people-focused alternative to the “corporate web”.
Even the IndieWeb website doesn’t do a great job of explaining what it is, or what it means to “join the IndieWeb”. As far as I can tell, it’s a collection of practices and technologies that connects independent blog-type websites together into a quasi social network. Sound familiar?
There’s a lot of overlap between Micro.blog and IndieWeb (webmentions being the most significant commonality), and IndieWeb isn’t one monolithic thing. It’s a collection of independent-but-related stuff like IndieAuth (for authenticating yourself online based on your website) and microformats (a feed like RSS, but using HTML classes on your site instead of data on a separate URL). There’s also an overarching philosophy – which I’m not sure I entirely subscribe to – of community, owning your own content, and nostalgia for what I think they’d call the pre-siloed web.
I’ve recently moved this blog from my own Concussion blog engine to WordPress. Concussion was getting annoying to write for1 and there were a few things I wanted to try out that wouldn’t work well on a non-CMS-based system.
I’ve got it all set up for Micro.blog and a bunch of IndieWeb stuff. (You can find me at micro.blog/sadlerjw.) Anything I post here automatically gets mirrored to Micro.blog and Twitter, and replies in either location get routed back to my site as comments.2
It’s interesting stuff, and it was fun to re-implement my site as a WordPress theme, but I feel like some things are missing. For instance, if someone replies to a post on Twitter, the reply gets sent back here as a comment. However if I reply here to that comment, it doesn’t get sent back to Twitter. Alternatively, I could write a brand-new post using the Twitter reply as a “reply-to” URL, and that would correctly be sent back to Twitter, but then the conversation as visible here would be scattered and hard to follow. I’m going to be experimenting with some other WordPress plugins to try to apply some finesse.
So: so far, so good. It does feel a little odd, as someone whose friends aren’t on these platforms, and who’s not a prolific blogger or “content producer”. We’ll see how it goes. If nothing else, it was a fun experiment!3
In the meantime, if your RSS subscription is including my title-less micro posts, and you don’t want that, check out the links on the Feeds page.
I had to add new posts using git, without a way to preview how they would be rendered; my article parsing regex was also failing on a new post I was writing, and for the life of me I couldn’t figure out why. ↩
I’ve got commenting turned off for now while I try things out. ↩