@gdp @maique Looks like Scribbles?
@maique Thanks for writing this up. I know itās going to take time to rebuild trust in the service after stability problems. Only one question: is there actually technical lock-in, or is it because no other platform can do what Micro.blog can do? I try really, really hard to avoid lock-in so want to know about this.
@maique Very good write up. I share your experience, and are not planning on leaving anytime soon, but I think if the service was growing a bit faster, more persons could step in.
@maique Thank you for writing this up. I think that it was very fair and honest.
Scribbles, yes?
@manton @maique I think itās user retention, not lock-in as such, but else I was nodding along to this post.
@maique Thanks for writing this. While we have been busy with other things on Micro.blog, I know you have been wrestling with reliability. While I havenāt experienced those problems lately, I have experienced them before. But I never know when it may not work so the reliability part is important (it just works). Iām less of a technical person than you are (āHeck, I have an ssh app on the iPhone, with pings configured for all the feeds that Iām importing into my M.b accountā - WHAT!!!)
Everyone and their cousin has a social network with working notifications, why do they keep failing here? The only way to get them reliably is to use Gluon, a really nice app made by Vincent Ritter.
Mine are working now, but they didnāt intermittently. But ironically, Vincent also makes the official Micro.blog iOS app, so this is indeed befuddling.
I would be lying if I hadnāt thought about moving elsewhere (before last week), but not lately. But yeah, I hate to disrupt my workflow again - Drafts, Mimi, etc. And I just moved the older posts from Blot š« So yeah, thereās that technical lock-in.
@maique Thank you! Thatās really helpful. So glad youāre part of the community. And weāll always support that feature you mention where people can participate even while their blog is somewhere else.
@maique great piece! Very well balanced. I can see that youāre very fond of M.b. I do wish the service had no issues at all but I guess itās not possible. Yet, interoperability is hard to do and maintain. I donāt try to defend M.b. but it is what it is. On the support issue, I did experience a few hours of downtime in the past. But, what Iāve been thinking recently is how I could become a volunteer to help @manton ⦠spending some time on help.micro.blog and answer the easy ones while leaving the more complex questions to Manton? i donāt know, but Iām open to help in one way or another.. because I love Micro.blog.
@manton @maique I think the issue is not trust on the team, of course, but on the teamās chosen infrastructure. I believe that this can be improved, but then again, it might require higher costs.
@pimoore a lot of the social features in Micro.blog (and indieweb in general) are tied to URLs. So I can understand how there are all kinds of subtle ways that URL controls will break other parts of the system. But Manton has said this is likely coming. FWIW, Hugo itself is deeply unclear on tag versus category distinctions and they basically operate identically just giving you two different systems.
@pimoore I hear youā but youāre talking like someone who wants a complex Hugo blog. By and large, MB was social software first, that wrapped around static blog hosting. Not blog hosting with an API for posting that later grew social. Organizing your content is pretty antithetical to the core idea of Mb which is make it easy as social media to post to your own blog. Itās specially about bringing the things that drew people to write on Twitter instead of their blog back to having a blog with all those benefits. Those of us who want piddly complex custom blogs are kind of outside the core initial idea and while supported, has to be balanced against losing what this is supposed to be.
An API in front of Hugo means this conversation doesnāt ever happen. I never find you. I probably never bother to reply.
Iām not saying youāre wrong by any stretchā I suspect custom URLs will be here within a year or two, for example. But as a product manager I feel almost compelled to support the challenge of not losing the original vision and differentiator to chase the super power users.
@pimoore tl;dr people who give a shit about .html at the end of the URL are pretty far outside the thesis of āMake it as easy to write to a site you own as social media was to post toā
@pimoore @jsonbecker I mean, I do think there is a lot of value to be had from treating your super users as well as possible ā the balance of these decisions is difficult mostly because the team is so small, and that canāt be changed with the snap of Mantonās fingers.
@pimoore @jsonbecker Maybe we could make those Apple-style working groups, for the different areas of interest in the platform. āHi Manton, here are the groupās latest findings⦠yes those are double-sided, why do you askā
@pimoore I mean youāre talking to someone who has considered writing his own blogging software several times because the thing he wants isnāt possible in Hugo, so I get the impulse. Then I remember I actually do blog now and thatās something I shouldnāt forget.
@jsonbecker Thatās a really good point, and bears keeping in mind when Iām requesting nitpicky stuff. I do want those things, but itās kind like coming here expecting 1:1 feature parity with Mastodon when it was specifically created to avoid some of those pitfalls (likes, boosts, hashtags, etc.). This place is different, and thatās okay. And if Iām not okay with it, there are countless other social networks and blogging platforms that allow one to nitpick, albeit with other bits from the MB experience missing. Everything is a tradeoff.
@jsonbecker šÆ
@ridwan My main website/domain is still on Blot and Iām grandfathered in to the original lower price ($20/yr) However, I wanted a certain look on my blog plus have other activities (Books, Now, etc.) tied in. If I put the effort into Blot, maybe I can but Iāll have to get the paid Dropbox plan for space.
@vincent @maique Thanks for that clarification. I guess you and Manton have much to discuss regarding design, especially at the backend. I donāt understand much of it, but if Gluon as a third-party app can work better than the native app, thereās something wrong.
Also, regarding the ecosystem, it hasnāt taken off much. Gluon is the only third-party app apart from people hacking RSS feed readers to read Micro.blog. And IIRC, you had considered shutting down Gluon (thatās when I stopped using it).
@zwin @vincent @maique I agree 100% on the principle (should do better than the official app). I use the official app coz I can edit posts, add tags to bookmarks, etc. Gluon has those nice touches like indicators on posts that may have replies, etc. But working notifications should be a special feature, right? Both apps have different interaction elements so you canāt really switch between the two. Many things are done server-side so you canāt use one app for only-posts and the other for conversations & replies. Lillihub gets close to being the perfect app but itās primarily a web app and works best on the desktop. So Iām saying this is lots of inconsistencies for a small service with ~7K monthly users.
@vincent From my side at least, I totally get it and understand your part-time role and limited scope within the Micro.blog LLC. Hence I never direct my help requests for official Micro.blog stuff to you but always appreciate when you step in even when you donāt have to. Youāre definitely putting in more time than youāre paid to from my POV.
@pratik I think now David offers support to Google Drive. If he does with OneDrive it would be awesome. I got 28GB of free storage from Dropbox. All thanks to early adoption during my uni days. š¤£