Last week I wrote about Micro.blog for iOS version 1.1, which adds several new features including support for multiple photos and longer posts. Today I want to demo how longer posts work on the web version of Micro.blog. Here’s another quick screencast with audio:
The folks at Realmac have been blogging about their progress with Typed.com, a new blogging platform that successfully raised $120k on Indiegogo last year. In the latest monthly report, they announce a new free tier:
“With this new free tier, people can sign-up, use the service, take their time. They can blog for free, for as long as they want, and when they need or want the extra features we offer they can upgrade to a paid account. We also think this will be free marketing for the service, the more blog out there that are hosted with Typed.com then more people will find out about the service.”
This blog is in the spirit of Buffer’s open blog or Ghost’s Baremetrics reports. It’s especially great to see a company sharing numbers when they know they still have a lot of growth ahead of them to get where they want to be.
If you’d like to start a new blog but aren’t sure where to host it, check it out. Typed.com has a well-designed admin UI that is refreshingly simple compared to much of the more bloated web software out there.
It’s also possible to use Typed.com as a microblog. I pointed to some tips for this last year. Since the title of a post can’t be blank on Typed.com, I suggest using a date/time for the title. My new microblog platform is smart about treating those kind of short posts correctly when reading from an RSS feed.
Dave Winer gives 3 reasons why you should be posting short items to your blog, including:
“Maybe your blogging software doesn’t support short items? Don’t worry, if people post more short items the software will adjust.”
I’m counting on this. I have a separate RSS feed for microblog posts, and it doesn’t look great in some news readers because the title is blank. Some folks have asked whether I should include a fake title there — the first few words of the post, or a timestamp. But the RSS spec is clear that title is optional. Only by breaking things a little will RSS readers improve to gracefully support title-less short posts.
Ev Williams announced a batch of new Medium features recently:
“There’s always another level. Another level of polish and power in our product. Another level of breadth to our content. Another level of dialogue and discussion. And another level of progress. Today, we are announcing a slew of updates to bring Medium to the next level and in the process make it more powerful, more fun, more democratic, and more essential.”
Those updates include new mobile apps, @-mention support, a publishing API, and editor improvements. There’s also a new logo. (I know they put a lot of thought into this, and it’s a strong idea, but to me the logo’s design is so clever it’s actually kind of distracting. A little more subtlety in how they’re using depth could improve future iterations.)
Daniel Jalkut blogs about what’s included (and what’s left out) in Medium’s new API:
“One of the most unique aspects to Medium’s API is the provision for specifying a canonical URL and license on a post being submitted to the service. The canonical URL refers to another web location that should be considered the original, or most authoritative version of a post, while the license designates whether the post’s copyright terms stipulate a post is sharable as public domain or under a particular Creative Commons license. These attributes together indicate that Medium expects and encourages users of the API to contribute content that is not intended to be exclusive to Medium.”
While I generally think the trend to centralized writing platforms is bad for the web, I’m happy to see these changes from Medium, especially the API and expanding custom domain support. Medium has grown very slowly and carefully. I expect we’ll see quicker iteration on these new features now that they’re officially out.
In the process of experimenting with Medium posting, Dave Winer shared his take on post title support:
“It seems they have arrived at what I think is the correct answer: posts can have titles or not, and the content system has to be prepared for either case. That’s where this blog was in 1999, before other blogging tools and Google Reader pushed the world toward requiring titles. And then Twitter came along not having titles at all, and the intersection between all the kinds of blog-consuming environments became almost empty.”
I’m very interested in this because microblogging shouldn’t include titles. While Medium is mostly traditional essays, clearly comments don’t need titles, and Medium’s quick-posting UI encourages short posts. I hope this approach will get more RSS readers to gracefully handle title-less posts.