Doug Lane is writing a series of blog posts about what real-world use cases for Micro.blog could help attract more mainstream users to the platform. It starts with this:
One of the biggest challenges that Micro.blog faces with its upcoming public launch is how to make the jump beyond its early adopter base of blog enthusiasts to “regular people”. It’s tempting to daydream about everyone from teenagers to grandmothers abandoning their social media silos en masse and simultaneously raising “Indie Blogger” flags, but that’s probably not realistic.
He then follows up with a few ideas. I think this approach is exactly right: carve out several niches that are perfect for Micro.blog and focus on those in marketing, providing as much value as possible for those users, then expand to more mainstream users from there.
Squarespace actually does a great job at this. The first thing you see when you click sign up — before being prompted to create an account — is to choose a template for your web site. At the very top of the list: a wedding blog and a product catalog.
Photoblogging and linkblogging are still some of the most common ways people use Micro.blog. From a business perspective, I also like it for product news. Earlier this year I posted some ideas for how to use a microblog.
I sent an update to Kickstarter backers today. I wanted to point people to the new Mac app for Micro.blog, and also show off some of the great photos that Micro.blog users have been uploading this week as part of the photo challenge. Here’s the email.
Hello Kickstarter backers! Today we’re wrapping up the 7-day photo challenge on Micro.blog. The challenge was a suggestion from the community: @douglane posted to his microblog with themes to inspire more people to take and post photos.
I’ve loved seeing all the new photos. Here are just a handful of the many photos that have been posted over the last week.
We also recently released version 1.0 of the Micro.blog app for macOS Sierra and High Sierra. This is the best Micro.blog user experience yet, with a timeline, posting to your blog, photo upload, and a new Discover section for finding posts and users to follow.
You can download the Mac app here.
I’m also continuing work on the Indie Microblogging book. I’ll be sharing more about the book as soon as I can. Thanks for your support!
We’re holding an IndieWebCamp in Austin next month! This is a 2-day event — Saturday and Sunday, December 9th and 10th — for anyone who wants to learn more about the IndieWeb, discuss web standards and tools, or just hack on your own web site. We’re lucky to have IndieWeb co-founders Tantek Çelik and Aaron Parecki in town for the event.
There was another IndieWebCamp in Berlin last week. Neil Mather had a great blog post about his experience there:
It ran over 2 days, with day 1 an unconference with a number of discussions, the topics and schedule decided entirely by participants in the morning. Day 2 was hack day, with everyone working on an indieweb related bit of work, be it on their own website or on a shared project.
IndieWebCamp Austin registration is open now. Tickets are just $5. Looking forward to planning some next steps for Micro.blog over that weekend. Hope to see you there!
Over the weekend I opened up a WordPress importer for Micro.blog-hosted sites. Now that Micro.blog can serve as your primary web site — with personal domain name, short and long posts, themes, and pages — some users may want to consolidate their older WordPress blogs to Micro.blog. I’ve just finished a round of testing and bug fixes with a couple sites, including the 2000+ posts on my 15-year-old WordPress blog.
Micro.blog has always had great support for WordPress. If you host on WordPress and want to bring your posts into the Micro.blog timeline, all you have to do is add the WordPress RSS feed. This new importer is for people who want to migrate their whole site to be hosted by Micro.blog, not just mirror posts to the timeline with RSS and continue to use WordPress for hosting.
To access the importer on the web, click on Account → Edit Domains & Design → Import. It will prompt for a WXR file, which you can export from your WordPress site under WP Admin → Tools → Export. WXR stands for “WordPress eXtended RSS”, which is an RSS file with some extra WordPress metadata.
It’s important to note that the WXR contains post text, but not file uploads. To solve this, Micro.blog parses the HTML for all your posts, looking for
img tags. It then downloads those referenced photos and adds them to your Micro.blog-hosted site. For this reason, it’s important that you keep your old WordPress site online until the import has finished. (The importer does not currently support WordPress photo galleries.)
If you try the importer, I’d love to hear what you think. And of course you can add a new Micro.blog-hosted site for just $5/month under the “New…” menu.
For the initial rollout of Micro.blog, we had a bunch of pins you can unlock, to encourage people to blog more. For example, pins that get unlocked after a certain number of blog posts, or when you upload a photo. We also added a couple of new time-based pins for special events, like mentioning “iPhone X” during the Apple event last month.
Today I added a Halloween pin. You can see some of the pins for my account in this screenshot:
I also talked about this on today’s Timetable. Happy blogging! 🎃
I’m glad to see #WomenBoycottTwitter getting some traction. Complaints come and go, but a real break sends a stronger message and gives us perspective. I would never have started Micro.blog unless I had spent enough time away from Twitter to see a better way. It’s not enough to just complain.
Very little has changed since I wrote my 10-year Twitter post last year. If you wait for Twitter to solve all the platform’s problems, you’ll be waiting a long time.
I had first suggested a 280-character guideline for microblog posts back in 2014. As I’ve said many times since then, and through launching Micro.blog, I believe expanding the limit will make for better conversations, less mangled punctation, yet still remain short enough that it encourages quick posting.
Twitter announced today that they are also experimenting with a 280-character limit! From their blog post:
We understand since many of you have been Tweeting for years, there may be an emotional attachment to 140 characters – we felt it, too. But we tried this, saw the power of what it will do, and fell in love with this new, still brief, constraint.
They focus most of the announcement on explaining how the current constraints are different for some languages, like Japanese, which can fit far more words into 140 characters. That’s true, but it glosses over the most important point.
Longer text allows for more thoughtful posts, fewer misinterpreted shouting matches, and Twitter desperately needs to improve the tone of conversations on their platform. I’m a fan of this change.
As I plan for the iPhone X pre-order, I wanted to write a blog post about all the iPhones I’ve bought, and when. I’ve skipped a few generations, and even made some seemingly oddball choices like getting the iPhone 5C when all my friends got the 5S. In the process of searching old blog posts to confirm whether I even bought the 3G or waited for the 3GS, I found this old blog post about WWDC 2008.
In the post I had collected 95 tweets from myself and others during WWDC. This was 9 years ago, so it’s a bit of a blur. But reading them again brings back memories. These old tweets are gold.
If I hadn’t collected the tweets, I would never find them again. And if anything changes at Twitter, they could just as easily be lost. Remember, it wasn’t that long ago that you couldn’t go back more than 3200 tweets in your timeline. Searching old tweets is still impossible in third-party Twitter clients.
Obviously I’m all-in on indie microblogging. I post to my own blog and let Micro.blog sort out cross-posting a copy to Twitter. But looking at these old tweets, I’m just struck with how foolish it was to ever post content exclusively to Twitter. It was an assumption that today mattered more than tomorrow, when the opposite is often true.
A photo is the most clear expression of this truth. Taking a photo doesn’t improve the moment. It’s for later.
Twitter in 2008 was a mix of microblogging and conversations. It was writing without pretense, with no expectation of likes and follower counts. It felt ephemeral, and maybe it still does to many Twitter users today. But you never know when you want that fleeting comment to actually last, and if you don’t control the post, there are few guarantees that it will.
In announcing plans to move A List Apart away from advertising, Jeffrey Zeldman writes about the decline of independent web sites:
In recent years, we’ve seen our rich universe of diverse, creative blogs and sites implode—leaving fewer and fewer channels available to new voices. As more content centralizes into a handful of all-powerful networks, there’s a dreary sameness in perspective and presentation.
I don’t know what the new A List Apart will look like, but if they can encourage designers and developers to embrace independent blogs again, I’m all for it. I like the way Zeldman has framed the change for A List Apart.
It used to be that A List Apart’s most popular authors were all frequent bloggers. I think the attention on Twitter instead of personal sites has effectively created a gap of lost years for many blogs: long stretches of time with very few if any posts. Perhaps Zeldman’s post is an indication that this trend has already reversed.
Gabe Weatherhead recently made some points on Macdrifter about the decline of indie blogs — that podcasting is a cheap substitute for written posts, and that tweets and link-blogging have killed thoughtful commentary:
I want to hear opinions and ideas from good writers, not pull quotes with a trailing off-the-cuff remark.
It’s a good post, but I see his conclusion differently. The solution isn’t fewer link blogs, but more of them. By taking microblogging back from Twitter, we create a natural place for traditional blogs to grow. Indie microblogging is the gateway drug for long-form content.
To everyone reading Zeldman’s post about A List Apart and nodding your head, retweeting the link, clicking the like button… Dust off your blog and actually post about it. A better web is built one page at a time.
Tonight we’re starting up a local Austin chapter of the Homebrew Website Club. This is a group from the IndieWeb community which already meets regularly in San Francisco, Portland, other cities, and online.
From the IndieWeb wiki:
Homebrew Website Club is a bi-weekly meetup of people passionate about or interested in creating, improving, building, designing their own website, in the same structure as the classic Homebrew Computer Club meetings.
For Austin, the first meeting will be 6:30pm at Monkey Nest Coffee, 5353 Burnet Rd. Everyone’s welcome. Bring ideas for your own web site, questions about Micro.blog, or just grab a coffee and hang out. We’ll meet in the extra room at the back of the coffee shop.
As I mentioned in this morning’s post about Medium, it’s important that Micro.blog-hosted sites can have their own domain name. Some people use their microblog to supplement an existing web site. Others use Micro.blog itself for hosting their full web site, because the focus on short posts makes the site easy to update.
Today we’re introducing a new feature for hosted microblogs: custom web pages. These can be used for expanded “about” pages, contact information, lists of current projects, essays, or whatever you want to write about on your web site. Micro.blog pages use Markdown and are automatically included in the navigation for your site.
Here’s a screenshot of an example page being edited:
If you have a Micro.blog-hosted site, check out the pages list under Account → “Edit Domains & Design”. Enjoy!
Dave Winer isn’t optimistic about the recent Medium changes:
We’re in the long tail of the demise of Medium. They’ll try this, and something else, and then another thing, each with a smaller probability of making a difference, until they turn it off.
This has been the concern with Medium since the very beginning. Because they defaulted to Medium-branded user blogs on medium.com instead of your own blog at a personal domain name, there was a risk that if Medium didn’t work out as a business, many great posts would disappear along with the service. You might get more readers in the short-term, but it’s a bad trade-off when links break and you have to start all over again.
Nick Heer wrote about the “sameness” of Medium sites — how the sites blur together as just pages on Medium’s platform. Several prominent sites have left:
Earlier this year, Film School Rejects and Pacific Standard moved away from the platform; this month, the Awl announced that they went back to WordPress with their old custom theme. The Ringer and Backchannel also left Medium. Once again, I can tell those sites apart from each other.
I think Medium has good intentions. But the premise was wrong, with an emphasis on medium.com/@username URLs that aren’t portable, and no obvious way to get a custom domain. Getting this right is IndieWeb 101.
That’s why on Micro.blog the microblogs are username.micro.blog by default. It sounds like a small thing, but that difference is everything. It’s easy to swap out for a personal domain name, with free SSL hosting, multiple themes, custom CSS, and it’s based on Jekyll so that it can be moved to any host.
Medium is stumbling forward, trying to find the right path because their initial foundation wasn’t right. I hope they get there.
Many people are initially confused by Micro.blog because they are expecting a strict clone of Twitter. They are expecting another App.net. But as I said in the Kickstarter video, clones of Twitter and Facebook have come and gone. They’ve all failed. A different approach won’t guarantee success, but it is required to have a chance.
I plan to stay the course. I’m inspired by the work of the IndieWeb, which was founded 6 years ago and is still gaining momentum today. I hope that the solar eclipse photos posted to indie microblogs today will last through the next North American eclipse 7 years from now, and longer.
There was a great article on AltPlatform about how compatibility between new blog-focused platforms could eventually become bigger than any one social network:
Open source tools like WordPress, 1999.io and Mastodon.social are creating many small networks of publishers, and popular tools like Twitter and Micro.blog could peer with them. If all of the social networks outside of Facebook interoperated at some level, they might eventually “flip the iceberg” and become the dominant form of social networking.
It’s going to take a while, but I have no doubt that this “flip” is exactly what will happen. The entire web should be the social network. It’s too big of an idea to be contained on a single web site.
I recently added “repost-of” support to Micro.blog’s Micropub API implementation. This lets you pass an extra URL — the post you’re writing about — in clients like Micropublish. There’s deliberately still no concept of a retweet or repost, though.
When I wrote last year about Instagram and reposts, I was concerned with introducing features that could be abused or lead us back to reinventing Twitter’s problems. There’s even more evidence now that quick reposting shouldn’t be implemented blindly. Look what happened on Soundcloud:
Similar to Tumblr’s reblog or Twitter’s retweet, reposts were designed as a way to help new music spread virally. But from the start, artists abused the feature by constantly reposting their own tracks, pushing them back to the top of their followers’ feeds every few days.
For Micro.blog, I believe the right approach is to first introduce a simple “quote” feature. This UI would be streamlined to support quoting a sentence out of a blog post, with your own thoughts tacked on. It would fit with the spirit of easy posting in Micro.blog, but it would encourage more thoughtful posts and naturally scale up from traditional linkblogging.
It’s always cool to see Webmention comments on real sites across the web. It’s not just a W3C spec. Like many ideas from the IndieWeb, this is a simple web technology that actually works today.
We’ve been improving Micro.blog’s support for Webmention. When you reply to a post on Micro.blog, from the web or iOS app, it will ping the site you’re replying to, giving that site a chance to include the comment. You can see these replies show up under recent posts from Aaron Parecki and Jonathan LaCour.
Drew McLellan had a good overview of implementing Webmention, including using services like Bridgy to bring in tweet replies:
The end result is that by being notified of the external reaction, the publisher is able to aggregate those reactions and collect them together with the original content.
Colin Walker highlighted Webmention when writing about Micro.blog:
It looks like a basic Twitter-style network but that is only scratching the surface; its simplicity belies its power.
Micro.blog also has limited support for receiving Webmention requests for people replying to a Micro.blog-hosted blog from their own site. As this support improves, both in Micro.blog and as more people enable Webmention on their WordPress sites, the distributed nature of the web as a broad social network will really start to shine.
This morning I updated Micro.blog’s XML-RPC posting to support the MetaWeblog API, which allows uploading photos to your hosted microblog. If you’re using MarsEdit to post to Micro.blog, edit your “System API” in MarsEdit’s blog settings to “MetaWeblog API” instead of “Blogger API”.
Working on the photo upload support has also helped clarify how Micro.blog should process text from the different posting APIs such as MetaWeblog and Micropub. After the next version of the Micro.blog iOS app ships, Micro.blog will start requiring Markdown and escaping HTML tags from Micropub, just as it currently does from the web interface. This will be a much better default for most people, and bring more consistency between web and iOS posting.
MarsEdit and other tools that use XML-RPC will still be available for when you want more control over the HTML that is posted. Micro.blog does allow Markdown in your MarsEdit posts, but otherwise it does very little processing of text from MarsEdit. It even lets you post long-form blog posts.
Today we’re adding Facebook cross-posting to Micro.blog. Facebook support is now built in, just like Twitter cross-posting, and can be configured for a microblog hosted on Micro.blog or any external blog with a feed.
Micro.blog’s cross-posting naturally works with long-form content or microblog posts. For longer posts, it includes the title with a link back to your blog. For microblog posts, it sends the entire text to Facebook.
Micro.blog also parses your post HTML looking for
img tags, downloads the photo and attaches it to the Facebook post. This means that microblog posts with photos look great on Facebook, but the source content is still on your own web site. It works really well with the Micro.blog app for iOS.
I feel like Micro.blog is starting to pick up steam. I’m looking forward to rolling out more improvements before the public launch.
Micro.blog’s business model is pretty simple. If you want Micro.blog to host a new microblog for you, or use the Twitter cross-posting with an existing site, there’s a small monthly subscription. We want Micro.blog to be the easiest way to start a blog.
Included in all Micro.blog-hosted microblogs is support for custom domain names, so that you can map yourname.com to your blog. While we’ve always supported SSL for the default yourname.micro.blog hostnames, custom domains need their own SSL certificate. Managing SSL certificates is a hassle, and until recently, also expensive.
I’m happy to announce that we are now rolling out free SSL hosting for custom domains, powered by Let’s Encrypt. While it’s not fully automated yet, we’ve already started enabling these for customers as requested. If you have a Micro.blog-hosted blog with a custom domain, email firstname.lastname@example.org and we’ll enable SSL on your site.
There are more features coming for hosted blogs leading up to the public launch of Micro.blog. Don’t forget to sign up on the launch announce list.
I was very excited to see this post from Brandon Kraft, about the potential for an expanded role for WordPress in the IndieWeb movement:
The dream isn’t to return to the past before social media, but help make social media part of the web in an organic way. For this post, you can like it or comment it on via this site, WordPress.com, Twitter, or Facebook, but all of the comments will appear here using Webmentions. The closed gardens will still exist, but it’ll make it easier for people to reach out between them.
People always ask me how Micro.blog is going. There are many answers to that: from the business side, or how the community is growing, or the technical bits of scaling the backend. But one simple answer is how Micro.blog’s success can be judged in posts like Brandon’s.
I still believe strongly in the dual nature of success that I posted about earlier this year:
Key for Micro.blog: it’s a success if more people blog. To provide value it doesn’t need to replace Twitter. But also, it can.
Of course, “if more people blog” is a simplification that leaves out what naturally happens next: the spread of more web standards and better tools for microblogging. If Micro.blog has played even a small part in encouraging IndieWeb standards within WordPress itself, that is great progress. I’ll be happy to raise the bar for what success looks like.
On the surface, an independent microblog might seem a lot like a Twitter account. There are some important differences: you own your own content, you can use Markdown or HTML for styled text, and you aren’t limited to 140 characters. An indie microblog can be just as easy to use as Twitter, but more flexible since it lives at your own web site, even with your own domain name.
So you’ve created a Micro.blog account or chosen to set up your own blog. How should you use your own microblog compared to Twitter or Instagram? Here are some ideas:
- Use it the same as Twitter. Write short posts on your own microblog and cross-post them to Twitter. This is essentially what I do. If what I want to say fits naturally in 140 characters, it goes to Twitter as-is and followers can reply or like it there. If it’s a little longer, Micro.blog automatically truncates the tweet and links back to my blog.
- Use it instead of tweetstorms. If you find yourself trying to express a thought and it’s going to take 2-3 tweets, consider posting it to your own microblog instead. Micro.blog suggests a limit of 280 characters. It’s still short enough that it encourages quick, easy posting, but it’s long enough that you can use it for much more well-formed posts.
- Use it for a photoblog. I’ve noticed some pushback against Instagram as they add more ads, clutter the UI with Snapchat features, and move away from a simple reverse-chronological timeline. I want to make Micro.blog a great alternative for photo-blogging, which is why you can discover users from photos and there’s a UI for filters and cropping. You can see all my photos here.
- Use it for a linkblog. Link-style blogging is for short commentary about another article, usually with a link at the end pointing to the other web site. Since microblogs are based on Markdown or HTML, you can also include inline links, which makes the blog posts look clean and readable on your own site. Micro.blog’s cross-posting will automatically parse out the link and append it to the tweet version of the post.
- Use it for company news. Because it can be integrated into an existing full blog or web site, a microblog is a convenient format for posting updates about your business or industry topics you care about. This is why Micro.blog allows custom domain names and also offers the Sidebar.js include.
Of course there’s no single correct way to blog. I’ve enjoyed watching Micro.blog users try different approaches to microblogging to figure out what works best for them.