I would say that’s accurate, without stepping too much over Manton’s toes. The idea of Micro.blog’s apps, and in part the service, is to make blogging as easy and casual as posting on social media. The idea being that it’s better to post to your own blog than to centralized platforms. Social media succeeds in part because it makes it easy to post quick, casual content from anywhere and get it out there. That’s the microblogging focus and why micro is in the name.
That said, blogs can do a lot more, and Micro.blog hosted blogs can expand to do very complex stuff blogging on par with that on other platforms. But this problem, “How do I create/write rich, complex long form posts?” is largely supported by another part of the MB ethos-- we should use webstandards and APIs to allow for there to be many different client experiences to work with your own content. This allows Micro.blog the apps to keep its product focus on a missing part of the market-- fast, casual, social style posting. Micro.blog the hosting service and API platform has the focus of “being the place for all your personal blog content”. Apps other than the micro.blog apps can solve the problem of “great long form writing experience” because of the API.
Given that the team is Manton (over all apps and services), Jean (community), and now Vince (part time, little bit of everything technical) there has to be a place to draw the boundaries. The MB choice was that the boundary on the official apps were “great short form posting”, for the API"an uncompromised experience for clients of our official API to expand on what you can do on MB", and for the service, “a fast, powerful, flexible blogging platform with crossposting and replies”.
I write posts like the one you link to occasionally. I use MarsEdit for that personally. Sometimes iAWriter If most of my content was like that and I did not want to use third party native apps, I wouldn’t choose micro.blog as my host because that’s decidedly very far from Micro anything.