Automattic and .blog

With the increase in scrutiny around how Matt Mullenweg manages the WordPress project, some people have asked whether it’s a risk to invest in .blog, which is owned by Automattic, and in fact whether Micro.blog is online only at the whims of the mad king. I’m not worried. It’s a fair question, though, and the answer is worth exploring in detail.

First of all, I believe Automattic runs .blog for the good of the web and to make money. The more people who blog, the more people who might choose WordPress.com for hosting. The web gets a little better anytime someone uses a .blog domain, because they probably just created a new website, and Automattic pockets a little cash. Everyone wins.

Unlike .com and .org, the pricing for .blog domains is variable. Shorter, common words cost more than you’d expect. We pay $2000 for the micro.blog domain, every year. We are a tiny company so it hurts a little each time the domain name renews. But I think the domain is worth it. Getting the domain in 2016 helped shape what Micro.blog would become.

I mention this because I don’t see Automattic stabbing its customers in the back and shutting down domains, cutting off a revenue source. What would be the point? A single subscription might not be very much to a multi-million dollar company like Automattic, but Automattic is built on thousands of subscriptions. You cut $2000 here or there, and pretty soon you’re talking about real money.

Next, I am conscious of centralized power and single points of failure. Micro.blog would not exist if I hadn’t become frustrated with Twitter locking down their developer API, years before Elon Musk took over. It’s why I want to work on an open platform where the business model is aligned with the interests of users and developers.

When we have a choice between two things… we try to do both anyway. Micro.blog supports ActivityPub and AT Protocol. It supports cross-posting to Mastodon and LinkedIn, Flickr, Bluesky, and Nostr. Take one away — such as when Elon put the final nail in the Twitter API’s coffin — and we still have something. Apple controls whether we can ship an iOS app, but not whether we can ship to the web, Mac, or Android. It is important to me that no single company can break my business and wreck my users' blogs.

Which brings us back to .blog. We recently launched a new special version of the platform called Micro.one. It is, obviously, using a different top-level domain, not owned by Automattic. If the worst were to happen, we would flip everyone to .one and carry on. Over time, I see us using .one more, as a new brand that can unify a suite of apps on the platform.

The point is the same as it is for so many other things, from features that depend on external services, to having redundancy in servers. It’s a risk to depend on a single company.

I still think .blog is a great top-level domain. I think Automattic is in this for the long haul. Even Matt’s worst critics are not going to convince me that he wants fewer people to have their own website, or that he is going to pivot Automattic away from blog hosting. And yet, it’s always good to have a backup.

Cooper

I actually had no idea Automattic owned .blog. Kind of wondering if I should pay more attention to who owns the TLDs I choose to use (but I won’t).

Manton Reece

@cooperbike It usually doesn't matter who owns a TLD. There are a couple of exceptions, though, for country codes that might have too much influence on who can use the domain. People have run into problems with .ly (Libya).

Jason Becker

not to take away from your actual point, but wow am I glad that I got my .blog domain on the first day it was available and must have some grandfathered in pricing. And I'm glad I have it registered through 2029 for now.

R Scott Jones

Appreciate your strategy here.

Manton Reece

@jsonbecker Multi-year registration is a good idea. I wish I could afford it! 🤪

Numeric Citizen

"numericcitizen.blog" is available... should I? Where should it point to if I register, as an alias to blog.numericcitizen.me, another domain that I own?

Jason Becker

I think I only paid $20 a year so… a little bit different.

Amit Gawande :verified_coffee:

@manton Getting worried because a TLD is owned by Automattic is taking it to extreme. I don't think Matt's fight is with independent blogs.

Manton Reece

@amit I agree.

dame

I hope you’re right about .blog, but you say “I mention this because I don’t see Automattic stabbing its customers in the back and shutting down domains, cutting off a revenue source. What would be the point?”

Matt has already done this exact thing multiple times over the past few months.

Manton Reece

@dame.bsky.social He has? He's closed access to WP Engine and some WP contributors, but I don't view that as the same as cancelling Automattic subscriptions.

dame

He hasn’t cut off a “subscription”, but he has repeatedly over the span of many months continued to do things that harm his company, his image, his customers, and the ecosystem. Automattic’s valuation is on the decline. This is a man who does not act in good faith and is detached from reality.

Paul Robert Lloyd

Not sure I agree with your assessment regarding Matt’s sanity given (more) recent events, but I love the resilience strategy, and how it now applies to your TLDs. Genius!

Numeric Citizen

@jsonbecker "numericcitizen.blog" via Cloudflare would be 21$ a year. I'm just not sure if it is a good idea to buy this. cc

Manton Reece

@numericcitizen It's a slippery slope to having too many domains. 🙂 But I did get manton.blog and it just redirects to manton.org.

Numeric Citizen

thanks!

Kev Rodgers

Half of all computer problems are DNS. The other half is disk space.

Manton Reece @manton
Lightbox Image