Mac users can use the native Micro.blog for Mac app. It’s a free download and supports most of the same features as the iOS version.
You can see a short video of it on Manton’s blog. You’ll even notice a rather handsome avatar make an appearance.
Unfortunately I cannot give this a spin yet since I haven’t upgraded my Mac to High Sierra. And it doesn’t appear I’ll be doing so for at least a month or two since I haven’t seen any updates from Apple on that front. High Sierra just seems far too unstable to switch to on my main work computer at the moment.
Colin Walker, though, seems to like this new app:
Manton has repeatedly said that this is just a version 1.0 app but, I have to say, it’s been rock solid. Browsing, replying and posting to the blog have all been a breeze and I’ve not had a single issue or error.
There has to be a line, a point where a comment is just that and not a reply. It’s a question of semantics but not everyone’s answer to “what is a comment and where does it belong?” will be the same.
I struggle with this a lot.
It is likely the point I should have made in my post regarding Micro.blog becoming a commenting service (and the fact that I don’t like that). I don’t want to reply on my blog to every reply to my posts on M.b because then I would have dozens and dozens of posts on my blog that would be very tough for readers to follow contextually. I believe the commenting mechanism that has been around for decades, even un-threaded, is far more useful than dozens of desperate posts stitched together loosely with a link that says “in reply to”.
Webmention attempts to bridge that gap between post and reply but that also is tough to follow along if the thread gets unwieldy.
However, I also don’t want to reply to every reply on my posts directly on M.b either (though, I do from time-to-time) as that isn’t much better than using any other silo like Twitter or Facebook. Should M.b go away, all of those conversations would be lost.
This isn’t a new issue nor is it exclusive to M.b. If I replied on my own blog to other people’s posts on their own blogs (like I am in this post to Colin Walker’s blog) then one side of the conversation could disappear at any time. I can only control my side of the equation. But at least if I have my own blog I have control of that one side.
I think it is good that these topics are being discussed again. The same debates have been swirling since blogging began, they swelled again when the indieweb movement began to take shape, and I think they are happening again as a result of M.b’s growing community. I do not believe there is one single answer to many them. You have to do what is right and sustainable for you.
For now, here are my personal rules for replying to posts. These will most definitely change over time.
As an aside: I know some of you do not want to leave a public comment. I love getting reader emails. I get a fair number of them. And some of them have been excellent conversations. So please don’t hesitate.
* I no longer have a Twitter or Facebook account. I do have a M.b account but I’m beginning to wonder if I need one as I have my own fully functional weblog. If I didn’t and I wanted a microblog and didn’t want to use Twitter, I could see having an account. If I wanted a more fully featured blog I still believe WordPress is the best tool for that. Also, I’m sure as the M.b community grows it could mean that my content would be discovered by more people. I think M.b may end up being a thriving, well run, community and service. It is why I backed Manton’s efforts via Kickstarter. But, if I have my own blog, and if I really don’t care much about my content being discovered, then I see little reason to syndicate to it. For the time being I’m still going to as I want to see how the service matures.
I miss my iPhone SE. Everything I ever wrote about it here on my blog was awash with my overwhelming love of the device. I still believe it is the best phone Apple has made to date.
The only reason I use an iPhone 7 Plus is the camera. I said I wouldn’t switch from the iPhone SE but I did once I saw the dual-camera. It was almost as if I bought a new favorite camera and was forced to turn in my favorite phone to have it.
I was reminded of this topic by Manton Reece. He recently wrote:
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.
Over 18 month’s ago I wrote:
I only have one feature request for the iPhone SE. Make it waterproof.
Now I have a few more requests. Make an iPhone SE at the exact same size with an edge-to-edge display, the dual-camera system, and make it completely waterproof. Oh, and you can throw in USB-C too. That would be the perfect iPhone.
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.
Kudos to Manton as Webmentions seems to work beautifully is Micro.blog. The improvements show and the value is starting to show too. So I guess I just need to stop complaining. I’ve been harping on webmention for a little while. I feel terribly about it. Because I want it to work so badly and I’ve just been frustrated that is seems so inconsistent! So I plan to shut up now and sit down and get it working properly. I’ll likely do that within the next few weeks.
To see Micro.blog’s webmentions in action you can see a few on my posts there and here on my blog. I’m looking forward to their presentation being much more valuable on my blog. My email inbox is open for suggestions.
I wanted to take a few moments to jot down a comparison between my wish list for this year’s WWDC and what was announced. Also, towards the end, some quick thoughts on the surprises that were announced.
Here are my wishes, in order from the previous post, and whether or not we got them.
My last minute wish that I threw in was for driving mode. And that is a huge yes!
If we’re keeping score that’s like 8 nopes, 1 kinda, and 4 yeses. Which doesn’t seem like a good score but somehow I was very impressed with WWDC overall. I think we’re in for a great year of software updates coming from Apple.
Now, onto some of the surprises.
There are of course many things I haven’t mentioned but ll-in-all a solid week of Apple updates.
One last thing; recently Tim Cook has been quoted as saying that Apple is focused on autonomous driving (which we knew) but that they are focused on it as a category rather than a feature. Apple finds autonomy as an interesting area moreso than simply self-driving. I’m very interested to see how this idea manifests itself in future products.
With JSON Feed, it’s not about disrupting RSS exactly. RSS is great and widely deployed; it’s not going anywhere. But we can take what was good about RSS, improve a few things, and maybe jumpstart new tools and apps that work together. Developers use JSON everywhere now instead of XML, and Brent and I felt that maybe XML was even holding RSS and blogging back.
As I thought. These are great reasons for JSON Feed to exist.
The rest of the interview is worth reading as well.
Manton Reece and Brent Simmons have created a new specification for creating feeds using JSON. They write:
We — Manton Reece and Brent Simmons — have noticed that JSON has become the developers’ choice for APIs, and that developers will often go out of their way to avoid XML. JSON is simpler to read and write, and it’s less prone to bugs.
JSON Feed has been implemented on a few platforms already and it was talked about a lot since its debut. I’m glad someone has created a spec around this so that the developers that would like to use this can now rally behind a unified specification. However, JSON Feed won’t be replacing RSS any time very soon.
RSS is something you could call a “good enough” solution. It is already in place, tons of stuff supports it, and works fine. And while the developers of all of the apps and services that use RSS could update their software to create and parse JSON Feed it is doubtful they will very quickly as the benefits aren’t all that great. The advantage of JSON Feed mostly comes when creating new services not replacing old ones.
I don’t think Manton and Brent believe JSON Feed will replace RSS. I don’t think that is why they created the spec. I believe they feel this is a good alternative for the developers that would like to use it and that they wrote the spec out of a need that they had. Which is good.
I’ve discussed the benefits of replacing RSS with JSON in the past. Me, in June 2015 on one of the benefits of replacing RSS with JSON:
RSS is a fairly bloated specification. It is a bit verbose and the file sizes for even a small blog can get relatively large quickly. JSON is, by its very nature, a bit more succinct. This would result in faster load times, easier caching, etc.
So while there are definite benefits, it is doubtful that RSS is going anywhere for a long time. There have been a few attempts to replace RSS with something that is smaller and easier to parse over the years and they simply didn’t catch on. This weekend Dave Winer (the inventor of RSS) chimed in on JSON Feed and he has a similar reaction to it as I have had; it is great that the specification exists but it will not be replacing RSS for news or blogs any time soon.
I’ve added a JSON feed to this blog because Manton created the WordPress plugin already.
Side note: How did I not see this one coming?
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.
Publishing most of my “tweets” here first has led to some frivolous posts. But, I wouldn’t have it any other way. Takes the pressure off of me to have every post be significant before hitting publish.
Jonathan LaCour, SVP, Product & Technology at Dreamhost:
We’d like to make it as easy as possible to launch a WordPress-powered microblog on DreamHost that integrates well with Manton’s upcoming Micro.blog service. In order to support that mission, DreamHost is kicking in a $5,000 pledge to the Kickstarter.
Nice move Dreamhost.
Manton Reece has added a thoughtful stretch goal to Micro.blog’s Kickstarter campaign:
If the Kickstarter reaches $80,000, I will use some of the money to make my very first part-time hire for Micro.blog: a community manager. The community manager will help set the tone for the service, work on documentation and best practices, and be responsible for curation when Safe Replies fails to automatically catch emerging problems.
Safe Replies sounds like something Twitter should have had a long time ago. Run over there and help Manton reach this new goal.
Manton Reece recently published an update to Micro.blog’s Kickstarter showing a video demonstration of the iPhone app he’s creating for the service. He mentions a really important point that I think many are missing (as I mentioned just a few moments ago). He says (at 53 seconds into the video):
Now, you can have Micro.blog host a microblog for you. That’s what the paid plan is about that is mentioned in some of the reward tiers on Kickstarter. It is super easy to get started that way. But you can also bring an existing blog. My personal blog, for example, uses WordPress. And so, when I use Micro.blog the iPhone app for the first time it asks me where my WordPress blog is and then I can post directly to my own site.
I’ve been following along with this project since Manton first mentioned it nearly two years ago so I’ve been aware of what he was building. I just don’t think the information on the site or on the Kickstarter has made that clear for people that don’t totally understand the underpinnings of the web. (Though, Micro.blog is arguably be built for those that do.)
The iPhone app looks very nice. Especially for a first public release.
We envisioned a pool of differentiated, fast-growing third-party applications would sustain the numbers needed to make the business work. Our initial developer adoption exceeded expectations, but that initial excitement didn’t ultimately translate into a big enough pool of customers for those developers.
I’ve been a paying subscriber to App.net for the entire life of the platform (that is, until they cancelled my subscription this week).
When App.net launched many were drawing a line of comparison between it and Twitter. And since this announcement I’m seeing many drawing a line of comparison between App.net and Micro.blog. This isn’t an apples-to-apples comparison.
If you read Dalton’s vision above, it doesn’t read anything at all like Twitter or Micro.blog.
App.net was an API for application developers to build on top of. Yes, something Twitter-like could be build on top of it. But so could so many other things. It had a data storage service, a push notification service, and even a crowd-funding feature called Backer that would, presumably, allow developers to pre-charge for new features for apps.
App.net was a very ambitious platform that, I believe, got pigeon-holed into a Twitter comparison because they created Alpha – a Twitter-like microblogging platform – as a demonstration of their own API. I think this muddied their messaging to the point where most people would describe App.net as a Twitter alternative.
Manton Reece’s forthcoming Micro.blog is not anything at all like App.net. Though, many are confused about Micro.blog similar to how many were confused about App.net. (I’ve had at least three conversations about Micro.blog where people have no idea what it will do.) They are comparing it to Twitter even though Manton doesn’t usually draw that line himself. And I think he will have to find a way to communicate its decentralization and the fact that it will work with your existing blogging platform so it too doesn’t get packaged and framed as simply a Twitter replacement.
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.
He’s right of course. He has said it a million times. So have I. Like right here. And so have many others.
Manton, by the way, is currently Kickstarting a book and service about independent microblogging. I told you about the service already. Go back his project even though it is very well funded already. This is important stuff.
It used to be impossible to imagine that Twitter could fail. And today, it’s still unlikely to vanish or even change much overnight. But the web will be better if we assume that Twitter is a lost cause. From the 10-year view, it’s clear that Twitter has already changed.
Assume Twitter (or any other service) could disappear and make adjustments where needed. I like it.
Renaming a product before its official launch may not seem like a big deal, but in this case it gives the app a new importance. Just by renaming it, the app feels more ambitious. It forces me to devote more attention to it, which means saying goodbye to some of my other web apps that I can no longer focus on.
I’m glad Manton has found the right name and direction for this service he’s been working on for some time. I’m anxious to see it get out into the public.
I want the web to be faster. Breaking links should not be part of the solution.
AMP is terrible. As is any solution that changes the URL. When wap.* or m.* was “a thing” I hated that too. Now, more than ever, there is less reasons to change the URL to load a web page tailored specifically to the viewport, device, connection. It is possible to do it without changing the URL.