Menu

Colin Devroe

Reverse Engineer. Blogger.

Like? Subscribe.

Yesterday I submitted a bug report for WordPress’ Gutenberg and this morning the fix was in the 5.1.1 release. WordPress dev community is killing it.

A new interview with Manton Reece of Micro.blog for 2019

Last year, around this time, I published an interview with Manton Reece – founder of Micro.blog (M.b) – about how the platform was growing and what the goals for 2018 were. It was such a great interview and it helped me to understand the direction that M.b was going that I knew I had to interview him again to check in for 2019.

Answering these questions isn’t easy. Manton and I have been volleying back and forth for about 60 days for this interview to come to this point. So before we jump into the interview I just want to take a moment to thank Manton for taking the time to thoughtfully respond to my questions. I hope the entire M.b community enjoys this interview and it helps to give an idea of what is happening there and where the community and platform are headed.

I’ve tried to include links to most everything we mention so that you’re able to find all of the little tidbits. If I missed anything, leave a comment or reply on M.b and I’ll try to track down what you’re looking for.

Now, onto the interview:

Thank you again Manton for taking some time to answer my questions. Last year’s interview was fun so I thought it’d be a good idea to revisit a few of the topics in it and also catch up with you on how Micro.blog is doing and see where it is headed in 2019. Last year you mentioned that most of the growth on the team would come in the form of curators or support. Has the team grown? If so, what does the team look like today and what will it look like in 2019?

Manton: Great to talk to you again! The size of the team has not grown since last year, but I think we’ve done more with the people we have. Jean MacDonald has hosted over 40 episodes of our Micro Monday podcast, and Jon Hays has lead recent improvements to our iOS app and new apps Sunlit and Wavelength. I still expect the growth to be on the curation side and hope that can be a focus of 2019. Where the other big social networks try to use algorithms to solve problems, we think if you want a great community, humans need to be actively involved — featuring content, listening for problems, and thinking about the impact of new features.

Customer support and system administration are the other areas that I’m looking forward to getting help with, but as the platform evolves it’s still valuable for me to be handling most of that myself. I hear from customers every day about what they love and what features are missing. Since we last talked, I’ve also moved my primary blog with thousands of posts from WordPress to Micro.blog hosting, and that has been a great way to prioritize improvements to the hosting part of the platform. Blog hosting is the actual business of Micro.blog and enables us to do everything else we want to do for the social network and community.

From an outsider’s perspective, I don’t know how you’re able to do as much as you do! You are coding Micro.blog, keeping up with the infrastructure software/hardware, dealing with support, paying the bills… the list goes on and on. Then, on top of all that, you’re building a few iOS apps like Sunlit and Wavelength. You also have your own podcast called Timetable and a long-running podcast called Core Intuition. Not to mention your personal blog, help documents for Micro.blog, and keeping up with the community and the Slack channel.

How do you prioritize all of this? Is one project more important than another?

Manton: I think good things can come from trying to do a little too much, but it’s not usually sustainable. Eventually it catches up with you and you have to simplify and wrap up or delegate some tasks. We are in that kind of period right now with Micro.blog. We will continue to do a lot, but some parts of the platform — like the iOS apps — can reach a point of maturity where we work on stability improvements and polishing existing features rather than adding brand new features.

Android is another good example. Many people ask for an official Android app for Micro.blog. Because I don’t have much Android experience myself, I know I would be stretched too thin right now to tackle it, so we are encouraging third-party solutions instead. There’s a new version of Dialog for Android which has full support for the Micro.blog timeline, posting, replying, the Discover sections, and more. I’m really excited about it.

The most important project is the Micro.blog web platform, because without that foundation nothing else is possible. Improving the API and blog hosting will always be something we work on, alongside other priorities that come and go.

I for one am very happy that Dialog exists. I’m also happy that it is pretty good too. What other third-party projects have you come across that more people should know about? And, what haven’t you seen made on top of Micro.blog that you wish existed?

Manton: People should keep an eye on Gluon, which is in development now for iOS and Android. I’ve enjoyed reading developer Vincent Ritter’s blog post updates about working on it — the early choices he made on how to build the app and later decisions to update the UI and rewrite portions of it.

Integrating other platforms is another area that is great for third-party apps. For example, IndieWeb-compatible tools like OwnYourGram (for copying Instagram posts to your blog) or IndieBookClub (for posting about books you’re reading or want to read). Having so many third-party apps that can supplement the basic features on Micro.blog means that we can keep the primary experience as streamlined as possible, because the goal is to make blogging easier. I’d love to see more advanced tools for managing posts as well, such as batch editing posts or for import and export.

Switching gears for a moment to Micro.blog’s long term financial sustainability. I know at first there was a funding push related to the Kickstarter campaign, and of course there are those that pay a few dollars per year for the hosted service or other features like cross posting. What does long term sustainability look like for Micro.blog? Does there need to be a lot of growth in the customer base? How else can people like me, who use Micro.blog daily but are not currently paying, help keep Micro.blog funded?

Manton: Kickstarter was perfect to get us started, but paid subscriptions are better long term. I want to build features that are valuable and worth paying for. So we’ll keep making our blog hosting more compelling so that it’s good for people who are just getting started with a new blog, or people who want to migrate from other platforms. We often see people who might have a primary blog on WordPress — and a secondary microblog or photo blog on Micro.blog — decide that it’s simpler to just consolidate everything to Micro.blog, importing their WordPress posts. We don’t expect all the millions of bloggers who host on WordPress to move over to Micro.blog, but even a relatively small number moving to Micro.blog will make the platform more sustainable.

We just rolled out several major new features for blog hosting, including categories and custom themes, so you can have full control over the HTML, CSS, and JavaScript on your site. You don’t need to be a designer or developer to use Micro.blog, but it’s nice to allow some more flexibility for those people who do want to tinker with their site. And now web developers can create custom themes for Micro.blog that can be used by other members of the community.

As for supporting Micro.blog if you aren’t a paying customer, the best way is to tell people about it. All our growth right now is from word of mouth. It’s great when people invite their friends from other social networks, or when they post about why they like Micro.blog on their own blog or talk about it on their podcast. You don’t need to have a large audience to make a big difference.

I’d be remiss to not mention the apparent resurgence of blogging. If not in action then in the collective consciousness. It seems many people are talking and writing about blogging lately. With Medium changing its policies, Tumblr being owned by Oath/Verizon/Aol, Twitter being a hive of villainy, Facebook selling our fears to our captors, and Instagram growing up to be like’s its parent… it seems that blogging is poised to have a huge comeback. Are you doing anything at all to capture that momentum? Or, are you just trying to keep on your roadmap as usual?

Manton: It feels like everything we’ve been working toward for a few years is starting to come together, as more people realize the downsides of these massive, centralized platforms. Whether someone is quitting Facebook tomorrow or a year from now, I want Micro.blog to be a great default choice for reclaiming ownership of your content and getting in the habit of writing or posting photos regularly. When Basecamp recently migrated their long-running blog Signal v. Noise away from Medium, they summed up the change just like we see it: “Traditional blogs might have swung out of favor, as we all discovered the benefits of social media and aggregating platforms, but we think they’re about to swing back in style, as we all discover the real costs and problems brought by such centralization.”

The other part of this is to have a safe, welcoming community. I hate to see people get discouraged from blogging because “no one” is reading, so it helps that we have the Micro.blog timeline and replies where a blog post can start a conversation, or new posts can be featured in the Discover section. I think 2019 is going to be great for blogging. Micro.blog differentiates itself because it offers a solution for both blog hosting and a great community.

Professional blogging; whether that be funded by advertisers, subscribers, fans – is a big business. What are your thoughts on how Micro.blog helps or ignores people or businesses that may want to use the platform to share their content and earn a living from it?

Manton: Micro.blog was designed for people, not “brands”, but there’s no reason it can’t be used for businesses as well. Toward the end of last year I wrote a “12 days of microblogging” blog post series, and on one day highlighted how businesses can use Micro.blog.

Personal blogs can evolve into a revenue source as well, like offering subscriptions or sponsorships. But Micro.blog will never have ads and we aren’t likely to add features specifically for people to make money from their content in the way that Medium is trying to do. We want to focus on helping people discover blog posts, and whether someone monetizes their blog or uses it for occasional self-promotion is up to them. It’s okay if most blogs are personal and non-commercial because that lends itself to authenticity, and there’s great value in just having a space of your own to publish to.

We also think podcasting is only going to get bigger, which is why our first new paid plan was microcast hosting for short-form podcasts. We keep increasing the limits and now you can publish even hour-long episodes to Micro.blog. Like personal blogs, podcasts could be sponsored, or they could be just for fun, or they could indirectly benefit your business, such as supplementing a blog or helping promote something else you’re working on.

I believe you’ve touched on open source regarding Micro.blog in the past. Some of your own projects, like JSON Feed, are open source. Will you be open sourcing Micro.blog or any pieces of it?

Manton: I don’t plan to open source all of Micro.blog in the near future. It’s a complicated project with several components across multiple servers, so it’s not really suitable for just “running yourself” right now. However, I’d love to open source more of it, especially when there’s an immediate benefit to people. For example, for the new custom themes feature, I rewrote all of the themes to use the Hugo blogging engine, and we’ve shared all our changes on GitHub. That’s something people can use right away. Jon Hays also wrote a framework called “Snippets” for the Micro.blog API and Micropub API that we’ll be using in our iOS apps, and we’ve open sourced that as well. I think there is more in our iOS apps (including Wavelength for podcasts and Sunlit for photos) that would be great to open source.

I think I catch myself looking for a search feature on Micro.blog at least twice a week. For instance, I’m big into houseplants lately and I wanted to find some people on M.b that were as well. And I can’t figure out how to do that. Is search coming?

We now have a basic search on the web version of Micro.blog under Discover. This currently searches any post that has been included in Discover. We have plans to add search to the native apps so that it’s easier to access, and expand it so that it searches even more posts on Micro.blog. However, one of the early design goals with Micro.blog was to launch without a full search index, because I didn’t like how Twitter’s search and especially trending topics could be gamed or expose the worst conversations on the platform, even in some cases being a place for more abusive, hateful replies. So we’re going a little slowly with search to make sure that we don’t recreate any of those problems.

I know I’m only scratching the surface for the questions that the community is likely curious about. I hope I did an OK job asking the important ones. Are there any topics I left off that you wish I had asked you about? Or anything you’d like to highlight?

Your questions were great. Thank you! I’d like to mention again what Jean MacDonald has done with our podcast Micro Monday. This podcast didn’t exist when you interviewed me last year, and now we have a great archive of episodes highlighting members of the community — how they got started blogging and what they are interested in, whether that’s related to Micro.blog or something else. It helps people understand Micro.blog while at the same time featuring stories from the community. I’m always inspired hearing what people are up to, and it’s a weekly reminder to me of how important it is that people have a voice on the web with their own blog.


What a fun interview! Until next year…

Signal v Noise exits Medium

DHH:

These days Medium is focused on their membership offering, though. Trying to aggregate writing from many sources and sell a broad subscription on top of that. And it’s a neat model, and it’s wonderful to see Medium try something different. But it’s not for us, and it’s not for Signal v Noise.

SvN was not long for Medium. It never felt at home there. Basecamp (the company, formerly known as 37 Signals) has too strong of a voice and brand design to ever have their blog live inside a platform with such web and brand hostility as Medium.

I think back to 2012 when SvN redesigned, I linked to that redesign then, and how they had carefully considered their typography, graphics (they had a different graphic for each category of posts), layout. Mig Reyes, at the time, wrote:

Instead of poring over other blogs, I spent a week studying books, magazines, and of course, Bringhurst. Capturing the right feel for body text was step one—it sets the tone from here on out.

If you care this much about your site/blog you cannot be holed up in some constrained content silo like Medium. Medium is an excellent (perhaps currently the best) web-based writing tool but the platform is more than just that. It promised exposure which is why many blogs like SvN gave it a try. But that was definitely the wrong reason to go there.

Nice pick up for WordPress of course but in reality SvN could have found a home on any platform they had full control over. I like the new design too.

Since Gutenberg has a very nice date picker I’ve now been able to deactivate the plugin I wrote in 2016 for replacing WordPress’s original post scheduler. I’ll keep the code on Github for Classic Editor users.

Matt Haughey on the mobile WordPress app

Matt Haughey vents his frustrations with WordPress:

Over the past week I’ve written a bunch of posts while out and about using the iOS WordPress app, often with photos of things I was seeing. But unless I was on WiFi or had 5 bars of LTE connectivity, I would get a Posting Failed, Retry? message. The wild thing is even after hitting retry a bunch, it would still fail. And then if I flicked over to my draft posts folder, the post wasn’t there. If I didn’t keep retrying and instead clicked anywhere in the app, the post would disappear completely.

Like Haughey, I too am frustrated with the WordPress mobile app (I’m on Android, and I have the same issues). I’ve actually removed WordPress from my phone because I can’t use it. It simply doesn’t work well at all. If I even try do post my photo posts with it crashes over and over and over and over. Which is why you’ve seen a lot less photos from me.

The Android apps I use every day

From the time I switched to Android in late-2017 (more here) I’ve been installing and uninstalling apps and services from my phone – trying to find the right mix for me. I expect the apps, preferences, and everything about my mobile experience to continue to change but lately it seems to have settled a little. So I thought I’d share what I’m currently using day-to-day.

My current Android home screen.

Pocket Casts – I have a 25-minute commute to and from work every day so having a podcast app that I like is very important to me. I’m so glad that Pocket Casts exists because Google’s default podcast app, called Google Play Music (for now) is not very good.

Pocket Casts’ Up Next feature is very well done, in that I can create my own playlist using the currently downloaded episodes, or cherry picked episodes, from any podcast I want. I set aside a moment once or twice per week to curate that list and Pocket Casts does the rest.

It also looks very nice in split-screen mode with the other app I use daily while driving Waze.

Waze – I had heard about Waze for years before I tried it in earnest. When I first downloaded it on iOS and tried it I thought it looked like a game. (And, yes, I suppose it is.) But, it turns out to be very useful in many ways. Like Google Maps it can give you directions from A to B, but that isn’t really what Waze is made for. Waze is made to make your morning commute faster and safer. The Waze-using community can report problems like traffic, accidents, police, etc. and anyone behind them can be warned in advance of these things. It has made a huge difference in my morning commute and helped tremendously in longer trips like our trip to Kentucky earlier this year.

Clip Stack – This little utility saves clipboard history and allows you to manage your clipboard. An app like this, on any platform, comes in handy more often than you’d think.

JW Library – My Bible and research/study app for all things biblical. Not only does it have tons of different Bible translations it also allows for notes, highlighting, video/audio, and more. The app has continued to improve since it debuted a few years ago.

Lose It! – I’m on a diet for the rest of my life so I use Lose It! to track my calories every single day. The app is updated often and is improving a lot each time.

Snapseed – It takes a little while to get used to this photo editing app. But I love that I can save my own “Looks” (or sets of photo edits). I use it on my Pixel 2 XL and also on my iPad. Nearly every photo you’ve seen from me since December 2017 has gone through Snapseed.

Flamingo – Unfortunately, if you don’t already have this app you can no longer get it. Flamingo is a sane Twitter app that records your place on the timeline and shows tweets reverse chronologically.

Spotify – I love Spotify. After trying Apple Music for a few months I can say that Spotify’s playlists just absolutely blow Apple’s offering out of the water. There is no comparison. I can understand why iOS users would use Apple Music due to how it is built into everything – but there is no reason to use it otherwise. Spotify is just better.

LaunchBoard – I use this app to quickly launch any app that isn’t on my home screen full time. You tap it, tap the first letter of the app you want, and launch the app. Think of it like using Spotlight on iOS. Same number of gestures too.

WordPress – Short status updates and some of my photo posts are created, and sometimes drafted sometimes published, using the WordPress app. It was unusable on Dreamhost but now that my site is hosted on Digital Ocean the app works great. Something I didn’t realize was that I can use this app without activating the bulky JetPack plugin. So I’ve done that and my site is much happier as a result. In fact, I’ve reduced my site’s footprint dramatically recently and I couldn’t be happier.

Chrome – One of the main reasons I switched to Android was being able to have a desktop and mobile browser of my choice. So I’m able to use Chrome (or any other browser) as my default. I also use Micro.blog via Chrome since that is the only way I can currently.

Messages – Pixel’s default SMS manager is called Messages. It works fine for what I use it for. I’m not looking forward to the updates coming to “Chat” that I’m reading about. These updates feel like HTML email – they are fun, but I don’t need those things. SMS works just fine for me. I wouldn’t mind, however, end-to-end encryption of all messages.

Voice Recorder – I record my audio bits using Voice Recorder. I haven’t be publishing many lately but I’ve been recording them still. This is a great way to capture content and ideas.


A few more apps that I have installed on Android that, while I may not use every single day, are great apps to have:

Wikipedia – I read a lot of information on Wikipedia. Mostly on my iPad. Having an app dedicated to it is very nice to save pages for reading later, doing research on multiple topics, etc.

Inoreader – I generally do not read RSS subscriptions on my phone unless I’m killing time. But, when I do I like having Inoreader on my phone. Feedly would work fine too.

Notable mentions are Microsoft Teams and Slack, Google Pay, Twitter app (for Moments when something happens), Dark Sky (though, I’ve been using this less lately since Google updates me on the weather), Google Photo Scanner, Trello.


Also, an app I use daily but that I didn’t have to install is the Camera. The Camera app is actually quite good for my use.

Any Android apps that I should check out that are not on my list?

An interview with Manton Reece of Micro.blog

I have fond memories of the very early days of WordPress (when it had just been forked from b2/cafelog), of Twitter, of Brightkite, of App.net, of Mastodon… just to name a few. The early days of any platform or so important to what they will become. They are the most fun to watch.

The early days of any platform can be frustrating too. Services sometimes go down, features aren’t released as quickly as you’d like, and small bugs can hamper your workflow.

I liken it to watching art be created. It can be a bit messy, it can sometimes confuse you, but when you see the final product you have the privilege of knowing how the platform got to that final state.

Yesterday I volleyed back and forth via email with Manton Reece, the founder and creator of Micro.blog. Micro.blog is in that same relatively early stage where new features are released with regularity, where the community is growing steadily, and where the users have the strongest voice.

He kindly answered a few questions. But here are a few highlights that I plucked from his answers:

  • Micro.blog is both an aggregator of blog posts and a blog/site hosting platform
  • Features on Micro.blog are rolled out slowly on purpose, to be sure they won’t disrupt the principles behind the service. And they often come from what users are already doing on the platform.
  • Native support for audio and podcasts are already part of the plan
  • Many users that use the hosting feature use their Micro.blog-powered site as their primary web site
  • Community support members for curation, help, etc. will be the primary area the team will grow, outweighing engineering

Here is the interview and his responses in their entirety.

First, thank you for making Micro.blog. For me personally it is surfacing some excellent independent microbloggers that I wouldn’t have found otherwise. Now that Micro.blog is open to the public, is there anything that you see happening on the platform, either now or during the beta period, that has surprised or delighted you?

Thanks for being part of the Micro.blog community! I’ve loved how people not only embrace the platform, but in many cases get back to writing at an old blog that they had accidentally neglected, or get inspired to start up a new microblog at their own domain name. So many beautiful photos have been posted, which we like to highlight in the Discover section, and the tone of conversations has remained thoughtful and respectful even as the platform has grown.

I’m also happy to see that many Micro.blog users have warmed up to some of the early decisions we made to not copy every feature from other popular social networks. For example, not showing follower counts or worrying about how many likes a post has received.

People seem to really enjoy the new emoji-based topics we introduced recently, to collect posts about books or music or sports. Little experiments like these are a reaction to what the community is already doing. The best thing we can do is build features that support what people are posting about — to encourage the kind of posts that make Micro.blog a nice place to be — and then see which of those features resonates.

Have you been surprised at all by the number of photos that people are posting? Or, did you always think that Micro.blog would be a great place for people to share photos? And, do you think you’ll see audio or video shared more on Micro.blog in the future?

I’ve always thought photo-blogging would be a perfect fit for Micro.blog, and we’ve tried to build good support for it in the iOS app, such as having built-in photo filters. Many people are frustrated with Twitter and Instagram and want to post photos to their own web site again. But I was still happily surprised to see so many photos. There was also some help from the community, such as Doug Lane running a 7-day photo challenge.

Our plan was to start with photos, with good photo hosting, and then expand to natively support audio and podcasts. After that, video. I think video can quickly become kind of overwhelming and busy when shown in a timeline — especially with auto-playing video, which we don’t want to do. So I’m comfortable expanding this support fairly slowly to make sure we get it right.

I see Micro.blog as two parts: 1. A community of syndicated microblog posts that are populated by people’s independent web sites using RSS or JSON feeds. And, 2. A blogging platform that allows you to create a simple blog (with an emphasis on microblogging). Is this the right way to look at Micro.blog now and into the future? And if so, why tackle both problems rather than simply #1?

That’s the right way to think about it. What I found while developing Micro.blog is that just building a more open social network-like platform wasn’t enough. If we wanted to encourage people to blog more, we needed to make blogging itself much easier. The best way to do that is to also offer to host someone’s blog for them directly on Micro.blog.

Blogs hosted on Micro.blog started with an emphasis on microblogging, but they have improved significantly since we initially launched, and now offer many features competitive with other dedicated blog hosts. There are Micro.blog users who have their full web site hosted by Micro.blog because it’s just more convenient.

This second part of Micro.blog is also very important to grow the service as a business. I want to run Micro.blog for decades to come. The only way to do that — to pay for all the servers and other supporting services — is for Micro.blog to be profitable. Since we never want to show ads, offering paid plans such as blog hosting is a great way to go.

Would you be willing to share any interesting stats? Some that I’d personally be interested in tracking would be the most number of posts in an hour, the greatest number of signups in a day, stats like that.

And as a follow-up: As the platform (meaning the software, hardware, underlying services, backup routines, databases, etc.) become more complex surely you’ll need to expand from being the two-person team Micro.blog is currently. What position do you think the next full or part-time team member of Micro.blog will fill?

I don’t currently have many stats to share. We have been so busy improving the platform that we haven’t built anything to track things like spikes in the number of posts. There is a 500-user limit on new registrations per day. When we opened it up to the public, the limit was just 100 which was reached pretty quickly as people would share a link to their friends.

There are so many areas that we could use a larger team for, like system administration and planning how to scale the platform. As you noted, the first person to join Micro.blog was Jean MacDonald, our community manager. I hope that the community will continue to grow such that we’ll need additional curators to help manage features like the Discover section.

Facebook recently announced they were hiring 10,000 moderators, and I know Twitter has a large staff as well. I expect one mistake that these larger social networks made early on was hiring too many programmers, and not enough curators. For Micro.blog we always want people who can interact with the community and stay ahead of any issues.

Discover has already seen a few iterations. First, it was a simple list of users. Then it expanded to include photos posted by the community. After that, a human-curated list of posts was added. And now, hashtag-like emoji’s allow you to find posts on topics like books, music, and football. Did I miss anything? This must be a fun part of Micro.blog to tweak and see how the community responds. I know I’ve found it to be very fun to have open a few times during the day. Can you share a little about how posts end up in the Discover tab? Who is making those selections and what are the next steps?

I feel like the current iteration of Discover is by far the best yet. There were a couple problems with just featuring a list of users. You can only feature so many users, so we randomly selected users to show from the featured list. Those users would get a lot of attention but unless we continually update the list, it might not be enough people to fill your timeline with interesting posts if you just pick a few people to follow. The list got stale quickly as new people were joining the platform.

Now, throughout the day we skim through posts and replies and put them in Discover. This is a better reflection of the activity on the platform. It’s not all posts, but it’s a good snapshot of the kind of things people are posting about. It looks good and isn’t overwhelming. It’s a great way to find new users who just joined Micro.blog, too.

Emoji topics are a little different. Whenever Micro.blog sees a new post, it checks it for emoji and adds it to a collection. If an inappropriate post shows up, we can just remove it from the collection without effecting anything else about that post or user on Micro.blog. There are a limited number of emoji, which keeps everything simple. I don’t think it will get out of control like Twitter hashtag search results often do.

One aspect I’ve always loved about microblogging was that it could be consumed and participated with in realtime. A few examples that come to mind are backchannels for live TV events like awards shows, or for conferences and meetups, etc. Is this something the Micro.blog team thinks about much? Are there any apps, features, or other considerations that would be made specifically to foster realtime interactions for things like this?

I agree this is a natural fit for indie microblogging. Something like live sports might not appeal to everyone, so it would be useful for both tuning into those feeds or filtering them out. Over the weekend, we put the football emoji in the Discover section for people who were posting about the NFL playoffs, as a simple experiment for making current topics more discoverable.

There are myriad other things we could talk about like Pins, third-party applications, indieweb building blocks like Webmention, and the all new Micro.blog logo and app icon. Is there anything you’d wish to highlight? If so, please do. And lastly, what is something you wished I asked but didn’t that maybe you’d like to make sure people reading this interview know (feel free to allow this to be nothing)?

The third-party ecosystem and larger IndieWeb community are both really important. There are several third-party apps for Micro.blog in development now, for iOS and Android. When I was designing the Micro.blog API, I based it on JSON Feed, Micropub, and other common APIs so that third-party Micro.blog apps could also be adapted for other platforms. And likewise, Micro.blog benefits from many existing IndieWeb tools and open source software like WordPress. The more we can push forward the user experience for indie microblogging, making blogging more approachable, the stronger the open web will be.

Thanks Colin! It was great to have a chance to share some of our thoughts behind Micro.blog.

Thanks to Manton for taking the time to write thoughtful responses. If you haven’t yet given Micro.blog a try head on over to there and give it a whirl. You could very well make an impact on the type of place it becomes.

You can follow Manton on Micro.blog at @manton. And I’m @cdevroe.

Facebook will drop the patent clause for React license

Matt Mullenweg:

I am surprised and excited to see the news that Facebook is going to drop the patent clause that I wrote about last week. They’ve announced that with React 16 the license will just be regular MIT with no patent addition. I applaud Facebook for making this move, and I hope that patent clause use is re-examined across all their open source projects.

Interesting outcome. Here is more context.

Matt Mullenweg on Automattic’s use of React

Matt Mullenweg:

I’m here to say that the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library. It will likely delay Gutenberg at least a few weeks, and may push the release into next year.

Automattic will also use whatever we choose for Gutenberg to rewrite Calypso — that will take a lot longer, and Automattic still has no issue with the patents clause, but the long-term consistency with core is worth more than a short-term hit to Automattic’s business from a rewrite.

This is a big blow to React. The framework will still be massively popular and adopted but the number of developers in a thriving ecosystem like Automattic’s products – like WordPress – that now have to move onto something else is a big blow. Automattic’s continued use of React would have meant thousands of jobs for a long number of years.

As usual, Mullenweg sees the longterm angle, and weighs that against the core principles upon which his company was founded, and I believe he’s taking the right path.

Side note: I still see so many developers that deal with WordPress day-to-day that haven’t yet started learning JavaScript in earnest. Mullenweg himself has urged the WordPress community for the last several years to invest in learning JavaScript. So, if you haven’t already… jump in.