Ugh, micro.blog has switched, without any notice, from a perfectly-serviceable Markdown editor to some kind of pseudo-code version which makes post editing virtually impossible.
A rant.
(apologies for the microphone quality, I'm on my laptop)
@bekopharm Thanks, but why the hell should I have to follow an individual to get product updates for something I pay for?
Whether I'm following him or not, it's absolutely garbage. Terrible, terrible product management.
@dajb Just moving in to micro.blog (@eludom@micro.blog). I think the approach I'm going to adopt is to edit all my posts in a local editor (emacs) and just cut/past into micro.blog.
@eludom@fosstodon.org @eludom@micro.blog
To be fair, @manton has improved things over the last few days. I'm hoping he does user research before making changes next time!
@dajb Congratulations (to me ?). You're the first person to reply to one of my posts that automatically forwarded mastodon -> micro.blog. I think micro.blog is going to work well as an open-ish collection point for the various online things I care about.
@eludom how is it going with MB so far? You had (still having?) some importing pains, are you good now?
@jtr ok. I have the core of a bash script that will upload images via the API, so can batch upload. Still working on the old posts. The markdown that org exports around figure/picture references can be arbitrary complex. One in by hand, still diagnosing what went wrong with the 2nd test ... May have been related to this week's markdown editor change. Going to try raw upload again ... Putting content/foo.md in in a zip, upload that.
@jtr I'll be growing into this MB for a while. It's good.
Starting to wonder if I want to point my oldest domain (port111.com) here. Want to get off ditigal ocean, so I'd have to move my old blog/static pages somewhere else. OLD copy still on github pages, but I don't want to support github. Pushing my git stuff to sourcehut now, so myabe there if they have pages. ​