I was sick a few days before Christmas and it forced me to take some extra time off after a very busy November and December. Happy to be back blogging and looking forward to 2020, so let’s wrap up the holidays with a post about Christmas movies.

This isn’t necessarily a list of the best Christmas movies. There are other classics that are usually on an all-time best list that aren’t here. This is a list of my 10 favorites.

1. The Nightmare Before Christmas — Perfect for Christmas or Halloween. So nearly flawless I had to put this at the top of the list.
2. The Muppet Christmas Carol — There are many great adaptations of A Christmas Carol, and last year we watched pretty much all of them. I wish there was room to include a couple of the animated versions, like Richard Williams’ A Christmas Carol and Mickey’s Christmas Carol.
3. A Charlie Brown Christmas — ”That’s what Christmas is all about, Charlie Brown.”
4. Klaus — Beautifully animated. Brand new, but now that I’ve seen it twice I know it will hold its own against the best. There’s a great interview with director Sergio Pablos on The Bancroft Brothers Animation Podcast.
5. Elf — We probably rewatch this more than anything else. Can’t say enough good things about the variety of movies Jon Favreau has worked on (not to mention The Mandalorian).
6. Meet Me in St. Louis — I’ll admit, I didn’t want to love this at first, years ago, but now that I’ve seen it dozens of times it’s a favorite, and I think the best of the older classics.
7. National Lampoon’s Christmas Vacation — One of our traditions is to cut a tree down at the Elgin Christmas tree farm, and there’s a little of Clark Griswold in the endeavor.
8. Die Hard — Definitely a Christmas movie.
9. A Christmas Story — ”You’ll shoot your eye out.”
10. Rudolph the Red-Nosed Reindeer — Check out this YouTube video about some of the editing problems with the recent TV version.

If I could only watch these 10 movies every year I’d be happy. But there are others we enjoy that deserve honorable mentions: Edward Scissorhands, Love Actually, It’s a Wonderful Life, Home Alone, The Grinch (2018), Jingle All The Way, and Christmas with the Kranks. And a special shoutout for the soundtrack of The Polar Express.

Happy Holidays! ❄️

This morning, Jack Dorsey dropped a bombshell:

Twitter is funding a small independent team of up to five open source architects, engineers, and designers to develop an open and decentralized standard for social media. The goal is for Twitter to ultimately be a client of this standard.

I should be excited about this, but instead my first reaction was frustration. Ten years after early Twitter employees like Blaine Cook and Alex Payne were pushing for a more open architecture, now Jack Dorsey realizes Twitter is too big and creates a team to work on… blockchain-based solutions?

Finally, new technologies have emerged to make a decentralized approach more viable. Blockchain points to a series of decentralized solutions for open and durable hosting, governance, and even monetization. Much work to be done, but the fundamentals are there.

The first step should be to check out the IndieWeb. There are people who have been thinking about and working toward more open social networks for years.

After a closer reading of Jack’s tweets, though, I think my first interpretation wasn’t quite right. Twitter isn’t necessarily interested in decentralizing content or even identity on their platform. Why would they be? Their business is based around having all your tweets in one place.

Early in the thread, Jack hints at what Twitter is trying to do:

First, we’re facing entirely new challenges centralized solutions are struggling to meet. For instance, centralized enforcement of global policy to address abuse and misleading information is unlikely to scale over the long-term without placing far too much burden on people.

This “burden on people” is the resources it would take for Twitter to actively combat hate and abuse on their platform. Facebook, for example, has hired thousands of moderators. If Twitter is hoping to outsource curation to shared protocols, it should be in addition to — not a replacement for — the type of effort that Facebook is undertaking. I’ve outlined a better approach in my posts on open gardens and 4 parts to fixing social networks, which don’t seem compatible with Twitter’s current business.

I’m going to be paying close attention to this. Good luck to Jack and the new team. I hope they seriously look at existing standards, because we’ve come too far to start over.

I’ve finished adding the special pin for anyone who participated in the Microblogvember challenge. Jean MacDonald also has an emoji recap of all the challenge prompt words.

There’s a link at the top of your Account page in Micro.blog, or click here to view your pins. If you don’t see the pin yet, it should appear whenever you post to your microblog next, which tells Micro.blog to check for new pins again.

Because some people started late or posted twice in one day, the “algorithm” for calculating the pin isn’t very strict. If you were blogging regularly in November and used 30 of the prompt words from the challenge, you’ll get the pin. This was a lot of fun and I hope we can do more challenges like this in the new year.

Now is also the perfect time to unlock the “Happy Holidays” pin by posting to your microblog with something about the winter holidays. It’ll match on a bunch of keywords including Christmas, Hanukkah, Santa, snow, reindeer, and a few others. Enjoy! ❄️

Interesting article from The New York Times about a report from the NATO Strategic Communications Center of Excellence. Researchers ran a series of experiments to buy likes, comments, and clicks on social media posts. They paid companies in Russia and Europe hundreds of dollars to buy thousands of likes and followers, writing up a report on the results:

But the report also brings renewed attention to an often overlooked vulnerability for internet platforms: companies that sell clicks, likes and comments on social media networks. Many of the companies are in Russia, according to the researchers. Because the social networks’ software ranks posts in part by the amount of engagement they generate, the paid activity can lead to more prominent positions.

The researchers then actively notified the social media companies about the fake likes and tracked what action the tech companies took, if any. Most fake likes and accounts used for the experiment remained online a month after they were reported.

It is very difficult for a massive platform like Facebook or Twitter to catch everything. Instead of trying to “fix” fake likes that are purchased, the solution is to remove the reason someone would purchase likes to begin with. If like counts weren’t featured so prominently and used for surfacing content, there would be no incentive to try to game the system.

Jean MacDonald has a great wrap-up post about the Microblogvember daily blogging challenge and the value of looking for “micro” versions of bigger projects:

Ever since I became the community manager of Micro.blog, I’ve developed an appreciation for the beauty of going “micro”: microposts, microcasts, micro meetups, microcosms of interesting humans interacting online on a human scale.

This is a key part of Micro.blog’s mission. Many people find writing a full-length blog post too daunting, but break it down into micro-sized posts and it’s easier for everyone. Jean continues:

This is what I like about a micro approach. Start with something small, and build on that. It also works with podcasting, for example. Micro.blog has spawned several microcasts (including our own Micro Monday) by making it easy to start small.

It reminds me of why we’ve added so many “full” blogging features to Micro.blog hosting, like longer posts, file uploads, categories, custom themes, standalone web pages, and podcast hosting. After you’ve “started small” and have a nice routine with microblog posts, the platform should grow to accommodate whatever you need next.

Early last Friday morning, one of the Micro.blog photo storage servers failed. I brought it back up shortly after I noticed, but dealing with the problem motivated me to make a change I’ve been thinking about for how photos are stored. Over the weekend I migrated the photo storage to a new system based on Linode’s Object Storage.

(Luckily, years ago when I was designing Micro.blog, I had anticipated I might eventually make a change like this. The old server was running Minio to provide an S3-compatible interface, internal to Micro.blog, so switching to a new system was much easier.)

When a photo is uploaded to Micro.blog, it has always been kept in at least 2 places: on a primary photo storage server, and on a copy of your published blog, along with HTML and other files. Both of these locations were backed up daily.

Over the summer there was a similar error to what happened last week. For some new uploads, only 1 copy of the photo was kept. If Micro.blog needed to rebuild your published blog files, there was a small window during which it could overwrite the latest photos that had been uploaded. Usually I’d be able to fix this from a backup, but I know at least 1 user who was affected by it, and there might have been a few more.

If you ever see broken images on your site, please reach out to help@micro.blog. You can also re-upload photos under Posts → Uploads in Micro.blog on the web and update any posts from the original photos.

Remember that Micro.blog also has built-in features for making extra backups for yourself, beyond the backups we already handle behind the scenes:

• Save new posts to the Internet Archive. There’s a checkbox to enable this under Posts → Design. When you publish a new post, Micro.blog automatically makes it available in the Wayback Machine.
• Export in Blog Archive Format. Micro.blog will make a .bar file that is actually a ZIP file with all your photos, HTML for posts, and a complete JSON Feed.

The new photo storage that is live now should be even more robust. Photos are a very important part of Micro.blog. I’ll keep improving this and adding storage redundancy wherever I can.

Today I sent the following update to Kickstarter backers.

Hi everyone! I’ve set a release date for the book Indie Microblogging: January 2nd, 2020. I’ll send an email that day to all Kickstarter backers with a link to read the book on the web.

You can preview the draft table of contents here: book.micro.blog

There’s a pre-order link on that page. You don’t need to pre-order the book because you will already have access as a Kickstarter backer, but please share the link on your blog, to followers on social networks, and with friends who might need a reason to dust off their blog or even start writing on the web for the first time.

Thanks for your support and patience as I’ve spent the last couple of years focused on building and improving Micro.blog. There is still a lot of work to do, but I’m excited to spend the next month wrapping up the book reward for Kickstarter backers.

And if you haven’t checked out Micro.blog lately, the community keeps growing and the platform has evolved to be great for full-featured blogs, not just microblogs. Photos, Hugo themes, categories, pages, podcast hosting, publishing from apps across iOS, macOS, Android, the web, and much more.

— Manton

P.S. Indie Microblogging is a book about the web, so I want it to be on the web first. After some time to incorporate fixes and improvements to the text, I’ll follow up with a print version for backers at the higher reward tiers.

I’ve blogged about Klaus a couple times. It’s one of those films that I was a little nervous about because I wanted it to be great, and it is. There is some wonderful character animation in this.

Animation World has an interview with director Sergio Pablos about what a positive experience it was to work with Netflix, and on getting few chances in life to do something great, especially with animated features:

You hope you’ve made something good, but you’re so close to it that you’re kind of blind to it. We’ve been trying to make a film for 15 years in my company and we’ve failed in different ways. Right? Sometimes a film would end up going elsewhere, or it wouldn’t even get made. Meanwhile, we’re taking service work to try and support our effort. So, it’s been a long road. But I always dreamt the day would come where I’d have a project I could be proud of.

Congrats to the team for doing something that feels new with 2D animation. I may need to get the art book.

As 2016 was winding down, I was determined to start 2017 with something new. On January 2nd, I launched the Kickstarter campaign for Micro.blog and a book I’m writing called Indie Microblogging.

In the years since then, I’ve put everything into Micro.blog to fulfill my promise to Kickstarter backers. Micro.blog does way more than I had dreamed it could do 3 years ago. But the more I put into Micro.blog, the more it needed of me, and the book kept taking a back seat until now.

I’ve set the ship date for the book: January 2nd, 2020. It will be published on the web for all Kickstarter backers, and if you missed the Kickstarter you can pre-order the book now for $20. The money goes right back into Micro.blog so that Jean, Jon, and I can continue improving the platform and growing the community.

When completed the book will be over 50 short chapters in 6 major parts, plus intro and conclusion sections that get to the mission of Indie Microblogging and the next steps. It will also feature several interviews.

You can view the draft table of contents here and pre-order the book. Thank you for your support.

You might think because I created Micro.blog that I have a perfectly simple blogging workflow that will work for everyone, all the time. Nope. I use a variety of different apps depending on what I’m trying to do:

• If I’m posting a quick microblog post and know what I want to say, I type it into the Micro.blog app for Mac.
• If I’m posting a single photo, I use Micro.blog on my iPhone.
• If I’m posting a bunch of photos like this post from Toronto, I use Sunlit to write a little something for each day.
• If I’m writing a longer post and have it all in my head, so I know I will post it very soon, I type it directly into MarsEdit and publish it to Micro.blog from there.
• If I’m writing a post and I’m not totally sure where it’s going, or when I’m going to post it, I type it into Ulysses. This is the majority of my posts. Then I copy it out as Markdown and paste it into Micro.blog.

And this only scratches the surface. There’s Wavelength for podcasts, and some people prefer apps like Icro, Gluon, Dialog, Quill, or automation via Shortcuts. This is why we link third-party apps from the posting screen in Micro.blog.

One of the things I’m most proud of with Micro.blog is that the API supports standards so you can use a variety of different apps for posting. There are so many different types of blogs out there, there shouldn’t just be one way to post.

We are getting really close to episode 400. Feels like a big milestone to me, and I’ve been wondering if we should change anything with the podcast format when we roll over into the 400s. But in the meantime, here’s 395:

Daniel and Manton try to take stock of long-term personal goals, thinking of how they align with and overlap with money-making goals. Manton reports back after watching Matt Mullenweg’s “State of the Word” talk at WordCamp US. Manton reflects on the important of simplicity for Micro.blog in contrast to WordPress, while Daniel considers that MarsEdit also serves as a more complex interface to Micro.blog. Finally, they digest the latest Apple announcements, focusing on the merits of the new AirPods Pro, and whether Apple TV+ is a justifiable pursuit for the company.

Daniel has already given me a sneak peek of next week’s manager check-in and it’s a good one. I think that is going to become a regular segment.

Brent Simmons marking the 20th anniversary of his blog:

It’s tempting to think that The Thing of my career has been NetNewsWire. And that’s kinda true. But the thing I’ve done the longest, love the most, and am most proud of is this blog.

The great thing about a personal blog is that if you stick with it, your blog will very likely span multiple jobs and even major life changes. You don’t need to know where you’re going to be in 20 years to start a blog today and post to it regularly. Writing about the journey — and looking back on the posts later to reflect on where you’ve been — is part of why blogging is still so special.

IndieWebCamp Austin is coming up in February at Capital Factory. This is our 3rd event in Austin and I’m excited to start getting the word out and help a lot of new people discover the IndieWeb. Registration is already open.

Tom Brown and Jean MacDonald are joining me as co-organizers and we’re looking for sponsors to help cover costs for the venue and breakfast for attendees. If you’re interested in sponsoring or work at a company that would be a good fit to support the IndieWeb, please email me: manton@micro.blog.

Platinum event sponsor: $2500

• Your logo on the IndieWebCamp event page.
• A verbal thank-you during the morning and closing of the event.
• You can bring t-shirts, stickers, and other promotional items to distribute to attendees.
• A special mention and link in the email we send to attendees the day of the event.

Silver event sponsor: $1000

• Your logo on the IndieWebCamp event page.
• A verbal thank-you during the morning and closing of the event.
• You can bring t-shirts, stickers, and other promotional items to distribute to attendees.

Bronze event sponsor: $500

• Your logo on the IndieWebCamp event page.
• A verbal thank-you during the morning and closing of the event.

Ben Thompson has an excellent article this week about free speech, political ads, and Facebook. There’s a good debate to be had about the roll of curation and fact-checking ads, but on the problems of massive, ad-based social networks there can be no doubt:

In the long run, though, it is very problematic that such a powerful player in our democracy has no accountability. Liberty is not simply about laws, or culture, it is also about structure, and it is right to be concerned about the centralized nature of companies like Facebook.

Platforms that have as many problems as Facebook does can always be improved, but by design they can never be good enough because their size alone is one of the problems.

The good news: it’s up to us. We can choose to reject these platforms and move to a more distributed web of indie microblogs. We can choose to reject the attention power-grab of the algorithmic timeline. We can choose to build the web we deserve… but it’s not going to happen if you keep feeding photos into Instagram.

There’s a powerful filter mechanism inside Micro.blog for automatically assigning categories based on criteria in the post. For example, if the post includes an img tag, assign it to a Photos category. Or if the post includes the 📚 emoji, assign it to a Books category. I blogged about this in September.

Today I’ve expanded this feature to also allow matching on whether the post is a short microblog post or whether it’s a longer post with a title. Like other parts of Micro.blog, it uses the title to determine how to categorize the post. Posts without titles are always considered short microblog posts.

To create new filters, go to Posts → Categories → Edit Filters.

You can use this in combination with matching the title or text in a post, or leave those fields blank when creating a filter to match all posts. This makes it easy to move all full-length posts into a category, which can also have its own RSS feed.

There’s a new built-in theme available on Micro.blog called Lanyon, based on the open source Hugo theme of the same name. It’s a clean, readable design with a slide-out menu for page links.

I’ve been working on getting several new themes ready for Micro.blog. Some Hugo themes work with only a couple tweaks, and some take more time. My fork of Lanyon with Micro.blog-specific changes is on GitHub.

Two new versions of the third-party Micro.blog app Icro have been released. The iOS version now supports push notifications, and a new version is available for macOS for the first time.

Because the official Mac app is distributed as a direct download, this is actually the first Micro.blog app available in the Mac App Store. It was ported to macOS using Catalyst, so it requires Catalina, which I just upgraded to. It’s great to have another microblogging option on the Mac!

For the last few years, right before the regular season starts, Jon Hays and I usually paste in our guesses for the top 8 in the west in chat. This year the west is up for grabs more than anytime in the last handful of years, so I thought I’d share my list:

1. Rockets
2. Clippers
3. Spurs
4. Blazers
5. Nuggets
6. Lakers
7. Jazz
8. Warriors

No doubt a few things are wrong here. For example, Dallas looks like a playoff team right now, and I left them out. But I’m excited to see how this shakes out, especially for the Spurs, who are exactly the team I was hoping they’d be now that Dejounte Murray is back.

Since the very beginning of Micro.blog we’ve encouraged you to use your own domain name with your microblog. It’s the best way to control your content and an important principle of the IndieWeb. Now it’s even easier.

If you don’t have a domain name yet — or need a new one! — Micro.blog can handle registration for you. We are using the Name.com API to purchase and configure the domain name for you. Payment is handled on your existing Micro.blog subscription and everything is automatic. No messing with DNS records.

Here’s a screenshot of finding a domain name, which is linked under the domain name section on Posts → Design:

I’m very excited about this feature. We’ll be expanding it based on feedback but it is already quite powerful, even including email forwarding. And of course, you can always register a domain name elsewhere on the web and point it to Micro.blog.

There have been a few IndieWebCamps recently, including in Amsterdam, New York, and Brighton. I’ve enjoyed reviewing the sessions, and after the Amsterdam event I noticed this post about content ownership:

When it comes to posting to Facebook or Twitter, you play a different game. You write and post it on their servers, therefore those companies own your data, not you. A photo (or video for that matter) is a special kind of data. Its file size creates limitations to its distribution, but no matter where it’s uploaded, it is always owned by its creator first.

While it’s good to acknowledge the unique hosting requirements of photos and videos, how we define content ownership shouldn’t be any different. People get lost in the weeds with running their own server, how to set up cross-posting to other social networks, where to post first, what formats and protocols to use, etc. But it’s actually much simpler than that.

I think in the tech world — and especially as programmers — we tend to make things more complicated than they need to be. We know too much about content ownership, most of it irrelevant for mainstream users.

If you want to control your content on the web, post it at your own personal domain name. That’s it. Everything else you want to do is icing on the cake.

Likewise, nothing else can be a replacement for that simple act of using your own domain name. You could write your own blog software with a custom database designed for ActivityPub and run it on a server in your basement. It doesn’t matter. Without the domain name, all you have is a pile of icing.

This has been the messaging for Micro.blog from the beginning. Keep it simple and make it easy for anyone to participate in the open web.

Following my experiment with importing Foursquare data, I’ve officially updated Micro.blog to support storing location information. The Micropub API now accepts checkin and location properties for sending venue name, URL, latitude, and longitude to Micro.blog. This works with the JSON format in OwnYourSwarm, which connects Foursquare/Swarm to your microblog.

Micro.blog on the web and the native apps do not send any location information. Right now this is purely an opt-in feature for third-party apps like OwnYourSwarm and custom solutions using the API. We consider location information very private and will never enable it automatically.

When a post has location information, you can see the coordinates in the posts list on your account:

The default Micro.blog themes do not currently do anything with this information. You can create a custom theme to access the coordinates as custom parameters, like this:

{{ if .Params.location_latitude }}
  <img src="https://example-mapping-service.com/?center={{ .Params.location_latitude }},{{ .Params.location_longitude}}" />
{{ end }}

The 4 available parameters are location_name, location_url, location_latitude, and location_longitude. The venue name is automatically prepended to post content so that no theme changes are necessary. I’d like to explore offering maps as a built-in feature in the future. Enjoy!

Years ago my wife and I were in Vegas and had a chance to see Elton John… and missed it. This year, when I realized he was playing in Toronto on the night of our 20th anniversary, I bought tickets as a surprise birthday gift and we planned a short trip around the concert.

We arrived in the late afternoon earlier this week, took the airport train to Union Station and the subway to our hotel, then went down to Polson Pier to catch the sunset. We had dinner and explored the Distillery District before checking out Jurassic Park for the Raptors game — too late, they had already closed it off — and settling for beers at the sports bar next door to watch the end of the game.

The next day we did a bike tour of the city. On the way to meet the guide, we wandered down a street to look at the trees and a woman said hi as she walked by. Realizing we were tourists, she stopped and told us that she had been friends with Jane Jacobs, who lived just a block away. There’s a sign outside her old house.

The bike tour was a great way to see a bunch of Toronto. Murals, CN Tower, trains at Roundhouse Park, sculptures at Ireland Park, the university, and several neighborhoods. We stopped for hot chocolate and then back on our own visited a couple libraries including the Sherlock Holmes room at the Toronto Reference Library.

Dinner in Little India and then the streetcar back for the concert. We loved it. Even with just a couple days we really got a lot out of visiting the city. Looking forward to coming back one day.

Garrett Dimon writes about removing all analytics from his web site and how little he misses it:

What over a decade of number-crunching analytics has taught me is that spending an hour writing, sharing, or helping someone is infinitely more valuable than spending that hour swimming through numbers. Moreover, trying to juice the numbers almost invariably divorces you from thinking about customers and understanding people.

We don’t have page-view stats on Micro.blog because they are incomplete without counting the Micro.blog timeline and feed readers, and I’d hate for someone to be discouraged when just getting started. Newsflash: your blog does not have a million readers. That’s okay! If you really want stats, you can add some custom JavaScript to include Google Analytics or Fathom Analytics, but most of the time it’s a distraction.

I love having everything together on manton.org. Whether it’s blog posts about tech, personal stuff, or photos, I don’t have to think too much about where to put it. If I’m writing on the internet, it goes on my blog.

But I’ve been wanting to experiment with sharing more location information too, and use that to try out location as a built-in Micro.blog feature, so I’ve created a new blog manton.coffee and imported my 2500 check-ins from Foursquare/Swarm representing about 8 years.

To build this, I upgraded Micro.blog to support venue names and location coordinates. We try to be very careful about privacy, and currently the apps do not fill any of this data in, but in the future it could be something people opt-in to for a post. The extra data is available to Hugo templates, which is how I’m including the little maps on the home page.

We’re working on some other features with higher priority than this, so consider this mostly a sneak peek for now. I’ll enable the Foursquare/Swarm import as an official feature after the glitches are worked out. Better integration with OwnYourSwarm should also be on the roadmap.

We’ve released a new version of our photo-blogging app Sunlit. Mostly a bunch of bug fixes, including these changes:

• Updated thumbnail previews in a new post to maintain the aspect ratio of the photo.
• Added an option in the Settings screen to clear cached photos and drafts from previous versions of Sunlit.
• Improved spacing of icons in tab bar.
• Fixed swipe left on a post to view the conversation.
• Fixed several other issues and potential crashes.

You can download Sunlit for free in the App Store.

I’ve removed the option for Facebook cross-posting on Micro.blog. Facebook recently disabled our API access, and my initial request for re-approval was denied. While I hope to eventually get it enabled again, I don’t want to have a feature on Micro.blog that is broken.

A year ago Facebook turned off API access for creating new posts unless they were sent to a Facebook page. I adapted Micro.blog to that change, but it already severely limited the usefulness of cross-posting to Facebook. At the time, Bridgy disabled all Facebook support:

Facebook’s moves to restrict its API to improve privacy and security are laudable, and arguably the right idea, but also mean that users can no longer use third party apps like Bridgy to create posts.

I hope that by officially saying goodbye to Facebook support we can focus on making the other cross-posting options in Micro.blog more robust. I’m currently looking into improving LinkedIn support, and we recently added Tumblr cross-posting to go along with Twitter, Medium, and Mastodon.

Facebook and even Instagram are at odds with the principles of the open web. I never want to remove a Micro.blog feature that users find valuable, but in this case we have little choice, and it’s best for Micro.blog to move on.

Yesterday we updated the iOS app for Micro.blog with several bug fixes and tweaks for iOS 13. Today I’m updating the macOS app with an important fix when running on macOS Catalina.

Here are the changes:

• Fixed post selection options popover on macOS Catalina.
• Updated for “notarization” to avoid launch warnings.

Along with macOS notarization, this release also now uses the “hardened runtime”. I thought this might break some features, but I haven’t noticed any problems. Choose “Check for Updates” in the app to get the latest version.

I’ve posted an update to Micro.blog for iOS with several bug fixes. Here are the changes in version 1.7.1:

• Updated a few more screens for Dark Mode on iOS 13.
• Fixed updating timeline when favoriting posts in Discover.
• Fixed alignment of popover when selecting a post.
• Fixed disabling cross-posting from post options screen.
• Fixed uploading videos to WordPress.

You can download it in the App Store.

There’s a new trailer out for Klaus, which hits select theaters and then Netflix in November. Amid Amidi at Cartoon Brew writes about director Sergio Pablos:

His goal hasn’t been to simply bring back 2d animation, but to push the craft forward, and Klaus’s distinct look is achieved via an innovative lighting and rendering pipeline that is applied to the drawn animation.

I’m excited for any hand-drawn feature film, especially one that comes from Sergio Pablos. Over the last few years his team has posted some early concepts and tests to their blog. I also mentioned Sergio on an episode of my podcast Timetable in 2017.

When Apple Arcade launched, I thought it would be fun to try a new game each day for 30 days. And it was fun! For… 18 days. On Saturday I sat down to play my 19th pick, Oceanhorn 2, and realized that playing a new game each day wasn’t working.

Unlike visiting 30 coffee shops, 30 libraries, and 30 parks — where each series of blog posts I explored Austin and got a lot out of it — playing video games has proven to be too big of a time commitment for me right now. I love video games and there are some great games in Apple Arcade, but if I’m on my phone for an hour I need to be using that time for something work-related. It was creating too much extra stress for too little return.

Oceanhorn 2 is also a good place to wrap up this experiment because it’s one of my favorites. It’s heavily inspired by Zelda. I’m going to enjoy playing it a little bit more over the next week or so. All the other games I’ve played are collected in this category on my blog.

Good luck to everyone participating in Inktober this month! We’ve added a special Micro.blog pin you can unlock by posting a photo of your drawing and the word “Inktober” somewhere in the post. To see your pins, click Account → View All next to the pins message.

If you’re drawing digitally, also check out these Inktober templates from Iconfactory for their iPad app Linea Sketch.

We posted episode 390 of Core Intuition. From the show notes:

Manton finds a workaround to his Sign in with Apple email problems! Daniel argues first that DTS should support pre-release software, and they discuss possible compromise approaches. Finally, they remark on Apple’s vigorous marketing push, and the thrill of promoting products we are proud of.

Only 10 more episodes to go before we hit 400!

As more Micro.blog bloggers use categories to organize their posts, I want to keep making categories more useful while retaining the simplicity of microblogging by default. Today we’ve added an option on the web (under the new “…” button when starting a new post) to choose categories right as the post is being created, as well as a new interface that can filter blog posts into categories based on the text in those posts.

For a while we’ve had a feature to automatically filter photo posts into a category. If you create a category called Photos or Photography, Micro.blog gives you this simple checkbox on the categories screen:

This is powered by filters that look for a match in the title or text of a post and then set a category for you automatically. These filters can now be managed from a new “Edit Filters” button on the categories screen on the web:

By default, filters are applied to new posts only. To also apply the filter to all posts, there’s a new “Run Filter” button. For blogs with thousands of posts, make sure to give Micro.blog a little time to update all your posts and publish them to your blog.

When we released Micro.blog 1.7 for iOS last week with Sign in with Apple support, Micro.blog could not actually send email to Apple’s private relay server. This is an issue that has popped up on the Apple developer forums and likely affects many developers. I was so excited for Sign in with Apple that I thought it was worth shipping anyway, crossing my fingers that we could resolve it shortly after iOS 13 was out.

Apple’s private email relay server is almost completely undocumented. In this blog post I’ll describe how I got it working.

The key issue is that the “return path” of your emails must be using a subdomain that can be verified by Apple. This blog post from SendGrid describes the solution in detail. I was happy to discover that I could customize this in the settings in Mandrill as well under Settings → Sending Defaults:

Here are the steps I took:

• Create a new subdomain. I decided to use mail.micro.blog. Set the TTL to just 1 minute, because you will need to change the DNS record multiple times during this process.
• Initially the subdomain should be a CNAME to your email provider. Mine was set to mandrill.com.
• Make sure you have SPF records for this new subdomain. Mandrill will walk you through this when you add a new subdomain under Settings → Domains → Tracking & Return Path Domains.
• Start registering the new subdomain in Apple’s developer portal. Apple will check the SPF records at this point. After you click Register, download the verification file.
• Create a new web site somewhere for your subdomain and update your DNS record to now point to that web host instead of Mandrill. The web site must support the latest encryption settings for HTTPS or it will mysteriously fail verification from Apple.
• I put the subdomain on GitHub Pages so I didn’t need to spin up a new server somewhere for it. If you use GitHub Pages, make sure to create .nojekyll file so that the .well-known folder that Apple needs isn’t skipped.
• Upload the apple-developer-domain-association.txt file from Apple to the new subdomain web site. Wait a few extra minutes to make sure the DNS has changed before clicking Verify at Apple.
• Also verify your root domain name and add the from email address you will be using to send email. Here’s what my settings look like when everything is working:

And finally:

• Change the DNS record for your new subdomain to point it back to mandrill.com.
• If any previous emails had already bounced, remove those from Mandrill’s blacklist under Settings → Rejection Lists so they will try to send again in the future.

As I type all of this out, I still can’t believe it’s so complicated. Apple should both document this and remove as much friction as possible, for example by allowing domain names to be verified by DNS records alone and providing much more detailed error messages when things go wrong.

I almost forgot to post to my blog for the 6th day of trying games on Apple Arcade. Remember those sliding block puzzles? The Enchanted World is that but set in a wonderful fantasy design where your character moves through the story using magic to set the world right.

I was going to stop my micro review there, but after I started playing the game I came across the story of the developer and designer who created it. Apple featured them in this newsroom blog post:

For creators and friends Ivan Ramadan and Amar Zubcevic, both 33, the game is much more than that: It’s a metaphor for a child growing up in a time of war. Both Ramadan and Zubcevic grew up in Sarajevo during the conflicts in the Balkans in the 1990s, and both had parents that used creativity to shield them from the violence and danger around them.

There’s also a longer feature on CNET about the developers.

Matt Mullenweg blogged that Automattic has received a Series D funding round of $300 million. He had some interesting comments in an interview with TechCrunch about how much they want to grow WordPress, comparing it to Android’s 85% market share and even going beyond that:

What we want to do is to become the operating system for the open web. We want every website, whether it’s e-commerce or anything to be powered by WordPress. And by doing so, we’ll make sure that the web can go back to being more open, more integrated and more user-centric than it would be if proprietary platforms become dominant.

I’ve long been inspired by Automattic. They were the best company to acquire Tumblr and they seem well-positioned to make a dent in the dominance of Facebook and Twitter. But also I’m thinking about one of the IndieWeb’s principles:

Plurality. With IndieWebCamp we’ve specifically chosen to encourage and embrace a diversity of approaches & implementations. This background makes the IndieWeb stronger and more resilient than any one (often monoculture) approach.

WordPress is at 34% of web sites right now, and I can easily see it getting to 50%. Growing bigger than that might take away one of the beautiful things about the web: the diversity and flexibility to move between platforms. I’m rooting for Automattic to take market share away from the big social networks, but there should be a variety of tools available to build web sites, including platforms like Micro.blog.

We added Sign in with Apple to the next version of Micro.blog for iOS 13. It can be used to sign in to an existing Micro.blog account, or to create a brand new Micro.blog account right from iOS. It is the fastest way to start blogging.

Because Micro.blog doesn’t have passwords, in previous versions we had to send you an email to confirm signing in. With Sign in with Apple, we can skip this email verification and quickly sign you in with Touch ID or Face ID.

If you have an existing Micro.blog account and use Sign in with Apple with the same email address, you’ll be signed in to your current account. If you pick an email address that doesn’t match the email address used in Micro.blog, or if you choose Apple’s private email relay, Micro.blog will create a new account and start a hosted blog trial for you.

A few things to be aware of:

• You can have multiple email addresses associated with your Apple ID. When signing in, make sure to pick the one that is used by Micro.blog.
• If you accidentally create a new Micro.blog account, you’ll want to delete it so that you can sign in to your real account.
• Micro.blog cannot currently send email through Apple’s private relay service. I hope this will be resolved soon.

This update to Micro.blog ships on Thursday with iOS 13. If you’re already running iOS 13, you can try this update early by joining the TestFlight beta.

Last year after Twitter changed their streaming API so that apps like Twitterrific and Tweetbot could no longer use it, I blogged that I wanted to do everything I could to support third-party Micro.blog apps:

With that in mind, I’ve mentioned before that I’d like to offer a push notification service for developers. iOS and Android developers could upload their push notification credentials from Apple and Google. Micro.blog would store them and deliver push notifications directly to third-party apps.

That is now a reality. Today there’s a new beta of Gluon for Micro.blog that includes push notifications. Micro.blog sends the notifications on behalf of Gluon so developer Vincent Ritter doesn’t need to run his own server.

The other popular iOS app for Micro.blog is the open source Icro. I’ve added a comment to this Icro issue on GitHub with details on the new API. I’m looking forward to working with anyone building native apps for Micro.blog to enable push notifications for their app.

I can’t believe it’s been 2 years since Brent Simmons announced JSON Feed. In the first months after the spec was released there was a lot of activity on GitHub and interest from developers. The format has proven really useful in Micro.blog, in feed readers like Feedbin or Brent’s own NetNewsWire 5, and just to make it easier to build new web tools.

We’ve received some great feedback, and I’ve been reviewing a bunch of the issues on GitHub. There are a few things that we want to incorporate into the spec. I’ve posted a list of proposed changes over on GitHub.

Richard Williams passed away a couple of weeks ago. The day after, my family and I went to see the Animation Show of Shows at the Alamo Drafthouse. It was a wonderful collection of films — beautiful to experimental, funny or thoughtful, with a variety of different mediums.

But thinking about it now, none of the short films were really in the painstaking hand-drawn style of Richard Williams, who had incredibly high standards for what animation could be. He would embrace doing the work of drawing every frame, with few holds or shortcuts.

The films in the show weren’t trying to do that, and that’s fine. But I hope someone again picks up the depth and quality that Richard Williams brought to the industry. I blogged about him back in 2013, and I remain inspired today.

Blogs hosted on Micro.blog provide a lot of flexibility with custom CSS, themes, and Hugo templates. But if you are making major changes to the design of your blog, you may not want to do that live and risk breaking anything for your site visitors.

I often test out changes on a 2nd fake blog I created on Micro.blog. It’s like an extra sandbox that I can play in to edit templates without touching my real blog, and it’s useful enough that I want everyone else to be able to do the same thing.

Micro.blog now lets you create a free test blog for your account with a URL like username-test.micro.blog. There’s a button to create the test blog under Posts → Design → Edit Custom Themes. It will appear as a free 2nd blog on your account, and you can post to it, upload files, or try out custom themes.

Because custom themes on Micro.blog can be shared across multiple blogs, when you’re happy with any changes you’ve made in your new theme, you can assign the theme to your main blog and all those changes will be applied to both sites. I’ve also added a “duplicate” option that makes a new copy of the theme so you can edit templates in the duplicate theme on your test blog.

I’ve updated Micro.blog today to help Mastodon users follow people on Micro.blog. It used to be that if you clicked from Mastodon to a Micro.blog user, you just ended up their blog home page. Now it redirects to a special version of the Micro.blog profile screen which includes a follow form.

This is very similar to Mastodon’s default remote follow form, or Aaron Parecki’s profile page. For more about how to use your own blog’s domain name as your Mastodon-compatible username, see this Micro.blog help page about ActivityPub.

DHH blogs about giving a chance to smaller companies to help fix the problems with massive tech companies controlling so much of the web:

The world is full of alternatives to the Big Tech offerings that give you 95% of the utility for 0% of the regret. But if you can’t even be bothered to give up 5% to help an alternative along, you also can’t be surprised when the alternatives are so few and far between.

This is how I’ve been feeling about Instagram. I hear people complain about Facebook all the time. But then some of those same people turn around and post photos to Instagram instead of their own blog.

Complaining helps when the company listening cares about the same problems we do. For example, Apple and privacy. But the solution to massive social networks is already in our hands.

Curtis Herbert has a great blog post about starting an Android version of his app Slopes. Adding social features made it more compelling to support multiple platforms:

In any given group of friends the odds of a mix of both Android and iOS users is very high (not to mention Europe is a big potential market for me, and Android is much larger over there than in the states). If someone on iOS loves Slopes, but their friend group ends up using one of my competitors because it supports both platforms and therefore the entire group can join in on the in-app fun, that’s going to go poorly for Slopes.

What I find so interesting about this decision is that Curtis seems to be intentionally expanding the scope of Slopes. Everything he writes about with Android makes sense if you first assume that the social features will be an important selling point and grow the audience for the app. Other indie developers might instead choose to keep the app focused on iOS and solve a more narrow set of problems, and that’s fine too.

I’m thinking of my discussion with Daniel Jalkut on last week’s Core Intuition about whether we should try to change the world (which often means bigger apps and more platforms to reach the most people) or focus on just building an app that’s really good at what it does (but might not be revolutionary).

Micro.blog would benefit from an official Android version, so a lot of Curtis’s post resonated with me. Luckily the third-party app Dialog (and upcoming app Gluon) can help fill that void in Micro.blog in a way that isn’t possible with non-platform apps like Slopes.

Dialog is a full-featured Micro.blog app for Android. Jacky Alciné blogged about it today while thinking about Micro.blog and IndieWeb mobile apps:

I decided to look at the client landscape for micro.blog, the most mature social platform that’s built around IndieWeb principles. I defined maturity as a platform that allowed immediate on-boarding into the community, provided a very simple (no-explainer) interface on how to get started and made it easy to go beyond it. That level of support is something I want my suite of tools to have - and I’m still working on it.

Because Dialog is such a polished app and already open source, I wondered if it could be the foundation for additional IndieWeb-related features for Android users. The official repository with the source code for Dialog is on Gitlab here.

I’ve also copied it to the Micro.blog account on GitHub, in case it’s useful for any GitHub users to browse or fork the code there. Thanks again to Mike Haynes for Dialog and for making it available in Google Play, as well as open-sourcing it!

Congratulations to Brent Simmons and all the contributors of NetNewsWire for shipping version 5.0 today. Here’s Brent with the announcement:

This release took five years to make, and for four of those years it wasn’t even called NetNewsWire. It was just a year ago that I got the name NetNewsWire back from Black Pixel — and I thank them again for their wonderful generosity.

Each major new version of an app is an opportunity to refocus, and NetNewsWire 5.0 prioritizes all the right things: it’s fast, embraces the open web, and feels at home on the Mac. NetNewsWire 5.0 takes everything Brent learned from previous versions, but rebuilt from scratch with modern features like Feedbin syncing, Dark Mode, and JSON Feed support.

And for folks on Micro.blog, NetNewsWire 5.0 also includes a sharing option to start a new microblog post right from an article you’re reading in NetNewsWire. It’s a great way to quickly share links on your microblog.

I’ve decided to add Tumblr as a cross-posting service in Micro.blog. This means Micro.blog can take your blog posts and automatically copy them to a Tumblr blog.

I usually avoid adding blog hosting services to Micro.blog’s available cross-posting destinations. After all, if it’s a good blog host that I could recommend as your primary blog, why not just post everything there instead of using Micro.blog’s own blog hosting? But the more I’ve used Tumblr in the last couple of weeks, the more I think about Tumblr as a community first and a blog host second.

To add a Tumblr blog in Micro.blog, on the web click Account → “Edit Feeds & Cross-posting” → “Add Tumblr”.

In related news, I’ve removed the upload file size limit when importing a Tumblr blog archive to use Micro.blog hosting. If you have a Tumblr, Medium, or WordPress blog that you’d like to migrate to Micro.blog, click Posts → Import.

Twitter announced in a blog post that they have removed over 900 fake accounts spreading misinformation about the protests in Hong Kong:

This disclosure consists of 936 accounts originating from within the People’s Republic of China (PRC). Overall, these accounts were deliberately and specifically attempting to sow political discord in Hong Kong, including undermining the legitimacy and political positions of the protest movement on the ground. Based on our intensive investigations, we have reliable evidence to support that this is a coordinated state-backed operation.

I like that Twitter is being proactive and transparent about this. It’s especially remarkable that they notified a competitor, Facebook, about similar fake accounts on Facebook’s platform.

Unfortunately there’s a deeper problem here. It’s not just the fake accounts and misinformation, but the way that Twitter’s design can be exploited. It is too easy to piggyback on trending hashtags to gain exposure.

Maciej Cegłowski of Pinboard called attention to the promoted tweets:

Every day I go out and see stuff with my own eyes, and then I go to report it on Twitter and see promoted tweets saying the opposite of what I saw. Twitter is taking money from Chinese propaganda outfits and running these promoted tweets against the top Hong Kong protest hashtags

I wrote about this in 2018 when introducing Micro.blog’s emoji feature:

Hashtags and Twitter trends go together. They can be a powerful way to organize people and topics together across followers. But they can also be gamed, with troublemakers using popular hashtags to hijack your search results for their own promotion or unrelated ranting.

We’ve expanded search and discovery in Micro.blog slowly for this reason. While Micro.blog is certainly too small to attract the attention of state-run propaganda, there has been spam going through Micro.blog that no one else sees. I’m convinced that limited search, no trends, and active curation are the right foundation so we don’t end up with a design that creates problems when Micro.blog does get bigger.

In all the Mac and iOS software I’ve worked on over the years, I don’t think I’ve ever had a new release ready as soon as Apple shipped their major updates to macOS or iOS. The timing just never works out, so I update a couple of weeks or months later. For iOS 13, I’m finally ahead of the game.

I just updated the beta of Micro.blog for iOS with a couple fixes, especially for dark mode on iOS 13. There’s more to do, but I feel really good about being able to have this ready.

If you’re running the beta of iOS 13, you can sign up for the Micro.blog beta here. Thanks for testing!

I’m excited to see where Automattic takes Tumblr, but even today there are already several Tumblr-related features built in to Micro.blog. Here are a few ways that Micro.blog can integrate with Tumblr.

Follow Tumblr users on Micro.blog: Micro.blog tries to play nicely with the rest of the web, so you aren’t limited to just following Micro.blog users. To follow someone’s Tumblr blog, on Micro.blog click Discover, then click the search icon, and enter their Tumblr domain name:

Click on the Tumblr user to preview their posts and follow them. Now when they post to their blog, those posts from Tumblr will appear in the Micro.blog timeline. Short posts, photo posts, and art from Tumblr look great in Micro.blog.

Add your Tumblr feed to Micro.blog: If you actively post to Tumblr and also have a Micro.blog account, you can add your Tumblr RSS feed to Micro.blog so that when someone follows you on Micro.blog, they see posts from both your main microblog and your Tumblr blog.

Click Account → Edit Feeds & Cross-posting, then paste in your Tumblr RSS feed:

Import your Tumblr blog to Micro.blog: Maybe you no longer maintain your Tumblr blog and want to move your old posts over to Micro.blog. First, export your posts from the Tumblr dashboard. That will give you a .zip file you can import into Micro.blog under Posts → Import.

Thanks to the “on this day” feature that Jonathan LaCour built for Micro.blog-hosted blogs, I noticed that 7 years ago yesterday I blogged about App.net reaching their funding goal. I still get asked about App.net sometimes. It is easy to look back on something that didn’t last and pick it apart. I’d rather look at the good things that came out of App.net.

When it was shutting down, I blogged my thanks to the App.net community:

I wrote in 2013 that it was not just a Twitter clone but an amplifier for applications that couldn’t be built before. It came along at the right time, took off, and then faded. The App.net founders deserve significant credit and thanks for trying something risky and succeeding to grow a community that lasted so long.

There is a guiding principle in Micro.blog that differentiates it from nearly every other platform. It’s not only about creating an alternative social network. The foundation is around blogs and IndieWeb standards because that’s part of unrolling the damage caused by massive silos.

Micro.blog is also designed around blogs because it gives immediate value to the platform, insulating it against the network effect that drives the success or failure of most other social networks: not all your friends are there yet. Unlike ad-supported platforms, Micro.blog aligns its business model with customer needs. Subscriptions for blog hosting let us deliver the best features we can, and also help support the rest of the platform.

Brent Simmons really said it best:

Micro.blog is not an alternative silo: instead, it’s what you build when you believe that the web itself is the great social network.

I often look back at this quote to help guide me as I evaluate the direction of Micro.blog. I believe that Micro.blog is the first platform of its kind. The closest competition might be Tumblr, acquired yesterday by Automattic.

Of course it was coincidence that Automattic acquired Tumblr pretty much exactly 7 years after App.net was funded. No one is paying attention to those dates. And yet, now that I’ve noticed it, there’s a kind of symbolism to it. Tumblr is effectively being re-funded.

Like Micro.blog, Tumblr is about making blogging easier. Like Micro.blog, Tumblr allows custom domain names for your blog, something no other major social network allows. Unlike Micro.blog, however, Tumblr’s community is only Tumblr blogs. Micro.blog’s community brings together not just Micro.blog-hosted blogs, but people using WordPress, Mastodon, or home-grown IndieWeb solutions.

Matt Mullenweg and the Automattic team have a bunch of work ahead of them to integrate Tumblr into the WordPress ecosystem. I don’t know how that’s going to play out, but I know that preserving all the Tumblr blogs and giving them new life is a good thing.

I wonder if Micro.blog and Automattic are on parallel tracks. Two companies wildly different in size and scope, but we can all learn from platforms that have come and gone, finding our own path to a shared vision of the future that embraces content ownership, supports healthy communities, and deemphasizes massive social networks. I’m wishing the team at Automattic the best.

Micro.blog is not a popularity contest. We don’t have follower counts or public likes because we think those numbers have overshadowed more important aspects of blogging, like the quality of writing and engagement within the community. But we do hear from podcasters using Micro.blog who hope to one day have sponsors for their podcast, and so they do need to know approximately how many listeners they have.

Today we’ve added a setting to enable basic MP3 download counts if you’re hosting your podcast on Micro.blog. It is off by default. It’s likely that most podcasts — especially podcasts that are just getting started — do not have many listeners, and that’s fine! If you don’t plan to have sponsors for your podcast, you can ignore this setting.

It takes time to build an audience. Don’t get discouraged. There’s value in telling your story whether it reaches 5 people or 500. I love recording my microcast Timetable because it helps me think through things I’m working on and share that process with anyone who is interested in Micro.blog.

There aren’t any fancy graphs for this feature. Just a download number for each episode under Posts on the web, next to the “Edit” and “Delete” buttons. You can enable it with a checkbox from Posts → Design. Micro.blog is not tracking the downloads until you enable it, and it doesn’t count you viewing your own podcast, so initially there won’t be anything to see until your podcast feed is refreshed and your MP3s are downloaded again.

With this setting enabled, Micro.blog modifies your podcast feed to use different MP3 download URLs. It may take some time before the new URLs make it to all your listeners.

Micro.blog’s download tracking does not closely follow the IAB guidelines yet. It is intended as a rough estimate. I’ll be working toward IAB compliance in the future.

Happy podcasting! Let me know if you have any feedback.

When I started reading Ruined by Design, my first thought was that I had missed the window for writing my own book, Indie Microblogging, because Mike Monteiro was making all the same points that I was writing about. Luckily that wasn’t the case. Mike does cover some of the problems with social networks, but most of the book is focused on how designers can think about their work. I recommend it. (And it’s just as important for programmers and everyone else who is contributing to a product.)

Mike was also a guest on today’s episode of Presentable with Jeff Veen. I finished the book last month, so the podcast was a nice recap of a few of the main ideas and stories from the book.

I love photo blogs. Last year, Jonathan LaCour wrote Microgram to allow anyone on Micro.blog to paste in a little JavaScript on their blog to show a grid of photo thumbnails. This has been a really popular add-on for Micro.blog — thanks Jonathan! — but we knew we’d eventually need this as a built-in feature.

Today I’ve added a new page for photos so that new blogs hosted on Micro.blog get something that works out of the box without JavaScript. We’re starting with a simple grid of photo thumbnails similar to Microgram, each linking to the microblog post, and I’d like to expand it with more options in the future.

It uses CSS Grid Layout, so you can also customize a bunch of things without changing the template. For example, to change it to 5 equally-spaced columns, click Posts → Design → Edit CSS and paste in:

.photos-grid-container {
  	grid-template-columns: 20% 20% 20% 20% 20% !important;
}

This new photos page is created automatically for any new blogs on Micro.blog going forward. If you already have a page called “Photos” and want to switch to using the new page, you can delete the page you created manually. Micro.blog will then show a “New Photos Page” button to create one of these new pages for you. (You can also rename or re-order the page.)

Apple this week rolled out an updated list of categories for their podcast directory. Some old categories were removed and new categories added. It’s a better fit for what the podcasting world looks like now.

If you have a podcast hosted on Micro.blog, I’ve updated Micro.blog today with the new categories. On the web, click Posts → Design to see the new list. (Your current category will continue to be used until you update your podcast settings.)

Thinking about starting a podcast? Micro.blog podcasting is $10/month and also includes a full blog and video hosting.

I wanted to highlight 2 new blog posts from the Micro.blog community about customizing themes. Because Micro.blog uses Hugo templates, there’s flexibility to change the design or even override our default feeds.

• Chet Collins used a custom theme to change his podcast feed to use different artwork.
• Ricky de Laveaga updated the Hello theme with some CSS tweaks including improvements for dark mode.

As Micro.blog matures, it’s important that we keep the default interface as streamlined as possible. It should be as easy as tweeting to start your first blog post. But I love that there’s a lot of power under-the-hood for people who want to tinker with it.

Micro.blog makes it really easy to post some text and a photo to your blog, but sometimes you want a longer post that includes multiple photos. Because Micro.blog puts all the photos at the end of your post by default, I’ve noticed some people looking for an easier way to draft longer posts.

I’ve added a new “Copy HTML” button next to photos on the Uploads screen in Micro.blog. Using this button, you can first upload multiple photos, then copy and paste the right HTML reference into your blog post draft wherever you want. Happy photo-blogging!

Jason Snell has a post for Macworld reacting to the news that Apple plans to fund original podcasts:

The great thing about podcasts—and I say this as both a listener and a creator of podcasts—is that it is, like the web, a free and open ecosystem for content. You can listen to any podcast in any podcast player. If Apple creates podcasts that can only be listened to in Apple’s own app, it is furthering a potential future where your favorite shows are scattered across multiple services and siloed in different apps.

No one is too alarmed by this Apple rumor, because maybe nothing will come of it. But a good way to think about it is to imagine if the popularity of Apple and Spotify were reversed. Imagine if Spotify was the one with 60% of the podcast app market and then they decided to release Spotify-only exclusive “podcasts”. It would be an obvious threat to the openness of podcasts.

I wish I could give Apple the benefit of the doubt on this, but the risks are too great. Apple has more power than any other company over the podcast ecosystem. Just because they haven’t interfered with anything so far doesn’t mean they can’t still ruin what we’ve got.

I want to give everyone a heads-up about a change we’re making next week. When Micro.blog launched, it was really important to me that the service was as affordable as possible. Because of that, there were options to use it for free with an external blog, use it with the $2/month cross-posting, or have Micro.blog host your blog for $5/month. We later added podcasting and video hosting for $10/month.

As Micro.blog has improved, I think our blog hosting has become a great value. The price of the $5 subscription won’t change. But the $2 subscription introduces a lot of confusion. It’s priced per domain name, and it’s not obvious when or how to switch between the different plans. It also adds a lot of complexity on the backend to manage all the possible subscriptions.

To fix this, we’re removing the $2 plan and updating the $5 blog hosting to also include cross-posting from any domain name. If you’re only using the $2 cross-posting, don’t worry. We will switch you to the new plan but apply a $3 monthly credit to your account indefinitely, effectively keeping your original pricing.

Pricing Micro.blog has always been interesting because it needs to appeal to people who just want a new social network (usually $0/month) but also to people who want a great blog host (often $20/month). I think these changes keep the right balance to accommodate the different needs that people have with Micro.blog, while making it simpler for new users. Thanks for your support!

Last year after IndieWeb Summit in Portland, I sat down with IndieWeb co-founders Tantek Çelik and Aaron Parecki to talk about the history of IndieWebCamp for my upcoming book, Indie Microblogging. Only part of the interview will fit in the book, so I’m including a full transcript of our conversation below and on GitHub, where I’ll be incorporating any edits and also publishing future chapter drafts.

Manton: Take me back to 2011: the founding of IndieWebCamp. What did that feel like? How you all got together. How the first IndieWebCamp got started.

Tantek: You weren’t at the Federated Social Web Summit in 2010, were you? Did you hear about it? Did it even cross your radar?

Manton: I assume it did. But that’s already been a while.

Aaron: Nine years ago…

Tantek: Because I think that’s where the inspiration originally came from.

Aaron: So 2010 was the Federated Social Web Summit — in Portland — and that was the invite-only but “you could kind of ask for an invite”-style event.

Tantek: Which we now know greatly biases towards people that feel privileged enough to ask for an invite, so it’s sort of a bad way to do it. I didn’t even put that together until the last year. Yeah, don’t do that kind of private conference.

Aaron: So I ended up there, Tantek, as well as a bunch of others. It was a fun group, but the thing that we took out of it was that the focus seemed to be on people building things for other people, building specifically platforms. They were coming with platforms and trying to make them work together. Which is a fine goal, but that wasn’t my personal interest in it necessarily. So it was more like, “oh, I have this Buddycloud thing, let’s make it work with Friendica”. Or Diaspora was there.

Tantek: The Diaspora 4 were there, which was cool. That’s where I really got to spend time with them.

Aaron: And there was also a lot of solving problems in theory without actually testing them out or building something first. And a couple of pretty in the weeds discussions that I ended up sitting in on and was like, “this is really complicated”. I feel like there is a better solution. That was where SWAT0 the concept was formed as well, right? Interoperability tests between social networks — can someone post a photo of somebody else using a different system be notified that they were tagged in a photo and then a third person comment on the photo and have that comment notification appear on the person who favorited it. Everybody has to be using different software for that test to pass. SWAT0: social web acid test.

Tantek: It was actually really hard.

Aaron: Very hard. It still is.

Tantek: As far as we could tell no one actually got it to work across different sites.

Aaron: The goal with SWAT0 was to have three different systems interoperating. Several people claimed that they supported everything needed for SWAT0 themselves. But by definition that doesn’t solve SWAT0 because you need three different implementations. So there were several people who were like, “I can be every person in this — every role in this test”. But then there’s no one to test it with, because only one person would do that at a time. And we are still kind of in that situation sadly. It’s still a very hard problem. We did in 2015 have a demo of it working between three different recommendations, although each implementation only was able to be one or two of the roles of the three.

Manton: And that was using Webmention?

Aaron: Yeah, exactly.

Manton: So back in 2002 what was the technology to.. It was way after Pingbacks and Trackbacks.

Aaron: Yeah, the thought was the OStatus stack. Atom. Salmon for the responses.

Tantek: PubSubHubbub, I think.

Aaron: I believe so, yeah. For finding the photo in the first place.

Tantek: But Salmon for the notification.

Aaron: Salmon for the notification of the comment. But in order for someone to see it in the first place they would be following an Atom feed, probably, with PubSubHubbub.

Manton: And so now Salmon is making a comeback with Mastodon, right?

Aaron: No, it’s already done.

Manton: It did briefly make a comeback and then got replaced.

Aaron: Mastodon ripped out their whole code and replaced it with ActivityPub. So after that event we were like, “okay, that was cool, but we want to focus on people being more empowered individually to participate in this federated network.”

Tantek: Everyone got to give lightning talks. That was part of it.

Aaron: Yeah, yeah.

Tantek: Which was great. About any topic, like why they were there and… What was your lightning talk on?

Aaron: Probably location stuff, because I was just starting geolocate at the time. But the sense I got was that the assumption was that in order to participate in a federated social network, you have to be on a platform that supports the protocols. The only way to do that was that if someone built the platform that interoperates with other platforms, and then you as an individual join one of those platforms. There was no “just my web site”.

Tantek: Or one-person platform.

Aaron: Or single-person platforms was like: why would you do that? That was the feeling there. That was why we did IndieWebCamp the year after, because we wanted to approach it from the grassroots of: someone should be able to take their web site and be able to use their web site to participate in the same distributed social network — federated social network.

Manton: As the conference was wrapping up, did you have a feeling that y’all would probably do IndieWebCamp, or was it making friends and catching up with people.

Tantek: We were mostly catching up with people, meeting new people. I was just looking at my notes, because I actually put my entire talk from it on their wiki because it’s like that’s how it’ll survive. Turns out wikis are more persistent than PowerPoint.

Manton: So in that time… 2010 is actually a really interesting time because Twitter had been around for a few years and really gained a lot of steam, and actually a lot of early bloggers — who were blogging all the time in the early days — around 2010-ish they dropped off. They started just doing Twitter.

Tantek: Even just 2009…

Manton: Twitter satisfied that “I’m going to post something”. And you can see that. I went back recently and looked at a bunch of people that were doing blogging software. Founders of Blogger, Movable Type, and Six Apart people. And very few of them kept their blog through that period. So could you sense that at the time?

Tantek: Totally. Just even personally, the last blog post I wrote on my old blog was in August of 2008. I did not have anything on my own site in 2009. 2009 was a really weird transitional period, because I both saw that happening and I saw it happening to myself. And then the other thing that happened simultaneously — which I think helped — is that Twitter was really unreliable in 2009. We all switched to Twitter and then it got really unreliable. It was so frustrating.

Tantek: First of all I’m embarrassed that I’m not posting to my own site anymore, and then I’m frustrated because this damn tool is never up. And that’s really where I came up with the idea of, well, I should post to my own site and if I could set up a system where I can always just post to my own site, whether or not Twitter was down, then I can just have my site post to Twitter when it comes back up. And I can abstract away that frustration of their site being down. Abstract away their unreliability, while still getting that participation with friends thing. So 2009 is when I started working on what’s now my web site. Launched in 2010. January 1st, I’m like: from now on everything is going on my site first.

Tantek: And then the Federated Social Web Summit happened and I was like, “woah, okay”. But the platform perspective that Aaron was pointing out. Wait a minute, you don’t need to use a whole platform. Everyone can do this themselves. So that was my lightning talk, basically, and it even ended with… I’ll show you the summary: use your own site as your identity; publish on your own site; and then syndicate with PubSubHubbub. That’s still true.

Manton: And the first one, importantly… The very first principle of the IndieWeb principles is that. Use your own site, own your own content. Domain names are a big part of that. Really the biggest thing. Unfortunately domain names have not changed since 2010. They haven’t changed since 2000. It’s interesting that something so important, that “step one” is still really confusing to people.

Aaron: Yeah.

Tantek: Oh, that’s you’re going with that. I thought you were going with like, “they’re still around”.

Aaron: And it’s still just as hard.

Manton: I’m going with: why aren’t they easier? Because a lot of what the IndieWeb does, if you look at Microformats and Micropub and all these core parts of the IndieWeb, they’re built on HTML and HTTP where we have some control over making things easier and having other standards.

Tantek: Yes.

Manton: Is there hope for making DNS also easier for people, or are we just kind of stuck with this for a while?

Tantek: The irony is I don’t know what you’re comparing it to. Look at the amount of time it takes you and the form you have to fill out to get a new phone number. I would challenge you to do an A/B test. How long it takes to get a new phone number from scratch, not having a phone number, to how long it takes to getting a new domain name. And I would bet that it’s actually fewer steps to buy a new domain name. So I definitely sympathize that it could be easier to buy a domain name, but compare it to other forms of identity that people take for granted. It is less work to do. Or maybe the hard part is picking a domain name.

Aaron: Yeah, that’s part of it. A phone number just gets assigned to you.

Manton: And everybody kind of knows how phone numbers work, I guess. No one’s surprise that there’s a 3-digit area code, and a 3-digit number, and a 4-digit… Whereas with domain names there’s certain things (and IP addresses) that people are surprised by.

Aaron: Getting the domain is the first step. But then once you have it you have to know that you now need to set up DNS on it and point it at a hosting provider. And that’s the part that’s different from a phone number. Because once you have a phone number, it almost certainly came with a phone. You don’t buy a phone number and then assign it to a phone. You do that all as one step.

Tantek: It turned out that the equivalent of phone number registrars, all cell phones… It would be as if every domain name registrar — and a lot of them do now — sell hosting. So right off the bat, they’re like, “here’s a domain name, do you want us to flip on a simple web site for you?” A lot of them do that. That has changed.

Aaron: Yeah. That’s true, actually. That has gotten better. It used to be that GoDaddy or Name.com or NameCheap only did domain names. And then they all started adding hosting plans to their product.

Tantek: Which makes sense.

Aaron: It absolutely makes sense. And when you use the hosting plan provided by the registrar it is actually very easy, because it is more like you just go there, type in the domain you want, pay, and then now you have the empty shell to put stuff on. Doing something with the empty shell of a hosting plan is another step, but at least they do make the DNS to hosting step combined into one.

Tantek: Other hosting providers have made it easier to one-key turn on WordPress, turn on Known. I don’t know there’s a domain name registrar that also has easy hosting that also has a simple turn on a web site CMS.

Aaron: DreamHost does a pretty good job of it.

Tantek: That’s true. DreamHost probably has the most pieces that they’ve put together. And they were the first to do LetsEncrypt automation. Domain name, security, hosting. So that’s evolved. It’s very impressive to watch, even during the whole eight years of IndieWebCamp.

Manton: And comparing it to the phone numbers, if you go get a phone from someone they can always give you a phone number — if you go to Verizon or AT&T. And maybe where we need to be eventually with the web is that any place you can go get a web site can give you a domain name, which is not really true right now. The big companies can, but a smaller webhost can’t necessarily.

Aaron: You can, but it’s more work as a service provider. There’s plenty of domain resellers. I built a system to do that at one point, where we wanted to be able to offer domains as part of the product we were offering. So I found a domain reseller that had an API and hooked it all up. You would come to us and click the button for, “I want this web site with this theme.” It worked seamlessly.

Tantek: Even GitHub should it doing that, right?

Aaron: Right, for GitHub Pages. Instead of just offering GitHub Pages and being able to map a domain to it, why shouldn’t they offer their own domain registration.

Tantek: And make a little money. There’s incentive there.

Aaron: It would be a no brainer for Micro.blog to offer that feature. Sign up for the Micro.blog account, then right there type in what domain you want and it just works.

Manton: I’d love to do that.

Tantek: It’s also the kind of thing you could always add. “Yeah, now I’m ready for a domain name.”

Aaron: Yeah, you upgrade your subdomain to a real domain.

Manton: So you had mentioned with the changes in the last seven years… Going back to that first IndieWebCamp. We’re just wrapping up IndieWeb Summit 2018. Does it feel the same in terms of the community and what people are excited about? Obviously standards and everything else have evolved.

Aaron: The biggest shift in that context that I’ve seen between the original ones, specifically, although even from 2014 to now. Now we actually have a lot more stuff working together than we did in 2011, obviously, and even in 2014. At the beginning it was the same goal, the same ideals, but we couldn’t demo me commenting on someone’s post. That didn’t work until way later. And because of that the sessions were all drastically different, because there wasn’t a thing to coalesce around except for the ideals of own your data, have a domain name, do stuff on your web site.

Aaron: So if you go back and look the original sessions from 2011 to 2014, it’s a wide variety of things. Now at IndieWebCamps you end up with a lot of people who are coming to it and then become aware that there are things that work and then want to learn how to do those things. Now at the beginning of the second day we have the intro to the building blocks session. What is IndieAuth. Get Webmention working. Even in some of the IndieWebCamps there will be a whole track of unconference sessions about those building blocks for the whole day, where it’s people who know they want to learn these things that already exist.

Tantek: You had a session called “own your phone number”.

Aaron: That’s right. Yeah, I have actually kept that up. My phone number and my cell phone are completely disconnected. They’re not coupled. So my phone number is provided by Google Voice and I forward it to a phone number that I don’t know that my cell plan is on. I have no idea what my phone number is — the one on my phone. And I give out my Google Voice number as my identity.

Manton: When was that talk?

Aaron: That was 2011.

Tantek: The talks were so varied back then. We were just figuring out so many basics that a lot of the talks were very exploratory. We figured out some things like, “okay, I figured out how to syndicate into Buzz and Twitter, how about other places?” Then there was advocacy for plain text formats and there was a BitTorrent session.

Aaron: Yeah, I think that’s the biggest shift I’ve seen is that there’s so much more stuff that’s actually working now that’s functional. And it means that people are coming and wanting to learn that. And of course there’s still the experimental stuff. There was a good set of experimental sessions at this event. But there’s a lot more of: we have stuff working now that you can figure out and learn how to use.

Manton: There are two things, too. There’s all the IndieWeb-friendly formats and protocols are much more mature and established now, so that you could talk about the building blocks as a real thing. But then there’s also… It seems like the software is much further along. A bunch of people will come to the IndieWeb and they use WordPress, because WordPress powers 30% of the internet and it’s super popular. But there’s still a pretty good mix in the demo sessions and what people are hacking on of WordPress stuff and also “no, I rolled my own”.

Tantek: Yeah, in fact lots more rolled their own, which is not representative I think of people out there in general.

Manton: What do you think about the fact that WordPress is a very dominant platform. Is that good because there’s an agreed thing there everyone can use the same plugins, or are there any drawbacks?

Aaron: WordPress specifically because it’s self-hostable, that benefit ends up overriding some of the other drawbacks of that kind of approach. The danger with something being so dominant.. It’s the monoculture problem. We don’t want to be in a situation where we just have WordPress instances talking to each other. That doesn’t actually solve the problem.

Tantek: Or just have Mastodon talking to each other.

Aaron: Just Mastodon or just Diaspora or whatever, right. That’s the danger. That’s the thing we’re trying to avoid.

Tantek: Because that has lots of even worse consequences.

Aaron: Yes, exactly. And even when it’s a friendly company like WordPress that’s behind it, it doesn’t matter — the same problems.

Manton: You start to build like platform-specific… It’s different than just building for the web in general where anybody can bring their own site and plug in. With Mastodon specifically, it’s based on open standards but it also feels very opaque in a way — how stuff talks to each other. It’s a little more difficult to just build a web site and be compatible.

Tantek: It’s also levels of barriers to entry. Because that’s one thing that myself and I think a bunch of people at the 2010 Social Federated Web Summit we’re frustrated with was a lot of the standards being tossed around — every generation has its own standards — were really hard, like Salmon. I tried to read through the spec and understand what it was doing, and I could not wrap my head around enough of it to even start anywhere coding.

Aaron: I had the same experience at that event. I even then later, a year ago, tried to revisit the spec because Mastodon was using it. I feel like I should be able to have my web site just be a part of this network. I refuse to make a new Mastodon account and treat it as a POSSE destination because that completely defeats the purpose of what Mastodon itself is even shooting for, which is an actually distributed social experience.

Aaron: So I was like, “okay, it can’t be that hard now”. Certainly things have gotten better, and I should be able to just take my web site and add the stuff it needs. I still can’t figure it out. And then they went and dropped Salmon anyway and switched to ActivityPub, so I’m glad I didn’t spend my time on that.

Tantek: It turns out that the difficulty of the standard to implement makes a big difference. Because if it’s super difficult then you end up with only a handful — maybe even just one or two people on the planet — that can implement it, and then you get monoculture by default. In effect, not by design. One of the things we realized was that the antidote to that is to make the standards as simple as possible. Literally as dumb and simple, and frankly decomposed. So that’s where we came up with the building blocks idea rather than having a stack. And the idea that building blocks is you pick and choose the ones that you need for your use cases. That doesn’t mean you’re committed to implementing a layer after layer after layer to get to a certain point.

Tantek: That was a big insight. The more accessible the standards are for any developer to build their own solution. That means that the more they’re going to get exercised, the more that they’ll get good interoperability, the more that they’ll be a community around it. Because that’s really what it came down to.

Tantek: I think that’s kind of where the IndieWeb community started to form — started to really grow and gain critical mass — is the growing number of people that were like, “oh, I can implement that on my web site in an hour or less.” And then in a day they could do amazing things.

Aaron: And it’s demonstrated by the fact that like you look at the RSVP list on the event page, there’s like over 20 people who have been able to have their picture show up on the RSVP list, which works by having them publish a page on their own website and send a Webmention to the event page. That’s pretty cool. They didn’t have to go and read through a whole spec that talks about everything from using an app to publish to your site to then have a federation protocol behind it. They just need to know about this much of the whole picture in order to have that work. And that’s a quicker win. Now maybe you expand and start working on the rest of the building blocks.

Manton: Webmention is a great example of something that is as simple as it possibly can be. Can’t really get that down any simpler. So people get it. Microformats is similar in that it’s very approachable and transparent. If you know HTML you can figure out how to do that. You have Microformats 1 and 2, and remind me… Because Microformats predates…

Tantek: …IndieWeb. 2005.

Manton: And did that launch at SXSW or something like that?

Tantek: Shortly thereafter. I think we had sessions about it at SXSW in 2005, in March. The site launched in June itself. Until then we had just been doing it on the Technorati wiki. And my co-founder of the Microformats.org community, Rohit Khare. He’s like, “hey, happy birthday, I bought you a domain name.” And I was like, “really, you think this is worth having its own domain name?” That was my actual response.

Aaron: Wow.

Tantek: Because it seemed like such a simple stupid dumb thing. And he’s like, “yeah.” Okay, I guess we should do this then, and then we set up the site and well, what do you need on a community site. You need a mailing list, you need a blog, you need a wiki. So we set all those up. Since then we’ve learned that the primary ways of actually making progress are the wiki and IRC channel (or Slack) — an archived IRC channel. But that was definitely a response to, again, complexity. Like the whole RDF world — all that insanity — and the Atom/RSS wars back in the day, and then Atom going to IETF instead of W3C because there was a giant fear that it would just be turned into RDF at W3C. That’s how Microformats 1 started.

Tantek: We basically did make it look as dumb as possible. Let’s just take the names of the terms from the vCard spec and use them as class names. That was what I proposed in 2004 at FooCamp. And I ran it by Ray Ozzie at the time, who was like architect at Microsoft or something, but also just from Lotus Notes, you know he has a long history. He’s like, “yeah, that could work.”

Manton: So now we’re almost 15 years since then. Looking forward, there’s a lot of talk about generations — 1, 2, 3, 4 — moving up and making it more approachable and just easier for people to use. Obviously we can’t predict 15 years from now. Who knows what’s going to be around. Is Twitter going to look the same, are blogs going to be the same…

Tantek: Is Twitter going to be around?

Manton: Exactly. There’re no guarantees. A lot of people… So much time, they don’t remember before Twitter and Facebook and so it’s hard to imagine sometimes that those things could go away. But they could. They’re just web sites. Businesses built by people that make mistakes and do good things sometimes.

Tantek: Yeah, sites that become boring and people move on to what’s interesting. I think Facebook really extended their lifespan by buying Instagram.

Manton: So moving forward, how soon… Because I’m kind of impatient and I want everybody to blog on their site immediately, like tomorrow, and for it to be easy to use. But this stuff takes time.

Tantek: Totally.

Manton: Where do y’all see just over the next few years. How close are we to making this more mainstream or is this going to be just more time churning away building tools, trying to spread awareness.

Tantek: It’s kind of hard to predict. I do feel like we’re entering a new phase right now. I think we’ve had two phases, two very long phases of the IndieWeb community so far. One was this I almost want to say like Big Bang phase in the very beginning where there were all these different things coming out. People trying all kinds of different approaches, like Ward Cunningham did his federated wiki project. He figured out a way to do all this Javascript-based wiki federation thing that he loved. And other approaches. But then we started to coalesce around: use your own site, use Microformats. We actually used Pingback for a while until Sandeep Shetty showed up and he’s like, “hey, I’ve got this proposal for a simpler version called Webmention that does this.” And everyone in the community was like, “well, that completely aligns with our values of making things simpler.” So we instantly adopted it even though none of us knew who this guy was. And then we just ran with it.

Tantek: So the first four years was this explosion of getting basics working. We got RSVPs and events working by 2013. And that was kind of like, “whoa, we federate events and RSVPs,” which we were always looking for ways that in the actual things we do, how can we use the technology that we’re making. And after that, clearly we need to get these standards — that are barely specified — solid, testable, working, dependable, to reach the next level of stability.

Tantek: And then there was the second phase which was the work of making all these standards formal and reliable and secure and handling edge cases. We did that from I would say 2014 through 2017, and a lot of that was done in the social web working group that I was co-chair and Aaron was in, edited a bunch of the documents. Evan Prodromou was also co-chair, from StatusNet. But that was kind of a maturing phase. There were a lot of new features people were figuring out all the time, and new infrastructure like Bridgy during that phase.

Tantek: But I feel like a big part of that second phase was everything that was getting built was getting fed back into fixing the standards. People would build something, they would get to the point where they were like, “hey, this didn’t quite work, we have to fix a standard to handle that.” Okay, we fix it. They get it working. We have test suites for all these standards. And now when people are implementing things like Webmention or Micropub or whatever they’re not really running into new problems. What they’re running into is questions of how, not “this doesn’t work”. So we’ve reached this level — and I think Microsub, that might be one of the last pieces that kind of wraps it up. That’s why I feel like we’re closing on the second phase.

Aaron: And IndieAuth, too, because that was only written as a spec this year. Before that it was actually very interoperable, and there were several implementations before, but it was never written down as a proper spec. So that’s now this process of let’s formalize that.

Tantek: And we even formalized how do we update the Microformats parser spec and the vocabulary. That’s been much more formalized as well. So people have an idea that when I proposed something, when can I depend on something vs. what’s experimental, and then what’s the path.

Aaron: So you mentioned these two phases of…

Tantek: The Big Bang, the amazing explosion of cool stuff and then this sort of maturing of the standards to make stuff work reliably even just amongst theirselves. You mentioned you want everyone to have their own presence. But when I think about that I think, “people want things that are reliable, that just work.” And I think this second phase was us doing the difficult plumbing work of the details to make things just work.

Aaron: That leads into what I think is the next phase is getting more people building systems using these building blocks. When that happens, and you’re a great example of this…

Tantek: Yeah, there’s an overlap. I think Micro.blog was evidence that that phase was ready to enter.

Aaron: So now as someone who is building out a platform that is intended for end users… Whereas I’m building my web site. I do not want an end user to use that software. It is not the goal explicitly. But you’re building software that is intended for end users. You now have a pattern to follow where if someone else comes along with the same goal and build something, they work together. And so I think in order to reach the goal of people can just use this stuff out of the box, we need more people building tools that are intended to work out of the box for people on the same stacks. And four years ago, if you had come around and started this thing, there wasn’t a pattern to follow to make that work across implementations. And there is now, because of the work over the last four years, since 2014, of formalizing these specs, and having that actually hardened.

Tantek: And we also did it the hard way.

Aaron: Totally.

Tantek: We tried to do each spec as its own little building block piece. I would say hard but honestly I think greater chance of long-term success. The traditional approach that architects take is the stack approach or platform approach where they figure out the entire API. The whole thing. If you look at how OStatus happened, or even like ActivityStreams and ActivityPub. That’s very much a “we’re going to solve the whole problem”. And then we’ll iterate that whole big thing and then it turns out that’s both really hard to do and once again you end up with the problem that there’s only a handful of people that can implement it.

Aaron: And also I think more importantly that also has the problem of: if you realize there’s a mistake in it, then you have to essentially throw out the whole thing and make a version 2. And Microformats is a good example is this evolution. Microformats 1 vs. Microformats 2… they’re completely incompatible. They don’t work the same way, but you can still send a Webmention with Microformats 1 markup and it works. Webmention doesn’t have to change. So people build out Webmention tools and infrastructure, the thing on top of that is the Microformats to make it actually look good and make a comment work. Microformats can change and evolve, and Webmention doesn’t have to evolve. Whereas when you end up with a monolithic stack, if you’re like, “oh crap, we don’t like the things we decided for this layer in the stack.” We can’t just swap out that layer because then the whole stack breaks. That’s part of why the approach we’ve taken is harder, because you have to treat each one independently and evolve each one on its own schedule. And they all have their own change-control process.

Tantek: It looks more chaotic.

Aaron: Yeah, and it is little more overhead in terms of: each spec has its own document and test suite that is for each one specifically. But I do think that’s the better approach for a longer term success.

Aaron: We’re essentially entering this third phase of now we have stuff, we need the tools built on it, but we also don’t want to then four years from now turn around and say to everybody who’s built these tools, “oh, we’ve changed now, we’ve decided that we’re going this whole different approach and redo all your stuff.” No, we want to make sure that those are all based on ideas that are technically proven and easily swappable in small pieces if you need. But if we were to suddenly say, “we decided that Webmention doesn’t work and we need a third parameter and go fix Micro.blog.” You’d be like, “well crap, now what, do I do that, do I abandon it, break interop and continue iterating on my own product?”

Tantek: The other big thing that happened is that we expanded greatly in Europe. International. I think that really started with… was it 2013, the first Brighton IndieWebCamp? We’re looking to try to scale it beyond — and we’ve done this somewhat in Europe — but I think we want to see more of it. The things in the community running and people running IndieWebCamps and Homebrew Website Clubs without needing to even check with Aaron or me.

Tantek: I would be happy to help out as a guide or mentor more than a leader in that respect. And I think that’s the way we’re going to keep scaling it. And in the next 4 years, I would like to see us in more countries. I would like to see us reach more diverse populations. Maybe people that aren’t just in the tech crowds, but people that are not earning as much money, right? Everyone has a phone number supposedly. No matter what you’re earning or not. And I even hear from developers of new services that kids just use SMS, they don’t even want to deal with email. And so people doing new apps have purely SMS-based sign-up flows and all that. So there’s definitely opportunities to reach — to keep innovating and figuring out how can we reach even a broader set of folks in that regard.

I’ve updated the Discover emoji on Micro.blog to add several new topics:

• breakfast: 🍳 🥞 🥓
• racing: 🏎️ 🏁
• cricket: 🏏
• guitar: 🎸
• knitting & crochet: 🧶
• travel: 🗺✈️

The /posts/discover API for Micro.blog apps has also been updated. It now returns the emoji that Micro.blog is currently tracking, and whether it’s one that is “featured” in the default popup menu in Micro.blog on the web. Since many of the emoji are seasonal, like sports, we can rotate out the default list throughout the year. (The iOS and macOS apps will be updated later to more closely match the web version of Micro.blog’s topics popup menu.)

Greg Morris has imported his WordPress posts to Micro.blog hosting and had a question about referencing photos in a template:

Card previews I really want to be able to solve - does anyone know how to pull an image out of a hugo post in order to put meta property=“og:image” into the head?

Micro.blog uses Hugo themes because they are fast and there’s so much flexibility to customize them. To test this, I created a theme and edited the layouts/partials/head.html template, adding this somewhere along with the other meta tags:

{{ with .Params.images }}
  {{ range first 1 . }}
    <meta property="og:image" content="{{ . }}">
  {{ end }}    
{{ end }}

This looks at the photos on a post and takes the first one, adding its URL to a meta tag. If instead of the original photo you want to include a smaller thumbnail, you can use Micro.blog’s special photos.micro.blog resizing proxy. Here’s an example to include a 300x300 thumbnail:

{{ with .Params.images }}
  {{ range first 1 . }}
    <meta property="og:image" content="https://photos.micro.blog/300/{{ . }}">
  {{ end }}    
{{ end }}

I still want to add more built-in designs, as well as add design settings so that custom themes aren’t necessary for common features. But there’s a lot of power here to make your blog whatever you want it to be.

Micro.blog’s goal is to encourage more people to post to their own blogs instead of only on big social media sites, and to have a great community where conversations can happen from those posts. The goal is not to completely replace any specific social network, but instead to help the future be a little more decentralized, with more variety and independence in the web. Important changes are possible if we don’t concentrate so much of the web’s content only on Facebook and Twitter.

I’ve been happy to see so many people who have found that Micro.blog does supplement existing social media so well that they can spend more time blogging, browsing the Micro.blog timeline, and participating in conversations. Other folks will jump in to Micro.blog from time to time, but might have most of their attention elsewhere, and that’s fine too.

Facebook’s mission is different. They want to connect everyone in the world. Billions of people writing posts and sharing photos on a single domain name. Mark Zuckerberg talks about this often. Sure, some great things can happen when you do that, to bring people closer together, but also terrible things. The trade-off is not worth it.

Micro.blog leaves certain features out on purpose because adding those features risks changing our mission from what it is to what someone else’s mission is. We do want the community on Micro.blog to keep growing so that it’s more diverse and valuable to people, and for many more people to start new blogs that we can host on our platform. We can do that while staying true to our original goals and not falling for the trap of trying to become the next Facebook or Twitter.

I don’t even want to link to that story by Casey Newton at The Verge because it’s so disturbing and tragic. I read the whole thing because as the founder of Micro.blog, where we value the balance between content ownership and curation, I had to understand what Facebook is doing so we don’t repeat the same mistakes.

Social networks like Facebook (and Twitter) are designed to reward the sensational video. The timeline algorithm, “like” counts, and quick re-sharing all contribute to surfacing both the best and worst content. Whatever drives engagement.

Facebook is right to hire thousands of content moderators. But they should be real employees with healthy working conditions, not people who Facebook feels no responsibility to take care of. This is the most damning article I’ve ever read about Facebook.

On road trips lately, I’ve been fascinated by out-of-business donut shops. If it’s late in the afternoon, sometimes a donut shop is just closed for the day. But it seems like many are closed for good, the old fryers and cooling racks gathering dust.

Why is this? My guess is that the startup costs for opening a donut shop are less expensive than many types of restaurants. There’s nothing special about a donut shop except that it’s fairly easy to get started, but no guarantee of success, especially in a small town. Most businesses fail.

Jacob Gorban started a new site for musicians to connect on Micro.blog. From the about page:

I had the idea for this list because I’ve had quite a few inspiring music-related discussions on Micro.blog and I wanted to make it easier for musicians to find each other on the service, to facilitate even better discussions and maybe even some collaborations.

Jacob has been posting videos of playing guitar to his blog and on YouTube. Even if you’re not a musician, also check out @JustGoodMusic, a new blog about music from John Philpin, with posts from Jacob and others.

Finally getting around to posting this. The last couple of weeks since WWDC have been busy. But as I usually do, I still want to capture a little of the week in San Jose. (Looking back on my old posts about WWDC from the 2000s is a great reminder of what the earlier conferences were like, and I wish I had more of those posts.)

Arriving Saturday evening in San Jose, I rented a car and checked into my Airbnb. This is the first time I’ve tried Airbnb for WWDC. Hotel prices are out of control and I thought it would be a good way to see a different part of the city. Daniel and I caught up over dinner.

Sunday morning I drove up to San Francisco. I’ve made it a tradition to visit the Walt Disney Family Museum every year, and moving the conference to San Jose hasn’t deterred that. I stopped at Blue Bottle Coffee in San Mateo on the way.

The special exhibit at the museum was Mickey Mouse drawings. It was an incredible collection. Afterward I had a bite to eat at the Presidio Picnic. Fog covered the Golden Gate Bridge.

I picked up Jon Hays from SFO on the way back, and we stopped at the new visitor center for Apple’s spaceship campus, then got coffee and lunch down the road at Chromatic Coffee. Also detoured slightly for a quick look at Winchester Mystery House. (Skipped the $39 tour. Ouch.)

I didn’t need the rental car anymore, so we dropped it back at the airport and took an Uber downtown, planning to go to sfMacIndie and watch game 2 of the NBA finals. That’s when the evening went completely off the rails. We were cruising down the highway and someone rear-ended our Uber so hard it felt like the car was standing still. Everyone was shaken up but okay.

The keynote was packed with new stuff. I knew this was going to be a big year, but I was expecting most of the news to be around Marzipan (Catalyst). That ended up being a small part of the morning. I watched the keynote from AltConf and worked on highlighting WWDC-related posts in our new Discover section for the conference.

I was feeling a little out of it most of the morning. As the day progressed and I saw friends or met new folks, I started to feel better. Brent Simmons held a NetNewsWire meetup in the afternoon.

Tuesday at lunch was our Micro.blog WWDC meetup. This is the 3rd year in a row we’ve held the meetup. It was great catching up with everyone. If you made it to the meetup, thank you! I sent an email to everyone who had RSVP-ed.

That night was The Talk Show Live with John Gruber and his guests Craig Federighi and Greg Joswiak. Great show.

Wednesday morning I stopped for coffee on 2nd street for a little work before walking over to AltConf. My flight was in a few hours so I had just enough time for one session: Leah Culver’s talk on making the podcast app Breaker as crash-free as possible. (Leah also co-founded Pownce back in 2006. I’m hoping to interview her for my book, Indie Microblogging.)

This was a bit of a strange year for me. While I’m sorry I missed some people and some events, I think it was good that I was back home early. I’m not going to make any other conferences this year. If you’re looking for places to go, I highly recommend IndieWeb Summit in Portland later this month, and Release Notes in Mexico in the fall.

Apple’s new stuff didn’t disappoint. I’m most excited for Catalyst and Sign In With Apple, which I blogged about here. These are both very practical solutions to real problems. The new iPadOS improvements are also welcome, and I’m looking forward to experimenting with SwiftUI. Overall, a great WWDC.

Micro.blog has been updated on the Mac. Here are the changes:

• Added new Open option when clicking a post to open it in your web browser. Useful for copying the link or viewing the post on the author’s blog.
• Added icons for Reply, Favorite, and Conversation.
• Fixed error reporting when posting fails and during timeline loading.
• Fixed photo compression to be more consistent across Micro.blog platform.

I tried many different UIs for this before settling on “Open”, including a share menu to match iOS. Nothing felt right. By adding icons for all the options, I could make “Open” use the default web browser’s icon, which helps convey what will happen. (It uses stylized versions of Safari, Chrome, or Firefox icons.)

Choose “Check for Updates” or grab the latest version from the download page.

Today I sent the following update to Kickstarter backers. I wanted to give everyone a progress update on writing the book, and a reminder about some of the new stuff in Micro.blog.

When I launched the Kickstarter for Micro.blog, I promised to write a book about independent microblogging. For the last 2 years Micro.blog has needed most of my attention, but as the platform has grown and matured, I’m finding more time to work on the book.

The book is not a simple how-to for creating a microblog. That is part of it, but we already have a help site with tutorials on microblogging. The book is also a history and guide for taking back social networking from massive platforms.

I have been repurposing draft sections of the book to my blog as posts. One of the latest is about open gardens — how we can think about the role of curation in social networks.

There are also interviews in the book. I sat down with IndieWeb co-founders Tantek Çelik and Aaron Parecki to talk about the first IndieWebCamp conference and new challenges, recording the full conversation. Today I have been working on transcribing it.

If you haven’t kept up with Micro.blog news, we were just covered last month in an article by Cal Newport for The New Yorker. And we’ve added many new features, from video hosting and blog categories to custom themes based on Hugo.

No one said that it would be easy to provide an alternative to Twitter and Facebook based on the open web, encouraging thousands of new bloggers in the process. It has been years of really hard work, with more to do.

If you still believe in the mission of Micro.blog, I would love your support. Fire up the Micro.blog app if it has been a while, dust of your blog, upgrade to a paid subscription, and let us know what we can improve next.

Thanks as always.

It was a good week at WWDC. Micro.blog helped sponsor last night’s LIVE near WWDC concert, and we held our 3rd annual meetup on Tuesday afternoon. I just sent the following email to everyone who RSVP-ed to the meetup.

Thanks to everyone who was at our WWDC meetup! If you couldn’t make it, or I missed talking to you in person, you can always send me an email if you have any questions or feedback.

Throughout the week at WWDC, I was asked how Micro.blog is going. New people join the platform every day, thanks to word of mouth, blog posts, and even mainstream stories like the article in The New Yorker. I’m an optimist. I believe if more people blog and use open tools, the web will be better, and platforms like Micro.blog will thrive.

But it doesn’t happen by accident. Facebook and Twitter are massive platforms. Our team at Micro.blog is tiny. Every time you tell someone about Micro.blog it makes a difference. Every paid subscription gets us a little further.

I hope everyone has enjoyed their time in San Jose! Your support of Micro.blog means a lot.

This is one of the most interesting announcements from WWDC for me. Aaron Parecki wrote a detailed technical post for Okta about it, as well as a post on his blog:

Sign In with Apple is a good thing for users! This means apps will no longer be able to force you to log in with your Facebook account to use them.

There are also 2 sessions at WWDC: Introducing Sign In with Apple and What’s New in Authentication, Safari, and WebKit.

I plan to support Sign In with Apple in Micro.blog. We don’t have passwords, and we require verifying an email address before setting up your account on Micro.blog, so using Sign In with Apple should make the initial sign up go more smoothly. It could also be an option for existing users who need to sign in again and don’t want to wait for the confirmation email.

Ben Thompson covered more about sign in on Stratechery this week:

Apple is going to leverage its monopoly position as app provider on the iPhone to force developers (who use 3rd party solutions) to use Sign In With Apple. Keep in mind, that also means building Sign In With Apple into related websites, and even Android apps, at least if you want users to be able to login anywhere other than their iPhones. It was quite the announcement, particularly on a day where it became clear that Apple was a potential target of U.S. antitrust investigators.

I’m generally against the App Store review guidelines becoming even more restrictive. I’d rather developers choose to adopt Sign In with Apple because it’s better than using Facebook and Twitter rather than be required to do so on Apple’s schedule. But in this case, I think the end result will be positive.

People often ask me how we “win” against the big social networks, bringing more open platforms and indie blogging to everyone. It happens in small steps, not overnight. Sign In with Apple can be one of those small steps. Anything that moves people away from signing in with Facebook and Twitter is part of the solution.

The 3rd annual WWDC Micro.blog meetup will be today at 12pm outside Grace Deli & Cafe. If you’re attending WWDC this week, grab a to-go box lunch and meet us there, or you can get a sandwich or wrap first from the cafe. Jean, Jon, and I will be there until 2pm.

It’s less than a block from the convention center: 303 Almaden Blvd. View the location in Google Maps or Apple Maps.

We’ll have some more Micro.blog stickers and we’ll also be giving away a VIP ticket to the LIVE near WWDC benefit concert for App Camp for Girls. We’d love to talk to anyone who is currently using Micro.blog or interested in learning more about indie microblogging.

Hope to see you there! Thanks for all your support.

In technology, the walled garden is a platform where one vendor controls distribution. If you want to make an iPhone app, your only choice is for Apple to approve it and sell it in the App Store. If you want to send a tweet, your only choice is to register on Twitter’s platform.

Walled gardens like the App Store are user-friendly and developer-hostile. They take power away from independent publishers and put it in the hands of gatekeepers. The problem is exclusivity: there is only one gate, and those stuck outside are unable to distribute the same content. You can make Android apps, but not iPhone apps. Nothing exists outside the walls that closely resembles what is inside.

Twitter is also a walled garden. Like the App Store, it is a closed platform with proprietary formats and a limited API. The difference is that Twitter’s garden is poorly curated and full of weeds. The walls are in such disrepair it’s hard to even tell where they are.

Mike Monteiro emphasized this frustration in a post about the problems facing Twitter’s leaders. He talked about meeting in person with Jack Dorsey:

We discussed Twitter’s role in the world stage. And I admired his vision, but feared his approach. Jack, and to an extent Twitter’s pet porg Biz Stone, have always believed that absolute free speech is the answer. They’re blind to the voices silenced by hate and intimidation. The voices that need to be protected. But anyone who’s ever tended a garden knows that for the good stuff to grow, you have to deal with the bad stuff. You can’t let the weeds choke the vegetables.

The issue isn’t that Twitter doesn’t care. It’s instead a design flaw in the platform. Because tweets don’t exist outside of Twitter, when you’re banned from Twitter, you need to start over with a new format or on a new social network. For this reason, and because their business depends on a large user base, Twitter is hesitant to throw anyone off their service. They’re unwilling to tend the garden for fear of pulling too many weeds.

It doesn’t matter who is guarding the walled garden’s gate if increasingly no one wants to go inside. So there’s a better word than “gatekeeper” to describe what we’re really after in building a great community-focused platform. It’s “curator”. Someone who is responsible for maintaining the best experience for users.

The answer to a walled garden is not to create a platform without rules. It’s not outsourcing decisions to algorithms, with recommended users and topics that can be gamed or lead new users astray. That’s not enough for the challenges brought to us by massive, ad-based social networks, where fake news and hate can spread quickly.

We need a new approach. Not controlled only by algorithms, but also not a walled garden that limits distribution of content. We need a system that prioritizes curation while preserving the freedom to publish outside of silos, with APIs based on the IndieWeb that are open by default instead of locked down with developer registration.

I think of this as an open garden. It’s an open platform that also cares deeply about maintaining a healthy environment. Outside of the garden, the soil is the same and the same plants can grow, and you are free to copy flowers and trees from inside the garden and cultivate them yourself or let them grow wild. But inside is well-curated. Inside strives to be a high quality, safe environment.

In my Kickstarter video for Micro.blog, I talked about this for social networking and blogs:

If we start to separate the publishing from the social network, it unlocks something. It empowers writers to feel like they own their work, even if that’s short posts. And it frees social networks to build a safe community, without worrying about censorship, because no matter what the networks do you can always post to a site with your name on it.

The fundamental problem in walled gardens like the App Store and Twitter is that they are closed. If they open up, they could in fact double-down on curation. There would be no need to loosen their quality standards because there’s an easy path to publishing without review by using the open web.

I first wrote about this in 2014 in the context of learning from Beats Music. For Apple to deemphasize their algorithmic top 200 lists in the App Store they would need to focus on curation. Here’s what Beats was doing:

Instead, they have a bunch of people — musicians and writers who deeply care about music — curating playlists. The top 25 playlists in a genre are so buried in the app that I had to search them out just to write this blog post, because they seem to carry no more weight than any other playlist. Much more common are playlists like “our top 20 of 2013”. That’s not a best-selling list; it’s based on real people’s favorites.

After Apple acquired Beats Music, they brought some of those curation lessons over to Apple Music, and later redesigned the App Store with more featured apps and stories. There is only so much they can do, because the foundation of a walled garden is difficult to change.

Twitter has likewise created an environment that ties their hands on curation, with discovery driven by trending hashtags and retweets. And for each rare time a popular account is banned for hate speech, there are still thousands of trolls who are making life miserable for users. Because there is no alternative, Twitter must allow nearly all content on their service. Because it exists apart from the open web, Twitter must give its worst users too much leeway before banning their account.

The open garden solves this problem. It’s the same web inside a platform like Micro.blog as on the rest of the internet. By adopting open standards but also drawing a line across which we can apply community rules, it’s possible to build features that protect users.

By encouraging the use of personal domain names, when Micro.blog does need to ask a member of the community to leave for violating our guidelines, that blogger can take their domain name and content with them, continuing to post to their own blog but blocked from interfering with the community. The curators of the platform have more freedom to block harassing posts because those problematic users can retreat to their own web site and leave everyone else in the community alone.

To summarize:

• Open gardens have curators instead of gatekeepers.
• Open gardens use standards so that the same formats exist inside and outside the platform.

This is only possible by embracing the open web. I believe it’s an important part of the way forward for all great platforms.

Love this new podcast from Joe Cieplinski. It’s a great example of trying something new with a short-form microcast. The first episode is really well edited, with everything from recording to publishing entirely on iOS:

Edited in Ferrite on iPad Pro with Apple Pencil. Show notes composed in Drafts. Published with Wavelength. No Mac involved. Micro.blog handles all hosting and publishing to the feed.

Seeing this kind of thing is exactly why we added podcast hosting to Micro.blog. There are a lot of people out there with a story to tell or a new way to tell it. It should be easy and inexpensive to start a podcast that you own, with your own domain name, that works with open standards.

Neil Stephenson has written a new book. In an interview with PC Magazine, he talks about the problems with social media:

We’ve turned over our perception of what’s real to algorithmically driven systems that are designed not to have humans in the loop, because if humans are in the loop they’re not scalable and if they’re not scalable they can’t make tons and tons of money.

I think more social networks should do things that don’t scale, prioritizing safety over profit. For example, in Micro.blog the featured posts in Discover are curated by humans instead of algorithms.

Significant parts of Facebook and Twitter run unattended. There was more pushback against Facebook last week after they refused to remove the edited Nancy Pelosi video, choosing instead to try to educate users that the video was fake. Monika Bickert, Facebook’s vice president of global policy management, went on CNN to defend their decision. She described how Facebook works with fact-checking organizations to independently confirm whether something is accurate:

As soon as we get a rating from them that content is false, then we dramatically reduce the distribution of that content, and we let people know that it is false so they can make an informed choice.

I signed in to Facebook to try to understand what they had done. I actually had trouble finding the video at first, maybe because none of my friends on Facebook had shared it. Searching for Nancy Pelosi did include Facebook groups such as “Nancy Pelosi is Insane” and “Americans Against Nancy Pelosi”, featured prominently in the search results. I finally found the video, but there was no callout that it was fake. (The version I saw was captured with a camera pointed at the video playing elsewhere, likely confusing Facebook’s algorithm for finding an exact copy of the video.)

Facebook is trying to solve this problem, but it’s a band-aid on a system that is working as designed to surface “relevant” content for more ad views. It’s not enough.

At the beginning of the month, I started a new blog post series: visiting a city park each day for 30 days. I’m now 23 days in, wrapping up the final week before I leave for WWDC in San Jose. For some parks, we’ve brought a picnic lunch, and for others I’ve sat with my iPad and worked on blog posts or the upcoming book. A few days there wasn’t time for anything but a short walk around and photo.

Unlike my previous 30-day series for libraries and coffee shops back in 2016, I’ve been consistent about taking a photo every day, which I’ve collected together as thumbnails on the main page:

Watching that grid of photos grow from a single photo to dozens is a daily reminder of how progress works on anything. It’s slow, but there’s confidence in seeing a project go from possible to inevitable.

This is really what blogging is all about. It’s not just the individual posts that matter. It’s also the collection, built over time with a system designed to encourage regular posting. I love that at the end of this 30-day series I’ll have a web page with photos of parks all over Austin, and bits of text that capture a small part of what each park was like.

I linked briefly to The New Yorker article by Cal Newport over the weekend, but wanted to add a few more thoughts. The article really does a great job of capturing what the IndieWeb movement is about, and Micro.blog’s role in it:

Even as it offers a familiar interface, though, everyone posting to Micro.blog does so on his or her own domain hosted on Micro.blog’s server or on their own personal server. Reece’s software acts as an aggregator, facilitating a sense of community and gathering users’ content so that it can be seen on a single screen. Users own what they write and can do whatever they want with it—including post it, simultaneously, to other competing aggregators. IndieWeb developers argue that this system—which they call posse, for “publish on your own site, syndicate elsewhere”—encourages competition and innovation while allowing users to vote with their feet.

As we’ve been consistently chipping away at Micro.blog bugs and features, moving the platform forward, I’ve always thought that eventually Micro.blog will get mentioned in the larger narrative about social networks from the mainstream press. We can’t control when we get noticed. We just have to be ready when it happens.

It’s great to see all the new folks joining Micro.blog! Whenever someone new has feedback, I’m reminded what we can improve so that the experience is better for the next person.

There’s one sentence in Cal Newport’s article that I keep going back to:

The Internet may work better when it’s spread out, as originally designed.

I have no doubt that this is true. It’s okay to have centralized services to make things easier for people, because it’s too much to expect that everyone should run their own server. The web can be “spread out” on multiple layers: a more diverse set of platforms, so that not all the power is concentrated in a couple massive platforms like Facebook; and more personal domain names, so that even if Micro.blog hosts 1000s of blogs, each one has its own identity on the web and can be moved.

Domain names are the key to content ownership. This is a fundamental part of Micro.blog’s architecture, not something that was tacked on as an afterthought. I’ve written more about owning your content here, which is one part of the solution to moving beyond today’s social networks.

Advertisements often make broad claims that their products are the “best” or “easiest” or “most popular”. These statements are impossible to prove, and I think make the marketing weaker because they sound like an exaggeration.

We’ve redesigned the Micro.blog home page for new users, to better explain what Micro.blog actually is. I wanted to emphasize that it is both a blogging platform and also a great community, as well as highlight who our team is.

As a sort of tag line, I wrote that Micro.blog is “the fastest way to blog”. I like describing it in terms of speed because it also implies ease of use. If it’s simple and fast, more people will blog. Micro.blog is the blog you will actually use.

But is it true? I’ve used many blog platforms over the years, and I can’t think of one that is faster to go from idea to starting a post to publishing it. In the native Micro.blog app for macOS:

• ⌘-N to start a new post.
• Type something.
• ⌘-return to publish.

It’s the same basic workflow on iOS and the web. By default, you don’t need to worry about a title field or categories or any other UI getting in the way. This focus on simplifying blogging means there’s no tabbing or clicking around unless you need more advanced features.

There is still a lot we can improve, especially how quickly a post shows up in the timeline after publishing it. I just tweaked that today. By stating up-front that performance matters, it’s a constant reminder to make everything faster. But in terms of the workflow of drafting a new post, I think Micro.blog has a clear advantage.

After launching support for Mastodon on Micro.blog, I blogged about how Micro.blog is evolving to support 3 types of usernames: normal Micro.blog users, Mastodon users, and IndieWeb-friendly domain names. This last type of username is where I think we can bring more social network-like interactions to the full web.

Here’s an example. In a post on Micro.blog, you can @-mention someone’s blog by including @domain.com in the post, using their domain name. If that blogger’s site supports Webmention, Micro.blog will send your mention to their blog, where it could be included as a comment.

I’ve been testing a new feature for this type of username in Micro.blog. You can now follow blogs in the Micro.blog timeline, even if the blogger hasn’t yet registered on Micro.blog. On the web, click Discover, then click the search icon, and enter their domain name. Micro.blog will auto-discover their JSON or RSS feed, letting you follow their blog just as you would follow any Micro.blog user.

This feature is designed for blogs with a custom domain name. It assumes one blog, one user, one domain name, so it doesn’t work to follow specific feed URLs yet. You’ll still want a traditional RSS reader for sites that have multiple feeds.

I’ll continue to improve this based on feedback, and start adding it to the native apps. Micro.blog is already one of the most open platforms of its kind, and I think this has a lot of potential to take it a step further.

I introduced the Tweet Marker API in 2011. In the 8 years since, I’ve been lucky to have the support of some of my favorite apps like Twitterrific and Tweetbot, plus popular Android apps, with some developers paying a monthly subscription to help keep the service running. But while Tweet Marker hasn’t changed recently, the Twitter world has changed.

Twitter previewed the next version of their API this week. I don’t see anything so far to contradict what I wrote last year.

I believe strongly that URLs shouldn’t change, and that public APIs shouldn’t just disappear. Owning your content and having your own domain name are important parts of Micro.blog too. So I was committed to running Tweet Marker indefinitely, regardless of what Twitter might do.

But two other factors were nagging at me:

• GDPR made me take a fresh look at some of the assumptions in the Tweet Marker API. Changes are overdue. They aren’t simple and would require coordination with client developers.
• Twitter’s third-party ecosystem has changed a lot since Tweet Marker was created. Twitter apps have a very uncertain future. Timeline syncing is often handled without Tweet Marker, such as via iCloud.

Tweet Marker’s time has come and gone. I’ve notified developers using the Tweet Marker API that I plan to wind down the service by July 1st. I’ve also cancelled all the paid subscriptions. (Actually I haven’t billed anyone in over 6 months, so I’ve been running the service for free.)

Daniel Jalkut and I talked about this back in December on Core Intuition 353. I plan to work on Micro.blog for the next 20 years or more, so it needs all of my attention.

Over a million people have used Tweet Marker. I’m proud of that. If you’re one of those people, especially if you supported Tweet Marker as a developer or with a subscription, thank you.

Bokeh will be a new private-by-default photo sharing app from Tim Smith, on Kickstarter now:

Bokeh will be ad-free, have a chronological timeline, and will be private by default. That means that all accounts will start off as private. Public accounts will have an RSS feed, will have the option to cross-post to other social networks, and will support custom domains. All accounts will have an indie web compatible export so you can self-host if you want to.

Tim has been active in the Micro.blog community from the early days of the platform, and I’ve talked to him about Bokeh leading up to the Kickstarter. I think there is a lot of potential for parts of Bokeh to be compatible with Micro.blog. There is some overlap with what we’re doing with Sunlit, but as I’ve written about, more smaller social networks that can work together is a good thing! I’ve backed it on Kickstarter.

We’ve launched a redesigned home page for new users on Micro.blog today. The old design was a little too sparse and didn’t do a very good job of explaining what Micro.blog is. The challenge is that Micro.blog is really 2 things — a blog hosting platform and a social network for microblogs — so the new design reflects that with a 2-column layout.

To give an example of what posts on Micro.blog look like, we include recent posts from the Discover section directly on the home page. There are also profile photos of the team members at the bottom so that new users have a better idea of who is behind the platform.

We know that of course you can’t watch a Netflix-exclusive show on Hulu or Amazon Prime Video. But wouldn’t it be great if you could? With the current open podcast ecosystem, that’s exactly what we have: any show from any network can be played in any podcast client by default.

You might think with my attack on Luminary that I don’t want big companies to succeed with podcasts, but that’s not it. There’s nothing wrong with trying to make money off of podcasting. I just think it’s possible to make money by working within the podcast ecosystem instead of against it.

Here are several great ways to monetize podcasting that preserve and even strengthen how podcasts work:

• Start your own podcast (or multiple shows on your own podcast network) and build an audience. You’ll then be able to accept sponsors or memberships.
• Offer an easier way to produce and host podcasts. This is what we’ve done with Micro.blog. For $10/month, we’ll host MP3s at your own domain name and give you a podcast feed. Plus we have a companion iPhone app called Wavelength just for recording podcasts on-the-go.
• Help smaller podcasts with a variety of tasks they don’t have time for, like finding sponsors or editing episodes.
• Build a membership platform to make it easier for podcasts to be supported directly by listeners with subscriptions. While the user experience for members-only podcasts is not great yet, it is possible to create private podcast feeds that work in many different podcast clients.

And here’s a way to monetize podcasting that will weaken the ecosystem:

• Leverage the popularity of podcasts by creating a proprietary distribution model with exclusive shows. This requires redefining what a podcast is to include shows that do not have an RSS feed. If you do this, do not call what you’re doing a podcast.

As I wrote in my blog post about Substack:

If we accept calling “any audio on the internet” a “podcast”, we undermine what makes a podcast unique: not just the convenience of delivering audio directly to your device, but the openness that ensures that podcasts work in a variety of players, without a single company with too much control trying to lock down the format.

Companies like Luminary and Spotify will most likely fail to dominate podcasting because listeners want to use their favorite podcast client to listen to podcasts. Try explaining why your exclusive “podcasts” don’t play in Apple’s app called “Podcasts”. But if someone does succeed in creating a “Netflix for podcasts”, it could eventually lead to a couple major problems:

1. An aggregator on the scale of Facebook or YouTube could emerge for podcasts.
2. The market could become fragmented like it is for video streaming services.

If either of those things happen, we will all be much worse off. (For more arguments along these lines, check out episode 323 of the Accidental Tech Podcast.)

In 2016, I tried working from a new coffee shop every day for 30 days, then later followed that with 30 days working from libraries. Each day I would post a microblog post and sometimes a photo. You can find links to all these posts on my 30 days page.

When it was all done, I wrote:

After wrapping up libraries, I thought I’d make it a trilogy of 30-day endeavors, with a final 30 days of working from city parks. This was a suggestion from Daniel Hedrick, who had worked from parks before, tethering to his iPhone since there’s usually no wi-fi. I loved the idea right away because it fit so well with the goal of getting out of the house and discovering something new in my own city. I even spent a couple hours earlier in the month researching parks and planning out whether I could do it.

But I quickly realized that I was burned out on commuting all over town, so I tabled the idea. Fast-forward a few years. This week, I’ve been struggling to stay productive as my attention is pulled in a few directions with tasks for Micro.blog.

I’ve also been working more on my book Indie Microblogging, which I can write from anywhere on my Mac or iPad. I think restarting the “30 days” idea will force me to carve out some uninterrupted time to write, and get me out of a bit of a rut from working at home. It will also be a great use of Micro.blog.

For day 1 of 30, I went to Walnut Creek Metropolitan Park in Austin. It’s a large park with hiking and biking trails. I actually did more walking than writing, but it’s a start. As with coffee shops and libraries, I’ll collect links to all the posts on a new page here.

John Gruber has a great post on Luminary and the trend of companies trying to redefine what “podcast” means. It’s not a podcast if there’s no RSS feed and it can’t work in multiple client apps:

Being client-agnostic is the spirit of the open internet, and I think it’s implicitly part of being a “podcast”. Openness was certainly part of how podcasting came to be.

Substack is another company that initially tried to ride the popularity of podcasts by calling their audio in email newsletters a “podcast”. I wrote about it here. I’m happy to notice that as of this week, Substack has real podcast support by adding private RSS feeds for newsletter subscribers. That’s the right way to go and now their audio shows work in any podcast client.

We do not need the “Netflix of podcasts”. Anyone can create and distribute a podcast — even Micro.blog has support for podcast hosting and a simple app for recording and publishing podcast feeds that work anywhere — so it would be a step back for the industry if a single company tried to control distribution.

The New York Times has an article today about demolishing Penn Station, full of incredible old photos:

With its swarming crowds and dust motes dancing in shafts of smoky light, the station was catnip to midcentury photographers, filmmakers, artists and architects. It was the architectural embodiment of New York’s vaulted ambition and open arms.

In 2016, I wrote a blog post on applying the lessons from Penn Station to the open web and podcasting. It’s still one of my favorite recent posts.

Following Jeffrey Zeldman’s article about the open web, Ben Werdmuller has a great post about how we shouldn’t care so much about startup unicorns, using Micro.blog as an example of another type of business:

Zeldman looks to Micro.blog as a potential answer. It’s a great company that could point to what a more general solution could look like, but not specifically because it works with the indieweb. Instead, it’s worth examining how it’s financially structured. Rather than a unicorn, it’s a zebra.

It would be great to have more small- and medium-sized companies that can move the web forward. They can innovate while still being grounded in somewhat boring business models. It matches one of my points here that we need multiple social networks that interoperate via the web instead of just a couple of huge platforms.

There’s a difference between companies that are paid for directly by users and massive ad-based networks. Ben Thompson outlines this in an article about regulation, arguing that the super-aggregators like Facebook require government intervention, where other companies that are better aligned with users’ interests can be “regulated” by the market:

I think, though, that platform providers that primarily monetize through advertising should be in their own category: as I noted above, because these platform providers separate monetization from content supply and consumption, there is no price or payment mechanism to incentivize them to be concerned with problematic content; in fact, the incentives of an advertising business drive them to focus on engagement, i.e. giving users what they want, no matter how noxious.

I’ve been thinking about Ben Thompson’s essay a lot since he published it a couple weeks ago. Micro.blog is a small part of the puzzle — and it’s a puzzle piece of a different shape that doesn’t fit cleanly into Ben’s diagram around free services — but I think it’s an important part to focus on.

I’ve been having fun posting short videos to my blog now that Micro.blog makes it easy. You can see the recent videos on this category page.

And it has been great to see what other people come up with. For example, I love these time-lapse videos: the clouds moving above Fort Tryon Park in New York City from Joe Cieplinski, and this beautiful one of Ha Long Bay in Vietnam from Jordon Wadlington. I sometimes forget that my iPhone camera has a time-lapse feature, and now I’ll be looking for an excuse to use it.

While on a 6-week walk from Tokyo to Kyoto, Craig Mod is disconnecting from social media and instead posting to “followers” using SMS:

What do I mean by “use the network to publish without being used by it?” On most services — Twitter, Facebook, Instagram, etc — in order to publish something you must stare into the maw of its timeline, resist whatever the algorithm has queued up for you, and then, if you’ve remembered what you were going to publish, publish.

At the end of the journey he will collect the photos and comments in a book. I think this could’ve worked as a microblog as well, because then users joining late could read previous posts in the series, but it’s a fascinating use of SMS.

Congrats to Federico Viticci and the MacStories team on 10 years of MacStories. To appreciate how long ago this was, I re-read Federico’s interview with me from 7 years ago. This was 3 years after his first post but the content feels like a lifetime ago.

I really like this interview because I think it captures that time on the App Store and as a Twitter developer. We talked about iOS 5 user interface design, my early indie apps before starting Micro.blog, but also a few things that are still relevant today, like using the iPad for real work and app pricing.

Most importantly, it was a few months before Twitter’s infamous 4-quadrant chart that would set in motion Twitter’s move away from third-party developers. My priorities changed significantly after that, eventually leading to Micro.blog.

We all expected Dark Mode in iOS 13, but according to this rumor from 9to5Mac, the next major version of iOS is also going to feature some major changes to windows and detachable sheets:

There are many changes coming to iPad with iOS 13, including the ability for apps to have multiple windows. Each window will also be able to contain sheets that are initially attached to a portion of the screen, but can be detached with a drag gesture, becoming a card that can be moved around freely, similar to what an open-source project called “PanelKit” could do.

We also get an answer to one of the questions Brent Simmons asked about split views:

Split Views on Marzipan apps based on iPad designs that run on the Mac will get the ability to be resized by dragging the divider and have their position reset when double-clicking the divider, like existing Split View apps on the Mac.

I hope that support for multiple windows maps over to macOS with Marzipan. We’ve been saying on Core Intuition that this WWDC is going to be special. Marzipan is the biggest shake-up to the Mac since the Carbon to Cocoa transition.

There’s a fantastic article by Jeffrey Zeldman in A List Apart this week, starting with the problems of venture capital-backed social networks and ending with the question of whether we can help fix the web:

On an individual and small collective basis, the IndieWeb already works. But does an IndieWeb approach scale to the general public? If it doesn’t scale yet, can we, who envision and design and build, create a new generation of tools that will help give birth to a flourishing, independent web? One that is as accessible to ordinary internet users as Twitter and Facebook and Instagram?

I believe strongly that the answer is “yes”. Brent Simmons also responds, using the example of how even focused apps like RSS readers can move things forward without needing to solve all the problems at once:

Do I claim it’s as accessible to ordinary internet users as Twitter (for instance)? I do not. But it’s the step forward that I know how to take.

This is a great attitude. There are steps forward that we can all take individually, from leading the way by blogging more ourselves, to building tools for others to use. Together these steps add up to something significant that really matters.

It has been very encouraging to watch the Micro.blog community grow and new people regularly post to their own blog first instead of the big ad-based social networks. Seeing so much progress — but also knowing how much more work there is still to do — gives me a lot of hope for the future of the web.

If you’re still using Instagram but want to copy your photos and videos to your own microblog, a great solution is OwnYourGram. This is a free service that checks your Instagram account for new photos and videos, then sends them to your microblog automatically. Along with video support in Micro.blog, we’ve also improved support for videos from OwnYourGram.

First, make sure you’re on the podcast + video hosting plan on Micro.blog. For $10/month, we’ll host audio and video for you in addition to photos, and generate a podcast feed for you if you ever want to start a podcast later. You can upgrade here.

Next, follow the instructions on this help page for setting up your Micro.blog account so that it works with Instagram. This just means telling Micro.blog about your Instagram username, and telling Instagram about your microblog.

You can use OwnYourGram to send a specific video from Instagram to Micro.blog to test that everything is working. After that, OwnYourGram will check Instagram for new photos and videos and send them to your microblog. Photos and videos on Micro.blog are real blog posts, so you can always edit the posts later after they are created automatically.

Last week I drove to New Orleans for Peers Conference. It was a bit of a whirlwind because we also released video support in Micro.blog and updated 3 of the apps, which I knew might be a little too much to attempt to do while traveling. In fact, we did miss a couple bugs and updated Sunlit the next day, and a new Micro.blog iOS update will follow this week with more improvements.

I had a great time in New Orleans. The drive from Austin is 8+ hours, but I took even longer to make sure I had enough breaks from driving, for lunch and coffee and catching up on work. I took a few photos which I’ve collected together using Snapthread here to share as a short video.

On the way I stopped at Goodthrough Coffee in Houston, then at the visitors center in the Atchafalaya Basin in between Lafayette and Baton Rouge, and then caught a rainbow as the rain cleared along the Mississippi River before cutting across highway 30 to I-10 and New Orleans

Peers Conference itself was great. Though it’s traditionally a web conference, this year leaned more toward business so the sessions were exactly what I needed to hear. It rained a bunch. Early Friday I settled in at Stumptown Coffee to work on Micro.blog. I didn’t end up seeing much of the city, but had a chance to walk around Jackson Square between sessions and there were great conversations in the evening over beers with fellow attendees.

Saturday I had breakfast at Merchant around the corner from the hotel and then hit the road back to Austin, stopping for lunch at a hotdog place in Lake Charles, Juiceland near a biking trail in Houston, and mostly missing the rain that had also drenched Austin until I was close to home. It was a long day but very glad I made the trip.

Sunlit 2.5.1 is now available in the App Store. This update fixes an issue with videos not appearing in the timeline after the major new version we released yesterday to add video upload to the app and Micro.blog hosting.

Here are a couple screenshots of the update with the video preview and new full-screen player:

We’ve updated Micro.blog today with a big feature: video upload to your microblog. The iOS and macOS apps — as well as our iOS app for photos, Sunlit — have all been updated to support video.

Video upload and storage is based on our podcast hosting plan. If you’d like to post video, you can learn more and upgrade here. Just like podcasts, video hosting is designed for short videos, from a few seconds to 1-2 minutes. Each video should be 45 MB or less, but there’s no limit on the number of videos you can upload, and videos are stored at your own domain name.

We are very excited about this and can’t wait to see how people use it. Now that we have this foundation for video, I’m looking forward to expanding it based on feedback. I think there’s a lot we can do. (There were also a couple of last-minute bugs with playback on iOS… We’ll get those fixed soon.)

There’s no shortage of opinions about Apple’s services-related event this week! I’ve listened to a few podcast episodes, and of course I had my own thoughts on this week’s Core Intuition and a separate blog post about News+.

My favorite discussion about News+ so far has been the latest episode of Connected. They talk about the good things Apple brings to this, but also the downsides.

Federico:

I was asked by someone on Twitter, do you plan on putting Club MacStories on Apple News+? The answer is a huge no.

Myke:

Literally every single person who subscribes to Club MacStories would cancel because they’re all users of Apple products!

Federico:

There’s always a cost to adopting a new platform. There’s a technological cost, and there’s an actual cost. And for me, it’s not worth it to rewrite my — what we do for Club MacStories for Apple News format — but it’s also not worth it to lose the money that I’m making from the service that I control.

Federico’s point here gets to the key issue with these aggregation platforms, whether it’s News+, Facebook, or the App Store. When you give up control over distribution, you also give up control over revenue. With publishing on the open web, there’s always an alternative: your own domain name and your own subscribers. (For the App Store, there’s no choice.)

Back to the episode…

Stephen:

I still don’t love how closed off News is. Like on the Mac, you just can’t get a URL to open it in a browser. You just can’t do it. You’ve got to send a text message to yourself or something. And on iOS, or really anywhere, sending content to things like Instapaper is very hit or miss. […] Apple News doesn’t play well with the web, and that’s very frustrating to me as a believer in the open web.

Myke:

We’re all worried about Spotify walling off podcasts. Well, Apple’s trying to do that to news. […] It’s probably good for consumers, but is it good for the industry? We don’t know yet.

Great episode. You should listen to the whole thing, because as I said there are some points in favor of Apple News as well, and the other announcements. But the segment I’m quoting from above was particularly good.

We’ve rolled out some more improvements to Micro.blog. For blogs hosted on Micro.blog, you can now save a post draft to Micro.blog, then come back later to edit and publish it. The macOS app has been updated with support for drafts and a new “Posts” section to make editing or searching your existing posts much easier.

Here’s a short video of the new feature on the Mac:

Saving drafts works on the web version of Micro.blog or from the macOS app. We’ll be updating the iOS app soon.

You can also now import from a Tumblr blog. Choose Posts → Import to upload the export file you receive from Tumblr. Micro.blog will import any photos in the archive and add them to your own domain name hosted on Micro.blog.

Micro.blog’s posting API has been updated with support for additional Micropub API features: retrieving a list of your own posts, marking a post as a draft, and updating the title or text in an existing post. This should make it easier for apps to support editing.

Most of what Apple talked about today isn’t shipping until the summer or fall. Apple News+ does ship today with iOS 12.2. It’s priced at $10/month for access to hundreds of magazines and newspapers. As I posted about briefly, I’ll stick with paying The New York Times directly for now.

Michael Tsai writes about the larger issue with Apple News:

I continue to find Apple News to be disappointing. It’s like Apple reinvented the RSS reader with less privacy (everything goes through an Apple tracking URL) and a worse user experience (less control over fonts, text that isn’t selectable, no searching within or across stories). So the idea of content that must be accessed from the app—and likely can’t even be opened in Safari—is not attractive to me.

I think there’s great potential for Apple News on the curation side, but the articles are too stuck inside Apple’s apps, and the cost to publishers is too high. You can tell Apple feels like they’re onto something important with Apple News. My concern is that Apple’s solution is based so heavily on what they know how to do well — let’s make everything a native app with a nice UI and leverage our massive credit card database — that they’ve missed an opportunity to solve something more meaningful for journalism and the open web.

Seth Godin blogs every day. Sometimes short posts, sometimes longer posts that read like they could be part of one of his books. Yesterday’s post was one of those longer posts about big, centralized platforms:

Like a landlord who owns every building in town, Google can’t lose. A successful business in the online ecosystem is one that has a few dollars left over after giving the rest of it to Google or Facebook (or Apple).

He’s also been on a roll with his podcast. And for more about Apple vs. Spotify specifically, I enjoyed the latest episode of the Supertop podcast.

We sent an email to some of our Kickstarter backers yesterday, giving people a chance to check out Micro.blog again if they haven’t been active recently. The platform has improved so much in the last year. It’s possible that it didn’t meet someone’s needs a year ago but will today.

One of the links in the email was to the 12 days of microblogging help page, which links to 12 blog posts I wrote in December to highlight how people are using Micro.blog. Unfortunately, most of those links no longer worked! I scrambled to figure out why some of the links on my blog weren’t working, finally discovering that I had broken them myself when testing the Medium.com import feature across multiple test blogs.

In the process, I decided to pull a complete backup of Micro.blog’s database from 30 days ago and use it to fix some of my old blog posts. This was a great exercise. I check the backups from time to time, but it’s rare that I need to go over specific data by hand and actually restore anything.

Last week, Myspace revealed that they had lost all hosted music from 2003 - 2015. I don’t think we can be too careful with the responsibility of hosting people’s blogs, so I’m glad I had this chance for a real-world test of Micro.blog’s backups. (I also recommend enabling the Internet Archive feature under Posts → Design, and occasionally downloading a complete archive of your blog from Posts → Export.)

My heart goes out to the families of loved ones at the mosques in Christchurch. After the Parkland shooting, I drafted a long blog post about gun violence but never ended up posting it. Even after editing it a few times a month later, it felt like the words or timing were always wrong.

Over the last couple of years we’ve seen a growing backlash against social media. I won’t look for the video of this tragedy from New Zealand, and I hope I never accidentally see it. It is heartbreaking enough with words alone. Every story I read last week kept pointing back to the frustration with how Facebook, Twitter, and YouTube are not doing enough to prevent their platforms from amplifying misinformation and hateful messages.

Margaret Sullivan of the Washington Post writes about the problems with social media leading up to and after a tragedy like this mass shooting:

To the extent that the companies do control content, they depend on low-paid moderators or on faulty algorithms. Meanwhile, they put tremendous resources and ingenuity — including the increasing use of artificial intelligence — into their efforts to maximize clicks and advertising revenue.

Charlie Warzel of the New York Times covers this too:

It seems that the Christchurch shooter — who by his digital footprint appears to be native to the internet — understands both the platform dynamics that allow misinformation and divisive content to spread but also the way to sow discord.

Nick Heer links to an article in The Atlantic where Taylor Lorenz documents how after following a far-right account, Instagram started recommending conspiracy accounts to follow, which filled her feed with photos from Christchurch:

Given the velocity of the recommendation algorithm, the power of hashtagging, and the nature of the posts, it’s easy to see how Instagram can serve as an entry point into the internet’s darkest corners. Instagram “memes pages and humor is a really effective way to introduce people to extremist content,” says Becca Lewis, a doctoral student at Stanford and a research affiliate at the Data and Society Research Institute.

Duncan Davidson asks: “What are we going to do about this?”

The last few years, the worst side of humanity has been winning in a big way, and while there’s nothing new about white supremacy, fascism, violence, or hate, we’re seeing how those old human reflexes have adapted to the tools that we’ve built in and for our online world.

I can’t help but think about Micro.blog’s role on the web whenever major social media issues are discussed. It’s almost all I think about. We feel powerless against world events because they’re on a scale much bigger than we are, but it helps to focus on the small things we can do to make a difference.

Micro.blog doesn’t make it particularly easy to discover new users, and posts don’t spread virally. While some might view this as a weakness, and it does mean we grow more slowly than other social networks, this is by design. No retweets, no trending hashtags, no unlimited global search, and no algorithmic recommended users.

We are a very small team and we’re not going to get everything right, but I’m convinced that this design is the best for Micro.blog. We’ve seen Facebook’s “move fast and break things” already. It’s time for platforms to slow down, actively curate, and limit features that will spread hate.

The new version of Sunlit is now available in the App Store. You can download it for free and use it with Micro.blog or to publish photos to an existing blog like WordPress.

Why does controlling our own photos matter? As I wrote in this post about the way out of the mess created by massive social networks, having posts at our own domain names unlocks a few very important features:

• Open standards mean interoperability with multiple tools. I can use IndieWeb tools like OwnYourGram to automatically copy Instagram posts to Micro.blog, or use traditional blogging apps like MarsEdit to upload and post photos.
• Content ownership gives the flexibility to move photos between hosting providers. You can host on Micro.blog or WordPress or some future blogging platform without URLs breaking.
• Smaller social networks get us away from ad-based businesses that sell our data. Because Sunlit is powered by Micro.blog, you can even follow Mastodon or PixelFed users and see their photos in the Sunlit timeline.

I’m very excited about this release and hope you like it. It’s time to move away Instagram. If you need help importing your photos, check out this video I made about batch importing from Instagram to Micro.blog-hosted blogs.

We are getting close to releasing the next version of Sunlit. The app has gone through a bunch of iterations over the years while we searched for the right features and design. This version is my favorite. We’ve simplified posting so that it’s easier and more consistent with Micro.blog, improved profile screens, and fixed even more bugs.

If you’re looking for an alternate to Facebook-owned Instagram that priorities community and content ownership, I hope you check out Sunlit when it’s ready.

Apple responds to Spotify. Daniel Jalkut and I predicted most of this response on Core Intuition a couple days ago. I’m going to quote a few parts of Apple’s response and comment.

Eleven years ago, the App Store brought that same passion for creativity to mobile apps. In the decade since, the App Store has helped create many millions of jobs, generated more than $120 billion for developers and created new industries through businesses started and grown entirely in the App Store ecosystem.

Apple likes to brag about how much money they’ve paid to developers, but they leave out how much they’ve kept for themselves: about $50 billion. To Apple, they are doing us a big favor by letting us ship iOS apps.

We’ve approved and distributed nearly 200 app updates on Spotify’s behalf, resulting in over 300 million downloaded copies of the Spotify app. The only time we have requested adjustments is when Spotify has tried to sidestep the same rules that every other app follows.

It’s very important to remember that Apple’s rules are not laws. Apple’s rules have changed over the years, and especially around in-app purchase it often feels that they are applied inconsistently. Because Apple runs the platform, they can make any guidelines they wish, but there isn’t necessarily any inherent legal or moral justification in specific rules. We shouldn’t accept that all of Apple’s rules are fixed and cannot be improved.

When you get to the scale of the App Store, there are also new monopoly and anti-trust questions. For more about this, see Ben Thompson’s article on Stratechery.

Back to Apple:

A full 84 percent of the apps in the App Store pay nothing to Apple when you download or use the app. That’s not discrimination, as Spotify claims; it’s by design.

In 2011 I wrote a blog post with the premise that Apple made a mistake with how they handle free apps in the App Store, and what followed was years trying to make up for that mistake because of the burden of running the App Store. I think there was some truth to that, but now the business is very different. The App Store is a huge money-maker.

And we built a secure payment system — no small undertaking — which allows users to have faith in in-app transactions. Spotify is asking to keep all those benefits while also retaining 100 percent of the revenue.

And yet in the previous quote, Apple says that 84% of apps pay nothing and they are fine with that. Uber pays nothing to Apple. Games with ads pay nothing to Apple. Why is it wrong for Spotify to also want to limit how much they pay to Apple? The line Apple has drawn around in-app purchase is arbitrary. They could just have easily restricted Uber accepting payments, or banned third-party ads.

Just this week, Spotify sued music creators after a decision by the US Copyright Royalty Board required Spotify to increase its royalty payments. This isn’t just wrong, it represents a real, meaningful and damaging step backwards for the music industry.

This is irrelevant to Spotify’s complaints about the App Store. While I think Spotify’s argument would have been stronger if they had focused on a couple of their core complaints instead of mixing in issues such as Apple Watch development, Spotify didn’t bring up other concerns about Apple’s business that do not relate to the App Store. Apple trying to interject Spotify’s relationship with musicians is whataboutism.

Overall, Apple’s response isn’t very convincing to me. There are still 2 fundamental problems with the App Store: exclusive distribution and exclusive payment. In that post from 8 years ago, I concluded with:

Apple, want to charge 30%? Go for it. Want to make the submission rules more strict? Fine. Want to adjust how you run the App Store to reflect what’s happening in the market? No problem. Just give developers an out. We are going to be back here year after year with the latest controversy until exclusive app distribution is fixed.

I think I’ve been proven right about this. This issue will never go away until Apple allows side-loading or makes it easier to let customers pay outside the App Store. In the meantime, I’ve been arguing for a 15% cut instead of 30% for all paid downloads and in-app purchase, which would go a long way to making this easier for developers.

We just sent a Sunlit beta to testers. This new version of our photo-blogging app includes an updated UI, easier posting, and fixes a number of issues. It also simplifies and removes several features, such as the filter and photo editing interface. (We may bring some features back later, but it was important to get back to basics and improve the core user experience.)

If you’d like to try it, you can join the TestFlight beta here.

I’ve been waiting years for this. Bigger companies have finally had enough of Apple’s 30% in-app purchase tax. Spotify founder Daniel Ek writes about Apple’s restrictions on telling users how to upgrade to Spotify Premium outside the app:

As an alternative, if we choose not to use Apple’s payment system, forgoing the charge, Apple then applies a series of technical and experience-limiting restrictions on Spotify. For example, they limit our communication with our customers—including our outreach beyond the app. In some cases, we aren’t even allowed to send emails to our customers who use Apple. Apple also routinely blocks our experience-enhancing upgrades.

Spotify has a companion site TimeToPlayFair.com with more details, and they’ve also filed a complaint against Apple with the European Commission. (As a side note, I hope Spotify’s pursuit of fairness will also apply to how they treat the podcast ecosystem after acquiring Gimlet Media and Anchor.)

Apple’s anti-competitive behavior was also a theme of Ben Thompson’s Stratechery this week:

What is even more striking, though, is that the App Store does have a massive antitrust problem: it is not Apple unfairly competing with app developers, it is Apple unfairly imposing massive complexity and extracting 30% of revenue with its contractual requirement, enforced by App Review, that developers use Apple’s payment mechanism.

Now if only more indie developers would speak out about this, maybe we’d make some progress with Apple. As I’ve said many times: 15% for paid downloads and in-app purchase is reasonable for the value that Apple provides. Just as importantly, Apple should relax the rules against linking to web sites outside the store.

Today is the 30th anniversary of Tim Berners-Lee’s proposal for the world wide web. Reflecting on the web’s success and the new challenges, he writes:

Against the backdrop of news stories about how the web is misused, it’s understandable that many people feel afraid and unsure if the web is really a force for good. But given how much the web has changed in the past 30 years, it would be defeatist and unimaginative to assume that the web as we know it can’t be changed for the better in the next 30. If we give up on building a better web now, then the web will not have failed us. We will have failed the web.

I believe this. The goal of Micro.blog is to make the web a little better. Let’s get back to what made writing and sharing photos online such a wonderful experience, and get away from the problems of the massive social network platforms that dominate so much of our activity online.

Micro.blog can now import blog posts from Medium. You can request a .zip archive of your content from Medium.com, then go to Posts → Import on Micro.blog to upload the file.

Because Medium no longer supports custom domain names, we don’t think it’s a good long-term solution for blogging. If you still want to reach your Medium followers, you can enable cross-posting from any blog to Medium in Micro.blog by clicking Account → “Edit Feeds & Cross-posting”.

Micro.blog does a few things to make transitioning from Medium to Micro.blog hosting easier. Just like the WordPress to Micro.blog import, it automatically downloads any photos referenced in your posts and stores them on Micro.blog. It also cleans up the posts a little, while preserving most of the original HTML. Of course it also sets post titles and published dates.

Today Substack announced support for sending audio episodes in email newsletters:

Subscription podcasting through Substack works in the same way as publishing newsletters. Once the feature is enabled, you can create an audio post that is just like a normal post and can go out to everyone or only to subscribers. After receiving the post by email or accessing it on the web, subscribers can listen to the audio through the Substack web player.

This looks like a great feature for Substack customers, but it’s not a podcast. As the podcasting industry grows, with everyone trying to monetize podcasts or build new businesses around podcasting, it’s really important that we keep using the right words to describe it. A podcast has to have a feed so that it’s available in podcast players like Overcast, Castro, and Apple Podcasts.

Michael Zornek said it well earlier this week after Spotify acquired Gimlet and Anchor:

It is not a podcast unless there is a RSS feed.

I’m not splitting hairs about this. If we accept calling “any audio on the internet” a “podcast”, we undermine what makes a podcast unique: not just the convenience of delivering audio directly to your device, but the openness that ensures that podcasts work in a variety of players, without a single company with too much control trying to lock down the format.

Luckily, I think the Substack folks probably know this. In their announcement post, they also added:

We may soon add the ability to add a private feed of episodes to podcast players, but we like the web solution for now. (Give us your feedback, etc.)

Here’s my feedback: please don’t call it a podcast until you have the feed ready, whether it’s a private feed or public. When we added audio uploads to Micro.blog, we had full podcast feeds and everything was available from your own domain name. The web will be better if we encourage the same support of open formats in all new platforms.

We’re changing the official Micro.blog user accounts so that they are easier to follow. It used to be that everyone automatically followed @help, where we posted occasional announcements. From now on, @help will mostly be used for replying to questions, with a new default account @news.

You can unfollow @help if you don’t want to see those replies in your timeline. New users will no longer automatically follow @help.

Here’s a summary of the different accounts and blogs:

• @help: help.micro.blog
• @news: news.micro.blog
• @monday: monday.micro.blog

And for the Micro.blog team:

• @manton: manton.org
• @macgenie: micro.welltempered.net
• @cheesemaker: jonhays.me

In addition, Micro.blog user @simonwoods maintains 2 blogs with updates about Micro.blog and “Today I Learned” for tips:

• @til: til.micro.blog, updates.micro.blog

Email is still a great way to get an answer to a question, but by splitting out these accounts we can be more responsive on @help as well. I think this setup will work better as the community grows.

We released version 1.5 of the Micro.blog app for iOS today. In addition to a couple bug fixes, it lets you pick a category for new posts. You can create categories on the web under Posts → Categories for blogs hosted on Micro.blog.

Tap the gear icon when composing a new post to view your categories:

We are launching several major new features for blog hosting on Micro.blog today. Any one of these features alone is a big change, and together I hope they will serve as a great foundation for years to come. The goal was to make blog hosting faster and more flexible for new features.

Custom templates: All the themes have been rewritten with extensibility in mind. As some of you may know, Micro.blog-hosted blogs were originally built on Jekyll. They now use Hugo. There’s an interface in Micro.blog for editing any of the built-in templates, or adding new ones for your own HTML or CSS. Click Posts → Design → Edit Themes.

Categories: You can create a new category for your blog under Posts → Categories, and those categories will appear when editing a post or when creating a longer post with a title. We hide the category options be default when you are composing a short post, but in the new macOS app you can show the categories by choosing View → Categories. A list of your categories will appear at the top of Archive on your blog for readers to browse.

Auto-filter photos into a category: If you create a category like “Photos” or “Photography”, Micro.blog will offer to automatically assign this category when posting a new photo. Behind the scenes this is based on a new filtering system that will enable more features for other types of content in the future.

API for categories: I’ve added categories support to both the MetaWeblog XML-RPC API and the Micropub API. This means that categories work great with MarsEdit. Categories are also included in your default JSON Feed in the “tags” field.

Sharing themes: When creating a new custom theme, you can choose to clone it from an existing GitHub repository. This will allow someone to create a completely custom theme and share it with other members of the community. There’s a “Blank” design if you are starting from scratch with your own templates.

New theme: I used the open source theme Arabica when testing these new features, and it’s now an option under Posts → Design. It’s a clean, simple design ported from Ghost.

Open source changes: All our themes for Micro.blog are available on GitHub. I have decided to keep the forked Jekyll repositories and completely replace the files with the Hugo version. I have mixed feelings about this, since the themes have diverged so much that they are no longer useful to the original authors, but I felt this was the best way to give credit to them for the designs, in addition to our credits page on Micro.blog.

Moving special pages: Micro.blog has some special pages like “About” and “Archive”. You can now re-order or even delete these under Posts → Pages. Combined with custom themes, this gives much more flexibility in customizing the navigation for your site.

We’ll be writing more about these new features in blog posts and the help site. If you notice any problems, please let me know. Thank you!

We can come up with all the specialized names we want — photo blogs, link blogs, travel blogs, microcasts — but sometimes it’s just a blog. To wrap up the 12 days of microblogging series, let’s talk about blogging.

Blogs can be news sites, corporate sites, travel sites, photo sites, tech sites, and personal journals. They are usually written in an individual’s voice. Readers want to keep visiting a blog because there’s a story, unfolding with each post. The passing of time is a fundamental element to what defines a blog.

This emphasis on time is even more obvious for microblogs. Because short posts are easy to write, there are more of them. But Micro.blog hosting supports any post length: short microblog posts like tweets, or full blog posts with multiple paragraphs and a title.

Micro.blog is a full blogging platform, so it has support for traditional blog editors like MarsEdit on macOS. You can import an archive of posts when migrating from WordPress. Because Micro.blog posts are full blog posts, they support editing, using Markdown or HTML, and natively have RSS and JSON Feeds. They support features you would never expect on a social network, like using a custom domain name or uploading a PDF.

But along with this blogging foundation, Micro.blog tries to learn from the user experience of social networks. Can we make blogging much easier, so that it’s your primary home on the web, and the first place you think to post? There are still many improvements we want to make so that the platform is easier to use and more consistent, but I think the last year has shown that the answer is “yes”. Blogging can be easier, and if it’s easier, more people will do it. And if more people are blogging, we can start to find our way out of the problems created by massive social networks.

That wraps up our 12 days of microblogging series. You can find links to all the posts on the help site.

We’ve seen a lot of people use their microblog as a daily log to track activities, from running or cycling routes, to meditation or posting photos of food. Some apps even make this easier, like indiebookclub.biz for sharing reading progress in a book.

In 2016 when I visited a different library in Austin every day, I found that the microblog format is helpful to stick to a routine. It becomes part of the day, knowing you need a quick post to your blog to record the visit or activity. Encouraging this kind of posting consistency is also why we have special pins you can unlock, such as the “Photo Challenge” pin after posting a new photo each day for a week.

For the last 11 days I’ve been writing about the way people are using Micro.blog: custom designs, microcasts, photo blogs, and more. You can find the rest of the posts in this 12 days of microblogging series over on the help site. Tomorrow we’ll wrap up with a final post.

I woke up this morning, picked up my phone like I always do — to make sure that Micro.blog servers hadn’t quietly burned to the ground in the middle of the night — and the first thing I saw was a notification about Apple’s new campus in Austin. Here’s John Voorhees writing about it for MacStories:

At the center of the announcement though is a new facility that will be located in North Austin not far from Apple’s current Austin campus. The new office will cost over $1 billion to build and sit on a 133-acre site, 50 acres of which will be set aside for open space. Initially, the Austin campus will house 5,000 employees, with the ability to expand to as many as 15,000. The new complex will run on 100% renewable energy too.

I love the contrast to Amazon’s over-hyped search for a 2nd major campus. Apple made a decision and announced it, without leaving the world hanging for months. While Apple has always had other smaller offices outside Cupertino, it’s great to see such a significant new commitment in other parts of the country.

Does anyone know the location for the campus yet? Near the current campus in Austin there are huge stretches of undeveloped property — old ranches that you can see along Parmer Lane or from the other side when taking the train from Lakeline Station. For years I’ve dreamed that this area could be preserved somehow as a park, not just eventually overrun with condos and restaurants. I’m excited that Apple is setting aside 50 acres of the new campus for open space. I hope they consider expanding that even more.

Update: This KUT article has a map of the planned campus.

It’s the 10th day of our 12 days of microblogging series, and today we want to highlight some of the authors who are using Micro.blog. Last month was National Novel Writing Month, and many posts about NaNoWriMo were collected in a special section of Discover on Micro.blog. Congrats to everyone who participated!

Serena finished the month with 50,344 words. Cheri Baker posted updates about her writing and announced her new novel. And for non-fiction, Rosemary Orchard has a new book about OmniFocus.

Josh de Lioncourt is another member of the community who has participated in NaNoWriMo. He joined Jean earlier this summer on the Micro Monday podcast. On Halloween this year, Josh recalled his first NaNoWriMo from 2013:

I’d promised myself that if I finished chapter one that night, I’d continue writing the rest of the book throughout the month of November as a NaNoWriMo project. As it turned out, I did finish chapter one. The next day I wrote chapter two, and by the end of November I had nearly sixty thousand words, fifteen chapters, and about one-third of what would become Haven Lost written in first draft.

We love books and want to do more to support writers. As I wrote about at the beginning of the year when introducing the emoji collections, we started with books:

Today we’re introducing a search collection using emoji, starting with books. Just include ? with your microblog text about a book you’re reading or related topic, and your post will automatically be collected on /discover/books.

For more posts in this series, check out our help page.

For the 9th day in our 12 days of microblogging series, we want to talk about developer blogs. Most developers on Micro.blog use their blogs like everyone else — posting photos, sharing stories, recording a microcast, or linking to articles they’ve read — but some developers use the microblog format as a programming journal, writing about coding problems and eventual solutions through a series of posts.

Brent Simmons helped popularize this format in the iOS developer community back in 2013 when he published 16 posts while working out how to implement syncing. I’ve noticed at least a few developers adopt a similar format during the development of Micro.blog third-party apps, such as Isaiah Carew working on Kiwi earlier this summer, Vincent Ritter on Gluon, and Mike Haynes designing Dialog.

Blogging is a great way to work through an idea. When you take time to write a few sentences or paragraphs about an opinion on almost any topic, you’ll find that you have a stronger understanding of it by the time you hit publish. It can be the same way for a programming challenge.

There have already been 8 other posts in this series, and we link to all of them over on the Micro.blog help site. Three more posts to go this week to finish out the 12-post series!

Micro.blog’s default design for hosted sites is based on an original theme that shipped with Jekyll. It is very plain, but works well on desktop computers and mobile devices. It’s also pretty easy to customize.

I recently set up the new Micro.blog news blog and wanted to apply a few minor improvements to the design: adding a logo to the header and fixing how cramped the quoted text looked. To add a logo to the header, you can use CSS to shift the text to the right, making room for the logo, and then add the logo as a non-repeating background image.

Here’s what my custom CSS looks like:

blockquote {
	letter-spacing: -0.5px;
	line-height: 1.6;
}

.site-title {
	background-image: url(https://help.micro.blog/assets/images/icons/ios/icon-60.png);
	background-size: 30px 30px;
	background-repeat: no-repeat;
	background-position-y: 12px;
	padding-left: 40px;
}

You can edit the custom CSS for your blog by clicking Posts → Edit Domain & Design → Edit CSS. I also posted during out 12 days of microblogging series about other custom designs from Micro.blog users.

It’s the 8th day in our 12 days of microblogging blog post series. Most Micro.blog accounts use the author’s name — personal blogs, writing about everyday topics or sharing stories and photos. But since Micro.blog-hosted blogs can have a custom design, separate pages, and a domain name, you can also have a microblog for your business, or use it as your main web site.

Because one of the goals of Micro.blog is to encourage people to post to their own blog more often, using a blog for your business site can also help keep it up to date, so that when customers visit there is recent news or product updates. The Omni Group has taken this one step further for their microblog at microblog.omnigroup.com, posting not just links to new software releases and screenshots of features, but also fun stuff like what they’re having for lunch at the office and cat pictures.

For Micro.blog, we realized recently that we were missing a company blog. We have the help account and we have my personal blog, but not everyone should have to follow me to get important news such as the latest iOS update or even the blog post series you’re reading now. So today we’re adding a new blog: news.micro.blog.

This new microblog will mostly link to other blog posts from me or Jean or Jon, as a way of collecting everything in one place. As we expand it, we’ll integrate it into the help site and Micro.blog home page.

Previous posts in this series included topics like podcasting, photos, travel blogs, and sharing your content to other social networks, which is particularly useful for business blogs. See the full list here.

For the 7th post in our 12 days of microblogging series, I want to talk about linkblogging. Micro.blog users have a variety of approaches to posting links on their blog. Some people read an interesting article and type in a summary of it, pasting in the URL to the full article, and some people prefer quoting a portion of the text directly in their microblog post.

I blogged a couple of years ago in detail about the technical approaches to links in RSS and how linkblogging has evolved, using examples from Dave Winer and John Gruber:

Instead of just including a URL, authors use a quote from the linked material as the foundation for the post. The majority of Daring Fireball posts adopt this format. While John Gruber is known for his full essays, those longer posts are infrequent today. He keeps his site active by linking to other interesting essays and tacking on his own brief opinion.

Posts on Micro.blog are formatted with Markdown. If you’re reading a web page on iOS, you can share it to the Micro.blog app to automatically fill in the basic structure of a post, leaving the cursor at the beginning of the post to add your own thoughts.

In the screenshots above, I’m sharing from Safari on iOS. Micro.blog adds a Markdown link back to the original post with the web page title. Or if there’s text selected, Micro.blog includes that text as a quote.

Note that Micro.blog will truncate posts in the timeline when they are over 280 characters. For a longer quote, it’s best to give you microblog post a title, turning it into a full blog post.

Previous posts in this blog post series covered photo blogs, microcasting, travel blogs, custom designs, artwork on blogs, and more. Check out the full list on our help page.

I love road trips and travel blogs. We have a family blog that we started a few years ago, adding new daily posts for summer vacations with the kids and other trips. A blog is a great way to combine text and photos to remember a trip, with the flexibility to keep it for yourself or share it on social media.

For the 6th day of the 12 days of microblogging series, we wanted to highlight 2 travel blogs using Micro.blog. Mary Hatfield writes on her microblog with incredible photos of trips across the United States and even to Antarctica:

When we woke up this morning we were in the Neumayers Channel (below Anvers) located on the western side of Wiki Island ready to take the zodiacs onshore. The weather was quite perfect this morning and it was our turn […] We walked across the fresh blanket of snow to the Damoy Hut, which was built in 1975 and kept in use until 1995.  It has now been restored to its original form and is used as a museum. The land here was an airstrip that enabled personnel and stores arriving by ship to be flown on to Rothera Station in early summer when sea ice prevents dirt access to the station by ship

Arin Mearig kept a daily blog for a 3-month trip to Switzerland, posting photos every day with captions for people she’s met and places she’s visited. From day 34:

quick recap - left the house at 5am, went to 4 cities, hitchhiked for the first time, went on buses, trains, cable cars, and a funicular, ate a delicious burger, saw some of the greatest views ever, and just walked in the door at 10:45pm

I’m inspired by these blogs to write more while traveling. Consider capturing some of your next trip on an existing blog or new microblog.

See this help page for previous posts in this serious, covering topics like photos, microcasting, custom designs, and more.

It’s day 5 of our 12 days of microblogging series. Yesterday I highlighted what Micro.blog users are doing to create unique custom designs for their blog. Today we want to highlight how artists are using Micro.blog to showcase their work.

I’ve loved seeing the drawings from Audra Ann Furuichi, who posts web comics and illustrations on her own site. Sky Sandison has sketches from around Edinburgh, Scotland. And Mike Hendley shares digital paintings as he works through them on his iPad.

Plus there’s great sketchnotes from Mike Rohde and Ben Norris, including one by Ben about my talk from Peers Conference earlier this year.

October was also Inktober, with many bloggers posting sketches to their microblogs every day. We have a special section of Discover for Inktober that collects many of those posts together.

While the iOS apps for Micro.blog are designed around JPEG photos, you can use Micro.blog on the web to upload other formats like PNG and GIF, which might be more suitable for illustrations. Just click Posts → Uploads.

Showcasing artwork on Micro.blog uses many of the same features as photo blogs, which I wrote about on day 2 of 12 days of microblogging. For previous posts in this series, check out our help page on Micro.blog.

It’s day 4 of our 12 days of microblogging series. Today we want to highlight how Micro.blog supports blog themes and what people can do to give their blog a unique design.

There are 3 ways to customize your microblog:

Pick from one of the default 7 themes. These themes are based on existing designs using the Jekyll blogging framework, but modified to work consistently with Micro.blog. We’ve open-sourced all our changes to these themes on GitHub.

Edit the custom CSS for your blog. I’ve been really impressed with what creative Micro.blog users have come up with. You can use CSS to change colors, fonts, hide elements, and more. Here are a few examples from Kitt Hodsden, Michael Barrett, and Khaled Abou Alfa.

Add a custom footer. The footer HTML is a good place to put extra information or JavaScript.

If you have any questions about using CSS, ask in the #design channel on Slack. And if you have any tips, write about it on your blog so that others can learn from it. I’m currently working on a major upgrade to the themes on Micro.blog that I can’t wait to share more about.

Previously in the 12 days of microblogging series, I wrote about microcasting, photos, and using your own blog as a home base.

For the 3rd post in our 12 days of microblogging series, we want to highlight how Micro.blog can serve as your social media “home base”. By centralizing your writing, photos, and other web pages at your own domain name, you can control your content but still share it out to other social networks.

Micro.blog has cross-posting for Twitter, Medium, LinkedIn, Facebook, and Mastodon. This feature is available for free if you host your site on Micro.blog, or $2/month if your blog is hosted elsewhere. It includes automatic posting to all 5 of those social networks and any new platforms we may add later.

Here’s how I personally use this feature. I never post directly to Twitter. I publish short posts on my own blog, and Micro.blog automatically sends them to Twitter and other networks. Occasionally I’ll sign in to Twitter and check if I have any @-mentions that need replying to. This way I can avoid the distraction of the Twitter timeline and focus on adding content where it’s most important to me: my own site.

With Mastodon, you have another option beyond cross-posting. Because Micro.blog supports the ActivityPub API, Mastodon users can follow your Micro.blog-hosted blog and you can follow and reply to Mastodon users directly in Micro.blog. I posted more last month about how this works and why it uses your own domain name:

Sometimes in the Mastodon world your identity can get fragmented across multiple instances. You might start on mastodon.social but then move to another instance, effectively breaking the link between your readers and your posts each time you move, with no way to migrate posts between instances. By supporting Mastodon and ActivityPub in Micro.blog, you can consolidate your identity and posts back to your own blog at your own domain name.

Your blog is also a great place to centralize your photos, while still integrating with Instagram and these other social networks. Instagram doesn’t allow automatically posting from your blog to their service, but you can use OwnYourGram or our Mac app to copy Instagram photos to your blog, and from your blog to everywhere else. More links in yesterday’s post.

For details on how cross-posting works — and the extra rules Micro.blog uses to make sure that your posts look good on other networks — see this help page. Happy cross-posting!

Yesterday we started the 12 days of microblogging blog post series to mark the 1-year anniversary of the public launch of Micro.blog. I posted about making it easier for people to share their stories in audio form with microcasting. Today I want to highlight photoblogging.

Sharing photos is an important part of Micro.blog. I put a custom photo picker and filters in the original Micro.blog iOS app to encourage everyone to post photos to their blog, so that you end up with a great collection of your best photos at your own domain name. Because photos are square by default, they look great in the Micro.blog timeline, and with cross-posting Micro.blog can attach photos to your tweets or send posts to other social networks.

We also have a companion iOS app just for photos called Sunlit. It has an Instagram-like timeline for browsing photos from your Micro.blog timeline, with the focus around blogs that I wrote about in my preview post as we were relaunching Sunlit 2.0:

To play nicely with microblogs, we introduced a new post type in the app for single photos. For longer posts, you can still collect multiple photos together, add text, and post them as a story directly to your blog.

Some people on Micro.blog focus almost exclusively on posting photos, like Robert Brook. Some people have even created separate blogs just for their photos at their own domain name hosted on Micro.blog, like burk.photos. There’s a special section of Discover that features photos from more Micro.blog users.

A couple of weeks ago, Jonathan LaCour on Micro.blog submitted a feature request for a photos JSON Feed. He used this feed to build Microgram, a snippet of HTML that you can paste into your blog to provide a grid of photo thumbnails. You can see my photos page at manton.org using Microgram in this screenshot:

One of the most common questions we get is how to migrate photos from Instagram to Micro.blog. I think we have 2 really good options for this:

• Micro.blog for macOS has a built-in Instagram importer. It will take the archive you get from Instagram and allow you to batch import your Instagram photos to Micro.blog, preserving the original dates and text from Instagram.
• OwnYourGram is a web-based app that connects to your Instagram account to automatically copy new Instagram posts to your own blog. Because it’s based on IndieWeb standards, it can also post directly to Micro.blog-hosted sites.

I hope you enjoy posting and browsing photos on Micro.blog! Tomorrow I’ll have the next post in the 12 days of microblogging series.

One year ago today, after months of feedback from Kickstarter backers, we opened up Micro.blog to the public. In that time, we’ve watched the community grow, seeing more folks than ever writing on their own blogs while sharing in the Micro.blog timeline and participating in conversations. We are proud of maintaining our commitment to a safe community space where harassment is not tolerated while promoting independent blogging.

We’ve also added a lot of functionality to the platform during this first year. To mark the anniversary, we are highlighting 12 features of Micro.blog over the next 12 days. We’re kicking off the 12 days of microblogging with a major hosting feature that rolled out earlier this year: microcasting.

What are microcasts? Just short podcasts. A major idea behind Micro.blog is that if blog posts are shorter and easier to post, more people will stick with writing on their own site every day. Podcasting should be easier too.

As I wrote when announcing microcast hosting and our companion app Wavelength:

Everyone has a story to tell. Whether that’s through short microblog posts, longer essays, photo blogs, conversations with friends, or now through podcasts, I hope that the Micro.blog platform and suite of apps can help.

I’ve been so excited to see new podcasts launch on Micro.blog, including our very own Micro Monday hosted by Jean MacDonald. For today’s episode, Jean interviews long-time blogger and Mac developer Brent Simmons about his podcast The Omni Show and working on the new NetNewsWire feed reader.

You can find recent episodes from a variety of microcasts in the Discover section of Micro.blog. Also check out Microcast.club, a directory of microcasts. Get started with your own microcast with this help article and join our Slack community where the friendly folks in the #microcast channel can help with questions.

Tune in tomorrow for day 2 of our 12 days of microblogging series.

Excellent article today from Ben Thompson. After laying out in detail why Apple has a strong argument in yesterday’s Supreme Court hearing, Ben moves to the larger question of the App Store monopoly:

To put it another way, Apple profits handsomely from having a monopoly on iOS: if you want the Apple software experience, you have no choice but to buy Apple hardware. That is perfectly legitimate. The company, though, is leveraging that monopoly into an adjacent market — the digital content market — and rent-seeking. Apple does nothing to increase the value of Netlix shows or Spotify music or Amazon books or any number of digital services from any number of app providers; they simply skim off 30% because they can.

I’ve been saying for years that the 30% cut is completely out of line with the value that Apple provides to developers. Developers should be calling for a more fair 15% rate across the board for all apps, and more flexibility to sell subscriptions outside the App Store. As I wrote earlier this summer, it shouldn’t sit well with developers when Apple talks about billions in services revenue, at our expense.

As I mentioned on this week’s episode of Micro Monday, we want to add category support to Micro.blog including a special section for photos. As a first experiment with a page for photos, I added a JSON Feed of your photos to all hosted blogs on Micro.blog yesterday at /photos/index.json. (It will be updated automatically next time you post to your blog.)

Jonathan LaCour wrote a JavaScript include called Microgram to take that feed and display a grid of photos. You can see it in action on my blog here.

We still want to do more on Micro.blog with photos, but this is a great solution that’s available today. And I think it shows off how JSON Feed makes these kind of integrations much easier. Thanks Jonathan!

I often say that Micro.blog is a success if more people blog. One of the most important goals is to encourage people to post at their own domain name. For more about why that matters and what I think Micro.blog’s role is among other social networks, see my post about the way out.

But we hear from a lot of people who want Micro.blog to succeed in more concrete terms as well. They want it to be a larger business that can hire more developers and curators. I want that too! Micro.blog is the most ambitious platform I’ve built and as it grows we will need more help scaling it.

If you believe in what we’re trying to do with Micro.blog, here are a few simple ways to support the platform:

• Subscribe to one of the blog hosting plans. You get your own domain name, themes, photo or podcast hosting, the new Mastodon-compatible support, and much more. This is what I use to host my own blog and podcast.
• Give a friend a blog subscription. If you already have a paid subscription yourself, click Plans → “Give Micro.blog” to invite someone to Micro.blog and pay for their first year of blog hosting at a discount.
• Tell everyone what you like about Micro.blog. We don’t have any gimmicky viral features to spread the word automatically. For other people to find out about Micro.blog, you’ll have to post to your blog, tweet a link, or talk about it on your podcast.

We are approaching 2 important milestones: the 1-year anniversary of the public launch, and nearly 2 years since the Kickstarter. Micro.blog has improved significantly since then and it will continue to get better with your support. Thanks!

Josh Marshall of Talking Points Memo has written some good posts about Facebook this year. Here’s part of today’s post about trust:

Facebook’s core problem is that it was a platform based on trust. I don’t mean it acted in a trustworthy way. But it facilitated things that were at core about trust and relationships. So it was in the trust business, regardless of what its corporate culture may actually have been about. Having failed at that and not convinced people it’s trustworthy it now seems committed to a corporate version of acting out, going to war with its own stakeholders, whether those are users, investors, the governments of the countries in which it operates.

See also my post last week about breaking up Facebook and the eventual pushback against Facebook-owned Instagram.

We start this week’s Core Intuition by following up on the Mastodon integration in Micro.blog. From the show notes:

Manton reports back to Daniel about the first week after adding Mastodon integration to Micro.blog. They talk about the merit and necessity of spending time marketing after all the coding work we do. Daniel talks about his recent struggle implementing support for Google’s OAuth2, and finally they talk about Apple’s new Hardened Runtime and the associated app notarization service Mac apps that are distributed outside the Mac App Store.

It’s nice to hit episode 350, but I was just listening to ATP’s 300th episode today and realized that they have reached their milestone in about half the number of years that it took me and Daniel. We didn’t record very often in the early years, and even now usually miss a couple weeks here and there, so I expect ATP will eventually pass us up in total episodes. 🙂

Two related articles about Facebook this week. First, from a huge report in The New York Times:

But as Facebook grew, so did the hate speech, bullying and other toxic content on the platform. When researchers and activists in Myanmar, India, Germany and elsewhere warned that Facebook had become an instrument of government propaganda and ethnic cleansing, the company largely ignored them. Facebook had positioned itself as a platform, not a publisher. Taking responsibility for what users posted, or acting to censor it, was expensive and complicated.

The New York Times interviewed over 50 people for the story, and it shows. There are a lot of interesting behind-the-scenes stories, especially Facebook’s relationship with Washington, and more than I can quote here.

Second, an article from The Washington Post about early Instagram employees becoming disillusioned with the platform:

Three of the early Instagram employees, including Richardson, have deleted it — permanently or periodically, comparing it to a drug that produces a diminishing high. One of the people said he felt a little embarrassed to tell people that he worked there. Two of the other early employees said they used it far less than before.

This is why I don’t ever want to sell Micro.blog. I can’t imagine having to sit on the sidelines and watch with disappointment what it might become if it drifted away from its mission.

I think pushback against Instagram is coming, as more people who have already left Facebook also remember that Instagram has the same leadership, and the platform is far enough off track that even the founders have left. It’s a good time to be posting photos to your own blog instead of Instagram.

In a post earlier this year, Ben Thompson recognized that the threat to Facebook is when it becomes accepted fact that using the app isn’t good for you:

It follows that Facebook’s ultimate threat can never come from publishers or advertisers, but rather demand — that is, users. The real danger, though, is not from users also using competing social networks (although Facebook has always been paranoid about exactly that); that is not enough to break the virtuous cycle. Rather, the only thing that could undo Facebook’s power is users actively rejecting the app.

Having your own domain name for blog posts and photos isn’t just about personal independence from the control of massive social networks. Owning our content is key to the way out of the current social network mess.

Some may call for Facebook to be broken up because it has too much power. But we can’t count on antitrust law to do it. Users must do it. We must do it by moving our attention away from companies we don’t believe in.

Last week we launched support for the ActivityPub API in Micro.blog. This is a major feature to add compatibility with Mastodon, including:

• Mastodon users can follow posts from your blog using a username like @you@yourdomain.com.
• Mastodon users can reply to your posts, and those replies will show up in your Micro.blog timeline.
• You can follow Mastodon users from within Micro.blog.
• You can reply to Mastodon posts in Micro.blog, and those replies will also flow back to Mastodon.

Unlike cross-posting (which Micro.blog also supports), enabling ActivityPub in Micro.blog does not use a separate Mastodon account. Everything can be accessed from within Micro.blog using your custom domain name as your web identity. I’ve mostly been testing with Mastodon, but as we continue to test and improve this feature it should also work with non-Mastodon ActivityPub servers.

There are a few steps to get started:

1. Pick a custom domain name. For me, this was easy: I wanted to use manton.org.
2. After setting up Micro.blog to host your blog, point the domain name to Micro.blog. We have a help page about this.
3. Micro.blog will send an email when SSL is enabled for your blog. If there are any delays, don’t hesitate to email us at help@micro.blog and I will make sure your blog is updated and ready for ActivityPub.
4. Click on Account → ActivityPub → “Set Mastodon-compatible Username”. Here you can choose what username other Mastodon users can find you with.

Thanks to everyone who has already tried enabling this on their Micro.blog account! We have learned a lot and fixed several bugs with conversations across both platforms. Looking forward to where this goes.

Earlier this year I migrated 15 years of posts on manton.org to Micro.blog blog hosting. Today I finished moving over 100 episodes of my podcast Timetable to Micro.blog podcast hosting. I had gotten out of the routine of recording Timetable, and I think moving it to Micro.blog will simplify the setup and make me publish the podcast more often.

Timetable had been hosted on WordPress using the Seriously Simple Podcasting plugin. There were at least a few ways I could’ve moved the episodes, but ultimately I decided on the following:

1. Downloaded all the MP3s to my Mac.
2. Adjusted the WordPress settings to show 120 recent posts in the feeds, then saved the resulting JSON Feed of all episodes. This let me parse the JSON much more easily than working with the WordPress API or XML.
3. Wrote a Ruby script that uses the Micropub API to upload each MP3, then create a new post with an audio tag, preserving the original post content and date.
4. Pointed timetable.manton.org to use Micro.blog.

Even if you don’t know Ruby, hopefully you can see in the script how easy is it to work with Micropub, which Micro.blog uses as its native interface to create posts and upload files. I just call out to the curl command-line tool to do the work.

If you’re new to Timetable, each episode is only about 5 minutes. Some of my recent favorites include episode 91 (Lose yourself), episode 92 (Good, better, best), and episode 100 (One year).

Last year we held the first IndieWebCamp in Austin. I blogged about how the event went, including sessions and topics covered, and what I learned from it:

I’m really happy with the way the event came together. I learned a lot in helping plan it, made a few mistakes that we can improve next time, but overall came away as inspired as ever to keep improving Micro.blog so that it’s a standout platform of the IndieWeb movement.

We’re going to do it again early next year: February 23-24 at Capital Factory. If you’ll be in Austin, mark that weekend on your calendar. I’ll make another announcement when registration is open.

Last year there was a lot of work and last-minute stress deciding on a venue, so this year we’re going to keep a bunch of things the same that seemed to work pretty well. By nailing down the details early, we’ll have much more time for promotion. I’d love to see us double attendance from last year. Hope to see you there!

Micro.blog now has 3 distinct styles of usernames to make the platform more compatible with other services:

• Micro.blog usernames, e.g. @you. These are simple usernames for @-mentioning someone else in the Micro.blog community.
• Mastodon usernames, e.g. @you@yourdomain.com. When you search Micro.blog for these usernames, Micro.blog will look for the user in another federated Mastodon instance so that you can follow them.
• IndieWeb-friendly domain names, e.g. @yourdomain.com. This is where I always thought we’d go for more distributed “the web is the social network” interactions. Replying to one of these usernames will send a Webmention to that user’s external web site.

I’m @manton on Micro.blog, my blog is manton.org, and because Micro.blog-hosted blogs support the ActivityPub API, you can follow me from Mastodon by using @manton@manton.org.

I just rolled out some ActivityPub-related reply improvements. I’ll continue to improve the Micro.blog timeline so that these usernames can all coexist nicely. We’ll also be updating the native apps to better support these usernames, for highlighting and auto-completion.

For some time, we have been considering how we could open up compatibility between Micro.blog and Mastodon. Any feature that could be disruptive needs to be approached carefully. In this post I want to talk about how Micro.blog supports Mastodon, why I think it’s useful, and anticipate some questions that we’ll get about this feature.

We’re launching 2 major features today:

• Micro.blog can now cross-post to a Mastodon user account, in the same way we cross-post to Twitter, Facebook, Medium, and LinkedIn. This takes a copy of your blog posts and sends them to a specified Mastodon account.
• Your custom domain on Micro.blog can now be ActivityPub-compatible, so that you can follow and reply to Mastodon users directly on Micro.blog. This also means someone can follow your blog posts by adding @you@yourdomain.com on Mastodon. (This username is configurable. Mine is @manton@manton.org.)

These 2 features are separate and either can be enabled if you want. I have tried to be very deliberate in how ActivityPub is implemented. It is off by default, and to keep the focus on blogging and content ownership, it only works with custom domain names.

One of the most important goals for Micro.blog is to encourage more people to blog. I wrote last year that it’s a success if more people blog. Based on the feedback we’ve received from the Micro.blog community, we are making great progress toward that goal.

We have a lot of things we want to help solve with Micro.blog, but blogging is a core part of the foundation. It’s not about being the most popular social network. It’s not about competing with every platform that launches. It’s much better for the mission of Micro.blog for us to embrace other platforms (as we’ve always done with the IndieWeb) rather than put up walls between APIs.

I recently published a post with 4 parts to how we get out of the current mess with today’s big social networks. I mentioned Mastodon in that post because while I don’t think Mastodon tackles all 4 parts of fixing this, I do think it has a role to play.

More compatibility with Mastodon lets us support the good things that Mastodon has accomplished, while still carrying forward what I think are the unique strengths of Micro.blog. It also opens up the Micro.blog community to interact with a much larger user base.

Sometimes in the Mastodon world your identity can get fragmented across multiple instances. You might start on mastodon.social but then move to another instance, effectively breaking the link between your readers and your posts each time you move, with no way to migrate posts between instances. By supporting Mastodon and ActivityPub in Micro.blog, you can consolidate your identity and posts back to your own blog at your own domain name.

As I wrote earlier this year, content ownership on the web is about domain names:

When you write and post photos at your own domain name, your content can outlive any one blogging platform. This month marked the 16th anniversary of blogging at manton.org, and in that time I’ve switched blogging platforms and hosting providers a few times. The posts and URLs can all be preserved through those changes because it’s my own domain name.

If you already have your blog on Micro.blog at yourdomain.com, we can build on that to allow @you@yourdomain.com or @whatever@micro.domain.com. This focus on domain names will continue to guide new features in Micro.blog.

Let me answer some questions:

• How is Mastodon support enabled on my account? In Micro.blog on the web, click Account → ActivityPub. You will be prompted to select a username. A paid hosted microblog is required so that Micro.blog can use your custom domain name.
• How can I find Mastodon users to follow on Micro.blog? As more Micro.blog users interact with Mastodon users, some of those users will naturally show up in conversations or even be featured in our Discover timeline. You can also add a specific Mastodon user by searching for their full username.
• Will Micro.blog now start showing follower counts? No, it’s important to me that we don’t change the Micro.blog user experience to resemble every other social network. When you follow a Micro.blog user from Mastodon, an individual Mastodon instance will have its own follower count just for that instance. Any follower count shown in Mastodon for a Micro.blog user will be wrong. This isn’t ideal, but it’s the best we can currently do with how Mastodon works.
• What about Content Warnings? Micro.blog does not support them. I’ve heard from Mastodon fans who like Content Warnings, but I’m concerned about introducing extra friction in both the posting and reading experience. We’ll reevaluate this feature later.
• What happens to direct messages sent from Mastodon to Micro.blog? Micro.blog does not have any private posts by design. Direct messages sent from Mastodon are converted into a private email.
• Is this going to make Micro.blog just like Mastodon? No, this is not a clone of Mastodon merged into Micro.blog or running alongside it. It’s a from-scratch implementation of a few common APIs that Mastodon uses so that both systems can talk to each other.
• Will third-party Mastodon clients work with Micro.blog? Not currently. We might consider this later, but because of the UI differences, I think it’s a better fit to have third-party apps designed for either Micro.blog or IndieWeb standards.
• What will happen to the Micro.blog community? I hope that this will help grow the community, without taking away from what has worked well on Micro.blog. While you might see some Mastodon posts, and those Mastodon users can interact with Micro.blog users, users from other Mastodon instances won’t know about our community guidelines or expectations for Micro.blog. The community will remain predominantly Micro.blog users who share our goals for the platform.
• How does Micro.blog’s mute feature work with Mastodon? Muting in Micro.blog has been expanded to support muting individual Mastodon users, or entire Mastodon instances based on their domain name. We have also preloaded a common list of Mastodon instances that are muted automatically because of code of conduct violations.

This is a really big feature. I hope you enjoy it! This is just the baseline. I’ll be working on bug fixes and improvements to make this integration work as smoothly as possible. If you have any feedback, let me know at help@micro.blog.

Seth Godin on daily blogging:

For years, I’ve been explaining to people that daily blogging is an extraordinarily useful habit. Even if no one reads your blog, the act of writing it is clarifying, motivating and (eventually) fun.

As he says, you’ve gotta get past the first couple hundred posts to see the most value. This is why indie microblogging is so useful. Start with some short posts, a few photos, and eventually it’s a habit. Stick with it and you’ll really have something.

In Micro.blog we have some pins to encourage people to blog more often. You’ll unlock pins after your first photo, 10 posts, setting up a custom domain, and more. Today, if you mention “Halloween” or “pumpkin” in a blog post you’ll unlock the special Halloween pin.

Micro.blog doesn’t have hashtags, trending topics, or retweets because I think the focus on those features in other social networks has led to people being exposed to harassment, hateful posts, and even fake news. For Micro.blog, it’s more difficult to accidentally stumble on a random post unless it’s part of a conversation you’re in or from a section that is actively curated.

This was an important design decision and we’re not walking away from it, but the downside is that it is more difficult to find older posts without a global search. As the first step in improving this, today we’re rolling out a new search screen. You can now search for users and across any post that has been featured in the Discover section.

Click on Discover from the web version of Micro.blog. I’ll continue to improve this throughout the rest of the year, expanding it to more posts, including in the native apps. Looking forward to hearing your feedback!

The Atlantic, quoting Ben Grosser, after news that Jack Dorsey is reevaluating whether Twitter should even have likes:

“Part of what’s happening in spread of disinformation is that people can essentially repeat what someone else said and spread it to the world, the retweet has an effect well beyond the Like in that regard,” he said. Grosser also indicated that removing just the like button would only make the retweet more powerful. “I fear that if they remove the Like button the fact that there are other indicators that include metrics will just compel users to use those other indicators,” Grosser said.

Removing likes and retweets is of course old news to anyone who has been on Micro.blog. I wrote 2 years ago about the potential harm of retweets. It’s a common theme in the talks I’ve given and in other blog posts since.

When I first started rolling out Micro.blog to early supporters, not having public likes, retweets, or follower counts was a kind of controversial, risky decision. Now it’s almost boring. We’re in the middle of 2 complementary transitions: a move away from massive social networks, and smaller platforms providing the flexibility to remove features and algorithms in service to the community.

A few months ago on Timetable, I talked about how Micro.blog needs the equivalent of a college orientation session to get new people used to how the platform works. I took some time this morning to record a quick intro screencast video. It’s a little rushed because I tried to fit it into 2 minutes, but I’m glad to finally have something. I’ll be working to update it soon.

I’m adding a link to the video at the top of the “welcome” email that new users get when they sign up. You can also watch it on the help site here.

Project Gutenberg is the code name for a redesign of the WordPress post editor. It’s an ambitious change set to ship next month in WordPress 5.0. Taking inspiration from Medium and appealing to web authors who use WordPress more like a CMS than a blog, Gutenberg features a block-based design for visually laying out the text and elements of a web page.

As I test Gutenberg, I keep coming back to one question: is it good for blogging? The goal with Micro.blog is to make blogging easier so that more people will have their own site instead of delegating their web identity to a social network. Gutenberg is more flexible than today’s WordPress, but it’s also more complex for someone who just wants to type in a few sentences and hit publish.

I’ve been talking about this with Daniel on our podcast Core Intuition. Many WordPress users will love Gutenberg, but there will be a significant number who just want a simple posting interface for blogging. This is where a traditional native blogging app like MarsEdit or the focused UI around microblogging seem like much better fits.

Put another way, as WordPress matures I think it moves further away from the ideal blogging interface for someone who wants to write every day. Even as we add features to Micro.blog — domain names, themes, full-length posts, photos, podcasting — the core platform will always be rooted in the simple idea of a text box and a timeline.

Sometimes I hear from people who decide Micro.blog isn’t for them because it’s “just for bloggers”. On the one hand, they aren’t wrong; it is partly a blog hosting platform. But I think that feedback reveals less that there’s a fundamental mismatch and more about how much we still need to improve the user experience. One of the key points of Micro.blog is to encourage more people to post content at their own site, even if traditional blogging tools were too much trouble for them.

There’s evidence that this part of the mission for Micro.blog is working. There are many people who could never get blogging to stick until they tried Micro.blog. Some of them are featured on the Micro Monday podcast.

Whether it’s Twitter-like posting, photo blogging, microcasting, or using Micro.blog as a full web site at a custom domain name, there are millions of people who would post more often if it was easier. If you tried Micro.blog a year ago, consider trying it again! It is significantly better now than it was at launch, and as it continues to improve I hope that many more people who “aren’t bloggers” will find a home at Micro.blog.

Earlier this week I wrote about some behind-the-scenes Webmention changes that improve how replies are handled for external blogs, and yesterday we increased the storage for hosted podcasts. Today I’m rolling out some more visible new stuff on Micro.blog:

• Added special sections of Discover for Inktober and NaNoWriMo. I love seeing the art that has been posted already, and we want to do more to encourage the writers on Micro.blog next month.
• Added new invite link under “Plans” to invite someone to Micro.blog. If you already have a paid subscription you can pay for someone’s blog hosting for a year! We’ve heard from customers who want to offer this to friends or family to make it easier for them to get started blogging. It’s a one-time $50 payment, so $10-off the usual year-long subscription.
• Added a progress spinner when loading the timeline on the web.
• Added “…” button on the user profile page on the web with option to mute or report the user, matching what was recently added to the macOS version of Micro.blog.
• Plus a few bug fixes and cleanup to make things run more smoothly.

After a very busy summer, I feel like I’m able to get back to deploying improvements to Micro.blog on a regular schedule. Still have a couple big features in the queue that I hope will be ready soon. Thanks for the support!

I rolled out a few Webmention improvements to Micro.blog today:

• Fixed the permalink for a reply when you aren’t signed in, which was preventing external sites from verifying the link after receiving a Webmention from Micro.blog.
• Added limited support for accepting replies from external sites that do not have a Micro.blog account. Previously, Micro.blog would discard replies that could not be associated with an existing user. Now, these replies will be included in a thread using the domain name for the author. (Brid.gy replies from Twitter are not supported yet.)
• Improved replying on Micro.blog to send Webmentions to any external site in the reply chain, not just the root post. This more consistently allows replies to be copied to multiple external blogs that are participating in the conversation.
• Behind the scenes, for the last few months Micro.blog has been recording all incoming Webmentions, even if they don’t target a specific reply or just can’t be processed yet. This should allow us to add more reply-related features for hosted blogs in the future.

There may still be some quirks to work out with these changes, but I’m happy to finish more of the plumbing around replies on Micro.blog. Getting closer to the IndieWeb vision for how cross-site replies on the web can work.

There has been a lot of distressing news lately, so it’s refreshing to read a story about developers who are just quietly making the web better. The team at the Internet Archive has fixed 9 million broken links on Wikipedia by scanning pages for broken links and updating them to point to the Wayback Machine’s copy:

And for the past 3 years, we have been running a software robot called IABot on 22 Wikipedia language editions looking for broken links (URLs that return a ‘404’, or ‘Page Not Found’). When broken links are discovered, IABot searches for archives in the Wayback Machine and other web archives to replace them with.

I wrote a blog post in 2012 about how fragile web pages are. This is always on my mind. It has informed a couple Micro.blog features such as our automatic mirroring of your blog to a GitHub repository. I hope that as the web evolves that this issue of broken links can be more directly tackled, so that the full responsibility for fixing this isn’t only on the Internet Archive.

It has been over a year since JSON Feed was announced. There have been a bunch of discussions about expanding the specification, but we are very happy with how well the initial version has worked. It powers all Micro.blog-hosted blogs by default and is also used on many WordPress blogs, home-grown sites, and other platforms, with great support in feed readers like Feedbin.

I haven’t had as much time to maintain the WordPress plugin for JSON Feed, though. David Shanske noticed this and offered to take the lead on merging pull requests and making other improvements to the plugin. Thank you, David! He’s now rolled all these changes into a new version.

You can grab version 1.2 of the WordPress plugin from GitHub or by searching for it in the WordPress plugin directory. Enjoy! And thanks again to David for moving the plugin forward.

I updated Micro.blog with several improvements today:

• Added a Markdown preview button when writing a post on the web, to test what the post will look like when published.
• Added a “Show More” button to the timeline and mentions on the web for scrolling further back.
• Fixed muting users to also hide posts in conversations.
• Fixed reliability of the before_id parameter in more places in the API.

Plus some other tweaks. These changes focus mostly on the web version of Micro.blog. We have updates to the native apps that will follow.

Jean published episode 30 of our Micro Monday podcast today. There have actually been over 30 episodes if you count the bonus episodes, but I wanted to officially mark the 30th episode as a milestone as I reflect on what the podcast has meant for Micro.blog.

This week Jean welcomes @amit:

Our guest this week is Amit Gawande, who codes for a living but lives for reading and writing. He is the creator of Microthreads, a tool for finding users and conversations to follow on Micro.blog. We talk about the many blog platforms he’s used over the years, and why the simplicity of Micro.blog makes it easier to just write.

I love that Micro Monday is so consistent with our values. Everyone has a story to tell and should be able to have their own space on the web to tell it. The podcast makes Micro.blog better at the same time as it gives members of the community another opportunity to talk about what they care about. Thanks to everyone who has been on the podcast so far!

We posted the latest Core Intuition this weekend. It’s a 45-minute episode without sponsor breaks dedicated to the Mojave release and Mac App Store. More from the show notes:

macOS Mojave is out! Daniel and Manton talk about the ephemeral nature of App Store features, and the wisdom of not investing too much stock in being featured, or any other external recognition. They catch up on the state of the Mac App Store and wonder about the expected App Store versions of BBEdit and Transmit. Finally, they talk about their own continuing plans for supporting Mojave, particular with respect to Dark Mode.

As part of hopefully consolidating a couple of my servers, I’ve moved the MP3 hosting to Libsyn. We have 10 GB of previous episodes, so I’m still not entirely sure what the best long-term hosting solution is. We’ve changed our mind a few times over the podcast’s 10-year history.

I watched the entire hearing yesterday, working with my laptop in the living room with the TV on. At several points I tried to type a quick post about what was unfolding, but I couldn’t do it justice in 280 characters. Since shortly after the 2016 election, I’ve kept most politics off my blog, trying to focus as much of my attention as possible on Micro.blog and related topics.

I have thoughts on Judge Kavanaugh’s tone and answers, of course. I have thoughts on how partisan the second half of the day was, so divisive and seemingly irreparable. But ultimately that doesn’t matter. What I’ll remember for the rest of my life is the first half of the day.

If Republicans on the committee thought Dr. Blasey would contradict herself or seem inauthentic, they must have realized within minutes that they had miscalculated. I wrote in my notes while watching it live: I can’t imagine anyone who could be more believable than she is.

It was very brave of her to go through this. I couldn’t stop thinking of all the women who must be watching, who have been sexually assaulted and lived with the memory for years, telling only a few people or no one. I hope when we look back on Dr. Blasey’s testimony that it will be an inspiration for many, even as it was so heartbreaking.

We rebooted the Homebrew Website Club meetup in Austin this summer after a break, and last week we met again at Mozart’s Coffee to talk about the IndieWeb. It was raining when I arrived at the coffee shop. Despite the weather we found some tables on the bottom deck and had a good turnout.

The meeting was informal. After introductions, we talked about the state of social media and silos, with some detours into Mastodon, Micro.blog, and the value of having your own site. The discussion inspired me to finish writing a post about the way out of this mess we’ve found ourselves in with massive social networks.

We’re going to keep the meetup at Mozart’s for now. The next meetup will be October 3rd, 6:30pm. I think it will start to become a little more structured: introductions, demos, discussion, and time for writing or working on projects. Thanks to everyone who made it!

There have been many articles written in the last month about the role of social networks. Some even reach the obvious conclusion: that the top social networks are too big. This interview on Slate was fairly representative, covering monopolies and centralized power.

But these articles always stop short before hitting on a solution. They always wrap up saying “it’s tough to solve this”.

I think there are 4 parts to finding our way out of this mess with massive social networks:

Better features: We should be careful before copying everything from Twitter. I don’t want to take features that failed us and recreate them in a new environment. Micro.blog leaves out features on purpose that we think undermine a healthy community.

Open standards: When I first stopped tweeting 6 years ago, it was largely because of the developer-hostile attitude from Twitter. Proprietary APIs reinforce the lock-in with content silos. This is why so much of Micro.blog is based on IndieWeb standards. It’s why Mastodon uses APIs like ActivityPub.

Content ownership: Controlling the writing and photos you post online isn’t about open source or the technical experience to run a server. It’s about using domain names for identity, so that you can move your data in the future without breaking URLs. I’ve written more about this here and it’s a fundamental part of the book I’m writing about microblogging.

Smaller social networks: Many people are looking for “the next Twitter”, but it’s not enough to replace Twitter with a new platform and new leadership. Some problems are inevitable when power is concentrated in only 2-3 huge social networks — ad-based businesses at odds with user needs and an overwhelming curation challenge. This might be Mastodon’s greatest contribution: getting people used to the idea of many smaller, interoperable communities.

There’s not only one solution. I think platforms like Micro.blog and Mastodon each have a role to play and can be complementary. Mastodon helps by encouraging smaller social networks, distributing the task of moderation, but doesn’t prioritize content ownership. (An account on an instance like Mastodon.social has no more ownership of its content than an account on Twitter. Both let you export your data but both live at someone else’s domain name.)

If you are frustrated with the state of social networks, I recommend blogging more. I love seeing new blogs and photo blogs just as we’re having a serious debate in the mainstream about social networks. The way out isn’t easy, but there’s a clear path waiting for us to take it.

Today we added a new screen to the web interface for hosted blogs on Micro.blog. Click “Posts” and then choose the “Uploads” tab to view your uploaded photos and microcast episodes. You can also upload new photos here to later include in a blog post.

Expect this part of Micro.blog to continue to improve. If you have any feedback, let us know. Thanks for your support!

Of everything you put into social networks, photos are one of the easiest and most rewarding parts to reclaim for your own site. Because we shipped Sunlit 2.2 this week, I want to share a guide for starting a new photo blog that you will actually consistently post to.

The first step isn’t technical. It’s a commitment to posting regularly on your own blog instead of first reaching for Instagram or Snapchat. A commitment to posting to a place you control, to a place you can look back to years from now as an archive of your best photos at your own domain name, regardless of what social networks come and go over the years.

If you already have a hosted blog on Micro.blog or WordPress, you can use that. If you want to start with a new space just for photos, use Micro.blog and click Plans → New Microblog. In the Micro.blog settings, you can map a custom domain to your new photo blog such as photos.yourdomain.com.

Instagram will let you download an archive of all your Instagram photos. If you use macOS, install Micro.blog for Mac. Choose File → “Import from Instagram”. Select the media.json file in the archive you received from Instagram, and Micro.blog will let you select some or all of your photos to import, preserving the dates and captions on your new photo blog. See this help page for more details on importing from Instagram.

To post a new photo, use the official Micro.blog iOS app or our new companion app Sunlit. There are also great third-party apps such as Icro for iPhone and MarsEdit for macOS.

When you post a photo with some text but no title, that photo will show up directly in the Micro.blog timeline.

Another option is to connect OwnYourGram with Micro.blog. OwnYourGram can watch your Instagram account for new photos, then copy them automatically to Micro.blog. Before setting up OwnYouGram, make sure to add your Instagram username in Micro.blog under Account → “Edit Apps”.

For an overview video of the new version of Sunlit, see my post from yesterday. Happy photo blogging!

This week we shipped the new version of Sunlit, featuring an Instagram-like timeline of photos from people you’re following on Micro.blog. You can post photos to a microblog on Micro.blog, or to WordPress and other compatible blogs.

The best way to understand Sunlit is to see it. I’ve prepared a short video below, talking through a few of the main screens, but the app has a lot more depth for editing photos and organizing photos into stories:

Sunlit is a free download in the App Store. There’s no in-app purchase. If you like it, I hope you’ll support Micro.blog with a subscription to a hosted microblog or new photo blog. You can learn more at sunlit.io.

Om Malik has a post on leaving Facebook for good:

Why? Because I don’t need it and don’t miss it. I left, not because of the company’s dodgy approach to privacy, data accumulation or its continued denial of its impact on shaping modern society. I left because it was making me someone I am not — someone who lives life through the eyes of others.

He also mentions Instagram and focusing more on his own photo blog:

I have started a photo blog — where I cross post all photos I share on Instagram. I think it is a matter of time, before it becomes my primary spot for sharing photos.

As I read this, Jon and I are wrapping up Sunlit 2.2, which will ship on Tuesday. It’s a Micro.blog companion app just for photos. I recorded a short preview video here.

NetNewsWire is returning home. Brent Simmons first shipped NetNewsWire Lite way back in 2002 and it played a significant role in the early popularity of RSS on the Mac. I’ve written a few things about it over the years, including this post in 2002 when I switched to using it.

It has been fun to watch Brent start over with Evergreen, document the progress in public on his blog and GitHub, and now it’s fitting to see that work evolve into the next official version of NetNewsWire. NetNewsWire 5 will also have great support for JSON Feed and Micro.blog. Congrats Brent!

We rolled out a few improvements to Micro.blog this week. There’s a new page on the web for managing muted users — click Account and scroll down to the “Edit Muted Users” button — and a new macOS release with a photo upload bug fix and an options menu to mute or report users.

You can download Micro.blog for Mac here, or choose “Check for Updates” inside the app. If you missed it when it was first announced, the app now supports uploading your Instagram archive as microblog posts.

About a month ago we added experimental support for Indiepaper to Micro.blog. It’s in the spirit of Instapaper or Pocket, but built on IndieWeb standards. You can read more about Indiepaper in our help.

I wasn’t sure where this would lead, but people are using it, so we’ve improved Micro.blog to include a page on the web for viewing or managing saved articles. After you’ve added an article to read using Indiepaper, a new link to access it will appear under Account → “Edit Feeds & Cross-posting”.

Thanks for your support of Micro.blog. As expected, we’ve had a bunch of new people join Micro.blog, which always translates to great feedback for making the platform better.

This week we rolled out a few improvements to podcast hosting on Micro.blog. I talked about some of it on yesterday’s episode of Timetable. Here are the changes:

• Increased MP3 upload size to 35 MB. With the default setting in Wavelength for iPhone this is over half an hour per episode. At lower bitrates, it’s over 70 minutes.
• Added custom email address to site settings. Google’s podcast directory apparently likes a contact email in your podcast feed, so this allows it. (But it’s blank by default in Micro.blog for privacy.)
• Updated podcast feed to use your “about me” text as the podcast description.

Speaking of podcasts, check out the latest episode the Supertop podcast. In addition to updates about their podcast client Castro, they cover my blog post about Anchor and other thoughts on what impact Anchor might have on the podcast industry.

Two quick follow-ups on my post yesterday about Apple removing Infowars from their podcast directory, and related actions by Facebook and YouTube. First, Alan Jacobs summed it up really well on his microblog:

What Alex Jones is being deprived of is amplification. Not the right and freedom to speak, but multiple megaphones.

And I love this quote from the Onion:

What we see here really could be the beginning of a slippery slope towards a horrific ordeal in which any citizen who violates hate speech policies or blatantly spreads lies that cause other individuals to receive death threats will immediately be discredited and, perhaps, even asked to host their demonstrably false content on a website that they actually own.

The best satire is often true. We’re seeing a major shift in how mainstream users view the role of these huge social networks.

BuzzFeed has an article about Apple removing Infowars from the Apple podcast directory:

Apple’s decision to remove all episodes of Jones’ popular show — rather than just specific offending episodes — is one of the largest enforcement actions intended to curb conspiratorial news content by a technology company to date. Apple did not host Jones’ shows, but it offered an index that allowed anyone with an iPhone to find and subscribe to them.

This is the way the web is supposed to work. Alex Jones can continue to host his podcast and his fans can subscribe manually. But Apple has no obligation to index it in their podcast directory and make it easy for people to find it.

More from the New York Times today:

Some tech companies, including Facebook and Google, which owns YouTube, had appeared reluctant to remove Mr. Jones’s pages entirely and were instead taking action against specific videos.

Google has now decided to terminate his YouTube channel. And:

Tech companies have long been wary of censoring speech, but an increasing amount of hate speech and misinformation — and louder protests from critics — have forced them to take action. Moves by the tech companies against Infowars and its peers have spurred a debate over free speech.

Facebook and YouTube are conflicted about how to handle this because their model is wrong. Unlike podcasts and blogs, which can live at a custom domain and move between hosting companies, videos on Facebook and YouTube are served directly on those platforms. If the videos are blocked, especially by YouTube which controls nearly all video on the web, there’s no obvious migration path away.

We’ve also seen this hesitation to curate with Twitter. My post about pulling the weeds covers the same issue.

Over the last dozen years we have let massive centralized social networks gain far too much power. We started paying the price with the 2016 election and the fallout continues today. The solution is clear: post to your own site, encourage other people to get their own domain name, and support smaller social networks like Micro.blog that are empowered by design to curate.

When I started using Twitter again for cross-posting, I made a few rules for myself so that I wouldn’t get pulled back into the platform. One is that I let Micro.blog post everything for me automatically, and I only favorite or reply to people when I get asked a specific question. I don’t follow anyone.

But every once in a while I feel compelled to jump in to a discussion. In reply to Joe Cieplinski’s blog post today about Apple having all the leverage, I posted this tweet:

The sad part of this is that developers actually do have leverage, but we’re just not organized and can’t agree on what is fair. It would take the whole community coming together. Most developers think that Apple’s tight control over app distribution is fine. (Spoiler: I don’t.)

Long-time readers of my blog will notice that I complain about Apple as often as I praise them. I hold Apple to a very high standard because they’ve earned it through great design and products.

I know Micro.blog isn’t perfect yet. There are many things we’d like to improve. But I’m proud that the values for the platform are consistent with everything I’ve been blogging about for 15+ years. Complaints I have against the power of big companies like Apple, Facebook, Google, and Twitter… The entire design of Micro.blog’s architecture is to do the opposite of what those companies do.

Jason Snell posted about Apple’s record services revenue:

As someone who’s interested in products, I find the focus on Services revenue to be a bit dispiriting. I get excited at the prospect of new products and seeing how consumers are accepting or rejecting products in the market. But the discussion of Services, especially in a financial context, is essentially a conversation about how Apple can grind more money out of every single person who uses an iPhone, iPad, and Mac.

Back in 2011 I explored the App Store’s 30% cut from the perspective of supporting free app downloads:

I’ve argued that Apple’s 30% tax is about growing that to significant profit at the expense of developers, but in the back of my head I’ve also been concerned that maybe it’s just to keep the App Store from falling into the red. Maybe they are really struggling under the weight of what they created, and long app review times and lack of focus around the Mac App Store launch are just symptoms of that.

In hindsight, 7 years later with $9.5 billion in services revenue per quarter, my attempt in that post to reconcile Apple’s cut seems like a stretch. To echo what Jason says above, I still believe that services should complement Apple’s core products.

iCloud storage is there to make the experience of saving files or backing up your iPhone better, not to nickel-and-dime users who need more storage for a backup. The App Store is there to make discovering apps easier, not to turn developers into a profit center. The more these parts of Apple’s business dominate their revenue, the more divorced their product planning becomes from what users and developers need.

$9.5 billion. As I’m posting this their stock price just pushed the company to $1 trillion in market cap. Many developers can’t make enough to support even a 1-person indie business full time.

As an exclamation point on the discussion around services revenue, Apple has also cancelled their affiliate program. Stephen Hackett sums up what I think many people in the community are thinking:

Payments made to people linking to apps with affiliate links comes out of Apple’s share of revenue generated by app sales and in-app purchases. How much money it costs them is unknown, but the idea that the reasons behind this move could be financial in nature feels pretty gross. Apple is a for-profit company, and it has no bottom-line reason to keep this program open, but sometimes doing the right thing comes with a cost.

And John Voorhees on Apple’s statement that the App Store no longer needs affiliate links:

If that’s the case, it’s short-sighted, but it’s certainly Apple prerogative to run its programs as it sees fit. Still, it’s not the right way to address the publications, developers, and others that have generated millions of dollars of referrals over the years in exchange for a modest 7% cut.

I’ve argued since the first days of the App Store that Apple’s 30% cut is too high. This tax on developers is completely out of line with the value that Apple provides. The fact that Apple is bringing in so much money from services — nearly as much as the Mac and iPad combined — shouldn’t sit well with developers who are still struggling. It’s even worse now without the affiliate program, which developers could use to recoup some of that 30%.

Note what I’m not saying. I’m not saying that Apple should lower the rate to match Stripe’s 3%, or that Apple should operate the App Store at a loss. It costs real money to maintain the App Store infrastructure and commit to featuring apps every day. But there should be a middle-ground that gives developers the best shot at a sustainable business.

Introducing a 15% tier for in-app purchase subscriptions (after the first year) was a good start. Most developers thought we’d never see that. We should be calling for an across-the-board 15% rate for all App Store transactions. It’s the right thing for Apple to do. As Apple’s services revenue continues to grow — and the TV streaming service will only add to that — the time to make this change is now.

Nick Heer has a comprehensive post on how web pages have become so slow despite huge improvements in our internet speeds. He covers JavaScript tracking, Google’s AMP, and a CNN web page that takes 30 seconds to load:

The vast majority of these resources are not directly related to the information on the page, and I’m including advertising. Many of the scripts that were loaded are purely for surveillance purposes: self-hosted analytics, of which there are several examples; various third-party analytics firms like Salesforce, Chartbeat, and Optimizely; and social network sharing widgets. They churn through CPU cycles and cause my six-year-old computer to cry out in pain and fury. I’m not asking much of it; I have opened a text-based document on the web.

As a contrast, consider my blog post from yesterday. All requests for the page (1 for HTML, 3 for CSS files, and an image) total only 34 K. The page loads completely in 1/3 of a second.

This is how most web pages should be. Lightweight, fast. It’s how all Micro.blog-hosted sites are designed. If you’ve let your blog become too bloated with JavaScript includes or images, it’s worth some time to trim out extra resources that don’t really matter.

Last week I added a new archive page to Micro.blog-hosted sites. It includes dates and the first part of each post, marked up with Microformats. Jonathan LaCour used this to write a script that parses the HTML looking for posts on today’s date in previous years, then pulls the full content for each post it finds and assembles them together.

But it gets better. After Jonathan mentioned that it took quite a while to parse the large HTML file, I added a JSON Feed version of the archive page. If you’ve posted to Micro.blog since yesterday, this has been created for you at your-domain.com/archive/index.json. Jonathan updated the script to use the JSON Feed and it can now return the “on this day” posts very quickly, with no configuration needed because it’s all driven from a JavaScript include on your blog.

You can see this in action on my own blog’s on this day page. It works for any Micro.blog-hosted blog by pasting in a few lines of HTML from the Micro Memories project on GitHub.

This is the potential for indie blogging and simple formats. Adding a feature to Micro.blog-hosted blogs enabled a new tool I hadn’t even thought of. There was some discussion in the IndieWeb chat, but it took very little coordination because all of this is built with web stuff, not proprietary APIs.

Nir Zicherman has a post on Medium about how podcast hosting should be free. Nir is the co-founder of Anchor, a company with $14 million in venture-capital funding. Nir writes:

Back in the day, you would have had to pay to store your photos online. But that outdated business model has virtually disappeared thanks to platforms like Google Photos, Instagram, Imgur, and others. At Anchor, we believe the notion of charging creators to host their content online is antiquated and unfair. And above all else, it serves as a barrier that prevents the podcasting ecosystem from growing and becoming more diverse, because it limits it to only those voices who can afford to pay.

I think Nir misses something important in his post. Many podcasts do not need to be directly monetized with ads, network memberships, or even listener donations. I never want ads on my short-form podcast Timetable, for example. I record Timetable because I enjoy it and because it helps people understand what we’re trying to do with Micro.blog, which in turn indirect benefits the platform. I want my own podcast at my own domain name so that I’m not dependent on a company that may or may not be around in a few years.

(Also, it’s misleading to say that it only costs Anchor $1/year to host a podcast. That might cover hosting, but it skips over all the other business costs including engineering, marketing, and support.)

Anchor seems to be going for the YouTube model. They want a huge number of people to use their platform. But the concentration of so much media in one place is one of the problems with today’s web. Massive social networks like Facebook, Instagram, and YouTube have too much power over writers, photographers, and video creators. We do not want that for podcasts.

Micro.blog podcast hosting isn’t free. It’s $10/month. But for that price you get not just a podcast feed but also a full hosted blog with support for microblog posts or longer essays, photo blogging, custom themes and CSS, posting from a bunch of third-party apps and our iOS microcasting app Wavelength, and most importantly everything at your own domain name so you own the content. The competition for Micro.blog isn’t Anchor; it’s Squarespace and WordPress.

Some things are worth paying for. I share Nir’s goal that podcasting should be more accessible and more affordable to more people, but it’s dangerous to give one company too much control over podcasting. Anchor’s business model demands scale. It’s still unclear how that will play out.

Last week I parked myself at a coffee shop one morning and re-architected how blog publishing in Micro.blog works. As some of you know, hosted blogs on Micro.blog are based on Jekyll. While this has some advantages that I wrote about in 2016, it brings some performance drawbacks as well. I’ve incrementally improved it with tweaks over the last year, but last week I finally blocked out enough time to solve more of the performance trade-offs with using Jekyll.

When you post to Micro.blog now, it will publish your new blog post on the web right away. It will also update the JSON Feed and bring the new post into the timeline. Then in the background, it will update the site index and other related pages.

This should have a dramatic impact to posting and seeing the new post show up in the Micro.blog timeline, especially for blogs with thousands of posts. Moving my own site (and it’s 2700+ blog posts) from WordPress to Micro.blog has been a great way to test these changes.

One reason that IndieWeb Summit was such a success was the range of projects to come out of the second day as attendees worked on their own projects. There were new tools and features of existing platforms, but also personal site updates and just fun stuff. And web rings are fun!

I know, I know… Is it 2018 or 1998? I’ve added a help page on Micro.blog for how to add a web ring to your blog using 🕸️💍. One of the great things about microblogging at your own domain name is you can experiment with features like this.

Daniel and I talk a little more about this on the new episode of Core Intuition out today. Enjoy.

I don’t read Medium often, but I do let the service send me weekly emails with posts I might be interested in. For some reason, this week’s email included a Jason Calacanis post from April about funding a Facebook replacement:

LAUNCH is going to fund seven, purpose-driven teams that want to build a billion-user social network to replace Facebook.

This is the wrong idea. We do not need another social network with 1 billion users. Part of the problem is having so many users and so much power concentrated in one place. And setting out to achieve 1 billion users means it’s an ad-based platform that will inherently revisit many existing problems. (The rest of the goals in Jason’s post I can get behind, though.)

Micro.blog will never be that big. What we need instead of another huge social network is a bunch of smaller platforms that are built on blogs and the open web.

At the beginning of the week I announced several new features in Micro.blog, including a change to show who someone is following on the web version of Micro.blog. While working on this feature, I inadvertently changed the behavior to remove you (while browsing a user’s profile) from the list of who someone was following. If you looked at a user’s profile, you were never in their following list even if they did follow you.

While this was a bug, there was a long thread on Micro.blog with some good arguments for why this change was actually a feature. We shouldn’t have to worry about checking whether someone follows us. After all, an important part of Micro.blog is to never show follower counts, and to never let a feature grow into a popularity contest and source of judgement. The content someone posts should speak for itself.

This created a lot of confusion, though, because it didn’t work like anyone expected. I think even the people who liked it could tell something needed to change.

I was out of town this week and away from my computer most of the day. This left me some time to try to see both sides of this feature, and I kept coming back to this: the whole point of showing who someone is following is to discover new users. It’s not about how many people they are following. It’s not about whether they are following you.

(As an aside, with a platform based entirely on blogs, no one should read too much into followers anyway, because it doesn’t count all the people who might read your blog in an RSS reader or find it from a Google search.)

I’ve now tried to reduce this feature to its simplest form that solves the problem of finding new users. So in the latest version of Micro.blog on the web and native macOS app, I’ve reverted the change from earlier this week and replaced it with a list of who someone is following that you aren’t following already. We’ll be updating the iOS app as well and submitting it to Apple.

From an API standpoint, the previous behavior is still available. Third-party apps can make the best choice for the user experience they’d like to see, although if people like this change I’d encourage third-party apps to also adopt it.

Thanks to everyone who offered feedback on Micro.blog or in email. It means a lot to us that y’all care that we get this stuff right.

I rolled out several new features to Micro.blog today:

• LinkedIn cross-posting. I don’t use LinkedIn very often, but I kept hearing this request enough that it slowly bubbled up to the top of the priority queue as I was making improvements to cross-posting. Micro.blog can now send any new post to LinkedIn automatically.
• Show following users on the web. For a long time you’ve been able to see who someone is following in the native apps, but not on the web version of Micro.blog. Now the web version more closely matches the experience on iOS and macOS. This is a nice way to discover new users to follow. (We still never show followers or follower counts.)
• Better hosted page redirects. Blogs hosted on Micro.blog can have pages in the navigation for things like contact information, a resume, current projects, books you love, etc. If you want to link to an external site, you can just paste the URL into the contents of the page. These redirects work better now without briefly loading the blog layout.
• Indiepaper for saving articles to read later. This is an experimental feature inspired by some ongoing work in the IndieWeb community. There’s a help page if you’re interested in learning more. I’ll have some more thoughts later on how this might evolve.
• Pass-through legacy URL redirects. The last missing piece to migrate my main blog with 16 years of posts to Micro.blog hosting. Because I had accumulated so many random files on manton.org that I didn’t want to migrate, this feature allows me to have Micro.blog host all posts and photos, but if Micro.blog sees a URL it doesn’t recognize it can forward that to a different URL on the old server. (I’ll be enabling this manually for people who need it for now.)

It’s really nice to finally have manton.org hosted on Micro.blog. I’ve learned a lot going through this that I can use to help others migrating away from Wordpress.

I also cleaned up the text on a few pages and made other small bug fixes. Thanks for using Micro.blog! Your support means we can keep making it better.

Tonight I imported all my WordPress posts from manton.org and moved them into Micro.blog hosting. I learned a lot keeping my blog on WordPress even after launching Micro.blog, but as Micro.blog-hosted blogs improved, it just made sense for me to migrate my 2700 posts over to the new platform.

Micro.blog automatically redirects old URLs it finds in the WordPress import, but I’m still sorting out other changes that might be necessary after blogging for 16 years. (I started on Radio Userland, then Movable Type, and then WordPress.) The best thing about this move is that I’ll be able to better understand the needs of users who are also maintaining large sites on Micro.blog.

When I was on WordPress, I had 2 separate RSS feeds: one for short posts, one for long essay-like posts. Micro.blog doesn’t have separate feeds like that, so you’ll likely notice this change in your RSS reader right away. New posts will appear and older posts will likely be marked as unread. Those blips should be temporary and then everything will be back to normal.

I love how fast my site is now. Micro.blog-hosted sites are mostly static and much faster to load in your browser than my old WordPress site.

Great article by Felix Salmon on Wired last month about Twitter, found via Buzz Andersen’s blog:

Twitter is becoming increasingly concentrated on a tiny core of power users. It’s less and less a distributed mode of many-to-many communication, and more and more a broadcasting hub for the elite—a highly unequal place where their least-considered, Ambien-addled opinions get amplified to a global audience of millions.

When Micro.blog launched, not showing follower counts at all seemed like a big risk. Now I think it’s recognized as a great feature. If we want an inclusive, welcoming community, the UI should encourage that by presenting everyone as equals.

Iconfactory has had to make some difficult choices for the latest update to Twitterrific. From the release history:

In the coming months, Twitter plans to discontinue the underlying services that we need to provide both push notifications and live streaming. As a result, we did not feel it was right to keep selling the push notification in-app purchase since we will soon be forced to shut it down. To that end, we've consolidated our in-app purchases to a single "Enhanced" option which eliminates ads and unlocks Google Translate.

More from their blog post:

We sincerely wish Twitter would have offered third party developers a better way forward for our customers. Apps like Twitterrific helped build Twitter’s brand and expand its user base. We even contributed to its lexicon and feature sets (Tweet tweet!) Twitter’s priorities over the last several years, however, have shifted away from end users and toward brands and big companies. We have no choice but to adapt as best we can.

I post tweet-like short posts to my own blog first and then let Micro.blog send a copy to Twitter, so I don’t use Twitter very often except to check replies a few times a day. Looks like Iconfactory is making this as smooth a transition as possible for existing customers. If you were wondering if Twitter’s API changes were ever really going to affect Twitter users, this release of Twitterrific is your answer.

Earlier this week I wrote about making Micro.blog an IndieAuth provider. This allows anyone with a Micro.blog-hosted blog to sign in to IndieWeb-compatible apps. For example, using OwnYourGram to automatically copy Instagram photos to your own blog on Micro.blog.

I’ve now expanded this support to let anyone use Micro.blog to authorize an app even if your blog is hosted outside of Micro.blog. If you host somewhere else, you’ll still be responsible for setting up posting, but having basic IndieAuth support can be useful if you want to connect your blog to tools that don’t need to post, like IndieWeb Ring or the IndieWeb.org wiki.

There are instructions on this Micro.blog help page for adding the appropriate HTML tags to your site.

In my talk at Peers Conference earlier this year I closed with this quote from Brent Simmons:

Micro.blog is not an alternative silo: instead, it’s what you build when you believe that the web itself is the great social network.

I’ve been thinking more about Brent’s post since then, and so for the keynote that Jean and I gave at IndieWeb Summit last week I wanted to start with that quote. Many people have written nice testimonials about Micro.blog, but this one really seems to capture the goal.

It should come as no surprise that I liked Brent’s full post from February about why Micro.blog isn’t like App.net. He made the case even better than I usually do, about how the web is more important than any one platform:

But if you think of the years 1995-2005, you remember when the web was our social network: blogs, comments on blogs, feed readers, and services such as Flickr, Technorati, and BlogBridge to glue things together. Those were great years — but then a few tragedies happened: Google Reader came out, and then, almost worse, it went away. Worse still was the rise of Twitter and Facebook, when we decided it would be okay to give up ownership and let just a couple companies own our communication.

Micro.blog is one of the first platforms to focus on domain names that decouple the timeline from post storage. Anyone can post a Micro.blog-hosted site at their own domain name today and move it all somewhere else tomorrow. It’s a simple, IndieWeb-friendly architecture that we think is essential to the next phase of the web.

I’ve added 2 new features to Micro.blog-hosted blogs:

• There's a new "Footer" button under Posts → "Edit Domain & Design" to enter any custom HTML or JavaScript on your microblog's theme. This is inserted before the </body> tag.
• The pages added under Posts → Pages can now redirect to an external web page. Just enter a full URL beginning with "http" as the contents of the page and Micro.blog will instead send the user to that URL. (Expect some improvements to this in the future.)

Thanks for your support. The $5/month for blog hosting might not seem like much, but it makes a big difference as we grow the Micro.blog platform and add new hosted blog features.

After posting about my time at IndieWeb Summit and the new IndieBookClub support, let me give some more details on what IndieAuth means for Micro.blog. I spent the second day of IndieWeb Summit working on this, and it has now been rolled out to all Micro.blog users. (If you haven’t posted in the last few days, after your next post your microblog will be updated with the new authorization endpoints.)

IndieAuth lets you sign in to other apps using your own domain name. If Micro.blog is hosting a blog for you, you can use that custom domain or your subdomain like yourname.micro.blog to sign in.

While this was possible before with extra configuration to delegate auth to another service, Micro.blog can now be an IndieAuth provider on its own. It’s much easier for IndieWeb apps to work with Micro.blog.

Here are some apps that work great with Micro.blog:

• Quill: web-based interface for posting to your microblog.
• OwnYourGram: automatically post your Instagram photos to your microblog.
• OwnYourSwarm: automatically post your Swarm check-ins to your microblog.
• IndieBookClub: post what books you're reading or want to read.
• Omnibear: Chrome or Firefox extension for quick posting.
• IndieWeb Ring: wait… what?

I’m really happy with the progress over the last week because it makes Micro.blog-hosted sites more useful. As I mentioned in my IndieWeb Summit keynote, the business model for Micro.blog is aligned with what users need. If you pay for Micro.blog hosting, we’ll keep making it better without worrying about ads or other user-hostile distractions.

As I mentioned in my IndieWeb Summit wrap-up, I added support for IndieBookClub while in Portland. IndieBookClub is a little like Goodreads, but built on standards like Microformats and Micropub so that you can post what you’re reading to your own blog.

Now that I’m back in Austin, I’ve tweaked the behavior to be smarter about recognizing the ISBN that IndieBookClub sends to Micro.blog. Posts from IndieBookClub also get the 📚 emoji added automatically so that they show up in the books Discover section on Micro.blog. Here’s a screenshot of what posts look like on your Micro.blog-hosted site:

If the ISBN is specified, Micro.blog will redirect the link to Amazon, although we may change that in the future. And it’s just a regular blog post, so you can always edit it using Markdown in Micro.blog.

Last week I was in Portland for IndieWeb Summit. This was only my second IndieWeb conference (the first was IndieWebCamp in Austin). I had a great time in Portland and got even more than I expected out of IndieWeb Summit.

The first day was short keynotes and sessions led by attendees on a range of topics. Jean and I talked about our experience and goals with Micro.blog in reaching even more mainstream users. I went to sessions on Microformats, timeline algorithms, code libraries for common IndieWeb building blocks, and Microsub. Some of this carried over to the beginning of the next day, including Aaron Parecki leading a discussion about IndieAuth.

We held a Micro.blog meetup at Von Ebert Brewing after the first day wrapped up. Thanks everyone for joining us!

Most of the second day was a hack day to work on our own projects, and at the end of the day everyone could present what they had worked on. I was so impressed with what people had come up with, whether that was improvements to their own site or prototypes for new tools.

It turned out that having this dedicated time was exactly what I needed to turn Micro.blog into an IndieAuth provider. This means that Micro.blog no longer needs to delegate to Twitter or GitHub for authorization when someone is using an IndieWeb posting tool like OwnYourGram or Quill. Users can instead authorize directly with their Micro.blog account. I also added support for the summary fallback parameter in Micropub, which makes Micro.blog compatible with IndieBookClub.

In the morning before I left Portland, I interviewed Tantek and Aaron for my upcoming book Indie Microblogging. We had a great conversation on the founding of IndieWebCamp, the accomplishments and changes in the community, and where everything is going from here.

Portland was great. For this trip I opted for an Airbnb close to the IndieWeb Summit venue. It was also just a block from Coava Coffee, where I spent a couple mornings catching up on work. I hope to be back in Portland for IndieWeb Summit next year.

Great post by CJ Chilvers about blogging regularly, via Micro.blog user @kaa, with a quote from Seth Godin’s podcast. Seth says to blog every day…

…because of the discipline it gives you, to know that you’re going to write something tomorrow. Something that might not be read by many people—it doesn’t matter—it will be read by you. If you can build that up, you will begin to think more clearly. You will make predictions. You will make assertions. You will make connections.

CJ adds:

Nothing has been healthier for my idea generation than to throw out ideas. Once they’re in the public, they feel completely gone. I’m free to come up with new and better ideas. And I do.

For more people to blog more often, blogging has to be easier. That is a key premise of Micro.blog — why blogging UIs should take inspiration from Twitter and Instagram, and why we have little incentives like unlocking the 30-day pin on Micro.blog for blogging every day.

We just posted our pre-WWDC podcast episode:

Manton and Daniel check in just before WWDC to talk about expectations from the conference, and strategies for saving money on the trip. They indulge in a bit more Siri criticism, hope that Apple will announce new MacBook Pros, and question whether Apple will dare to poke fun at Google’s Duplex technology during the keynote.

If you’ll be in San Jose, hope to see you at the Micro.blog lunch meetup on Tuesday. I’d love to talk to listeners about Micro.blog or Core Intuition, and we have a major update to Sunlit in beta that I’ll be showing off.

The writing has been on the wall for years. Now that Twitter plans to move ahead with deprecating APIs that apps like Twitterrific and Tweetbot use, it’s even more clear that there’s no overlap between Twitter’s priorities for the API and what traditional clients need.

When I wrote about Icro, the first third-party app for Micro.blog, I said that I always want to encourage other developers building for Micro.blog. It’s worth exploring how these Twitter API changes compare to Micro.blog and how we can improve.

The streaming API is a big part of this. Twitter apps currently use the streaming API to deliver tweets in real-time without polling, or to notice when someone is @-mentioned so that a push notification can be delivered. Losing this API is especially frustrating because it means developers need to rewrite a bunch of code only to make their apps a little worse instead of better.

Micro.blog doesn’t actually have a streaming API yet. Micro.blog supports multiple APIs, but no persistent connection. The new app Icro doesn’t have push notifications, although the official Micro.blog app does. For a brand new app like Icro, it would be a lot for the developer to also run a server just to do push notifications.

As I think about how we solve this, I remember a discussion in the Twitter developer community when the iPhone first got push notifications. It was an open question: should Twitter third-party developers run their own servers for push notifications, or should Twitter itself deliver push notifications on behalf of third-party apps? Obviously third-party developers have had to run their own servers.

I think a goal for us with Micro.blog should be that third-party developers get access to the same basic tools that we use to build our own apps. Rate-limits should be the same for an app like Icro as they are for the official Micro.blog app, for example.

With that in mind, I’ve mentioned before that I’d like to offer a push notification service for developers. iOS and Android developers could upload their push notification credentials from Apple and Google. Micro.blog would store them and deliver push notifications directly to third-party apps.

This has a few pretty big advantages:

• Third-party developers won't need to run their own servers. This levels the playing field so that any Micro.blog app, no matter how small, can offer basic features like notifications.
• Push notifications are more capable now than at their introduction in 2009. They can be used not just for an alert message but for silently sending data to an app in the background, such as when new posts have been added to someone's timeline.
• It's more efficient. Instead of keeping persistent connections open to Micro.blog servers, Apple and Google handle the persistent connections between devices and the cloud. Micro.blog can simply forward @-mentions to the clients that have requested them via Apple and Google infrastructure.

This is a little bit of extra work for Micro.blog, but Micro.blog is already doing similar processing when a reply comes through. For every reply to a blog post, Micro.blog checks if there is a Webmention endpoint so that it can forward that reply to an external site, such as one hosted on WordPress. Opening up push notifications feels like a natural extension to that.

Some developers might not be comfortable outsourcing this to Micro.blog. That’s fine. In particular I’d like to hear any concerns over security or features where this approach would be too limited. (To be clear, we’d offer this for free. Our business is blog hosting.)

Back to the Twitter news. John Gruber summed it up this way:

Twitter isn’t explicitly saying that they’re shutting down third-party clients, but I don’t know that it’s feasible for them to exist if they don’t have access to these APIs. It’s like breaking up with someone by being a jerk to them rather than telling them you’re breaking up.

That’s a great analogy. Micro.blog is barely a year old, so there is plenty still to do, and there are parts of the API that aren’t as mature yet as they will be. But I think we’re transparent about what we’re trying to do and how we can support developers. We’re not going to be jerks about it.

I’m really excited by what I’m seeing from the community. Icro is in the App Store. Slate is another iPhone app currently in beta. Dialog for Android is in the Google Play Store as a public beta. And then there are all the apps following IndieWeb standards that are compatible with Micro.blog.

WWDC is only a couple weeks away. We’ll have a Micro.blog meetup on Tuesday (June 5th) at lunch. I’d love to talk to developers at the meetup or anytime that week in San Jose to get feedback on how we should handle streaming and notifications.

I’ll have more to say tomorrow specifically about the technical side of Twitter’s streaming API, but for now I want to highlight where this all started. In August 2012, Twitter posted to their blog about upcoming changes to their API. This was the post with the infamous 4-quadrant chart showing which third-party apps Twitter wanted to encourage, and which apps (in the upper-right quadrant) they didn’t want third-party developers to work on anymore.

From the post:

In the upper right-hand quadrant are services that enable users to interact with Tweets, like the Tweet curation service Storify or the Tweet discovery site Favstar.fm.

Although it wasn’t clear in the blog post, Twitter later clarified that Storify and Favstar were fine. Nevertheless, Storify announced last year that the service would be shutting down… tomorrow, actually. Favstar is shutting down next month.

The post from Twitter continues:

That upper-right quadrant also includes, of course, “traditional” Twitter clients like Tweetbot and Echofon. Nearly eighteen months ago, we gave developers guidance that they should not build client apps that mimic or reproduce the mainstream Twitter consumer client experience.” And to reiterate what I wrote in my last post, that guidance continues to apply today.

It has taken nearly 6 years, but it feels like today’s API changes finally wrap up the work that started in 2012. The apps that are possible with the new Account Activity API are exactly the apps that were encouraged in those other quadrants. The pricing makes no sense because it wasn’t designed for traditional Twitter apps like Twitterrific and Tweetbot.

Two months after that post from Twitter, I quit the platform and stopped posting to @manton in protest. I only wish I had started working on Micro.blog immediately in 2012.

I’ll be attending IndieWeb Summit next month. If you’re interested in indie blogging or what we’re doing with Micro.blog, consider joining us for the 2-day conference in Portland. I like how gRegor Morrill highlighted that the group should be more than just programmers:

You don’t need to be a programmer! In fact, I would love to see more non-programmers attending. We need writers, graphic artists, designers, UX engineers, and anybody that wants to reclaim some of their online presence with a personal website.

There’s a lot of overlap between the Micro.blog and IndieWeb communities. As we’re now in Micro.blog’s 2nd year, I expect the platform to become more mature, and I’ll be wrapping up a few loose ends with IndieWeb technologies. IndieWeb Summit will be a great time to reflect on what we’ve been able to do and look to what’s next.

People often write about Micro.blog, but I don’t usually do a good job of pointing to all the reviews. A new blog post this week from Lance Somoza stood out to me:

It reminds me of the earlier days of the Internet, where everything was more whimsical and less threatening than the current status quo. When it comes to free services, we have sadly come to expect a gimmick, trade-off, or worse in exchange for our data. Micro.blog’s opposition to this idea, simply makes it a joy to use.

Thanks everyone for taking a chance on the platform. I’m really happy with how the platform has grown, from new photo blogs and microcasts to third-party apps like Icro. We don’t have ads and we don’t have venture capital funding. The support from the community drives everything.

Last month I gave a talk about microblogging at Peers Conference in Austin. In it I covered Twitter’s changing attitude toward developers, from the early days when everyone wanted to build a Twitter app — as John Gruber wrote in 2009, Twitter apps were a playground for new UIs — to when Twitter started actively discouraging traditional third-party Twitter clients.

For Micro.blog, I always want to encourage third-party apps. We support existing blogging apps like MarsEdit, and we have an API for more Micro.blog-focused apps to be built. I’m excited to say that a big one just shipped in the App Store: Icro.

Icro is well-designed, fast, and takes a different approach to some features compared to the official Micro.blog app. In a few ways, it’s better than the app I built. This is exactly what I hoped for. We wanted an official app so that there’s a default to get started, but there should be other great options for Micro.blog users to choose from.

Here are a few screenshots from Icro:

Thanks to developer Martin Hartl for building Icro and being part of the Micro.blog community. You can download it for free from the App Store here.

I’ve never sent an email to all Micro.blog users until today. As indie developers, sometimes I think we worry so much about accidentally spamming a customer that we err too much on the side of sending essentially no email. As we’re at about the 1-year mark for Micro.blog, it seemed like a good opportunity to send an update. Here’s the text of the email that went out.

A little over a year ago we started rolling out Micro.blog to Kickstarter backers. So much has happened since then — from new Micro.blog platform features to companion apps like Sunlit and Wavelength — that I wanted to highlight a few milestones.

First, thank you for your support. We wouldn’t be able to continue to improve Micro.blog without the feedback from the community. Special thanks to everyone who has supported Micro.blog directly with a paid plan for a hosted microblog.

If you haven’t checked out Micro.blog lately, here are some things that happened just in the last few months:

• We launched a microcast called Micro Monday to feature members of the community. Each week, a different Micro.blog user joins Jean MacDonald for a quick interview about how they blog and what they like about Micro.blog.
• To make it easier for anyone to create a short podcast, Wavelength lets you record, edit, and publish a microcast from your iPhone. You can also upload MP3s from the web and serve a podcast at your own domain name.
• Sunlit is our iOS app for posting photos and discovering photos and new Micro.blog users to follow. It's a free app with more control over publishing stories with photos, text, and different filters.
• There's a new theme for hosted microblogs called Marfa. We use this theme on Micro Monday.
• Medium was added as a cross-posting option. Post to your own blog and Micro.blog will automatically send a copy to Medium.
• Expanded the Discover section on the web and in the native apps to highlight photos, podcasts, and more. It's a great place to see what people are posting about or find new people to follow.

You can always add a new hosted microblog or upgrade a trial by clicking “Plans” from Micro.blog on the web.

Any questions or feedback? Don’t hesitate to let us know: help@micro.blog.

— Manton

We shipped version 1.3.4 of the Micro.blog iOS app. It includes a bunch of photo-related improvements and bug fixes, including better support for non-square photos.

We’re on a bit of a roll with Micro.blog, shipping microcast hosting, our brand new app Wavelength, a new blog theme, and this iOS update all in the last week. Great time to join or come back to the platform.

We just wrapped up a bunch of improvements to the initial Wavelength for Micro.blog app. Here are the changes:

• Updated MP3s to 128 kbps, mono. We'll consider adding a preference for quality and stereo in the future.
• Fixed playback volume using correct iPhone speaker.
• Fixed a few potential crashes and improved publishing error messages.
• Fixed Auphonic username field to not use auto-correct.
• Fixed glitches with consistently using external microphones.
• Fixed error sometimes when splitting segments.

I recorded and edited the last 2 episodes of Timetable exclusively with Wavelength on my iPhone X. It’s really great to see some new microcasts pop up over the last few days. Thanks for trying it out!

We have something really big to announce today. Micro.blog now supports hosting short-form podcasts, also known as microcasts, with a companion iPhone app called Wavelength for recording, editing, and publishing episodes.

Before the Kickstarter campaign last year, I started my Timetable microcast to talk about the things I was working on, with a focus on planning what would become Micro.blog. Creating a short podcast is really fun. It’s much easier to record and edit than the longer podcasts we’re all used to. But it’s still not easy enough, and even after nearly 100 episodes of Timetable my workflow was cobbled together with too many apps: Ferrite, Logic, Auphonic, WordPress, a shell script, and sometimes Transmit.

Micro.blog is about making short-form content you own as simple to post as a tweet because we believe blogging should be easier. Podcasting should be easier too.

We’re rolling out a new hosted plan on Micro.blog to accommodate microcasts. When you upload an audio file to your site — either from the web, Wavelength, or a third-party app — Micro.blog will automatically create a podcast feed for your microblog. Listeners can subscribe directly, or you can add the feed to the Apple Podcast Directory and it will show up in popular apps like Overcast and Castro. Everything can be served from your own domain name, just like a normal microblog. We’ve been using this infrastructure for all the episodes of our weekly Micro Monday microcast.

New hosted microblogs with microcasting support will be $10/month. Microcast audio files will be limited to 20 MB. Existing microblogs hosted on Micro.blog can be upgraded to support microcasting for an additional $5/month.

Everyone has a story to tell. Whether that’s through short microblog posts, longer essays, photo blogs, conversations with friends, or now through podcasts, I hope that the Micro.blog platform and suite of apps can help. If you haven’t checked out Micro.blog lately or are learning about it for the first time, now is a great time to join the community. Thanks!

I posted a link to this last week, but it’s worth some additional comments. Apps of a Feather is a new site to spread awareness about upcoming Twitter API changes:

We are incredibly eager to update our apps. However, despite many requests for clarification and guidance, Twitter has not provided a way for us to recreate the lost functionality. We've been waiting for more than a year.

I have a long history with Twitter. I was user #897. I built multiple apps for the platform. I invested so much of my time and code into the Twitter ecosystem.

Then Twitter leadership showed us the future, and it was clear that third-party developers had little or no place in it. It was just a matter of time. And now, maybe time has run out.

If you still love Twitter, absolutely tell them to reverse course and rebuild their relationship with third-party developers. These are great apps and great developers, and I don’t want to see their business cut down because of a developer-hostile platform outside their control.

Meanwhile, we’re working to make Micro.blog better every day. It’s the most ambitious thing I’ve ever worked on. Building for the open web needs to be done in parallel to hoping the other social networks improve, whether you’re still waiting for those sites to do the right thing, or already know it’s time to move on. I only wish we had started sooner.

We just posted Core Intuition 322. From the show notes:

Manton and Daniel react to Apple’s news release about expectations for the Mac Pro coming in 2019. They speculate about what could explain such a long delay, and Daniel devises a theory, or pipe dream, that the Mac Pro may be ARM-based. They also discuss Apple’s disclosure of a Pro Workflow Team comprised of creative professionals, and compare it to Apple’s apparent study of the needs of education professionals. Finally, an update from Daniel about MacBook Pro keyboard repairs, with a surprise twist!

Stephen Hackett also commented today on Matthew Panzarino’s visit to Apple Park to get a status update on the Mac Pro:

There’s also the increased rumors around ARM-powered Macs. Like with the Intel transition, Apple’s pro products will surely be the last to make this move. It may be that 2019-ish Mac Pro will be the Intel Mac’s swan song.

I think Stephen is right, but on Core Intuition today we explored the opposite: what if the 2019 Mac Pro is the first ARM-powered Mac? What it was like to be at WWDC when Apple announced the Intel transition, the value of third-party pro apps, and much more on this episode. Enjoy!

We start this week’s Core Intuition talking about the Apple education event in Chicago. More in the show notes:

Daniel and Manton talk about Apple’s Chicago education event, and Apple’s challenge in breaking into the education market so dominated by Google. They scrutinize whether the special event was “event-worthy” or not. Daniel talks about his motivation problems with shipping MarsEdit updates, and complains again about App Store Review uncertainty. Finally, they talk about the challenge of knowing whether a product with lackluster success is on the brink of something great, or should be moved on from.

Thanks for listening and subscribing to the show.

We released an update to Micro.blog for Mac today with support for multiple accounts. I created a quick screencast video to show off what it looks like:

There’s also a new help page with some more information about why you might want separate accounts or blogs.

Naturally because of the goals of Micro.blog, I see a lot of discussion about “owning your content”. It’s an important part of the mission for Micro.blog to take control back from closed, ad-supported social networks and instead embrace posting on our own blogs again.

But what does it mean to own our content? Do we have to install WordPress or some home-grown blogging system for it to be considered true content ownership, where we have the source code and direct SFTP access to the server? No. If that’s our definition, then content ownership will be permanently reserved for programmers and technical folks who have hours to spend on server configuration.

IndieWebCamp has a generations chart to illustrate the path from early adopters to mainstream users. Eli Mellen highlighted it in a recent post about the need to bridge the gap between the technical aspects of IndieWeb tools and more approachable platforms. With Micro.blog specifically, the goal is “generation 4”, and I think we’re on track to get there.

I want blogging to be as easy as tweeting. Anything short of that isn’t good enough for Micro.blog. You’ll notice when you use Twitter that they never ask you to SFTP into twitter.com to configure your account. They don’t ask you to install anything.

More powerful software that you can endlessly customize will always have its place. It’s good to have a range of options, including open source to tinker with. That’s often where some of the best ideas start. But too often I see people get lost in the weeds of plugins and themes, lured in by the myth that you have to self-host with WordPress to be part of the IndieWeb.

Owning your content isn’t about portable software. It’s about portable URLs and data. It’s about domain names.

When you write and post photos at your own domain name, your content can outlive any one blogging platform. This month marked the 16th anniversary of blogging at manton.org, and in that time I’ve switched blogging platforms and hosting providers a few times. The posts and URLs can all be preserved through those changes because it’s my own domain name.

I was disappointed when Medium announced they were discontinuing support for custom domain names. I’m linking to the Internet Archive copy because Medium’s help page about this is no longer available. If “no custom domains” is still their policy, it’s a setback for the open web, and dooms Medium to the same dead-end as twitter.com/username URLs.

If you can’t use your own domain name, you can’t own it. Your content will be forever stuck at those silo URLs, beholden to the whims of the algorithmic timeline and shifting priorities of the executive team.

For hosted blogs on Micro.blog, we encourage everyone to map a custom domain to their content, and we throw in free SSL and preserve redirects for old posts on imported WordPress content. There’s more we can do.

I’m working on the next version of the macOS app for Micro.blog now, which features multiple accounts and even multiple blogs under the same account. Here’s a screenshot of the settings screen:

The goal with Micro.blog is not to be a stop-gap hosting provider, with truly “serious” users eventually moving on to something else (although we make that easy). We want Micro.blog hosting to be the best platform for owning your content and participating in the Micro.blog and IndieWeb communities.

David Smith has shared the stats he’s been collecting on Apple Watch usage from his apps, hoping that Apple will drop support for the original Apple Watch (Series 0) sooner rather than later:

So far the data is looking promising that this dream of mine might actually be possible. The Series 3 is being adopted incredibly quickly and just last week became the most popular Apple Watch overall amongst my users with 33% of the overall user-base. The Series 0 is steadily falling, currently at around 24%.

Federico Viticci adds this in his link from MacStories:

I've been wondering about when Apple could drop support for the original Apple Watch in new versions of watchOS. For context, the original iPhone, launched in 2007, couldn't be updated to iOS 4 in 2010, three years later. The Apple Watch will have its official third anniversary next month.

The big difference between the Apple Watch and the original iPhone or iPad is that many people (perhaps most) do not run third-party apps on the watch. Those people are not even counted in David Smith’s numbers. Unlike the iPhone and iPad, which are significantly improved with new apps, the Apple Watch is pretty good with only the built-in Apple features.

After a few years, I still wear my Series 0 every day. Here’s what I use it for:

• Telling time. Also glancing at the upcoming event.
• Notifications from Slack and Micro.blog.
• Fitness. I don't launch the Workout app. I just let the watch notice when I'm exercising.

For these tasks, performance and API support just don’t matter as much. The way I use my Apple Watch is the equivalent of someone who only tells a HomePod to play Apple Music and asks no other questions. A little sad, but it works fine and I expect to keep the Series 0 for another year or so before upgrading.

I feel for developers who want the Apple Watch to be a much more mature platform. I want that too. But I don’t think it’s as simple as copying what has worked for native apps on Apple’s other platforms.

The future of the Apple Watch isn’t just better widgets; it’s voice. Both WatchKit and Siri need a major shakeup. Apple should make Siri more consistent across Apple Watch, iPhone, and HomePod, with a more flexible server-based API like Alexa. If they can do that while also rethinking WatchKit at the same time, even better.

The latest Core Intuition is out. Daniel and I talk about WWDC and related topics for the full episode:

Daniel and Manton talk about Apple’s announcement that WWDC is officially happening in San Jose again. Daniel struggles to make a financial case for attending, while Manton continues to believe it’s essential to at least be in town for a few days. They talk about the possibility that other conferences would be a better use of time and money. Finally, they indulge a little speculation about WWDC and whether the promo art ever hints at any of the actual news to be announced.

Thanks for subscribing! Looking forward to seeing some Core Intuition listeners out in San Jose.

We’ve started a new podcast! Jean MacDonald will be hosting a weekly show talking with members of the Micro.blog community. I join her on the first episode to talk about our blogs and goals for the podcast.

You can listen to Micro Monday on the web, subscribe in Overcast, or follow @monday on Micro.blog. Thanks for listening! Update: Check out our subscribe page for more links.

We released an update to Sunlit today. Lots of little bug fixes and improvements. (The App Store has been slow this week, but it should show up in your Updates tab soon if it’s not already there.)

I also updated the Micro.blog timeline to add tiny photo thumbnails for Sunlit stories that have a title. Here’s a screenshot:

Because Micro.blog is focused on microblogging, short posts without a title still show directly in the timeline, but longer posts with many photos and a title just link back to your web site. Adding this little preview gives a hint for what is behind those links.

We just published this week’s episode of Core Intuition, talking about the new Sunlit release and other topics. From the show notes:

Manton and Daniel celebrate Sunlit 2.0’s release, and talk about the decision to make it a free app that supports the Micro.blog platform. Daniel admires Manton’s proclivity for shipping new things, and they both despair the difficulty of canceling existing projects. Daniel rants modestly about the difficulty of getting his MacBook Pro keyboard repaired, and finally, they discuss the App Stores and the ongoing disparities between Mac and iOS versions of them.

Thanks for listening!

We rebuilt Sunlit for 2.0 so that it’s focused around blogs. You can collect photos together in stories and publish them directly to a Micro.blog-hosted site or compatible blogs such as WordPress. It’s a free download. (If you need a great place to host your photoblog, consider signing up for a paid microblog on Micro.blog.)

To show off Sunlit in the App Store, I created a few app preview videos. Here’s one of them:

Thanks for your support. Sunlit 2.0 is just the beginning for what we want to do with photos and microblogging. Hope you enjoy it.

Rewatched the original Blade Runner recently, and finally saw the sequel last night. As with all great films, still thinking about it the next day. The parts that were good, were really good.

There was a conversation on Micro.blog about the length. It would have been an even more powerful movie with a couple scenes cut short. Maybe it could have squeezed into a PG-13 rating too.

Nevertheless, it holds its own with the original. I say this as a compliment: a rare sequel that is no better or worse. Feels unique but consistent — in pacing, visuals, and music — as if 35 years haven’t passed since the first one. Loved it.

The new update to Micro.blog for iOS is now available in the App Store. As I wrote about yesterday, it includes an improved conversations gesture. Here’s the full list of changes:

• Added swipe left on a post to view the conversation.
• Added feed settings button when writing a new post for quickly toggling off cross-posting.
• Added confirmation alert when removing a post.
• Updated character counter to not include Markdown.
• Updated sharing from other apps to not use the current draft or save it.
• Fixed compatibility with some XML-RPC servers.
• Fixed opening conversations from links in the timeline.

Enjoy!

I just submitted a new update to the Micro.blog iOS app. It adds a couple new features, including better support for quickly toggling off cross-posting, but what I’m most excited about is swiping to view conversations. Here’s a 45-second screencast demo:

It should be out in a couple of days after Apple approves the release. Thanks for supporting Micro.blog.

A couple years ago on a trip, I finally tried Instagram Stories. Because I don’t like posting things that disappear, I planned to keep copies of all the short videos from my story, and then stitch them together in Final Cut, add some music, and publish them to my blog once a week. It didn’t take long to give up on this. Instagram and Snapchat make it easy to share on their network, but difficult everywhere else.

I much prefer Snapthread’s approach. Becky Hansmeyer has created an app that does exactly what I was trying to do, but instead of fumbling around with Instagram and Final Cut, it’s effortless. And it works with live photos. Highly recommend checking this out in the App Store.

DHH writes about how Basecamp is experimenting with removing their “applause” feature — the clap icon that Medium has also recently adopted:

But as I read through the replies from the few dozen people who answered the question on any given day, I was faced with the dilemma of the clap. If I applauded an update from Sam yesterday, but don’t today, does that mean I’m expressing discontent with the most recent work? If I don’t applaud for Javan on the same day as I applaud for Sam, does that mean I’m parting favor of one over the other?

The problem with these “just click a button instead of sending an actual reply” features is that they fool us into thinking we’ve done something meaningful by clicking. Anyone can click a Twitter heart button to show that they’ve noticed a tweet or enjoyed it. It takes very little effort and doesn’t mean much.

On Micro.blog, favorites are private. They are just for your own use, like bookmarks. We’ve found that the lack of public likes encourages people to reply to posts instead, even if it’s just a quick “Thanks!” or “That’s great!” or other comment. It’s a little more meaningful because it requires a bit of effort.

In an interview with Piers Morgan, Trump said something revealing when pressed on his retweets of a racist group:

Well, I know nothing about them. I did a retweet. You know, retweets... sometimes you do... retweets are very different. When you do your own tweeting, when you do your own social media, it's fine. When you do those retweets, sometimes they can cause problems.

What Trump is trying to say is that retweets aren’t as important as a tweet you type yourself. Retweets encourage a sort of thoughtless approach to sharing.

We don’t like retweet counts or follower counts in the UI of Micro.blog, because it’s another place for judgement — ”this person must not be very interesting if they have so few followers” — instead of letting someone’s content speak for itself. Likes, claps, and retweets aren’t a substitute for a real conversation. We’ll eventually have some form of public reactions on Micro.blog, but we aren’t in any hurry to get there.

Over the last couple of days we’ve shipped a few improvements to Micro.blog. There’s an update to the Mac version with some bug fixes and better support for showing the title field when you’re writing a longer blog post. The default themes have been updated too.

It’s also much easier to preview themes for your microblog. Under your account there’s now a “Preview Themes” button that lets you click through and test out the themes. Here’s a 10-second screencast recording to show how it works:

Yesterday we sent Sunlit 2.0 to beta testers. The feedback has been great so far. We just pushed a new version with several important fixes, especially to publishing existing stories.

It’s a little overwhelming to ship a brand new app in the middle of everything going on with Micro.blog — opening the platform to new users, trying to stay on top of bugs and feature requests, and planning for the future. But it just feels right that Sunlit should be part of the Micro.blog suite.

We love photos and we love blogs. Sunlit combines those things in a way that accommodates more advanced features than can fit in the main Micro.blog app.

Micro.blog makes it as easy to write a quick short post as it is to send a tweet. The timeline and simple posting interface are part of that. Sunlit supports microblog posts while taking a different approach in the UI, focused around stories and longer blog posts, whether they’re hosted on Micro.blog or elsewhere on the web. And we can do it without much fanfare on the Micro.blog server side because the technical scope of the platform already supports it.

Here’s a short screencast demo of the upcoming version of Sunlit. We’ve rebuilt it for blogging and Micro.blog. You can create stories with photos and text to publish to your blog, with editing and filters, plus a new Discover section for browsing photos.

If you’d like to try the TestFlight beta, email help@micro.blog. You don’t need a Micro.blog account to use it — it also supports publishing to WordPress — but we think it makes a great companion to Micro.blog. Enjoy!

We posted Core Intuition episode 313:

Daniel and Manton talk about digging oneself out of customer support debt, and strategies for improving the efficiency of support mechanisms. They react to Apple’s disabling of free In-App-Purchases, and speculate about whether it was intentional or not. This leads them into a re-evaluation about the risks of selling on the App Stores, and the lure of selling directly to customers.

And just for subscribers, Extra Intuition episode 4, with Daniel and I talking about cryptocurrency and my experience trying to cash out.

Colin Devroe interviewed me about Micro.blog:

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.

I’m happy with how the interview turned out. It’s one of the best summaries of what we’re trying to do with Micro.blog, all in one place. Hope you like it.

Responding to a post by Chris Adamson about iOS conferences, Marco Arment notes that podcasts and YouTube have partially replaced the need to sit in a room and listen to someone give a talk:

Podcasts are a vastly more time-efficient way for people to communicate ideas than writing conference talks, and people who prefer crafting their message as a produced piece or with multimedia can do the same thing (and more) on YouTube. Both are much easier and more versatile for people to consume than conference talks, and they can reach and benefit far more people.

It can’t be overstated how important it is to meet people face to face in our community. I forgot to mention this: I’ll be attending Peersconf in Austin this April. This’ll be a new conference experience for me and I’m looking forward to it.

I wrote a short guide on microblogging with WordPress over a year before Micro.blog was opened to Kickstarter backers. A few things have changed since then, so it’s time for an update.

There’s now a long introduction to WordPress and Micro.blog over at help.micro.blog. Parts of it are taken from my upcoming book, Indie Microblogging. I’m wrapping up the book for the first part of 2018 and will likely sell it online for anyone who missed the Kickstarter.

Two great feed readers added support for Micro.blog this week: Evergreen and Feedbin. Evergreen is still in beta but improving quickly. Feedbin is a mature, well-designed RSS reader and sync service.

Here’s Brent Simmons announcing the Micro.blog support in Evergreen:

This is hugely important. RSS readers exist not to just make reading easy but to make the web a conversation.

And Ben Ubois on the Feedbin blog writing about the new Feedbin sharing, including some thoughtful words for what we’re trying to do with Micro.blog:

Micro.blog is good for blogging, because it acts as sort of gateway-drug into that habit. Say you start off just using it for Twitter-like microposts, but then you realize you have more you want to say. Micro.blog detects the length of your post and prompts you to add a title, turning that post into a full-fledged blog post.

Support from Evergreen and Feedbin represent the start of a new wave of third-party support for Micro.blog. There are other third-party iOS apps and even an Android app in development, including Micron for iOS in public beta now. There’s also a command-line tool for the Micro.blog API called speck.

Thanks for the support, everyone. If you haven’t tried Micro.blog yet, there’s a lot of activity in the community and in new apps. Now is a good time to join.

New episode of Core Intuition is out. We talk about what’s new with Micro.blog, cryptocurrency, and more:

Manton talks to Daniel about just missing jury duty during a busy work week. They talk about the virtues of differentiating a product by both features and personality. Finally, they react to the Stellar cryptocurrency’s surprising value, and the potential for cryptocurrency and blockchain technology to change the world.

Thanks for listening!

I love how the Micro.blog community is using the new emoji topics that I wrote about yesterday. We started with books because many people were already sharing what they were reading or wanted to read in 2018. This is working out so well that I definitely want to improve and expand upon it.

Some people have asked for more topics, and several already work: music, basketball, football, and tv. I’m thinking that some of these will pop up in the Discover section when they are actively being used, or when there’s a special event. For example, during the Super Bowl you’d see 🏈 to click on.

On Micro.blog there were some good discussions around this feature. Chris Aldrich said he was already using different book-related emoji, and Ben Norris wondered about supporting those too:

I love this! I thought I was ironic that you started it almost right after I went through and posted the books I read this last couple years on my microblog. I used 📖 instead of 📚 though.

I decided to add the open book and bookmark to the books topic, so they all map to the same place, but stopped short of adding all the other single-book emoji because I thought they might be confused with notebooks. After a few more days it may be more obvious how we should treat this.

Belle Cooper also had a good question about whether this is really much better than hashtags:

This is a cool idea, but I'm not sure I get how it can't be gamed compared to hashtags. Or is that not the point of using emojis instead?

My answer is that they can be gamed, but the limited number of emoji means we can have a better sense of what people are writing about. It’s just simpler. Also, the backend implementation is not a search; it’s a live collection of posts that is updated whenever Micro.blog sees something new, and there’s a mechanism to easily exclude any inappropriate posts that show up without needing to block users or delete posts.

The Micro.blog community has grown a lot in the last couple of weeks. Every new feature has the potential to change how people interact with the platform, and I think this experiment with books has been almost completely for the better. I don’t think every post needs emoji — most microblogs will continue to be mostly text and some photos — but sprinkling in an emoji every once in a while will start to add value to the Discover section, and it also keeps Micro.blog fun.

Micro.blog doesn’t have special support for hashtags. It doesn’t automatically link them. There’s no global search yet. While Micro.blog users can include hashtags anyway, especially if they are cross-posting to Twitter, I’ve found that the timeline is much cleaner and readable without hashtags.

I’m not saying we’ll never have hashtags. But I’m not in a particular hurry to introduce native support for them. (Once a feature is added, it can’t easily be taken back. So we try to be deliberate in everything we do.)

Hashtags and Twitter trends go together. They can be a powerful way to organize people and topics together across followers. But they can also be gamed, with troublemakers using popular hashtags to hijack your search results for their own promotion or unrelated ranting.

It’s the organizational and discovery aspect of hashtags that I most want to bring to Micro.blog. There have been several recent discussions on Micro.blog about book clubs and reading, and this seems like a perfect topic to experiment with. I’ve also noticed that people love to include an emoji in their microblog post as a kind of theme indicator — everything from 📚 to 🏀.

Today we’re introducing a search collection using emoji, starting with books. Just include 📚 with your microblog text about a book you’re reading or related topic, and your post will automatically be collected on /discover/books. There’s also an emoji link at the top of the Discover section in the iOS and Mac apps. (Make sure you’re on the latest version of the apps released yesterday.)

If people like this, we’ll generalize it and start surfacing other topics. Enjoy, and happy reading!

Rather than New Year’s resolutions, Aleen Simms has a list of liberations for 2018: things to let go of and not worry about. In particular I like this one about not looking at numbers:

Twitter followers, podcast download stats, blog post views, the scale, whatever. Life isn’t a video game. Happiness doesn’t have a numerical value attached to it.

It mirrors a philosophy we have with Micro.blog to launch without follower counts or public likes. Follower counts are not very useful for a new platform. They add anxiety and unavoidably lead to value judgements when considering whether to follow someone, instead of letting the quality of someone’s writing and photos speak for itself.

Andy Flisher posted to his microblog about how Facebook takes the opposite approach, encouraging the numbers game:

Facebook has genuinely ‘encouraged’ me to get more likes for my birthday than I did last year! 🤯 No wonder the youngsters are growing up so needy for likes and follows, not healthy 🙁

A social network doesn’t have to be like this. Micro.blog is a way to post to a web site that you control, and a place to discover and talk with other members of the community. Micro.blog is not a popularity contest.

Thanks everyone for your support of Micro.blog this year! We’ve come a long way since I launched the Kickstarter campaign for Indie Microblogging back on January 2nd. We really appreciate all the feedback and new users who are embracing Micro.blog.

Yesterday we added another “secret pin” to Micro.blog for the holidays. You can unlock it by posting to your own blog and mentioning Christmas, Hanukkah, or one of a bunch of different winter themes and celebrations for this time of year. (It also works for posts from last week, so you may already have unlocked the pin.)

We love adding pins because it encourages people to blog more, and we hope to do more in 2018. This is also a great time of year to earn the Daily Blogger, Photo Challenge, or Night Owl pins!

Wishing you and your family and friends the best this week. Thanks again for being part of the Micro.blog community.

Mike Monteiro wrote on Medium this week about the daunting, insurmountable problems facing Twitter’s leadership team. He talked about meeting in person with Jack Dorsey:

We discussed Twitter’s role in the world stage. And I admired his vision, but feared his approach. Jack, and to an extent Twitter’s pet porg Biz Stone, have always believed that absolute free speech is the answer. They’re blind to the voices silenced by hate and intimidation. The voices that need to be protected. But anyone who’s ever tended a garden knows that for the good stuff to grow, you have to deal with the bad stuff. You can’t let the weeds choke the vegetables.

I love the metaphor of a garden. In fact, I wrote a whole chapter of my upcoming book Indie Microblogging about gardens. The chapter is a longer version of what Mike says above, but with a twist.

The issue isn’t that Twitter doesn’t care. It’s instead a fundamental design flaw in the platform. Because tweets don’t exist outside of Twitter, when you’re banned, you’re done. For this reason, and because their business depends on a large user base, Twitter is hesitant to throw anyone off their service. They’re unwilling to tend the garden for fear of pulling too many weeds.

Imagine instead a service based on blogs, where the internal posts on the platform were the same format as the external posts. The curators of the platform would have more freedom to block harassing posts and ban nazis because those problematic users could always retreat to their own web site and leave everyone else in the community alone.

That’s how the web is supposed to work. It’s a core principle of Micro.blog.

Twitter will continue to improve. I believe they’re trying. But the root issue can’t be fixed without starting over.

Another week, another set of new podcasts. Daniel and I talked on Core Intuition about opening up Micro.blog and speculated on UIKit for the Mac:

Manton and Daniel talk about the major update to Micro.blog, and how to cope with demand as it either meets or doesn’t meet daily limits. They opine about the virtue of having a baseline product on which to build future updates. They react to Mark Gurman’s report that Apple has a plan to make it easier to bring iOS apps to the Mac, and finally, they catch up on Daniel’s post-release MarsEdit activity.

I also posted episode 91 of Timetable. It’s about 3 minutes on Eminem lyrics and getting your one shot.

Like most Apple controversies, the iPhone performance/battery issue seems overblown. I like Ben Thompson’s take from today’s daily update:

The biggest problem here is Apple’s lack of transparency and communication: if iOS is slowing down iPhones for battery reasons, then iOS should say so. Pretending everything works perfectly until it is painfully obvious that it doesn’t fits with Apple’s generally secretive ethos, but it runs into the painful reality that it isn’t actually true.

Apple usually tries to do the right thing. But they are absolutely crippled in how they communicate with users and developers. At this point, 6 years after Steve Jobs died, clinging to the Steve-inspired obsession with secrecy just looks clumsy. It’s the right lesson for the narrow window of product announcements, now applied universally to the wrong parts of their business.

Micro.blog is now available to anyone. There’s a limit of 100 new sign-ups each day, so that we can better respond to feedback as the community grows. Thanks so much to the thousands of Kickstarter backers and new users who have helped us improve the platform this year.

We’re also rolling out the following improvements across the web, iOS, and Mac versions of Micro.blog:

• New app icons on iOS and Mac! We love this redesign by Brad Ellis. Micro.blog now feels much more at home on macOS.
• Added photo upload to the web version of Micro.blog.
• Added a "Show More" button to load more posts in the timeline on iOS and Mac.
• Fixed Discover section in iOS and Mac to allow selecting posts.
• Improved iOS sharing from Safari to include the page title in addition to URL and selected text.
• Experiment with following domain name user accounts. The first is @nytimes.com, letting you see headlines from The New York Times home page in your timeline. (This is not affiliated with the New York Times. It's possible because Micro.blog works with RSS feeds.)

Plus a bunch of minor improvements and bug fixes. You can download the latest versions of Micro.blog from the iOS App Store or directly for your Mac.

This week on Core Intuition, Daniel and I talk about how the MarsEdit 4 release is going:

Daniel and Manton catch up on MarsEdit 4’s progress a week after releasing. They talk about the anxiety and fear of making a huge mistake when releasing, and the relief of discovering you haven’t. They reflect on the effectiveness of direct email to inform existing customers of updates, and Manton looks forward to releasing Micro.blog to the public, and how much PR fanfare he should be looking to generate.

I’ve been working on several new features for Micro.blog this week. Consistent with Daniel’s advice on the show, I think we’re going to roll out new stuff for Micro.blog next week and start ramping up promotion. Really excited about the way things are coming together.

Twitter announced today they will make it easier to chain tweets together in the official app. John Gruber summarizes the pro-tweetstorm argument on Daring Fireball:

This is a good idea. People are creating threads without official support, so true support can only make it better.

The problem is that Twitter threads take the place of blog posts. Most people won’t think to switch to their blog instead of firing off a series of tweets, but some will. Promoting Twitter threads to such a prominent place in the UI will encourage more people to create Twitter threads. It will lead to more content in Twitter and less on the open web.

Micro.blog takes a different approach. When you type over 280 characters, instead of offering to split it into multiple posts in a thread, it reveals a title field and lets you turn it into a full blog post. I feel really good about this solution because the UI actively tries to make the web a little better instead of worse.

Over the weekend we hosted the first IndieWebCamp in Austin. I’m really happy with the way the event came together. I learned a lot in helping plan it, made a few mistakes that we can improve next time, but overall came away as inspired as ever to keep improving Micro.blog so that it’s a standout platform of the IndieWeb movement.

There’s nothing like meeting in person with other members of the community. I know this from attending Apple developer conferences, but the weekend in Austin only underscored that I should be more active in the larger web community as well.

The first day of IndieWebCamp started with introductions, a chance for attendees to demo their web sites, an overview of IndieWeb building blocks by Aaron Parecki, and then brainstorming what topics the afternoon sessions should cover. After lunch, we held sessions on WordPress, static sites, Micropub posts, Webmentions, payment APIs, audio, decentralized aggregation, and post kinds.

The second day was a hack day, with a chance to work on our own web sites. This was a very valuable day for me — being able to bounce ideas or questions off other attendees. I chose to make an improvement to Micro.blog’s Micropub API endpoint to accept “bookmark-of” POSTs, mapping them to favorites. This evolved into opening up Micro.blog to allow favoriting any URL, even if the post doesn’t exist in any feed that Micro.blog knows about yet.

At the end of the day I was happy enough with the feature that I deployed my code and database changes. I demoed it using Indigenous for iPhone and Micro.blog for Mac, favoriting an indiewebcat.com post on the web and watching it show up in the app under the post’s domain name. Micro.blog got better support for Microformats with this change, pulling the author info, post text, and photo when you favorite a post via Micropub.

For the last few years I’ve attended WWDC and Release Notes each year, and I’d usually give a talk at CocoaConf. This year I added WordCamp and IndieWebCamp, and gave a talk about indie microblogging at Refresh Austin. I hope that it works out to attend another IndieWebCamp or IndieWebSummit in 2018.

Special thanks again to Tom Brown for helping out with planning IndieWebCamp Austin, EFF-Austin for hosting their holiday party after our event, and our sponsors DreamHost, Polycot Associates, and SuperBorrowNet. We should do this again next year.

Instagram is experimenting with a repost feature. From The Next Web:

Instagram appears to be finally working on a native Regram button. It’s a feature many users have been waiting for for some time. Currently, users wanting to reshare content have to either save the image or video to their device and re-share it from their own account, or call upon one of several third party apps like Regram, a popular Android option.

I wrote last year about how I thought the lack of Instagram reposts was deliberate. Early versions of Instagram were built carefully, and it seemed designed to encourage posting your own photos:

When you have to put a little work into posting, you take it more seriously. I wonder if fake news would have spread so quickly on Facebook if it was a little more difficult to share an article before you’ve read more than the headline.

If Instagram ships this, it will likely increase memes and other non-photos in your timeline. Along with ads, it will make the timeline feel even more cluttered.

Meanwhile, Ben Thompson covers Facebook’s curation efforts and how the lack of friction on social networks is both a good and bad thing. If it’s difficult to post, fewer people will do it. But if it’s too easy — with few limits on what is appropriate to share with your followers — you’ll get the dumpster fire that we currently have.

I believe in a middle-ground solution. Make it easier to post to your blog. That’s what indie microblogging is all about, why I’m writing a book on it, and why I built Micro.blog. But don’t make thoughtless re-sharing completely frictionless. That’s what leads to fake news spreading, why hateful tweets are exposed in algorithmic trends, and why safe communities must have some amount of curation.

Facebook is right to hire 10,000 curators. But what they’re missing is the balance between curation and an open platform, with the freedom to post to your own site. That’s why Facebook is a dead-end for the web.

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.

Daniel Jalkut shipped MarsEdit 4 today. This version includes many improvements, from brand new icons to support for WordPress “Post Formats” which are convenient for microblog posts.

Micro.blog-hosted blogs also have full support for posting from MarsEdit 4. You can post short microblog posts, or you can add a title, upload photos, and write longer posts. Blogs on Micro.blog are really fast, have custom domain names, and support importing from WordPress.

Congrats Daniel! I’m sure we’ll be talking about this milestone on Core Intuition.

Vincent Ritter has a new post about Micro.blog, and how it’s helped put a focus back on his own blog:

Later this year I finally got my invite through for Micro.blog. Just logging in, seeing the simplicity and the really amazing community of people, I knew this was something special. This ultimately made me rethink my entire site and what I want to do with it.

I created Micro.blog to encourage other people to blog more. It’s working. But I’ve realized it goes both ways: seeing all the great posts out there has inspired me too. Thanks Vincent and everyone who is taking the idea of an indie microblog and running with it.

I rarely change my home screen, but I updated it after having more time with the iPhone X. Seeing Shawn Blanc’s home screen reminded me that I should post an updated screenshot of my own screen.

The notable icons are Micro.blog and Ulysses in the dock, where I do most of my writing and blog post drafts. I also stopped using Instagram since there are so many great photos being posted to Micro.blog, so I have Halide there instead. Great app for quickly adjusting the exposure before taking a photo.

New for the X, I’ve added an empty row to the top of the screen using David Smith’s blank icon tip. Much easier to reach all the icons with one hand.

Today I sent the following email to Kickstarter backers. I’m working through the waiting list of invites to Micro.blog now. I know it’s taken the better part of a year, but we’re almost there.

We are just about ready to open up Micro.blog to the world. Starting later this week, we’ll no longer require an invite code. Up to 100 users will be able to register on Micro.blog each day. This helps us focus our attention on the community and take care of new users as we ramp up to the public launch.

I’m also excited to share 2 more things that are happening next month:

IndieWebCamp: December 9th and 10th in Austin, TX. If you’d like to learn more about indie blogging, work on your own web site, or just chat with me about Micro.blog, consider joining us in Austin. You can register here. More info from the web site:

IndieWebCamp Austin 2017 is a gathering for independent web creators of all kinds, from graphic artists, to designers, UX engineers, coders, hackers, to share ideas, actively work on creating for their own personal websites, and build upon each others creations.

Stickers: I’ve just ordered a new batch of Micro.blog stickers for IndieWebCamp and Kickstarter backers. Expect to receive an email from Kickstarter to confirm your shipping address.

In a little less than 2 weeks we’re holding the first IndieWebCamp in Austin: December 9th and 10th at Capital Factory. You can register here. Doors open at 9am and we’ll have coffee and breakfast tacos while everyone checks in.

Saturday night after IndieWebCamp will be the EFF-Austin Holiday Party. There’s a meetup page to RSVP for the party. Even if you can’t attend IndieWebCamp for the full weekend, you’re welcome to join us anytime Saturday and stick around for the party. (Please register for both so we can better plan for the event.)

Who should attend IndieWebCamp? Anyone who cares about the independent web. Anyone who remembers how the web used to be — the creativity of personal web sites, the freedom of open APIs — and how it could be that way again. From the event web site:

IndieWebCamp Austin 2017 is a gathering for independent web creators of all kinds, from graphic artists, to designers, UX engineers, coders, hackers, to share ideas, actively work on creating for their own personal websites, and build upon each others creations.

I hope you can make it. If you have any questions, email me at manton@micro.blog.

As I’ve been improving the import and export functionality in Micro.blog, I’ve done a lot of work with WordPress’s WXR format, which is based on RSS. While there’s nothing particularly wrong with WXR, it’s more complicated than it needs to be for non-WordPress sites, especially when you start to tackle image uploads that exist outside of the post text.

Micro.blog can also push an entire site’s Markdown, HTML, and images to GitHub, which is the most complete mirror and perfect for migrating to another Jekyll server. It introduces so many extra files, though, it’s not reasonable to expect that other blog platforms could support the same level of detail.

I’d be happy to ignore the WordPress-centric nature of WXR and use it as a common blog archive format if WXR provided a mechanism to store image uploads. Helping people migrate from WordPress to Micro.blog-hosted blogs has only emphasized to me that a better format is needed.

In chatting with the IndieWeb community, the idea was proposed that an HTML file using h-feed would provide portability and also an added bonus: it could be opened in any web browser to view your archived site. Images could be stored as files with relative references in the HTML file. (I’d throw in a JSON Feed file, too, so that importers could choose between using a Microformats parser or JSON parser.)

The files would look something like this:

• index.html
• feed.json
• uploads
  • 2017
    • test.jpg

The basics from h-feed would follow this structure:

• h-feed
  • h-entry
    • p-name
    • e-content
    • dt-published
    • u-url
  • h-entry
    • ...

Only index.html and feed.json would be required. Any other paths in the archive would be determined by the contents of the HTML. (I’m using “uploads” in this example, but it could just as easily be “archive”, “audio”, or any other set of folders.)

For large sites, the HTML could be split into multiple files with appropriate <link> tags in the header to page through the additional files. While it could contain CSS and your full blog’s design, I’m imagining that the HTML would be extremely lightweight: just enough to capture the posts, not a way to transfer templates and themes between blogs.

The whole folder is zipped and renamed with a .bar extension. Easy to move around and upload all at once. I’ve created an example file here (rename it .zip to open it).

I’d love to hear what you think. I talked about this on a recent episode of Timetable as well. Might be a nice topic to follow up on at IndieWebCamp Austin in 2 weeks.

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!

“People will want to go to it because you’re passionate about it, and people love what other people are passionate about. You remind people of what they’ve forgotten.” — Mia in La La Land

Business without direction is hollow. Your company can be full of users or money but if it’s empty of purpose, no one will truly care about what you’re building.

This is one of several problems with Twitter today. It’s not just that the leadership team is overwhelmed and paralyzed. They can no longer articulate to users what Twitter the company is passionate about.

Josh Marshall of Talking Points Memo on last night’s victory for Democrats:

When a President is locked below 40% approval and often closer to 35% approval, his party will face a brutal and unforgiving electorate. This was a fact a decade ago and it’s a fact today. We’ve just been stunned into an unwarranted uncertainty by the fact of Trump’s victory one year ago today.

November 2018 feels like a long time from now, but it will get here.

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.

We just published this week’s Core Intuition, talking about the latest iPhone X news:

Daniel and Manton recap their experience placing pre-orders for the iPhone X, discuss Apple’s unusual PR strategy for iPhone X reviews, and debate the appropriateness of Apple firing an engineer for letting his daughter film a YouTube video of his pre-release phone.

When you’re done listening to that, also check out Timetable 77. Still waiting for my iPhone X to arrive.

While writing about the limited SiriKit support in the upcoming HomePod, Stephen Hackett points out one of the biggest problems with Siri:

While I’m glad to see some progress here, I think that it is time Siri become much more cloud-centric. Alexa and Google Assistant can do the same set of tasks across devices, while Siri still remains very device-centric. Apple has its reasons for this, but its approach could lead to a less-than-ideal user experience.

I agree. See my previous blog posts on wanting a more open voice platform and Siri’s slow pace of change.

We all know that Apple’s strengths are in design and having incredibly high standards. We love Apple’s attention to detail. When Apple competes directly with other products, these strengths always produce better products. Apple wins.

The problem for Siri is that Apple’s competition with Amazon and Google isn’t on a level playing field. Siri won’t “catch up” to Alexa because the architectures are fundamentally different, with SiriKit locked to the device while Alexa expands quickly to new products and thousands of extensible skills in the cloud.

Every week, Alexa gets better. Apple’s usual strengths won’t help them stay competitive because Siri isn’t even in the same game.

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! 🎃

Micro.blog for iOS version 1.2 is rolling out to the App Store right now. This update features a new sharing extension, to make it easier to send photos and links from other apps to Micro.blog. It also has better support for the iPhone X screen.

We ended up rushing this update out a little to make sure it was approved in time for the iPhone X release, so there are a couple glitches we missed in testing when sharing photos. Working on a 1.2.1 update now to make the sharing extension more robust.

Thanks as always for using Micro.blog. In addition to the iOS app, the Mac beta is also getting regular updates. (This blog post was written and posted with it.)

Jason Snell mentioned on this week’s Upgrade that he had found a way to frame his iPhone 8 review, and today he posted it. Where most iPhone 8 reviews last month seemed overshadowed by the upcoming iPhone X, I think Jason’s review may have benefited from a little distance from the September Apple event.

It also reminded me about the missing headphone jack, which in the excitement of the pre-orders I had forgotten about. Sigh. From the review:

These upgraders also get to experience for the first time what the rest of us had to come to terms with a year ago: A one-way ticket to Dongletown, courtesy of a Lightning-to-headphone-jack adapter required by the removal of the headphone jack.

And on wireless charging, which I’m equally skeptical about:

Inductive charging is slower than USB charging, so if I’m trying to top up my battery before heading out, I’ll invariably prefer plugging in a Lightning cable. Dropping the phone on top of the small circle of the charging pad so that it’s properly aligned for the charge—the phone indicates that it’s charging and a small light appears on the charger base—is not really any less difficult in terms of mental focus than plugging in a Lightning cable.

As Daniel and I have discussed at several points on Core Intuition, I think Apple really gambled on splitting the product line between the 8 and X, and the pronunciation fumbles only add to the confusion and perception that the 8 isn’t a cutting-edge product. It’s at once the best phone in the world and old news.

It remains to be seen whether this split will impact sales. I’ll be watching for the quarterly results and Ben Thompson’s take.

Meanwhile, I’ve stuck to my first impression that it’s time for me to have a phone with the best cameras again. That means the iPhone X. I’ll miss the size of the iPhone SE, but now that my iPhone X pre-order is wrapped up, I’m looking forward to trying something new, and hoping that it captures a little of that first-generation iPhone feeling, when we knew we were holding a bit of the future.

We posted episode 302 of Core Intuition today. From the show notes:

Manton and Daniel anticipate the night of iPhone X pre-orders, and the shame of waking in the middle of the night to order a phone. They catch up with their faltering ambitions to ship MarsEdit and Micro.blog, and acknowledge the merit of sharing ambitions with others to help motivate progress. Finally, they contemplate whether eliminating a feature altogether is preferable to shipping it with obvious deficiencies.

Good luck to everyone trying to pre-order an iPhone X tonight!

Just posted episode 2 of our members-only podcast Extra Intuition, with special guest Gus Mueller! From the show notes:

Daniel and Manton are joined by Gus Mueller of Flying Meat. They talk about their early days in the indie Mac community, and Gus’s commitment to developing for the Mac. Along the way Gus let us know about a new Mac app he’s working on, and invited listeners to get in touch about beta testing it!

Gus announces a brand new Mac app he’s working on. Really exciting to see this when it ships. You can listen by becoming a member.

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.

Daniel and I wanted to do something special for our 300th episode, so we’ve launched a membership program for Core Intuition listeners. Included in the membership is access to a brand new podcast we call Extra Intuition, plus a private Slack channel for members to discuss the show and suggest future topics.

It’s been a fun journey over the last 9 years of recording Core Intuition, and the main podcast will stay as it has been, with new episodes for free every week. Extra Intuition is our chance to deviate a little from the formula and try something new.

Daniel has also posted about the membership and first episode:

Our first episode of Extra Intuition is already live, and it features a discussion about the early days of our friendship, and how we decided to start Core Intuition.

We’d love your support. Thanks for listening!

I posted a new Timetable today after listening to the Release Notes podcast where Charles and Joe discuss requiring in-app purchase subscriptions. As I talk about on Timetable, I’ve been working on the Mac version of Micro.blog, so it was a good opportunity to make a final decision on Mac App Store support.

Speaking of Release Notes, I’ll be out in Chicago for the conference next week. If you’re attending, hope to see you there. Ask me for a Micro.blog sticker.

One more week until our 300th episode! From the show notes for today’s episode:

Daniel and Manton talk about Daniel’s struggle to finish and release MarsEdit 4. They compare notes about using the WordPress API to import content, and Manton reveals he is working on a Mac app for Micro.blog. They check in about the impact that increasing competition, or perception of it, on their long-time friendship and collaboration.

We’re announcing something new next week. Hope you can tune in for it.

Micro.blog launched with 6 unique themes, and advanced CSS support to customize many aspects of the design. I love seeing users take one of the existing themes and make it their own, such as what Dan Counsell has done with colors and fonts on his site.

The publishing engine for Micro.blog is based on Jekyll, so of course the themes are Jekyll themes as well. I wrote last year about why I chose Jekyll. I’ve forked several themes to improve their support for microblogs, JSON Feed, and IndieWeb standards.

A few of these changes are now up on GitHub. You can find these themes in the @microdotblog repository:

• default
• primrose
• hyde

I’ll be updating the other themes on GitHub soon. While you can’t upload an entirely new theme to your Micro.blog account yet, many people have asked for that, and hopefully these themes will provide a starting point.

Nick Heer writes at Pixel Envy about Twitter’s half-hearted attempt at transparency on fake news and the election:

As tech companies play an increasing role in democratic processes worldwide, a regular theme has been their reluctance to admit to their own influence in a legal context. They’re perfectly happy to trot out the old Silicon Valley trope of changing the world and brag to candidates about the effectiveness of advertising on their platforms when it suits them. But when it’s time for them to be introspective about their own responsibilities, they suddenly clam up and claim that they can’t possibly have influence.

It’s time for a reckoning. I don’t know if it’s government regulation. But we are on the edge of pushback against ad-supported, ginormous platforms. Once it flips, as it did against Uber, there will be an opening for real change.

For this week’s Core Intuition, Daniel and I spend the whole show talking about Twitter’s 280-character change and related fallout. It makes a good complement to my initial blog post, as well as yesterday’s episode of Timetable.

And of course I liked this part of Colin Walker’s blog post:

Having gotten used to a 280 character limit on micro.blog I can honestly say it makes a world of difference.

Dave Winer wrote about the need for Twitter to take risks:

So if you think the 140-char limit is so great, why isn't Twitter making money for its shareholders? If you were management at Twitter would you be conservative or would you take risks? As a shareholder, I want them to take risks. Big ones. Why not? They don't really have anything to lose.

My daughter’s Twitter account has access to the new 280-character limit, so I’ve had a chance to see the new UI. Instead of counting down, it uses a circular progress bar until you get near the end of the limit. The UI is further proof that Twitter didn’t make this change on a whim. They plan to ship it.

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.

I installed 10.13 High Sierra today. It takes a long time, presumably because of the file system conversion. Make sure to block out a couple of hours.

Stephen Hackett has a full review. One of the most interesting features to me is Safari’s new ability to automatically enable Reader Mode when viewing certain web sites you configure:

Safari’s stripped-down view is learning some new tricks. The feature can be set to automatically engage, displaying text, images and video in a clean format, leaving ads and funky layouts behind.

Speaking of Stephen, his kids are running the Kids Marathon to raise money for St. Jude Children’s Research Hospital. You can read about it and make a donation here.

Manuel Riess has been writing about why he didn’t stick with previous blogs. On the topic of paying too much attention to stats:

When using Wordpress, it’s easy to get the basic numbers of interest: how many visitors, from which part of the world etc. The next level is Google Analytics… what a plethora of settings and numbers! I stared at them all the time after a new post went up, it was exhausting.

I highlighted Manuel’s microblog in an email to Kickstarter backers recently, as an example of using custom domain names. You can follow him on Micro.blog.

I still haven’t looked at stats for Timetable. And I’ve resisted adding follower counts and page view stats to Micro.blog for the same reason. If all that drives you is the number of likes on a tweet, or subscribers to your podcast, it’s easy to get discouraged when the numbers don’t pan out. Or worse, overthink your writing when you know a bunch of people are paying attention.

Everyone has something to say. Write because you love it, or to become a better writer, or to develop an idea. The stats should be an afterthought.

Micro.blog users have wanted the ability to edit microblog posts for a while. We planned to add it, but first I thought we needed an edit history and probably a window of time during which edits are allowed, to prevent people from abusing edits by changing the meaning of a post in an earlier conversation.

While I still want those things, I realized that they were just excuses to put off implementing the feature. And with full pages and longer posts, editing was increasingly a big omission.

This week I rolled out a complete overhaul to the posts interface under your Micro.blog account. The layout is better, it’s more prominently linked in the UI, there’s an easy way to switch between posts and pages, and you can finally edit posts.

There are a couple quirks of the UI still to improve. For example, if you’d like post edits to be reflected in the timeline, you should click the Remove link in the timeline so that Micro.blog pulls the latest version from your microblog. I’ll be working on polishing those areas over the coming weeks. But already it is much better. Enjoy!

I posted a new episode of my Timetable microcast. Here’s a bit from today’s episode about blogging and tweeting:

My "blog first" strategy is actually really simple. I just follow the rule that I never post directly to Twitter unless I'm replying to a question. If I want to post something to Twitter, I fire up MarsEdit on my Mac, or I open the Micro.blog iOS app, and I post it there. Then of course Micro.blog sees that and sends it to Twitter for me.

I’m getting back into the groove of publishing these episodes. This was the third episode of Timetable this week.

So many great iPhone 8 and iOS 11 reviews out today. My favorite aside has to be the headphone jack mini-rant in Nilay Patel’s The Verge review:

And I would be remiss if I didn’t point out that there’s no headphone jack, which is still routinely annoying on every phone that omits it. Apple’s own headphone dongle is one of the lowest-rated products on the Apple Store, with just 1.5 stars. It’s been a year, and the Lightning audio ecosystem is still extremely immature.

When I was at STAPLE! last week I bought a t-shirt from an artist who had to enter credit cards into the Square app manually because he had lost his Lightning dongle for the Square reader. Minor inconvenience, and fixed with an extra $9 purchase from the Apple Store, but nevertheless a real compatibility issue that will never go away.

We’ll eventually get used to this. Many people already have, thanks to the AirPods. That doesn’t mean it wasn’t the wrong decision, though. (I’m happy to give Apple full credit when they embrace a standard, like Qi charging or USB-C.)

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:

Micro.blog for iOS version 1.1 is now available. This release adds a number of new features:

• Added support for longer posts with titles. Type more than 280 characters to reveal an optional title field.
• Added Markdown syntax highlighting while typing.
• Added formatting bar for common styles. Select a phrase and tap the link button for easier markup.
• Added support for uploading multiple photos.
• Added a Browser sharing item to open the current post on the web.
• Fixed a potential crash in profile links and glitch when holding down to select text.

Here’s a quick screencast showing some of the highlighting and title support:

Hope you like the update. You can download it from the App Store

Some people are concerned that replacing Touch ID with Face ID is a design compromise. While I rarely give Apple the benefit of the doubt when they scrap an existing standard, like the headphone jack, this new Face ID skepticism seems premature. John Gruber writes:

There is clearly skepticism out there about Face ID. Some people think Face ID is going to suck, and a lot of people are flat-out assuming that they’re going to miss Touch ID. We saw the same thing with Touch ID when it was announced, and the skeptics were very wrong. I haven’t used it personally, but I am pretty sure already that the skeptics are going to be wrong about Face ID too.

With Touch ID, there are some obvious limitations that we just accept. For example, of course Touch ID doesn’t work with gloves on. How could it? But with Face ID, the technology is so advanced that we have no basis for judging when it should or shouldn’t work, so I think we’re going to expect it to work all the time.

For Face ID to be successful it has to be delightful, like a magic trick. The threat to magic is inconsistency. One glitch and the illusion is ruined forever, and you never believe in it again.

I’m not worried about Face ID. I’m not even worried about the notch, which is a compromise. Apple seems very confident in both Face ID and the iPhone X. Not confidence from hubris. Not feigned confidence, justified as courage. They actually believe they’ve got a winner, and so do I.

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.

We posted a new Core Intuition, all about the iPhone X and other products from yesterday’s event. From the show notes:

Manton and Daniel react to the announcement at Apple’s annual iPhone event, comparing notes on the allure of the iPhone X, Apple Watch 3, and new Apple TV. They talk about the impressiveness of all the significant product updates being made in parallel, and lament the slightly confusing state it leaves the high end iPhone market in.

Approaching 300 episodes over 9 years. If you’re new to the podcast, consider subscribing in your favorite podcast app. Thanks!

Michael Gartenberg writing for Six Colors about the iPhone X:

It’s arguably the most beautiful product ever made by Apple and the jewel in Apple’s crown. The aesthetics must be seen to be appreciated. This is something Apple competitors aren’t even close to. If the iPhone 8 raises the bar, iPhone X raises the bar so high it can’t be seen. This is, quite simply, the best smartphone money can buy.

High praise. Apple had me at the cameras, but I’m relieved that the design of the phone itself is so great. On Core Intuition last week I had worried that if the design fell short (or Apple did something clunky like put a Touch ID sensor on the back) that I’d have second thoughts.

This is the first iPhone in years that many people are going to stand in line for. It might not be priced high enough.

David Nield of Gizmodo has a sort of re-introduction to RSS, with an overview on why it’s more useful than ever:

One of the main reasons RSS is so beloved of news gatherers is that it catches everything a site publishes—not just the articles that have proved popular with other users, not just the articles from today, not just the articles that happened to be tweeted out while you were actually staring at Twitter. Everything.

Obviously I’m a fan of RSS. Micro.blog has great support for it throughout the platform. But even though I subscribe to hundreds of feeds, I even caught myself recently loading a few favorite news sites manually instead of using the feeds. Doesn’t hurt to be reminded that there’s a better way.

Slightly longer Core Intuition this week as we cover several topics. From the show notes:

Daniel and Manton follow up briefly on Manton’s backup strategy, and catch up with Daniel's progress with MarsEdit. They talk about the merits of using cryptographic signing for software licenses, and balance the risks and rewards of combatting piracy. Daniel talks about the recurring lure of taking a salaried job, and how the privileges of staying indie continue to win out. Finally, they look forward to next week's iPhone event and the expected hardware announcements from Apple.

I’m excited about the upcoming iPhone event on Tuesday. Seems like it’s set to be a big one.

Tim Duncan is matching donations to relief efforts for the U.S. Virgin Islands, hit this week by Hurricane Irma. He writes at the Players Tribune about living through Hurricane Hugo when he was 13 years old:

Hugo hit at night. The first thing I remember is a loud boom from the windows blowing out of our house. My mother and sister burst into my bedroom and led me by the hand into another room. We spent the rest of the night sitting in a small bathroom, our eyes wide open. None of us could sleep. We heard the bangs and booms of debris. Once in a while, I’d peek down the hallway at my dad, who was watching our ceiling. One of the beams had a crack in it, and the crack slowly grew bigger throughout the night. I think my dad was praying.

The whole story is a must-read. Next week, Tim is chartering a plane to deliver supplies. I’ll repeat what I said last year: thank you. Everyone still in the storm’s path, stay safe.

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.

I pre-ordered the book Ink & Paint a few months ago to add to my collection of books on animation. I love these untold stories, and the women working at Disney in the early days of the studio were notoriously uncredited.

It arrived today and now I see that it’s a massive achievement. Large format, 380 pages, full of old photos and details about the artists.

Mickey Mouse coffee mug for scale. Really looking forward to reading this.

The iPhone SE was an incredible value when it first shipped — a perfect balance of size, great camera, and nearly-flawless design. I still love mine. It’s arguably the best overall phone Apple has ever made.

The iPhone SE likely won’t see an update until next spring. At that point, the camera that was competitive at launch will be 2 generations behind. This isn’t a surprise; we knew this was coming. It’s just the more I see the photos from Traci’s iPhone 7 Plus camera, the more I’m pulled back to the cutting edge. The dual-camera approach is a major step forward.

Apple will announce new iPhones in a couple of weeks. Unless the design of the high-end “pro” version is a disaster, I plan to go for it.

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.

Daniel and I talked mostly about subscriptions on this week’s episode, and then closed with a wrap-up of our projects as summer winds down. Here’s a transcript of the first part of the show, lightly edited.

Manton:

Hi Daniel. You know a topic that we’ve had on the show a few times over this last year is subscriptions and pricing and revenue, especially in the context of Micro.blog and the new MarsEdit release. We’ve talked about in-app purchase and different revenue models for MarsEdit. And developers keep trying things. The big news in the last week was Ulysses has switched to a subscription model.

I find this interesting, and I know we chatted in the Core Intuition Slack a little bit about this as kind of a preview of the show. I’m not sure how to feel about this in general because Ulysses is the first app I’ve seen — the first big app — that is doing subscriptions without changing their app. What I mean is a lot of apps that do subscriptions, they have subscriptions because they’ve done something significant like add their own syncing backend, or publishing service, or there’s some service-oriented aspect to the app that justifies subscriptions. And Ulysses is just saying — they had a big post saying — “You know what? This business is going to work better for us. We think it’s going to be better for users too. We’re just switching; the app’s not changing. We’re just going to start charging per month.”

Daniel:

Right. And they have their typical making the case for it blog post: Ulysses switches to subscription. And as you said it’s very straightforward; they’re not doing this halfway. And their basic points are things we’ve heard from other developers and I think you and I, Manton, we appreciate this as well, even if we’re not convinced that subscriptions are the right choice necessarily for all of our products.

But you know there are some really compelling things. One of the things that rings truest for me is getting away from that whole major upgrade cycle. And especially when you’re looking at someone like me who has been now seven years since the last major update, whenever a developer makes that argument, “Oh, now I can just work on features and add them to the app and release them when I feel like it, or as soon as the feature’s done users can start benefiting from it.” All of that sounds so good to me.

There’re a lot of great arguments to be made. I don’t necessarily share your feeling that customers expect something service-oriented. I can definitely see that argument in it. I know it’s made often. But I am going to be watching Ulysses closely because I think a lot of customers are starting to understand that it’s sort of just like… Maintenance is a service. Maintenance of the software is a service and that’s something that a lot of people can justify paying for. You know especially with an app like this where it gets at sort of people’s… This is one of those part of people’s identity type of apps, where it’s like: you use this because you are a writer.

You can also say a big risk here is that there are a lot of different ways to write and there are a lot of different apps you can use. Somebody who uses Photoshop for a living… Historically it’s been harder to justify using other tools because it’s just such an industry standard, so I guess something like Ulysses is going to be like: is what they provide to people unique enough and something that people like enough and identify enough with that they’re willing to say, “Okay, part of my identity is I’m a writer with Ulysses and I’m going to pay $40 a year for that privilege?”

Manton:

Yeah, I think there’re a couple of things to go through with this, and your comment on maintenance is a service… That’s true, but nothing has changed with software in that regard, right? Software has always been work: supporting customers, doing new versions doing bug fixes, having compatibility updates for new versions of the OS. The difference with software as a service like web apps and subscriptions is: there is a real cost. If you’re running Dropbox or something you can’t do that for free.

And users I think get that there is a hosting cost, there is a bigger cost to running those services, and that’s why they are charged by the month usually, because it’s not free to run them. Whereas an iPhone app that you ship, it’s not free to support, of course. And Ulysses has a medium-sized team. They have an actual team behind this, and they probably have potentially multiple engineers and multiple support people. That’s not free, but it’s different than thousands of dollars a month in hosting costs that have to be offset or there’s no business whatsoever.

That’s how I draw the line usually, where there are some types of businesses that they have to be charged per month. They cannot be done any other way. You could support them by ads, potentially, if you’re big like Facebook and Twitter, but otherwise you have to charge users per month because you just can’t run the service otherwise.

And apps aren’t like that. Apps, there’s choice. There’re different ways you can make a business out of selling an app.

Daniel:

It’s true, but I really don’t think most users think about it that much. People who click the button or tap the button in an iPhone game to get like 100 emeralds or whatever, they’re not thinking through, “Well it costs cost money to make virtual emeralds.”

Manton:

That’s a unique case.

Daniel:

Well, it’s a unique case but it reflects the fact that I think in the vast majority of cases it’s far simpler: users recognize and accept that software is either available to them or not available to them based on whether they pay, and they choose whether to pay not based on some intricate analysis of the market viability or the business sustenance. They just think, “Do I want this, and am I willing to click this button to say yes, pay?”

That’s one thing. I do agree that there’s a challenge in marketing subscriptions in general. I just don’t think that you know the arguments about whether the developers need to pay for keeping servers running or not really comes into it as much. It’s more just about a pure value proposition to people.

Manton:

I don’t think so, though. I really think users… They don’t think about it in the terms that I just outlined, but their gut feeling is, “I’m paying for this because this is the kind of service that needs to be paid per month.”

If you ask someone will they be shocked if they go to WordPress.com and it charges them per month, of course they won’t. Yes, it’s a web site hosting service, it charges per month. But then if you ask them if the text editor should charge per month. Most people will say no, it should be a one-time… And this is not because they know the business models perfectly, but it’s just this is the accepted way this software has been done. And software as a service — subscriptions, traditionally — it’s a mature market, 15, 20 years. People are used to subscribing to these things, and so they understand it. And a text editor is not the same thing. I think users get that.

I mean it’s still too early to know how well this is going to work. I have a feeling, since Ulysses is really well loved… (I use it. I use it on the Mac and on the iPhone. I love the app; it’s really well done.) I have a feeling it’ll work out fine. But you just take a quick look in the App Store and you see the reaction is not kind. One-star reviews. “Loved this app, now I hate it because it’s subscriptions.” So that reaction shouldn’t shock anyone, because this is kind of a big switch and people are not used to paying per month for this type of app.

Daniel:

It doesn’t shock me, the reaction, but I also think that this is a classic example where a very angry, loud minority, probably, is going to get the attention. They’re going to make a stink about it. We saw this happen with TextExpander a year ago when they switched to a subscription model. As far as I can tell, TextExpander is doing very well, and it’s because, again… I mean you can argue and probably will that they have a service component…

Manton:

I will, yeah. [laughter]

Daniel:

But I honestly I don’t think that that plays into it. I don’t think typical users are thinking through the mechanics of how software works. I suppose at one point you know somebody could have made an argument that people aren’t going to pay money for software anymore because you don’t get a box and it doesn’t come with a CD-ROM and there’s no physical thing there. But we made that leap and we got to the point where it was like, okay, now people are paying $600 for an Adobe download.

This is always going to be changing. How software is marketed, how it’s priced, what people are willing to pay for it, how they get it. And I don’t think the technicalities of whether there’s a running server process on a web host somewhere has as much to do with it as you think it does. I think it’s just, point blank, does this do things I want and am I willing to pay for it.

You and I, we do customer support for our customers. A lot of them don’t understand the intricacies of how software is delivered and how it’s installed. They just know that it gets on their device somehow and then they use it. All of your arguments are totally valid about this sort of mindset of this classic traditional, savvy computer user. And I think we have to keep in mind, more and more, these ideas about how we think software is supposed to be sold and delivered. You know every year there’s a whole new class of adults who comes into purchasing power who has never known some of these old ways of selling software.

I think there’re problems with subscription pricing, but I don’t think if you took an average sampling of people, I don’t think that… I guess I have to admit I would be really curious to know what an average sampling of people would think about it. But I just don’t think that they would be going to the sophisticated analysis that you are, as much as you think.

Manton:

I agree they wouldn’t have that analysis exactly, but again their instinct — their first reaction — would be this app is good for subscriptions and this app is not. Again, no one is shocked if they go to Spotify that it’s a subscription. No one would say this should be a flat one dollar forever charge. It’s just accepted that, yes, this type of app is a subscription product. And the opposite is true for a text editor. The default assumption for people is that it’s a one-time fee and maybe they have to pay again later at some point, but they get to keep using that app.

And that’s another distinction that’s worth pointing out: there’re a lot of different ways to do subscriptions. Right now we’re talking about automatically recurring subscriptions where you pay per month or per year and at the end of that period it renews and you can’t use the app after it expires. That’s what we’re talking about. There’re other kinds that people have experimented with too, though.

For example, Sketch — great vector drawing app that I love — that is kind of subscriptions, but not really. It’s more like a support contract where you pay for a year and you get updates. After that year, you don’t get updates anymore. But the app doesn’t stop working. You can still keep using it.

And that’s kind of a middle-ground that I know a couple developers have experimented with, and I think for certain types of apps that works really well. I think for Sketch that works really well, especially because their competition is in the fully recurring — you know I’m talking about Adobe — fully recurring, automatic renewal subscriptions. They are almost there but not quite. Their app is less expensive. It’s better for some people. And so I think that fits that market really well. But there’re a couple different ways to do this and traditionally the recurring subscriptions has not been used for apps like Ulysses. It’s just rare to see an app like that have that kind of business model.

Again, with TextExpander, like you hinted at, my argument there would be: first of all, they still have the standalone version that you can buy; and second of all, when they introduced subscriptions they have a team version that syncs your snippets to all your computers. Same thing for just you using it solo or with a couple of people. And so they introduced the business model change with the addition of new features that were enabled by subscriptions. And that’s the distinction of where I draw the line there.

Daniel:

Yeah. Obviously there’s been more apps doing this kind of subscription, or like you said with Sketch, kind of a semi-subscription approach. And I guess I’m just not going to be too surprised if after a few years, whatever this sort of hunch that you think people have that something is or isn’t suitable for subscriptions, that they’ll just kind of get over it. I guess that’s the bottom line. Does this reflect a sort of market necessity, or is it just kind of like a whim.

I guess we’ll be able to watch a dueling example of this playing out because one of the competitors to Ulysses is Scrivener. And as I was reading the responses to Ulysses going subscription, I saw at least one customer saying this kind of snarky comment like, “Thanks for making my decision to switch to Scrivener.” And in fact if you go to the Scrivener forums, one of their customers asks point blank, “Are you switching to…” Or they said, “Please don’t switch to a subscription model.” And the Scrivener developers, they answered very bluntly saying, “We don’t want to switch to a subscription model.” They put a flag in the ground for traditional purchase one version, pay for upgrades, etc… So I guess we’ll be able to see as time goes forward which one of these models works best, or if they both work, and how it affects customers’ happiness.

Manton:

Right. And this is a really neat example that we have because there’s this contrast. Both those apps are different, certainly, but they both appeal to writers, and so there’s certainly overlap. Some people love both apps and use them for different purposes. The business model is now very different. And with Scrivener I think it’s $45 for the Mac version. Add on some more for the iOS version. But that’s a one-time fee. So if someone uses that app for five years, let’s say, they’re going to be paying much, much less than Ulysses. Probably roughly one-fifth the price.

Doesn’t matter in the short term so much. And subscriptions are also nice because you can start using an app with a very low investment of just the monthly fee. But in the long run if that continues, people will notice the price difference and they’ll think about it.

And the reason I’m coming from this side of things is that I am a little concerned that… This subscription fatigue thing. I really do think it’s real. I think people will be burned out on subscriptions if all apps are subscription-based. I think that will be a big problem for the market and just the industry in general. And as someone who is trying to build a business that can only work with subscriptions, I have no choice. It has to be subscription-based because of the hosting costs of running a social network and a blogging platform.

I’m a little concerned that people will be burned out and I don’t want them to drop my service. I want them to drop something else if they decide they have to cut their monthly expenses.

We’ll see how it plays out; it’s super early. I was just listening to the Accidental Tech Podcast, and they briefly addressed this in one of their Q&A episodes. The consensus on the show was the market will sort of out, don’t worry. If too many people charge for subscriptions and users are burned out, they’ll stop buying those apps and those apps will have to die or change their business model.

They weren’t worried. I am more worried than that. I think there is a concern. We’ll just have to see if that is valid. I know developers right now are looking at Ulysses, and if it works for them, they will copy it. That’s going to work for some people and not for others.

Daniel:

You know when it comes down to it, part of this subscription thing is developers, actually starting to demand payment for what they do.

Manton:

[laughter] Yeah.

Daniel:

And you know, when you look at people like me… It’s funny, the Scrivener folks say in their post as well that it’s been seven years since they had a major upgrade. And I look at that and I think, Ulysses can switch to subscription pricing and they can charge $40 a year. If you compare that with Scrivener, they can have seven times fewer users and still make the same amount of money.

A lot of us who are amateur at business, we have this problem: we neglect to ask and demand payment for the true value of our work. Part of the problem when you go indie, and you go from having a well-paid job to maybe making half of that and hopefully trying to get back up to where you’re making the same amount of money you were for the big job. Part of that disparity of income is I think a failure to demand payment for what what your work is worth.

And so I think it may be an extreme that going to this $40 a year might be an extreme counterbalance to that, but I think it’s an example of pushing back in the other direction. I think it’s fair to say people who have been using Scrivener for seven years, having paid for it once for $40… Whatever that amount per year is is not a fair compensation for the work. So somewhere in the middle maybe. If it’s going to come down to a test of whether a business model that asks for $40 a year wins or a business model that asks $40 every seven years wins, the subscription pricing is going to win. That’s ultimately going to keep the product better maintained and better developed. It’s going to cause users to like it more.

And I don’t know the subscription fatigue thing, I agree, but most users don’t need like 20 apps — 20 paid apps, anyway. I have some subscription fatigue for things like Netflix. I only have Netflix and then I added HBO. And I have my Apple Music subscription. I’m not going to go subscribe to all of Apple Music and Spotify and whatever else — Tital or whatever else. But I am willing to add subscriptions for things that bring me new value that I can justify.

And I think that people are going to be the same way with with apps. Maybe there’s only five apps I want to subscribe and pay for, but I’m going to pay for those. If every user out there subscribed and paid for five apps at $40 a year we would be doing pretty well as a software industry.

Manton:

So Daniel, you make some good points about subscriptions, and I also think that you’re right in a way that maybe subscriptions for these types of apps — that I personally think is pushing the limits — it is at one extreme, and maybe we’ll come back into the middle a little bit. Because of course I completely agree that apps should not go without revenue for seven years, and that’s not really the user’s fault, exactly. Developers should be more disciplined about… I’m trying to say that without insulting anyone, including my co-host.

Daniel:

Anyone on this show. [laughter]

Manton:

But that’s too long, we can all agree. If your if your model is paid upgrades, maybe you can go that long if you have a successful app, but you shouldn’t. You should go at most two or three years before doing a paid upgrade. That’s a reasonable amount of time. Especially for Mac software, you’re not going to get any one-star reviews if you do a paid upgrade after three years. People understand that there’s going to be a paid upgrade at some point, most likely.

So maybe there’s a middle ground there. Maybe this is pushing the limits. As you were talking about you just want to pay for Netflix, but not Hulu and HBO and Apple Music and all these other things, I think there’s a parallel to the app world here as well, and it’s Setapp.

We’ve talked about this a little bit on the show, but Setapp is like the cable package for people who don’t want to buy one-off subscription services. We pay for Netflix, we pay for HBO, we pay for Hulu, we pay for Playstation Vue, we pay for all these things. And at some point you kind of want to consolidate that into a cable-like package where you’re paying one company and you’re getting a lot of things. And we don’t quite have that in the streaming world and we don’t certainly have that in the developer world, but Setapp is that model where it’s a subscription but you pay for many things at once, so that you’re not burned out on paying 20 different developers $4 a month.

Daniel:

Yeah, I think it’s a great argument if you say what if you had to pay for a subscription for each of the shows that you watch on TV. There’s a logical extreme where obviously it’s not going to work, and maybe that’s an example where the ATP argument that the market will figure it out comes into play. I mean there’s just no way I would pay… Imagining that scenario is a bad scene because I think in practice what would happen is that I would just stop watching TV. So it’s bad news for the TV makers if you follow that same argument. If I have to pay for each of the shows that I relatively religiously watch now then I would find a new hobby, I guess. And maybe software buyers would likewise… I don’t know what they’d do. Maybe they’d switched to writing with a typewriter or something.

It’s going to be interesting to see because I don’t know if Setapp is exactly the right solution. I really applaud them… They’ve really tackled this experiment with gusto, and it sort of seems like it’s working for them. It doesn’t seem like it’s working nearly as well as they had anticipated, from what I’ve picked up. I saw some links talking about how much they’ve sponsored and how many big events they’ve sponsored, and you sort of start doing the math on it and it doesn’t really sound like it’s… I wish I had it all at the tip of my fingers, but some other information came out where it showed I think that they had shared their subscription count and doing the math on it it sort of seemed like, well that sounds like not a great deal.

You actually saw some concrete evidence of how well they’re doing on Dan Counsell’s blog. It’s his Micro.blog-hosted blog as it happens, and he shared his numbers for RapidWeaver. Actually RapidWeaver and Squash, two of his apps, but I have to assume RapidWeaver is by far the greater revenue source in this case.

Both of them are in Setapp. We don’t know a ton about how Setapp developers are compensated except for it’s been shared that it’s sort of proportional to the price of the app standalone. RapidWeaver is not one of the lower-priced apps in Setapp, so I would have to assume Dan Counsell’s cut is higher than many participants in Setapp. So keep that in mind, but he shares his numbers and he points out that the numbers are actually going up. Fairly fairly quickly, really, over a few months. In May, he says he took $1446 from Setapp, and in August it’s up to $1913. Which is a great growth rate if you just look at it in isolation. However, I’m not sure that reflects a great overall business numbers from Setapp, if you consider that he’s probably being compensated better than many app developers in the program.

Let’s say generously that he can look forward to you know $30,000 a year in revenue from Setapp in the near future. And if that’s true, boy that’s really great if it’s extra money, if it’s not eating into his sales, etc. But this is being looked at as the future of software, it’s not great. $30,000 a year is not great for most developers in the U.S. at least trying to make a living off of software. And particularly for an app like RapidWeaver that I have to imagine — if not now then definitely in its heyday — was making way more than $30,000 a year. I imagine it still is making multiples of that per year.

So I don’t I don’t expect Setapp to be mature and to the point where it does fulfill this dream of keeping developers fully employed by participating in the program. But I do think this is evidence. This is middle evidence. This is evidence that there’s real money coming through Setapp, and it’s also evidence that it’s not a real great amount of money.

Manton:

Right, and I haven’t seen too many real numbers, but this is consistent with what we’ve heard — even some people in the Core Intuition Slack, who are on Setapp, have said — which is it’s some extra money. It’s not, “I can’t shut down my direct sales or my Mac App Store sales and just use Setapp”, but it’s money coming in. It’s growing. And the consensus I hear is, “I’m willing to just let it grow and see what happens”, because it’s extra money.

You’re kind of hedging your bets by being in Setapp because whether you sell directly and have paid upgrades as RapidWeaver has had for quite some time — and I know they’ve had some big successful paid upgrades that they’ve blogged about — or whether you’re taking Ulysses’s approach or TextExpander or 1Password, those kind of approaches with subscriptions. In case your primary bet doesn’t work out, if Setapp grows, that’s extra revenue that will appeal to a different set of users. If someone is burned out on subscriptions or they’re tired of paying paid upgrades or they don’t want to pay $45 at once for the app, and they go to Setapp, they are still your customers, which is nice.

I feel like Setapp, in a lot of ways I think people have been a little too negative about it, and maybe the expectations at the beginning were just too great for it. But if Setapp sticks with it, and develops stick with it, and it keeps growing, I think there’s something there. It doesn’t need to take over the world, but it could still be a nice bit of extra revenue for developers that are there.

Daniel:

It’s interesting because one of the apps in Setapp is none other than Ulysses. So you get this interesting situation where if a few more of these Setapp apps start offering subscription pricing on their own, then you get to the situation where if you’ve got three $40 a year apps then you do start to face that point. If I were subscribing to Ulysses and let’s say RapidWeaver had its own subscription, and Screens is on here. If I was subscribing to each of those independently, I would be paying more at that point than the Setapp price.

Manton:

Is the Setapp price $10 a month, or $20?

Daniel:

$10 a month.

Manton:

So it would only take a couple subscriptions individually to say, “Well, maybe I’ll just use Setapp instead.”

Daniel:

If that happens, that’s going to be an interesting example of where developers might suffer. A lot of this hinges on the Setapp model not taking money away from the developers. So if you’re in a situation where you’ve got three people paying $40 a year each for three apps that are also Setapp, if that individual gives up those subscriptions in favor of Setapp then suddenly those three developers are making a ton less money.

At some point I don’t know whether this Setapp setup is going to be something these folks want to stay in. And I can see for example Ulysses being in Setapp as sort of a way to get some subscription money before they had chosen to go that route route.

I don’t know if we’ve seen an example yet — if we have, I don’t think it’s been highly publicized — but I don’t think we’ve seen an example yet of companies leaving Setapp. I wonder if some of them will be compelled to if doing the subscriptions themselves is a better deal.

Actually, Blogo is in here, which is one of my competitors, and it’s also I think exclusively a subscription app on its own. And they made the switch a year or two ago. But that’s another example where it’s like okay, get a few of these and if you’re paying for them separately of course you’re going to go switch to Setapp, save some money, but then I don’t know. There’s going to be some friction there if that happens.

Manton:

And it’s complicated because you say of course you’re going to switch, but most people don’t know about Setapp. And I think most developers are not pushing it prominently even though there’s an advantage to pushing it a little bit because there’s some some complicated math there with referral numbers but RapidWeaver as an example, it’s a $90 app. I know they have regular paid upgrades that are probably half that or less. So, pretty expensive app. But I know they have tons of users that love the app, really well respected app. When you go to RapidWeaver — RealMacSoftware.com — you buy it directly or from the Mac App Store, it’s $90. It doesn’t say, huge button that says Setapp.

Actually if you scroll way down to the bottom there is a referral link to Setapp. Buried way, way at the bottom — in the footer of the page — but I think most people are going to buy direct from the developer or through the Mac App Store and Setapp is not going to hurt the general sales. If it does, it’ll be a real small percentage of people I think.

It gets complicated though. There’s certainly the thing that we’ve talked about before which is if your competitor is in Setapp, and a potential user knows about a Setapp, they may just use your competitor’s app because it’s Setapp without having to pay extra, versus going to your site. There’s a lot of ramifications for these different models competing.

Daniel:

I wonder if there’s a rule on being in Setapp if you have to link to them. I’m looking now on Edovia’s Screens for Mac, and it’s a similar type of deal. It says download trial, buy now, and then as part of the little text underneath it says Screens is also available on the Mac App Store and Setapp. Does the Ulysses app have a link?

Manton:

That’s a good question. Let’s check. And even if it’s not a rule because of the referral money, there’s an incentive to just put a link anywhere, somewhere, even if it’s not super prominent.

Daniel:

Yeah. I don’t see anything about it on the Ulysses page, so maybe it’s not a requirement. Maybe it’s just a coincidence that both of those had it.

I think Setapp, back when they were first coming out, we had this discussion. I don’t think this is exactly the right solution what they have right now, but I think they are set up to be in a position to provide what could be the right solution. And I think it’s going to be when that friction — you know, let’s assume they get successful enough that that friction occurs, where enough people know about Setapp to know that they can go to Setapp and then that doesn’t work out as well for the developers. I think what Setapp could do is be in the business of providing basically the equivalent of cable mini-packages. If you could put together your a la carte list of apps and say, “Okay, I want these five apps let’s say, and I’m willing to pay for these five apps for $10 a month.” Obviously at that point it would have to be apps that are included in the main Setapp bundle. They would be in a really strong position then because they can capitalize on that problem we were talking about, hich is I don’t want to pay for each show separately. But at the same time they can also give their developers a more substantial cut because you’d be selling a smaller number of apps that it’s obvious the customer really wants those apps.

Manton:

Right. I think you’re right that they’re well positioned to do something and to fill whatever this hole ends up looking like in the market. The key to me is they shouldn’t give up. Developers shouldn’t give up like just see this through. Even if a developer is not making very much money, it’s probably mostly free money. It’s probably not hurting your direct sales too much, so just see it through and then six months later, 12 months later, re-evaluate and we’ll re-evaluate on the show too how we think it’s going. But this feels like it’s something, but it needs time to develop and mature.

Daniel:

Yes, I think so. I think we’re going to see a lot of stuff happening over the next year, especially. Seems like the subscription idea is percolating. Setapp is there as an example of something different that somebody is trying. Maybe we’ll see something new yet still.

I kind of wish I wasn’t due for a major upgrade, because I wish I could sit back and watch and see what works. But I think I’m just going to have to push forward and get my get my app out. Probably sell it the old-fashioned way.

Micro.blog now has Markdown highlighting as you type in replies. Micro.blog has had basic Markdown support since the Kickstarter launch, but we’ve been improving how it processes Markdown and where the visual highlighting is used in the web UI.

Here’s a short screencast of the new reply UI:

Don’t have a Micro.blog account yet? We’ll be inviting more users soon. You can sign up on the announce list.

In a post on Daring Fireball today, John Gruber makes a convincing argument for Safari showing favicons in tabs:

With many tabs open, there’s really nothing subjective about it: Chrome’s tabs are more usable because they show favicons.

Even more surprising to me is that Safari doesn’t use favicons for pinned tabs. Instead it uses a special monochrome vector icon. Ever since adding favicon support to Micro.blog, I’ve had on my to-do list to create one of these vector icons for Safari, but so far I haven’t been able to justify the effort. (And judging by a handful of my favorite sites, no one else has bothered to create a pinned tab vector icon either.)

Why does Apple require a separate icon format here? Probably for the same reason as John Gruber’s guess about normal tabs:

I don’t know what the argument is against showing favicons in Safari’s tabs, but I can only presume that it’s because some contingent within Apple thinks it would spoil the monochromatic aesthetic of Safari’s toolbar area.

It seems clear that these pinned tab vector icons are a dead-end. There are already too many sizes of favicons. Safari should have basic favicon support in tabs and do it with as few extra icon files as possible.

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.

I don’t use Apple News very often. I much prefer reading blogs in Reeder and Micro.blog, with a daily check on the other news sites I pay for. But last night I noticed a headline in the iOS today screen and tapped over to a few stories in Apple News.

Scrolling down in the “For You” tab about politics I was surprised by a couple news stories about a plan by Democrats to “silence non-liberal media” (People’s Pundit Daily), and another on the Trump-Russia “collusion fantasy” (The Daily Caller). These were right-wing opinion pieces sprinkled with conspiracy theories, yet placed next to reputable news organizations like The New York Times, CBS News, and Politico.

I thought Apple News was highly curated and better than this. Personal essays are fine in Apple News, because that’s part of blogging, but they shouldn’t be suggested to a mainstream audience looking for real news.

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 help@micro.blog 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.

A few years ago, Daniel and I launched Core Intuition Jobs, a site for companies to post job listings for Mac and iOS developers. It was a really nice success. At one point I thought we might even focus more time on it, and expand it with a companion site of resources to help developers.

Fast forward a year or two, though, and it became clear that without that attention, the site couldn’t just coast along. New listings were becoming more infrequent. The site needed marketing and regular improvements, just like any product.

And worse, while the whole point was to build something just for Cocoa developers, the site would still sometimes receive job listings for Java or Python developers, for example, and we’d need to refund the listing and remove it from the site. It wasn’t a lot of maintenance, but it was enough that we had to decide whether to put more work into the site or focus on our main podcast and other projects.

This week we decided it was time to move on. Existing job listings will continue to run until they expire. No new jobs are being accepted.

Thanks to all the companies who used Core Intuition Jobs. Now when we are asked about other places to post jobs, we’re pointing people to the email newsletters iOS Dev Weekly and This Week in Swift, as well as Core Intuition podcast sponsorships. Good luck to everyone looking for a new job!

John Gruber remembers what it was like watching the iPhone announcement:

Apple had amazing product introductions before the iPhone, and it’s had a few good ones after. But the iPhone was the only product introduction I’ve ever experienced that felt impossible. Apple couldn’t have shrunk Mac OS X — a Unix-based workstation OS, including the Cocoa frameworks — to a point where it could run on a cell phone. Scrolling couldn’t be that smooth and fluid. A touchscreen — especially one in a phone — couldn’t be so responsive.

I felt the same way. Even the day I brought the iPhone home, I wasn’t sure that it was actually going to work. I was ready to be unsurprised if it turned out to be unstable — crashing often or overheating. It was stunning how good it was. It absolutely felt like a phone from the future.

One thing I had forgotten about from 10 years ago was the activation process, which was definitely not from the future. It was rooted in the past, connecting to iTunes like an iPod. Here are some of my tweets from that day, showing the long delay between picking up the iPhone from the store and actually using it, plus my last-minute decision to even wait in line:

6:34am: Good morning iPhone Day! Weather forecast in Austin for today: 40% chance of showers and storms. 10:15am: It's only 10am but already realized I need to go to Plan B. Bribe friends already in line to use their 2nd iPhone purchase. 11:09am: Change of plans. Heading to the Apple Store now to join in the line-waiting fun. Will it be too late? 12:26pm: I expected rain, but that seems unlikely. It's hot like a real Austin summer here in the iPhone line. 2:32pm: Hanging out in The Line with Jeremy of Barton Springs Software and @damon. Apple Store is closed. Had some lunch and a Starbucks soy latte. 4:03pm: 2 hours left. We can redeem our free Starbucks coffee coupons now. Excited! (About the iPhone. Not the coffee.) 6:30pm: Got my iPhone. 7:35pm: Activation will have to wait. Ratatouille. 8:18pm: Movies all sold out. Pre-activation dinner at Kerby Lane instead. 9:53pm: Activation took less than a minute. Also, no plan choice. Just $20 added on to what I already pay, I guess. 11:56pm: @danielpunkass Wait, what? You can make calls on it? (But seriously, you're right. It's a computer first and a phone second.)

Apparently I waited in line most of the day. I remember it only being a few hours. I also love how trivial these tweets seem. A big reason to have a microblog is because even the most mundane posts today carry extra significant years later.

Great to see Daniel Jalkut announce a public beta of MarsEdit 4. There are a lot of new features in this version, but the one that I love the most actually might seem minor. It’s just a short line in Daniel’s announcement, under WordPress-specific enhancements:

Post Format support

For anyone using WordPress for microblogging, this is a big deal. It means you can post with the “status” post format for your short posts. It’s a really convenient way to post to a WordPress microblog from a Mac. (And of course, you can use MarsEdit to post directly to a Micro.blog-hosted blog as well.)

A few years ago, Jon Hays and I built an app for photos called Sunlit, powered by the App.net API. We evolved it to work with other services, like Flickr and Instagram, but as App.net faded away we could never justify the investment to rewrite significant parts of the app to bring it forward and keep it relevant. It also wasn’t clear what the app should do if we were to modernize it. So we let the app sit in the App Store, kind of neglected, and even discussed removing it from sale.

As I rolled out Micro.blog to Kickstarter backers, Jon dusted off the Sunlit project and experimented with something that should’ve been obvious to us earlier: Sunlit should post to blogs. And more than that, it should work well with microblogs and IndieWeb standards. It should become a great app for photoblogging. The new version of Sunlit can post photos to Micro.blog, WordPress, or any site that supports the Micropub API.

To play nicely with microblogs, we introduced a new post type in the app for single photos. For longer posts, you can still collect multiple photos together, add text, and post them as a story directly to your blog. There’s also a brand new editing interface with filters and advanced adjustments:

Jon has put a bunch of work into this while I focus on Micro.blog. Sunlit 2.0 is already feature complete and in beta testing now. We expect to ship it sometime this summer.

We just posted Core Intuition episode 287, following up on Chris Lattner, WWDC, and Uber. From the show notes:

Daniel and Manton react to Chris Lattner's early departure from Tesla, and segue into speculation about his job prospects, and the challenges of effective technical interviews. They talk about the new frameworks announced at WWDC, and overcoming fear of incompetence when learning new things. Finally, they react to Uber CEO Travis Kalanick's resignation, and think about what’s next for the company.

Thanks for listening. If you’re new to the show, you can subscribe in iTunes or Overcast.

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.

As I expected would happen, using iOS 11 on my iPad Pro after WWDC has inspired me to revisit the universal version of Micro.blog for iOS. Here’s a screenshot of my current build:

I plan to include this in 1.0. I’m in the process of moving the app from TestFlight to its final home in the App Store. As we prepare for the public launch, this’ll make it much easier for everyone to download it, and it shouldn’t be limited or scaled up on the iPad.

Last week, Uber sent an email to customers linking to the results of its investigation and the next steps for the company:

After a report of inexcusable workplace harassment surfaced earlier this year, our board and senior leadership took immediate action. They asked former U.S. Attorney General Eric Holder and experts from the law firm Covington & Burling to conduct a thorough investigation. After four months of review, this week they released their report, which you can read here.

People always deserve a second chance. Companies, not so much. I see no reason to use Uber again, especially when there are now many ride-sharing apps that are just as good.

Uber had a strong brand, and now they’ve undermined it. Uber had the best user experience, and now most ride-sharing apps have matched it.

Uber is still in more cities, but that’s less of an advantage than I first assumed. Austin went without Uber and Lyft for a year and the city’s roads didn’t descend into chaos. It was fine.

Maybe ride-sharing is a winner-take-all market as Ben Thompson has convincingly argued. But maybe ride-sharing is just one commodity feature in the future of transportation, and as these services are integrated into larger platforms like Apple Maps and Google Maps, Uber’s dominance will fade just as their differentiation has faded. (On the extreme side of this, some competition to Uber such as RideAustin already treat the infrastructure as nothing special, operating as a non-profit to serve drivers and riders.)

It may seem foolish to bet against a company with billions of dollars in revenue, but Uber has little competitive advantage in software to show for the huge investment and current loses. They have more drivers, but with frequent turnover, how loyal are those drivers? I took a ride with Fasten and my driver thought that signing up and driving with Fasten was so similar to Uber that perhaps Uber was even secretly running it.

Uber reminds me of the Trump campaign and administration: mistake after mistake, and they get away with it. But at some point the second chances have run out, and the problems will stick and have real consequences, taking the whole thing down.

Companies are not always built to last. Sometimes it’s unfair — products that never find the right customers despite the founders’ best intentions. But sometimes companies deserve to fail — mismanagement, bad products, and toxic culture.

Companies fail all the time. I hope everyone at Uber is ready with a new job when it’s Uber’s turn.

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.

Dave Winer writes today about how because of the way the Facebook news feed works, sometimes you never seem to hear from friends again because they’re demoted by the algorithm. Your friends are posting, but you never see what they’re saying. Also:

For other people you are a missing person. You being the person who dutifully informs all your Facebook friends of what's going on in your life. You, the friend they never seem to think of. No surprise they're not thinking of you. The Algorithm decided you don't count.

If you want to see this in action, visit Facebook in a web browser and see what it shows you. Don’t scroll or click anything, just wait a few seconds and hit reload. Then hit reload again. And again. Each time you’re presented with a completely different view of what’s important. It’s unusable.

I know there are so many great podcasts that it’s difficult to listen to everything. I’m still making my way through all the commentary about WWDC. But I just finished Jeff Veen’s Presentable episode 25 this week and particularly enjoyed it.

Jeff talked to Jeremy Keith about his new web design book, and about the web industry repeating the same old mistakes, with a really great discussion about the IndieWeb. When asked about how people prefer to post on a social network, because maybe fewer people will find their own site, Jeremy said:

I always get frustrated when people talk about this as a reason not to do something. For me, that was the whole point of the web — that nobody was stopping you. You're right, maybe nobody will read this thing that I've published, but I could publish it and nobody was stopping me. To see people stop themselves, to act as their own gatekeeper...

There’s much more that I can’t capture in a truncated quote. Highly recommend listening to the full interview in context.

We just posted a new episode of Core Intuition. From the show notes:

Manton and Daniel compare notes on recent MacBook Pro repairs and the relative merit of purchasing AppleCare. They react to Tim Cook’s admissions that an Apple “car” project exists and is still underway. Manton looks on the bright side of “Planet of the Apps,” and Daniel looks on the dark side. Finally, they talk briefly about the controversy around an excerpt from “One Device,” by Brian Merchant.

There’s still a lot to cover from WWDC. It’s a good time to be a Mac or iOS developer.

Because I don’t follow anyone on Twitter, about once a week I’ll randomly click through a few Twitter user profiles to see if I missed anything interesting. Usually the answer is no. If something important is happening, it’s also being discussed in more detail on blogs, and I’ll see it.

Yesterday I checked on the last tweets of a few developer friends who stopped posting either after the election or on inauguration day. I have a lot of respect for anyone who makes a quiet, peaceful stand on principle. It’s not easy to go against the flow.

The 2016 election was a disaster. It still hurts to think about it. I keep telling myself and others: heads down, keep working. I have to believe we can get through this.

Today another story exploded on Twitter: a shooting at a congressional baseball practice. If you had clicked through from the trending links on Twitter this morning you’d have seen the worst speculation, misinformed partisan tweets, and unhelpful “facts” before we knew what really happened. When we should all be striking a solemn tone for the injured, the tweets instead quickly turn dark.

For a service that prides itself on breaking news, Twitter is an absolute dumpster fire in times like this. The best of Twitter is the thoughtful tweets and discussion, connecting new friends and diverse opinions. When real news breaks, the service runs uncontrolled, in fits of nervous energy and hate. It’s a terrible place.

Micro.blog will never have trends, search, or even retweets until we can elegantly solve this. The world doesn’t need another platform with so much manipulative power.

When I was in San Francisco last week, I visited the Eyvind Earle special exhibit at the Walt Disney Family Museum. Eyvind was a background painter and concept artist on Sleeping Beauty and other 1950s Disney features. I love this series of small paintings he made to train his assistants:

Today, something like this would be done digitally in layers. In 1959, he had to paint each layer multiple times to fully demonstrate the technique. No shortcuts.

At WWDC last week, Apple introduced changes to their RSS feed extension for podcasts. Before reviewing the session, I was worried that Apple would be moving to Apple News Format instead of RSS. That would’ve been a major setback for the open web, since Apple News Format is such an app-specific, closed format, controlled by a single company. Luckily the actual changes Apple introduced are pretty minor and shouldn’t upset the status quo much.

There are 2 sets of changes: support for supplementary episode types, like bonus content; and metadata for show seasons, likely influenced by popular shows like Serial, where people new to podcasts might be confused about where to start listening. There are a few new tags for these types of shows under the itunes RSS namespace.

Episode type is the simplest change. It looks like <itunes:episodeType>full</itunes:episodeType> and can have values “full, “trailer”, or “bonus”.

For seasons, the episode number and season number can be split into separate elements. It’s compatible with the traditional RSS title, so there’s little downside except extra clutter in your RSS feed. Here’s an example:

<channel>
  <itunes:type>serial</itunes:type> <!-- or "episodic" -->
  ...

  <item>
    <title>S01 Episode 01: The First Episode</title>
    <itunes:title>The First Episode</itunes:title>
    <itunes:episode>1</itunes:episode>
    <itunes:season>1</itunes:season>
    ...
  </item>

</channel>

Jason Snell’s first reaction to these changes was positive:

I’m excited by these changes because, yes, some of my podcasts are seasonal and are best consumed from the first episode onward. I’ll be adjusting my own podcast feeds to take advantage of Apple’s extensions as soon as it makes sense to do so.

Ben Thompson covers the extensions briefly and then focuses his weekly article on analytics and podcast advertising:

The new extensions are a nice addition, and a way in which Apple can enhance the user experience to the benefit of everyone. As you might expect, though, I’m particularly interested in the news about analytics. Problem solved, right? Or is it problem caused?

After reading Ben’s take, I don’t think these changes are significant enough to have much effect right away. That should be a relief to all of us who love podcasts and don’t want a shake-up.

When designing JSON Feed, we resisted adding everything that Apple Podcasts needs to the official spec. Now that more podcast tools have adopted JSON Feed, I expect there to be a discussion among developers about the best path forward for podcast-specific extensions in JSON Feed. That discussion should now include support for show seasons, too.

On Core Intuition last week, I said San Jose was “more confined” than San Francisco. I meant that mostly as a good thing, although I do miss the open spaces in San Francisco: the parks and incredible views near the water. Gus Mueller has a post about how San Jose felt closer together and less crowded:

In San Jose you had a clear view of the sidewalks and you generally knew who was a developer and who was a local. And because it wasn't so crowded, you ran into people all the time. You didn't have to organize meetups, you just kind of went out and you knew you'd run into someone to hang with.

Gus was also a guest with Marco Arment on The Run Loop podcast. They talked a lot about the different feel of WWDC in San Jose. Seems a universal opinion that San Jose is a good fit.

“We remember what happened last year and how it felt in that locker room. We used it and built on it. And got back here. It’s amazing. It makes last year okay.” — Tim Duncan, after game 5 in 2014

I said on Technical Foul last year that the championship wouldn’t mean as much to Kevin Durant if he won in Oakland instead of Oklahoma City. But there’s something I didn’t realize until these playoffs: maybe it’s not going to mean quite as much to the rest of the Warriors either, compared to if they had won without Durant. Compared to if they had come back with the same team again, as the Spurs had done in 2014 after letting the series slip away the year before.

Kevin Durant was the obvious finals MVP tonight. He was the reason — with help from Zaza Pachulia taking out Kawhi Leonard — that the Warriors coasted through the first few rounds of the playoffs. He was the reason that LeBron James could average a triple double for the finals and it still wasn’t enough.

It was a good NBA regular season. It was a good last few games of the finals. But the playoffs were disappointing to many people because it didn’t look like the Warriors were going to have to work very hard to win. It wasn’t the comeback story it would’ve been without Durant. I’m hoping next year will be different.

Federico Viticci reviews the new 10.5-inch iPad Pro at MacStories. On the screen size:

While some had assumed that Apple would take the same 2732 x 2048 display of the 12.9” iPad Pro and condense it to a smaller size, the company has introduced a new resolution in the iOS device matrix – a decision, I think, made to hit 264ppi on a 10.5” panel while retaining UI elements that are large and comfortable to tap. Cramming the large iPad’s display in this model might have resulted in a richer multitasking experience at an even smaller scale, but I believe touch usability would have suffered.

I assumed until reading Federico’s review that when my 12.9-inch iPad Pro was ready for an upgrade, I’d downsize to the new 10.5-inch. That no longer seems like a good choice. While my MacBook Pro is getting repaired this week, I’m using the 12.9 as my exclusive computer. The extra resolution in split view is really great. I don’t think I’d want to give that up.

Three years ago I wrote that Apple should end the App Store top 200 lists, learning from Beats Music how to double down on curation:

I wrote about Beats Music earlier, how it underscored to me that Apple needs to find the next product category to fall in love with, just like they used to feel about music. Of course we know that Apple already loves apps. Show that by doubling down on featured apps, staff picks, and app playlists.

And:

Apple shouldn’t wait until Thursday to feature a few great apps. Feature apps all the time. They’re on the right track with some of the “best of” sections in the store, and with the “Near Me” feature. Go a little further and it will make all the difference to bubble up great apps, and let the junk in the App Store fade away.

I think they’ve done it for iOS 11. While the top charts aren’t completely gone, they no longer dominate the App Store user experience. Featured apps are center stage.

Product manager Pedraum Pardehpoosh at WWDC even used the same phrase “double down” when describing Apple’s new focus on editorial content. During session 301, he said:

We thought this was a perfect time to double down on the editorial curation that’s distinguished the App Store since its conception.

Joe Cieplinski addresses the information density in the new App Store, pointing out that apps will be featured every day:

That’s a big change from the weekly update schedule Apple has maintained since the beginning of the App Store. You can’t name something “Today” and then not update it every day. So instead of a few new items getting featured once a week, something new will be featured every single day.

The “Today” tab is effectively a blog: reverse-chronological posts about what’s noteworthy in the store. It’s a much better default UI for content that is actively curated.

The old App Store was designed like a database. Databases are good at showing grids and lists from an algorithm. But the App Store should tell a story about new apps. A blog-like format is the best way to do that.

This plays to Apple’s strengths in design and taste. Where Google might hire more engineers to improve their store, Apple should hire more writers.

So far I’ve only used the new App Store on my iPad, and only for a few days. After we’ve all lived with it for a few months, it will be easier to judge whether it works for developers. But it’s almost exactly what I was hoping for a few years ago. This redesign for iOS 11 is one of my favorite things to come out of WWDC.

It’s WWDC week. I’m back home after a short week in San Jose. Monday’s keynote was a big event, with great news for Mac and iPad users, but I keep coming back to the most surprising “miss” in all of the announcements, and the one thing that I thought was surely a lock for the conference: SiriKit.

When I was on The Talk Show last week with Brent Simmons, John Gruber wrapped up the episode by asking about expectations for WWDC. I’m a big fan of the Amazon Echo, and I think Siri is behind in responsiveness and extensibility. I predicted at least 20 new domains and intents for SiriKit, if not a more open architecture that could grow into as big a platform as Alexa’s thousands of skills.

This week should’ve been a great one for Siri. Instead, we got not the hoped for 20 new domains but literally only 2, for taking notes and managing to-do lists. HomePod will have no support for apps at all, and it will initially ship only into a few English-speaking countries, erasing the traditional advantage Siri had over Alexa for localization.

There are good ideas in SiriKit. I’m excited about experimenting with creating “notes” in my app, and I like that in session 214 and session 228 they highlighted some of the new tweaks such as alternative app names and vocabulary. But there has to be more. Siri deserves several sessions at WWDC and much more attention from Apple.

Voice assistants represent the first real change in years to how we interact with computers, perhaps as important as the original graphical user interface. The company that created the Knowledge Navigator concept video should be firmly in the lead today. A year from now, at WWDC 2018, the lack of significant improvements to Siri will have stretched to 2 years, and that delay is going to look like a mistake even to Siri’s most vocal defenders.

We posted a new Core Intuition this week about WWDC. From the show notes:

Daniel and Manton catch upon WWDC, and Manton’s ailing MacBook Pro. They talk about new hardware announcements and react to highlights from the Keynote. Manton laments Apple’s continued, slow progress with SiriKit, and Daniel is frustrated that HomePod is not a Wifi hub. Finally, they talk about iOS Drag and Drop and compare it with Apple’s traditional tendency to move slowly but surely into the future.

After we recorded, I watched the first episode of Planet of the Apps, and started to get into more of the conference session videos. We’ll be following up next week on more from WWDC.

Jean MacDonald was on the latest episode of Collin Donnell’s new podcast The Run Loop. They talk about App Camp For Girls, Micro.blog, Portland, and more, with a preview of Jean’s talk at CocoaConf Next Door. It’s a great episode to queue up before WWDC.

And a related reminder: we’re having an informal meetup on Tuesday at lunch for anyone interested in independent microblogging. Sign up for more information here. Hope you can make it and say hi to me and Jean.

Brent Simmons and I were guests on The Talk Show this week. We talk about JSON Feed, Userland Frontier, Micro.blog, and much more.

Brent also announced Evergreen for the first time on the show. Evergreen is a new open source feed reader for the Mac. I’m really looking forward to where this app could go.

One quick correction as I’m re-listening to the episode. For some reason I said that I became interested in Frontier when it pivoted to be open source software. I meant free, not open source. I worked with Frontier in the mid-90s, around the 4.0 release that Brent mentioned, and as I blogged about back in 2004 when Frontier’s kernel was actually open-sourced.

It was fun to revisit this era of Mac scripting on The Talk Show, and I hope that when we look back on the origin of JSON Feed we have similar good memories. There were a bunch of people who made the format what it is, participating in debates about field names and scope. It all contributes to the traction that JSON Feed is getting now.

JSON Feed includes an attachments array, which is similar to the enclosure element in RSS that enabled podcasting. We love podcasting and included an example podcast feed in the JSON Feed specification. However, because the Apple podcast directory and its RSS namespace are so central to many podcasting tools, it wasn’t clear how quickly podcast apps would adopt JSON Feed.

The answer is: pretty quickly. This week we’ve seen announcements from Breaker, Cast, and Fireside. Actually not just announcements, but working implementations to parse or generate JSON.

I’ve also pushed up a change to the WordPress plugin on GitHub to add support for attachments. After some more testing, I’ll update it in the WordPress directory.

Update: FeedPress also just announced support for JSON Feed. This is another important one for bloggers and podcasters. It effectively gives a JSON version to everyone using FeedPress, even if the FeedPress customer’s site is still backed by an XML feed.

Dave Winer posted today about NetNewsWire needing better support for title-less feed items:

These items have no titles for artistic reasons. The author did not put them there. You, as a software developer, are not entitled to add them (haha that's a pun).

I agree with Dave on this. Titles are clearly optional in the RSS 2.0 spec. The fix for the “Untitled” text that some feed readers use isn’t for authors to add titles where they aren’t needed, it’s for the UI in feed readers to improve so that they gracefully handle title-less posts.

(And this is not to pick on NetNewsWire. I’ve seen other apps and feed syncing services with the same assumption about titles.)

When I wrote about defining a microblog post, blank or missing titles was one of the fundamental points. If we want to have blogging software that’s as easy to use as a modern social network, titles can’t be required.

I’m hopeful that as feed readers adopt JSON Feed, developers will dust off their older code for feeds and make improvements for title-less RSS items as well. This is why we highlighted microblogging as a use case in the JSON Feed spec.

WWDC is only 1 week away, but I have another event on my mind as well: IndieWeb Summit in Portland, June 24th - 25th. From the description for the 2-day conference:

The seventh annual gathering for independent web creators of all kinds, from graphic artists, to designers, UX engineers, coders, hackers, to share ideas, actively work on creating for their own personal websites, and build upon each others creations.

I’m still trying to figure out if I can make it. If you care about indie blogging and open formats, consider attending. I had a great time in Portland earlier this year meeting more of the IndieWeb folks. They are leading some of the most important work on simple formats and protocols, with a focus on personal web sites instead of silos.

This week we added a selection of photos to the Discover page on Micro.blog, and today I uploaded a new TestFlight beta with the same feature inside the app. It’s another way to find users to follow, or just see what the Micro.blog community is up to.

Here’s what the iPhone screen looks like:

I think photoblogging is a really important part of indie microblogging. When I share photos online, I want them to be at my own web site in addition to cross-posted to Twitter and other social networks. Photos always capture something — a moment with family or friends, visiting a new place, or just the everyday routine as it changes — and I want Micro.blog to provide a great user experience for photos, from filters to hosting.

I’ve been impressed with how quickly people have adopted JSON Feed. There are a bunch of feeds in the wild now, as well as code and templates for popular languages and web frameworks. The next step is support in feed readers, including brand new feed readers, which is already happening.

Feedbin and NewsBlur both added support for JSON Feed. I like how Feedbin’s Ben Ubois puts it:

One of the criticisms I’ve seen of JSON Feed is that there’s no incentive for feed readers to support JSON Feed. This is not true. One of the largest-by-volume support questions I get is along the lines of “Why does this random feed not work?” And, 95% of the time, it’s because the feed is broken in some subtle way. JSON Feed will help alleviate these problems, because it’s easier to get right.

Micro.blog can also read from JSON feeds. I’ll be switching over all the hosted sites to prefer JSON. I’m doing that slowly to make sure there aren’t any issues with duplicate posts. (There shouldn’t be, but it’s something to watch out for with self-hosted sites if your post IDs change.)

The WordPress plugin is almost in the WordPress directory. I’ll link to it as soon as it’s live, because it will make installing the WordPress plugin much easier.

I talked with Ben Brooks over Slack this week about Micro.blog and JSON Feed. From the chat:

Micro.blog and JSON Feed share a common goal, which is to encourage more blogging on the open web, and new tools that can make blogging easier. I feel like we’ve gotten off course a little since the early days of blogging, with so many people now putting all of their writing into closed, centralized platforms like Twitter or Facebook. I think we can make it easier to own your own content, have your own domain name, and maybe learn from the UI in modern social networks too.

Slack makes for a really interesting interview format. Some of the spontaneity of a podcast, but with live editing and an automatic transcript. Similar to what Talkshow.im was trying to do before they shut down.

I want to point to some developer activity in the Micro.blog community. The first is a macOS Today Widget called TodayPoster by Bryan Luby. It gives you a text box to post directly to Micro.blog-hosted blogs from the macOS Notification Center.

The next is a Mac client built with Electron. Developer Matthew Roach has a blog post about it with a download link.

There’s another iPhone app in development as well. It’s not ready yet, but from a screenshot by Francisco Cantu, looks like it will be a good alternative to the official Micro.blog iPhone app.

We just posted episode 283 of Core Intuition, with thoughts on last week’s JSON Feed announcement and more. From the show notes:

Daniel and Manton discuss the new JSON Feed format and initial public reaction to it. They talk about Panic’s source code being stolen, and Daniel celebrates/laments his new MacBook Pro.

Brent Simmons was also interviewed on Collin Donnell’s new podcast, The Run Loop. Brent talks about some of his previous apps like NetNewsWire and Glassboard. Then they cover what JSON Feed is and where it could go.

Really excited to announce JSON Feed today with Brent Simmons. It’s great to see all the feedback and links to new feeds. Special thanks to everyone who contributed to the spec, debating field names and requirements over the last few months.

The premise was simple: the time is right for a JSON-based approach to feeds. We hope that JSON Feed is straightforward enough to be implemented quickly, and capable enough to push the next decade of blogging software forward. We love RSS too and tried to learn from its success.

Micro.blog already supports JSON Feed nearly everywhere. There are feeds for hosted microblogs and your timeline, and the Micro.blog custom JSON API itself is actually just JSON Feed with Micro.blog-specific extensions.

I’m looking forward to seeing what everyone does with this. If you’ve shared any code or templates for JSON Feed, or if you’re working on apps to support it, let us know.

Kirby Turner has a detailed write-up on his workflow for posting from his iPhone. It uses a combination of Editorial, Working Copy, and Jekyll:

The workflows save me time and simplify the publish steps. For instance, Jekyll uses YAML as front matter for each post. There’s no way I want to write this front matter by hand on my iPhone each time. I can use TextExpander, but seeing the front matter can be distracting on my iPhone. So I let Editorial’s workflow work its magic to generate the YAML front matter before handing off the document to Working Copy.

Check out his embedded video for what it looks like in action. I love Jekyll, and it’s a big part of Micro.blog, but there’s no denying that the nature of static sites makes mobile posting more difficult. Looking forward to seeing more iPhone workflows like this that make microblogging easier.

After a couple months away from Timetable, because I’ve been focusing so much of my time working on Micro.blog, I’ve finally returned to the microcast for a sort of second season. Timetable will be published daily now, Monday through Friday, to chronicle the actual release of Micro.blog and the Indie Microblogging book.

Episodes 38 and 39 are out now. You can subscribe in Overcast or iTunes.

538 started a nice series on the case for each of the top 5 MVP candidates. But my favorite MVP article is Matt Bonner’s sandwich analogy for The Players Tribune:

You’re probably getting hungry as you’re reading this, and maybe you’re even thinking about making a sandwich of your own. And that’s smart. Your head’s in the right place. Those ingredients sound really good. The fixings are crucial — and you can’t have your best possible sandwich without them.

It’s not all jokes, though. Matt’s insight into the Spurs system, where you move the ball instead of hogging it, puts Kawhi’s 25.7-point average in perspective:

And since there’s so little ball domination in that system … it makes it pretty impossible for any one player to put up a huge scoring average. Even Tim Duncan — arguably the greatest power forward to ever play the game — never had a season in which he averaged 25.7. And that’s really all you need to know.

Last night, the Spurs lost in Portland by 1 point. It was a game that didn’t matter much, so the Spurs bench finished the game. Portland’s win was mostly a fluke — a Spurs turnover at the end, then a steal that was mishandled and fell to Blazers’ Noah Vonleh for the buzzer-beater layup. But here’s the important point: the Spurs probably wouldn’t have lost if Kawhi was in the game for the final minute.

That’s not to take anything away from the bench. Those guys are great. Living in Austin, we got to watch Kyle Anderson and Jonathan Simmons finish plenty of great games for the D-League. It’s just that San Antonio has played many close games this season, and this is what happens when Kawhi is in the game late.

I’ll be shocked if Russell Westbrook doesn’t win MVP this year. But any of the top 5 candidates deserve it, and Kawhi is focused on other things. Maybe it’s fitting that the award will end up going to a player like Westbrook and his fans who seem to care so much about whether he wins.

We published Core Int 277 today with thoughts on the Mac Pro and more. From the show notes:

Daniel and Manton react to Apple’s surprisingly transparent “roundtable” meeting with several members of the press, and celebrate the many positive signals coming out of the event. They engage in a friendly debate about the likelihood that Mac users will defect to Windows. Finally, they talk about the merits of professional software, and the negative impacts that a poor market for such software may be having on iOS as a platform.

As I say on the episode, I wouldn’t have been disappointed if Apple had officially discontinued the Mac Pro, as long as that meant a greater focus on other things for pro users. I’d like for Apple to have a Mac-based answer for Microsoft’s tablets and Surface Studio, for example.

Last Friday we published Core Intuition 275. From the show notes:

Daniel and Manton talk about Manton’s decision to hire Jean MacDonald as Micro.blog’s Community Manager, and the psychological effects of transitioning from a single to multi-person company. They also react to this week’s Apple announcements, focusing mainly on Apple’s new Clips app and how it relates to Apple’s historic focus on facilitating user creativity.

This episode captures the biggest shift for my business since I left my regular job a couple years ago. I’m also hoping to resume my Timetable podcast soon, since there’s more I’d like to talk about that won’t always fit into Core Intuition.

Earlier this month I flew up to Portland for a few days. It was a great trip. I posted about attending the Blazers game and meeting the IndieWeb group at the DreamHost office. I also sat down with Jean MacDonald to talk about what she has been up to and show her what I’ve been building for Micro.blog.

Today I sent an update to Kickstarter backers about the stretch goal promise I made to hire a community manager. I couldn’t be happier to announce that Jean MacDonald will be helping me in the next steps for Micro.blog.

It became clear as I’ve been talking with Jean that she will add so much to the project. Making the announcement today has inspired me even more to finish rolling out Micro.blog and to see where the community takes it.

On last week’s Core Intuition, I told Daniel that the approach for Micro.blog has to be different than for my previous apps. It’s such a big opportunity that if I don’t focus everything on it, then it will not work. I covered the same theme in a post last month:

I’ve realized as I work toward launching Micro.blog that this product is different. It has a much greater scope than anything I’ve built by myself. To be successful, it needs a team.

No single decision will guarantee success. But today’s announcement is a big milestone for Micro.blog because it’s more than a promise or hope for things to come. Jean’s experience will be essential to guiding the community and moving the platform forward.

Stephen Hackett marked his 10th anniversary of using Twitter by writing about how great Twitter has been for connecting people. Of course, the company’s problems are also well known:

The company itself seems to struggle in getting even basic decisions right. I often joke that Twitter may be doomed, but I don’t say it in pure jest.

He made a similar joke on Connected 133 that Twitter will be gone in 5 years. I think it’s a toss-up. But one thing I’m pretty sure about: the hate tweets and harassment problems can’t be fixed by waving a magic wand. They are fundamental and must be planned for at the beginning.

App.net officially shut down last night. As I wrote about earlier this year, App.net was an important milestone in the move to more open social networks. I’m glad the platform existed and I enjoyed participating there as a user and developer.

Linkrot and the lack of permanence on the web is a recurring theme for this blog. In the final days as App.net was winding down, I wanted to put my money where my mouth was. I spun up a couple new servers and wrote a set of scripts to essentially download every post on App.net. It feels like a fragile archive, put together hastily, but I believe it’s mostly complete. I’ve also downloaded thumbnail versions of some of the public photos hosted on App.net.

I’ll be making the posts available somewhere, although I don’t know exactly what form the archive should take yet. I’ll also be considering whether to integrate it with Micro.blog, for anyone who wants to migrate to a new microblog and didn’t have time to manually export their posts. (I’ve already built a similar feature to import from Twitter’s .zip archives.)

To my Kickstarter backers, thanks for your patience as I took an unexpected detour this week. Major work on Micro.blog continues. I have a big announcement for next week and invites should be ready the following week. I’ll post an update to Kickstarter soon.

Fifteen years ago today I started this blog during SXSW. Although I didn’t think much of it at the time, because Twitter hadn’t been invented yet, my first post was essentially a microblog post. 145 characters and no title. (Titles on the old posts were added later during the migration to Movable Type.)

I’ve written about 1100 posts since then, and another 600 microblog posts. Some of my favorites last year:

• Twitter at 10 years. Reflecting on the state of Twitter and where to go from here.
• Today's social networks are broken. Partly a mission statement for Micro.blog.
• Core Intuition 259 transcript. Daniel and I discussing Apple's new design book after the election.
• Proud to have voted for Hillary. Still pretty upset about November.
• Podcasting lock-in and the lesson from Penn Station. What happened to Penn Station in New York, and similarities between podcasting and blogging.
• Kapeli's suspension is a test for Apple. One of many posts about App Store rejections. Apple's power over indie developers is a recurring theme.
• Apple apologists. There's no need to defend Apple when they make mistakes.
• Blog when you disagree. Why blogging longer thoughts is still very important.
• Is this even possible? Visiting a new coffee shop every day for a month. After that I worked from libraries.

And the year before:

• A great developer can come from anywhere. This was not universally loved when I published it, but it seems to have outlasted the controversy. One of the best things I've written in a while.
• Every device needs the web. Reacting to the lack of WebKit on tvOS.
• Marketing, mission, movement. The best marketing is creating products that people can believe in.
• Two weeks notice. Not a single post, but a bunch of posts with the #2weeks tag, chronicling my work and thoughts as I quit my regular job after 14 years.
• I think it's a bust. My thoughts on Swift not addressing the problems I have. Essentially still true.
• Don't solve everything. I avoided trying to figure out cross-site replies. And now we have Webmention.
• Why Ello isn't enough. Purely centralized will never last.
• WWDC 2015, basketball, and cartoons. My trip to San Francisco.
• Jordan Breeding. Remembering and being inspired by others.

And earlier:

• The unremarkable yesterday. Why I like to blog and write in a journal.
• Defining a microblog post. A few guidelines that are simple enough to last.
• The third era of WWDC. Written in 2014, but appropriate again with the move back to San Jose.
• Ending the App Store top 200. Curation and learning from Beats Music.
• Waiting for App.net's killer app. I was very hopeful about App.net. Shortly after this we shipped Sunlit.
• What the Tweet Marker award means. Most of my Tweet Marker posts are technical and not worth re-linking. This one is a little more timeless.
• Permanence. Reading this again several years later, I can't believe it's taken me this long to build a publishing platform.
• Carousel. That great scene from the first season of Mad Men.
• 30% of the future. From 2011, so on first glance it doesn't seem to age well. After all, services are an important part of Apple's business now. But I think I was right.
• Healthcare fallback plan. 8 years ago was a very different time politically. Includes some quotes I still like.
• Go without food. On sacrifice and finishing your projects.

Whether you started visiting this blog years ago or just today, thanks for reading. I hope to still be writing in another 15 years. (I’ll be 56 years old. My kids will be grown up. Nearly everything will be different.)

Stretching time out has a way of highlighting what matters. And if it matters, it’s worth writing down. I hope you’ll join me for the next chapter as I try to move indie microblogging forward with Micro.blog.

Ben Thompson’s daily update email today covers fake news and algorithms. It’s a great post, although a little disheartening in the way that most coverage of filter bubbles and the election tend to be. One line in the closing paragraph:

Algorithms have consequences, particularly when giving answers to those actually searching for the truth.

It mirrors something I wrote in January about algorithms and curation:

Software has consequences. How it’s designed informs what behavior it encourages. If it’s built without thought to these consequences, it will succeed only by accident.

Quick posting via retweets on Twitter and re-sharing on Facebook contributes to the spread of fake news. As the New York Times article Ben links to says, fake news is “designed to attract social shares and web traffic”. Bad news stories with dramatic headlines can spread more quickly than they would if everyone posted an original comment with their link.

It’s too easy to click a retweet button without thinking. Fake news is as much a user experience and design problem as it is an algorithmic problem.

From last week’s flight through Los Angeles and up to Portland.

I’ve been working on a post about walled gardens, the App Store, and social networks. I think it could be an important essay — a new take on the future of platforms.

But if it’s not? If I’m wrong, and the idea is unoriginal or doesn’t go anywhere? That’s fine too! It’s just a blog post.

I love that blogs can scale from the trivial to the important. The microblog post about what you had for breakfast. The half-baked rant about something you’re passionate about. And sometimes, the rare essay that really hits the mark and makes people think.

Uber has been in the news lately, and not in a good way. I’m taking a short trip this week and decided to more actively look for ride-sharing alternatives. I’ll be trying Fasten in Austin and Lyft elsewhere.

One nice discovery in this search: Lyft produced a wonderful animated short film called June. It’s directed by John Kahrs, who as I blogged about a few years ago did Paperman at Disney.

I’m still annoyed that Lyft joined with Uber to first actively campaign against regulations in Austin and then ultimately left the city. But Lyft funding a film like this makes me feel better about supporting the company. There’s also a behind-the-scenes video.

Ten years ago I wrote a post about customer support. Nothing in my attitude toward customers has really changed since then, although my products have changed along the way.

Most of my Mac and iOS apps could be built by one person. Even Sunlit, which I developed with Jon Hays, could be maintained by one person. And so when providing support for my apps, I’ve always embraced being an indie company and said “I” instead of “we” when talking about my company Riverfold Software.

I’ve realized as I work toward launching Micro.blog that this product is different. It has a much greater scope than anything I’ve built by myself. To be successful, it needs a team.

This is why my first priority with the Kickstarter stretch goal was to bring someone new to the project. I was initially nervous about making that announcement. I thought that nervousness was because the stretch goal might not work, or because my post was long and could be misinterpreted, but I realize now that I was nervous because I knew it mattered.

The first decisions a new company has to make will end up shaping many things that follow. I worked at VitalSource for over 14 years because the technology decisions and leadership at the beginning were so strong they carried forward for years.

The same rule applies for a very different kind of company: Uber. When you look at their series of missteps, it seems clear that these are inherent problems that go back to day one. I think John Gruber is right when he says Uber’s response is “too little, too late”.

We can learn from every company culture that fails. I don’t expect to make all the right decisions with Micro.blog. But I’m going to try very hard to make the first decisions correctly, because it will make everything easier going forward.

Back in July, I posted this to my microblog, which was cross-posted to Twitter for some additional discussion:

Not shocked that Swift classes won’t be subclassable by default. But it underscores Swift’s priorities. And for that reason, I’m out.

The “I’m out” was meant as a Shark Tank reference, and not to be taken too seriously. But I was serious about taking a break from Swift until version 4, when it would at least be more stable. Daniel and I followed up that week with a more in-depth discussion on Core Intuition 242.

A few days ago Craig Hockenberry posted about how the rapid pace of improvements to Swift can get in the way of learning the language and using example code:

It’s gotten to the point where every time I come across some information written in Swift, especially on Stack Overflow, I cringe. I know that I’m going to have to not only figure out the code, but also which version was used for the answer.

I have absolutely no regrets sticking to Objective-C. As Swift 3 was wrapping up, it seemed that the churn around syntax changes was even worse than I feared. From an Apple dev forums thread at the time:

For the expected quality of software in a third-generation project in late Beta, Swift 3 has become a trainwreck of Microsoftian proportions--at least in terms of process and expectation. Many of us devs are spending 90% of our time not developing our app, but babysitting Swift and trying to understand so many unvetted changes.

That settled down with the final Swift 3 release, but I expect many developers won’t upgrade from Swift 2.3 until Xcode forces them to. There’s even a whole book by Erica Sadun on migrating code.

I still consider Swift a beta language. I just hope that the Swift team and community recognize that this level of instability isn’t acceptable forever. A programming language is not an iOS or macOS release. There shouldn’t be a new major version of Swift every year.

I have a tradition when I go to San Francisco for WWDC. I arrive early on Sunday before the conference, drop my bags at the hotel, and take a cab to the Presidio. The weather is usually beautiful. I visit the Walt Disney Family Museum, maybe sit in the grass with a coffee, then go for a walk to take in views of the Golden Gate Bridge.

I’ve done this the last handful of years. It’s always a perfect reset to whatever stress was happening with my own coding projects and business. You can find blog posts and tweets from past years.

I attended WWDC in San Jose a few times. Moving WWDC back there will probably end up being fine. If you’re at the convention center, or hanging out with attendees at a restaurant, or taking a break to work at a coffee shop around the corner, or even going to a party — many cities will suffice for that. I’m sure the conference will be great.

I’ll still miss San Francisco. I know it’s not a perfect city. But it’s historic and unique. That’s why I recorded a podcast episode about it over 10 years ago, and I’ve learned much more since. I always get something out of the trip.

I use Twitter much differently than most people. I haven’t returned to my @manton account in over 4 years, and instead I cross-post all my blog posts to @manton2. I reply and like tweets when I get mentions, but I don’t actually follow anyone.

But despite this weird use of Twitter, I follow the company closely and still maintain the Tweet Marker timeline syncing API. So I’m excited to see Iconfactory launch a Kickstarter campaign to fund new work on Twitterrific for Mac.

I’ve backed the project. It’s a good opportunity to support one of the pioneers of Twitter development.

Great post from Paul Kafasis of Rogue Amoeba about Piezo sales for the year after leaving the Mac App Store, and how it suggests that Dash’s post-MAS sales weren’t a fluke. Rogue Amoeba’s data points to this key point:

Far from the Mac App Store helping drive sales to us, it appears we had instead been driving sales away from our own site, and into the Mac App Store.

For me, the question of whether to use the Mac App Store is also closely tied to using in-app purchases in addition to Stripe. As I work to get Micro.blog shipped to Kickstarter backers, and eventually launched to a wider audience, I’ve wondered whether there should be an in-app purchase to make subscribing to Micro.blog from iOS easier. Of course the Mac App Store and in-app purchases are different things, but both require juggling multiple payment systems with the hope that it will be easier for users.

And it would be a little better for customers in the short-term. The problem is that it would be much worse for me as a solo developer trying to do too much. The backend systems would be more complicated, and I think the product would suffer because of it.

I’m taking some time to resume Timetable recording. From the latest episode:

Now that the Kickstarter campaign has wrapped up, I move to the next phase of getting Micro.blog ready, planning for invites, and focusing on the Slack community.

I started Timetable over a year ago to document what it was like to build Micro.blog and figure out how to launch it. Each episode is about 4-5 minutes long. Reaching this point with the Kickstarter finished is a huge milestone, but there is plenty of work still to do and talk about.

Twitter made an announcement today about stopping abusive accounts and hiding low-quality tweets. I think filtering search results in particular is a very good step in the right direction:

We’re also working on ‘safe search’ which removes Tweets that contain potentially sensitive content and Tweets from blocked and muted accounts from search results. While this type of content will be discoverable if you want to find it, it won’t clutter search results any longer.

As I work on Micro.blog, I’ve tried to be mindful of where users can stumble upon posts that they don’t want to see. Replies is a big one, and I’ll be focusing most of my attention on that. But search, trends, and hashtags are also a problem, because they let anyone’s posts bubble up to a much wider audience. I’m launching Micro.blog without them.

Twitter and Facebook are both powerful tools to help people organize. We’ve seen some of that over the last few weeks of protests. While these social networks are also broken in significant ways, they’re not all bad. They bring people together and expand the reach of posts from our own web sites. That’s why many people embrace cross-posting.

Even more important is the free press. Not just big sites like the New York Times and Washington Post, but also small sites like yours and mine. Trump will continue to attack and undermine the mainstream press. Everyone who publishes on the internet should consider where that leads.

It’s not a good foundation to concentrate so much writing into one place like Twitter or Medium. Distributing writing across more web sites protects us if one massive site shuts down. It gives us flexibility to move to the next popular network if one emerges.

Sometime in the next 2 years, a reporter or blogger is going to break a story about the Trump administration. It’s going to be too important to ignore. But to be taken seriously, it can’t be an anonymous Twitter account that’s easy to cast doubt on. It has to come from someone accountable who has built a reputation by publishing good work and owning it.

Owning your content by having a microblog at your own domain is empowering. Maybe you’re writing about what you had for lunch. Maybe you’re photo-blogging an important trip. Maybe you’re posting from your iPhone at a protest outside the White House.

It doesn’t matter what it is. If it’s happening and worth writing about, it’s worth owning. Now more than ever.

Maybe you aren’t building a new social network. Maybe you aren’t obsessed with the rise and fall of tech giants. But if you are at all interested in why Instagram and Snapchat took off, check out episode 102 of Exponent with Ben Thompson and James Allworth:

Ben and James discuss the history of messaging apps, the rise of Snapchat, and why Instagram Stories was such a brilliant move.

I feel like I just had a whirlwind business school class in 57 minutes. So much of what they talk about is applicable to what I’m working on.

We posted this week’s Core Intuition today, with the latest Apple developer news and a debate on Alexa vs. Siri:

Manton closes in on the last week of his Kickstarter, and Daniel catches up on his progress. They discuss new beta updates from Apple for both Mac and iOS. They react to Apple’s forthcoming review prompting system for iOS, and the ability for developers to respond to reviews on both Mac and iOS. Finally, they debate the merits of Siri vs. Alexa on grounds of reliability and viability as an international, long-term success.

I haven’t kept up with Timetable recordings lately, but hope to do another one before the Kickstarter campaign wraps up too. Thanks for listening.

I’ve been following Seth Godin and reading his books for many years, but recently two of his statements caught my attention. The first is an older video episode with Gary Vaynerchuk, where Seth talks about why he has no presence on social media except automatic cross-posting of his blog posts.

The second is equally relevant to what I’ve been thinking about with Micro.blog. Seth says that we’ve surrendered control over how our software works to algorithms instead of human decision-makers who can take responsibility for mistakes. It’s too easy to blame the computer:

That person who just got stopped on her way to an airplane—the woman who gets stopped every time she flies—the TSA says it's the algorithm doing it. But someone wrote that code.

Algorithms are a shortcut. They should give us more leverage to go further, faster, not dictate where we go.

The social web is now permeated with algorithms. Today, Twitter again promoted what’s trending higher up in their app. That may be a step in the wrong direction. Trends can sometimes surface the better parts of Twitter, but they’re also an invitation to view the worst possible tweets you’ll ever see.

Let’s not be afraid to add curation by humans. That’s not an admission of failure. It’s an acknowledgement that algorithms are imperfect.

Software has consequences. How it’s designed informs what behavior it encourages. If it’s built without thought to these consequences, it will succeed only by accident. For 2017, one of my goals is to slow down and be more deliberate about features that can have this kind of impact.

Since I launched it over 3 weeks ago, thousands of people have watched my Kickstarter video, but I haven’t watched it again myself since that first day. I knew if I watched it I’d find new problems with it, and remember all the things I wanted to fix. It’s too late.

I had fun creating it. I wanted something with a hand-drawn feel, because to me blogging is about individual creative expression. It’s about not being afraid to publish something that isn’t perfect — something that is personal and a little rough, like a quick sketch.

Because I love traditional animation I wanted to draw all the frames with a pencil and paper, not digitally. Here’s me flipping through some of the drawings:

At 30 frames per second, doing any animation at all is extremely tedious, even with these little sketches. I made about a hundred drawings and scanned them in one at a time. I composited everything in Apple’s Motion, then ended up using Motion for sliding objects around and fading them in or out, which cut back on the number of drawings I would have otherwise needed.

The inspiration for introducing the video was the early 1920s-era Max Fleischer and Walt Disney cartoons, like Alice’s Wonderland. I also thought it would more naturally cut from me talking at the camera to illustrating the story of why independent microblogging matters.

I’m not sure whether I will ever do another Kickstarter campaign. But I hope to have the chance to make a video like this again. I learned a lot from it.

Kevin Hoctor has a great post about staying above name-calling and focusing instead on positive change during a Trump presidency. Standing up for people, exposing lies, and supporting the free press:

If you have a website, use it. Write more words than you can fit into a tweet. Call out injustice and hold your House and Senate representatives responsible for their actions and their voting. This is a marathon, not a sprint.

You’re not alone if you’ve been aimlessly reloading news sites all day for weeks. It’s easy to fall into a trap of indecision, failing to create anything, unsure of what to do next that will matter. I struggle every day to rebalance my time on the right things.

But to Kevin’s point, a marathon is finished one mile at a time. And I’ll add a quote from Steve Jobs, which I think about sometimes when I can’t focus on making real progress:

Everything around you that you call life, was made up by people that were no smarter than you. And you can change it, you can influence it, you can build your own things that other people can use.

Remember that Twitter was still in the middle of taking off 8 years ago when Obama was first elected. Not quite mainstream, no Trump account. We’re going to blink and it will be 2018 and then 2020. Everything can change again if we work to make it better.

Since I launched on Kickstarter, backers have asked if there should be a Slack community to discuss Micro.blog and related microblogging topics. I wasn’t sure. I know some people are already in multiple Slack groups, including the excellent IndieWebCamp IRC/Slack, and I also didn’t want to distract from any posts that should happen in the open on blogs.

Some discussion just fits better in chat, though. There’s an emerging community of indie microbloggers. Having a place to share tips, tools, and ask questions about Micro.blog just makes sense.

I’m experimenting with the Slack channel now, and I’ll be opening it to all Kickstarter backers next week. If you’ve backed the project before Monday, expect a backers-only project update with information on how to join.

This week on Core Intuition, Daniel and I talk about the halfway point to my Kickstarter campaign, running ads, and more:

Manton talks about marketing for the Kickstarter, how many people watch the video, and how to transition from marketing the passionate philosophical backers, to making a case for the sheer utility of the product. They talk about modern advertising technology that allows hyper-focused delivery, and follow up on Chris Lattner's departure from Apple, and the exciting opportunities he will likely have at Tesla.

The last segment of the show is about Chris Lattner going to Tesla. We recorded before we listened to the latest ATP, but our conversation still holds up as pretty relevant. Hope you enjoy it.

I was a guest on the latest episode of Release Notes this week. We talk about the Kickstarter launch of Micro.blog and more:

Today Manton Reece joins us to talk about Micro.blog, the new microblogging service that he’s developing. We talk to Manton about why he thinks a new microblogging service is needed, the importance of owning your own content, and his successful Kickstarter campaign.

Speaking of Release Notes, the conference is coming back for 2017 in a new city: Chicago. I haven’t been to Chicago in years, so I’m excited for an excuse to visit.

I blogged about my time at Release Notes 2015, but never got around to posting thoughts from 2016. In short: it was a great conference. For a snapshot of the talks, see Matthew Bischoff’s slides and Ben Norris’s sketchnotes.

Apple dedicated their home page to Martin Luther King today with a photo and quote:

Commit yourself to the noble struggle for equal rights. You will make a greater person of yourself, a greater nation of your country, and a finer world to live in.

When Apple does this sort of tribute, it’s a reminder of why we expect the best from Apple, and why we complain when they fall short. We hold Apple to a high standard because they’ve set the bar high for themselves, not just by building great products, but by not being afraid to stand for something.

Webmention has been on my radar for a little while, and I mention it in the Indie Microblogging text on Kickstarter. It’s great to see it go from an IndieWebCamp spec through the W3C process now as a standard recommendation:

The Social Web Working Group has published a W3C Recommendation of Webmention. A Webmention is a notification that one URL links to another and is a simple way to notify any URL when you mention it on your site. From the receiver’s perspective, it’s a way to request notifications when other sites mention it.

The replies on Micro.blog are kind of a stopgap while infrastructure like Webmention rolls out to more web sites. I think Webmention will become an important part of cross-site mentions.

There’s a lot happening at once right now. As I suggested in a microblog post yesterday, the first measure of success is whether more people are blogging. Meanwhile there are new formats and APIs like Webmention. You don’t replace Twitter overnight, or even try to. But step by step, we’re going to end up with a better web, and I think independent microblogging is part of that.

Dalton Caldwell and Bryan Berg announced the official shutdown of App.net today:

In May of 2014, App.net entered maintenance mode. At that time we made the difficult decision to put App.net into autopilot mode in an effort to preserve funds and to give it ample time to bake. Since then every dollar App.net has charged has gone towards paying for the hosting and services needed to keep the site running. Unfortunately, revenue has consistently diminished over the past 2+ years, and we have been unable to return the service to active development.

As I wrote about just last week, the founders of App.net deserve our thanks for trying something very difficult and succeeding beyond what anyone expected. I’m still amazed at everything they were able to do.

So, what now? I believe the next step for the open web and Twitter-like services is indie microblogging.

This isn’t the first time that David Smith has built something that I kind of wanted to build myself, too. Today he announced a cool side project for searching podcast audio:

You can easily search for a term or keyword and then play the actual audio back to find if it was the section you were thinking about. I even tag the sections with timecoded Overcast links for easy sharing.

I’d love to see David spin this into either a commercial product or set of free tools. He could host more shows, or let podcasters run their shows through PodSearch and export the results. For example, I’d want this for Core Intuition, along with edited transcripts eventually.

I started my microcast Timetable a little over one year ago. I’ve recorded 35 episodes, so fewer than 1 a week. My goal is still 2-3 a week, so hopefully I’ll work up to that for 2017.

This podcast is one of my favorite things to do right now. It’s so much easier to record and publish a 5-minute podcast than a 1-hour podcast. All I need is something to talk about.

Here are the feed descriptions for each episode over the last year, starting with the earliest. Reviewing these provides a neat snapshot into the journey of building Micro.blog. You can subscribe at timetable.fm.

1: On the first episode, I introduce the idea behind the show and the topics I hope to cover.

2: On this episode, I talk about trying tea instead of coffee, how I named this podcast, and my work schedule as I wrap up the week.

3: On this episode, I talk about finishing some work and the new iPhone microphone I bought.

4: This morning I was downtown to work at a coffee shop for a few hours before lunch. I talk about getting out of the house and last night’s icon sketches.

5: Today I stopped at the post office to pick up some stamps to mail stickers for the new microblogging app and platform I’m working on.

6: I start with some thoughts on basketball, my potential Kickstarter campaign, and whether it’s better to start strong or finish strong. (Go Spurs Go!)

7: This morning I was distracted a little with backups, ordering a new hard drive, and thinking about my iOS app, which was just rejected by Apple.

8: Recorded in 3 segments, I set my alarm early this morning to get some coding done before the day starts slipping away.

9: Today I mention the iPhone app rejection, talk about why the iPhone app itself is secondary to the web version, and reveal more about the Kickstarter.

10: I take the iPad Pro and my microphone out to the front porch, to think through what work I need to focus on for today.

11: Back from a sick day or two, I talk today about Twitter’s algorithmic timeline change and why it would be nice to launch a product when your competitor has some bad news.

12: Back from a quick trip to Portland, today I’m thinking about the music for my Kickstarter project.

13: I finally drop the stickers in the mailbox at our neighborhood post office. Thinking this episode about what it means to be lucky.

14: At my 10th new coffee shop in as many days, I write a few blog posts. And on this episode I talk about it.

15: I reflect on 6 months as an indie, think about stealing time for projects, and plan how I can use working from a coffee shop in the morning to provide a better structure to my day.

16: This week I’m thinking back on how Staple! Expo went over the weekend, and why it never helps to panic when something isn’t going perfectly to plan.

17: It’s spring break week, which means the kids are out of school and SXSW is taking over downtown.

18: I’m playing Nintendo’s new iPhone app Miitomo, watching my Mii character pace around the room as he (and I) wait for our iPhone SE delivery. Also talk about the library routine and Rails 5.

19: I finally record a video for my Kickstarter project. Now I just need to edit it and do everything else.

20: I talk about receiving the Loish art book and my current thoughts on Kickstarter goals and rewards.

21: Today I take stock of the last few weeks of client work and recovering from 2 months of focusing so heavily on my personal blog.

22: Last week was stressful. This episode is about being mad at nothing and everything, and why fireflies are magical.

23: I play a clip from the Upgrade podcast and then talk about my struggle to wind down a product correctly.

24: I summarize my week in San Francisco from the perspective of not just the WWDC technical news and events, but also of using the trip to refocus on my priorities for Riverfold Software.

25: Back after a summer break, on this episode I talk through what we can learn from Tim Duncan’s incredible 19-year career.

26: I talk about getting derailed with home repairs, the U.S. presidential election, and writing about the Dash controversy.

27: One week after the election, I react to Apple’s design book announcement and talk about why social networks may be broken.

28: Not enough sleep yet still focused on getting work done. I review today’s blog post and play a clip from the Moana soundtrack.

29: I got a new domain! I talk about the .blog registration process and my evolving plans.

30: From a listener question, I talk about steps in November to wrap up old projects and finish new ones.

31: I try the new WeWork location at the Domain, listen to a singer at the car dealership, and remember that I need to get out to talk to real people about my work.

32: I share some thoughts on the first day of Super Mario Run and how my work week is wrapping up.

33: The morning after Christmas, I give a quick update on Micro.blog plans and Kickstarter’s Launch Now review feature.

34: Happy New Year! I talk about the first day of the year, and the final day to finish my Kickstarter project for Micro.blog.

35: A week after launching the Kickstarter, I talk about its success so far and why I believe I can build Micro.blog, with a clip about optimism from Gary Vaynerchuk.

One week down. The launch on Kickstarter is going great. It’s fantastic to see everyone’s reaction to the project. More than ever, I’m convinced that the time is right for this.

I wanted to highlight a few posts and links. I was a little caught off guard by activity on the first day, so I’ve yet to really reach out to press contacts who might want to write about Micro.blog. I’ve been focused on replying to questions about the service and book.

John Voorhees wrote for MacStories about the Kickstarter:

Micro.blog has a lot in common with social networks like Twitter, such as replies and favorites, but with an important difference. Instead of locking users into a proprietary system owned by someone else, the content created by individuals is owned and controlled by them. As part of the Micro.blog service, Reece is also building publishing tools with Markdown support, including a native iPhone app, to help people get started with microblogging.

John had interviewed me at WWDC last year about what I was up to. While I didn’t have the name Micro.blog yet back then, I was actively working on the service and you can hear many of the same themes from back in June as I’m saying today.

I thought Marco Arment summed up the urgency well:

We’ve all been pouring a lot more of our writing and attention into Twitter and Facebook than the rest of the web, and the diversity and decentralization of the web has suffered greatly. Far too much power now rests in far too few hands, and we’re starting to suffer tremendous consequences.

Reaction from the WordPress community has also been encouraging. I knew I wanted to reach WordPress fans, because Micro.blog works great with WordPress, but I’m not as plugged into that community. I was excited to see Matt Mullenweg tweet a link to it. And WP Tavern did an excellent write-up, mixing interview questions with previous posts of mine:

During his 14 years of blogging and 10 years of using Twitter, Reece became an advocate for the open web. He said he used to be excited about Twitter and built apps for the platform but grew disillusioned at their approach to locking down the API.

I’m thankful for local articles as well, such as this story from Silicon Hills News by Laura Lorek. Laura is just in the last day of her own Kickstarter campaign for a podcast companion to the Austin news site.

Not to mention blog posts from Brent Simmons, Gus Mueller, Becky Hansmeyer, Ben Brooks, Dave Peck, Chris Aldrich, John Johnston, and the hundreds of tweets and links I’ve seen over the last week. It’s really special to see it spread so far. Thank you again to everyone who has linked to the project.

Now that I’ve had a week to reflect on the campaign, and listen to feedback, I’m starting to form a much clearer picture of how the rest of the month needs to play out. This is the kind of opportunity that doesn’t come around very often. I’m looking forward for the work ahead.

Even before announcing Micro.blog, I’d get asked about App.net. It may surprise you to hear that there’s still a community there, 2 years after the service was put into maintenance mode. All my microblog posts are cross-posted automatically, and I’m always happily surprised to continue to get replies on App.net.

I was an early believer in App.net. I wrote in 2013 that it was not just a Twitter clone but an amplifier for applications that couldn’t be built before. It came along at the right time, took off, and then faded. The App.net founders deserve significant credit and thanks for trying something risky and succeeding to grow a community that lasted so long.

Now, with social networks broken in ways we didn’t fully acknowledge before, the time is right for another shot at a more open, ad-free microblogging platform. That’s why I’ve been working on Micro.blog.

I could use your help to spread the idea of independent microblogging. We don’t need just another Twitter or Facebook clone. We need a new platform that encourages blogging on the open web. You can learn more on Kickstarter here.

On Monday, I launched my Kickstarter project about independent microblogging, with a focus on owning your own content and making blogging easier. On Tuesday, Lindy West left Twitter in a post about Twitter’s inability to deal with harassment. On Wednesday, Ev Williams announced that Medium would lay off 50 employees.

The message is clear. The only web site that you can trust to last and have your interests at heart is the web site with your name on it.

That’s the main goal with Micro.blog. Build a service and write a book that makes independent blogging more approachable. No one knows exactly what the web will look like in 10 years, but we can take the first step to get there. If you’ve been frustrated by the ad-based silos and waiting for a reason to post to your own site again, I’d love your support.

Yesterday morning I woke up early, after not enough sleep, and flipped the switch to launch my Kickstarter project. I’ve been amazed at the response, seeing it funded on the first day. If you backed it or shared a link with friends, thank you. It meant a lot to see so many people embracing the idea.

I’ve backed 18 projects on Kickstarter but never created one myself, so I didn’t know what to expect. Was the funding goal too high? Too low? Even at the last minute I was noticing problems with the video and wished I had more time to improve it.

But I really wanted to launch something new at the beginning of 2017. I settled on January 2nd a couple of weeks ago and decided to stick with it. I announced the date on Core Intuition. I booked a sponsorship slot on 512 Pixels to lock myself into the date. I gave my mailing list an early heads-up that it was coming. I even set a promoted tweet to run, for some reason. (And I quietly deleted some other advertising ideas from my OmniFocus list, because I just ran out of time to pursue them.)

Today, I took a few minutes to re-listen to episode 34 of my short podcast Timetable, which I had published on Sunday, the day before launching on Kickstarter. It’s fascinating to me in the context of the success of the project so far, and in general people’s positive reaction to the video, because I think you can hear the doubt in my voice about it. I was not confident.

And I felt the same way yesterday morning, staring at the “0 backers” text on Kickstarter for a little while, wondering if maybe I had rushed it out without enough planning. That’s a really bizarre feeling. It’s much different than selling traditional Mac or iOS software.

Right now I’m feeling incredibly lucky to have the chance to launch this project — to see it spread and to hear everyone’s feedback and ideas. I have a bunch of work to do. And I have new features that I wanted to build for Micro.blog which I haven’t announced yet, which now it looks like I’ll be able to prioritize.

I’ll have more thoughts soon. In the meantime, I’ve been answering questions on Kickstarter and email, and I’ll be sending a project update later today to all backers with details on what comes next. Thanks again for your support!

At St. Edward’s Park.

Tomorrow I’m launching a Kickstarter campaign for Micro.blog and a short book about blogging called Indie Microblogging. I’ve had fun working on the video for this project, trying to tell the story of why independent publishing matters.

Of course the video has me talking at the camera, but it also incorporates some animation and screencasts. Here are 4 stills from the video:

I can’t wait to share the full thing. I’d love your support when it launches.

“That you are here — that life exists and identity,
That the powerful play goes on, and you may contribute a verse.” — Walt Whitman

Four days after the election, still stunned by the news that Hillary would not be our president, I went to a funeral for a good friend of mine from middle school. Devin Kennedy-Puthoff was creative and passionate. He was really fun to be around. Though I lost touch with him as we grew up, I’m very thankful to have known him.

People pass in and out of our lives. The friends we have when we’re younger might not stick with us. We might have different friends in high school and college. And different friends again as adults.

That’s okay. We all need different things at different points in our lives.

Twenty-five years, thirty years… It’s a long time. Reaching back into the past so far, untangling the stories in our mind, leaves fragments. These memories aren’t complete or precise. They are less complicated and so in a way, more true.

A few nights later, magician David Blaine had a TV special on. I was thinking of a day when Devin and I were practicing magic tricks with quarters. Kids hanging out with nothing much to do, turning free time and a couple quarters into something.

To this day, when I see a magic show, I often think back to that moment. When I see a movie about magic, or teach my kids to make a quarter disappear, I think back to that moment with Devin when life was a little simpler.

At the funeral, I was wondering why that memory was so strong that it has stuck with me all these years. I think it’s because there was something pure about it. Time strips away everything in a memory that isn’t essential.

If you read every post on my blog for the last decade, you’ll know what I think about the tech world, but very little about my family. If you read every post from my private journal, you’ll know the rest. Taken together it might be too much. Too complicated.

Who we are is not just what we’ve done. Who we are is that moment that someone will remember later, as I remembered Devin, for years or decades. That moment that is so true because we’ve forgotten everything that doesn’t matter.

One reason I like microblogging on my own web site is that I can control the links and simple formatting. I’ve noticed lately that Twitter can’t consistently auto-link even certain domain names, for example.

This difference is illustrated well in a post I made this morning, which included timetable.fm and micro.blog. Twitter auto-linked the .blog but not the .fm. The cross-post to App.net auto-linked the .fm but not the .blog.

Here are the 3 versions:

In the final screenshot — the original from my own site, from which the others were pushed out automatically — you can see how I’ve specifically linked the domain and phrases I wanted to. It’s a minor thing, but it just looks better when the author has a little control over the formatting. (And while I don’t use it here, my own short posts can contain text in bold or italics via Markdown, too.)

Following up on my post about Twitter at 10 years, I decided to mark the actual 10-year anniversary of my first tweet by posting from my @manton account, which I haven’t touched in over 4 years. After so much time, you can be sure the tweet was going to be exactly 140 characters:

Hi! 10 years since my first tweet. 4 years since my last. You can follow the blog cross-posts via @manton2. This message will self-destruct.

Why post again? I’ve had some fun experimenting with cross-posting to @manton2. As I wrote when I first started this:

And yet, many people get their news from Twitter. Since I started microblogging on my own site, I’ve had time to reflect on the role of indie microblogging and cross-posting. I think the IndieWebCamp has it right: publish on your own site, syndicate elsewhere.

Overall I think it has been a success. I use my upcoming platform Micro.blog for the cross-posting, so using Twitter has helped me improve Micro.blog too. And I get more people who don’t actively follow RSS feeds to read my blog posts again.

As promised, I’ve already deleted that last tweet at @manton. I’m also not replying to mentions over there, although I try to reply or favorite tweets I see from @manton2. I know this Twitter strategy might seem like a strange compromise, but I think it’s working because it puts a focus on my independent blog instead of on Twitter.

When first writing about mirroring this blog, there were only 2 places — WordPress.com and GitHub — that came to mind as good choices:

I believe both will last for decades, maybe even 100 years, and both embrace the open web in a way that most other centralized web sites do not.

I still believe that, but Bloomberg has an article about growth and spending problems at GitHub:

In September 2014, subscription revenue on an annualized basis was about $25 million each from enterprise sales and organizations signing up through the site, according to another financial document. After GitHub staffed up, annual recurring revenue from large clients increased this year to $70 million while the self-service business saw healthy, if less dramatic, growth to $52 million.

These numbers seem fantastic except that GitHub is losing money overall. GitHub has transformed from a small profitable company to a large unprofitable VC-backed company. Here are some of the goals from GitHub’s 2012 announcement about taking funding:

We want GitHub to be even easier for beginners and more powerful for experts. We want GitHub everywhere — whether you use Windows or Mac or Linux or some futuristic computer phone that hasn't been invented yet — we want GitHub to be an awesome experience. We want to make it easier to work together than alone.

They’ve made progress in the last 4 years. I’m not sure the GitHub user experience has improved more quickly because of funding than it would have otherwise, though.

I love GitHub and use it exclusively for my source and my client projects, because there’s a productivity benefit to having everything in one place. I hope GitHub can turn the corner on profitability. And most importantly, I hope they have a sustainable long-term plan beyond this initial quick growth.

Federico Viticci has another fantastic long-form essay, this time about using the iPad Pro for a year. It’s the story of his iPad workflow plus mini reviews of each app that make using the iPad as a primary computer possible.

I haven’t finished reading the whole thing yet, but I’ve been paying particular attention to the theme of file management. I use Dropbox for my most important files — documents, notes, and photos — because I want them synced everywhere and accessible in an obvious, transparent way. iCloud is too opaque and app-specific.

Federico covers this conflict early in the essay with a list of iCloud downsides:

iOS apps like Documents and Workflow can't access or display the contents of other apps' folders. This prevents the existence of a full-featured iCloud Drive file manager that offers functionalities Apple doesn't want to build in their iCloud Drive app. There should be an API to allow third-party apps to gain access to the entire contents of your iCloud Drive filesystem, just like there are APIs for photo and music access.

I’ll be happily surprised if Apple ever adds such an API. It seems unlikely. And if that’s true, it means iCloud will be permanently crippled compared to Dropbox.

The trend to new iCloud-first apps like Ulysses and Bear is fine. It doesn’t appeal to me, though. I use Ulysses on the Mac because I can sync with Dropbox. There are so many Dropbox-capable iOS text editors that I feel confident using my current favorite and switching whenever I want.

Federico also describes using GitHub and the iPad app Working Copy for collaborative editing:

Working Copy's diff support has been a boon for how we edit Markdown and collaborate on articles. We can keep track of every edit and comment in a centralized location without creating duplicates. Working Copy makes it easy to follow the evolution of a document through multiple commits; every writer can chime in with their own suggestions and Working Copy will handle file merging and conflict resolution thanks to GitHub.

GitHub is useful for much more than code. I personally love the simplicity of Gists and GitHub Pages. It’s great to see how MacStories can use GitHub for editing articles, too.

My content is all on this blog or linked from it, but if you’re following RSS feeds or Twitter it’s not as obvious where everything is posted. Here’s a summary to clear things up.

Microblog posts: Posted here and in a special RSS feed. Also automatically cross-posted to Twitter and App.net, with some occasional truncation.

Longer posts: Posted here and in the default RSS feed. Also automatically cross-posted to Twitter and App.net with the title and link. Twitter cross-posting is handled by my upcoming Micro.blog platform.

Photos: Posted to Instagram and then copied here using this workflow. They don’t show up in either of the RSS feeds above. They’re not cross-posted to Twitter.

Timetable: Posted to timetable.fm which has its own feed. Discoverable in your favorite podcast client.

Core Intuition: Posted to coreint.org. I’ll usually post a link here on the blog for each new episode.

All posts: Switching to WordPress brought a new global RSS feed, but I redirect it to the longer posts for now. There’s a new everything RSS feed which contains all posts: microblog, full posts, and photos. Enjoy!