”Micro.blog is now available to anyone. There’s a limit of 100 new sign-ups each day, so that we can better respond to feedback as the community grows.”
Colin Devroe made a good point.
He is subscribed to my main feed and wondered why he didn’t see my Watch follow-up post about the woman on the train.
The answer was that it was a microblog post and, therefore, in the /feed/microblog feed instead.
I never actually considered Twitter to be a microblogging platform, at least not for my own purposes.
At its most basic level your Twitter profile fits that brief (a reverse chronological list of short posts from a single author) but the lack of true ownership and the overarching social aspect meant I could never really see it as such.
Blogging now takes multiple forms but recently feels like it has been co-opted by journalists, despite being subject to editorial constraints, and businesses for “content marketing” – such a horrible term!
While waiting for the Micro.blog app to launch I thought I’d take a different approach with posting now that the site itself is largely sorted.
My main posting routine from Ulysses is largely set in stone, incorporating a mixture of Phoenix and Enlight for editing images but this is a bit overkill for microblogging. I also wanted to automate the selections specific to microblog posts.
Webmentions are a simple way to send and receive notifications that a URL has been mentioned elsewhere on the web.
They supersede pingbacks, having begun as a simpler version, and now have the support of a W3C recommendation for a web standard.
If there’s one thing that backing the Micro.blog Kickstarter has taught me it’s that blogging is really holding its own.
The enthusiasm for self-hosted, independent blogging (beyond microblogging) is amazing and the range of available platforms, from CMS style set-ups to static site generators all of which I was unaware, is diverse.
They say exposure is everything on the social web and best practice advocates cross-posting to multiple platforms to gain the most exposure we can. I can’t help but have a dilemma with this.
In this post I will outline why I wanted to self-host a microblog, what I felt was required to do it properly, how I accomplished the various steps and, where appropriate, explain why I made some of the decisions I did.
I used to be an early adopter, I was among the first to put my name down for anything.
I joined Twitter early before hardly anyone even knew what it was, or what it could be. I signed up for every clone that came after and virtually every other service that appeared.
Way back in 2008 Dave Winer wrote “Microblogging should be decentralized” arguing that reliance on a single, for profit platform such as Twitter was a bad idea.
Admittedly, this was against the backdrop of the fail whale but the idea of a federated service seemed sound – the catch would be that Twitter would have to enable it and build the required tools (or allow developers to build them and we all know how that went!)