Today I posted another episode of my daily podcast Timetable. It’s a short episode about the MarsEdit 4 release and why even competing apps should be compatible and embrace the open web. Here’s a transcript.
Today, MarsEdit 4 shipped. I posted to my blog with a link to the new version, and I included some comments in the blog post about using MarsEdit with Micro.blog.
Congrats to Daniel. This has been years in the making. It’s great to see it come out, and we’ll be talking more about this on my other podcast Core Intuition later this week.
Even if Daniel wasn’t my friend and co-host of Core Intuition, I’d still be excited about MarsEdit, because more blogging software is a good thing. The Mac version of Micro.blog kind of competes with MarsEdit, since you can use Micro.blog to post to WordPress, just like you can with MarsEdit. But it’s also a nice complement, because you can use MarsEdit to post to blogs that are hosted on Micro.blog. And MarsEdit is full-featured and has more features that you might want to upgrade to, even if you’re using Micro.blog.
And this is how I think software should work, and why the open web and open APIs are important. You should be able to switch between apps without changing everything.
You should be able to use MarsEdit to post to your blog. You should be able to use Micro.blog — the Mac app or the iOS app — to post to that same blog.
Imagine if you could use the official Twitter app to post to Facebook. You open Twitter, you click new tweet, and then you click in the destination (somewhere in the UI), and you select Facebook instead. And instead of going to Twitter, it goes to Facebook.
Sounds crazy. How could that possibly work? Why would Twitter or Facebook ever allow something like that?
But that’s how it should work. We are so used to these silos and these apps that are not compatible with anything, that we just accept it. But that’s how it should work.
You should be able to use multiple apps to post to different services. And that’s what’s happening with apps that are built with some compatibility in mind, especially on IndieWeb standards. That’s what’s happening with MarsEdit and Micro.blog, although on a much smaller scale.
I’ve been thinking about how much work we have to do to reach the audience of potential indie microbloggers. Last night, I attended AustinRB, a local meetup here in Austin for Ruby programmers. There was a great talk on metaprogramming — really enjoyed it. And as I mentioned yesterday, Tom Brown, who is also helping me out with IndieWebCamp planning… He gave a talk on the IndieWeb.
And listening to questions from the audience, it was just so obvious how far we have to go. Everyone is so used to Twitter and Facebook and Instagram, that in a way we have to outline the IndieWeb and services like Micro.blog in a way that mainstream users of other social networks can relate to.
It’s a big jump to go from only thinking about Twitter, to all of a sudden thinking about your own domain name, sending replies between independent web sites perhaps, to thinking about a timeline that is based on feeds from all over the web. It’s a big jump.
And in a way, it’s kind of discouraging when I think about making that case for how the web should work. It’s a massive task to explain the value of the open web and the danger of relying on 100% centralized networks.
But on the other hand, there are a lot of people in the world, a lot of people who want to write on the internet, who care about what they say and how they say it. WordPress powers 29% of the web.
The market is there. It’s just a matter of reaching everyone. And so that’s encouraging.
And it starts in communities like the IndieWeb. And hopefully in the community we’re trying to build on Micro.blog.
It’s not too late to register for IndieWebCamp. It’s this weekend in Austin. Go to IndieWeb.org. I hope you can join us. There’s a lot of work to do to build the web that we need. Thanks for listening today.
✴️ Also on Micro.blog