Just released a new 3.0 beta of Micro.blog for iOS. This includes a big change, borrowed from the 2.x versions: Markdown syntax highlighting when writing new posts. We are getting close to release. The only major feature left is WordPress posting support. TestFlight here to follow along.


@vincent good question 🧐 I thought this was working at some point (maybe looong ago), with a preformatted post. The link title was the title of the page and the selected text was put in a blockquote. But maybe I was dreaming, or the iOS API changed? A quick search just found parsing the page with JavaScript in the docs. You’re the expert though 😅✌️

@vincent it probably was working years ago and nobody checks the Radars about it being broken since a decade or so 😉

@mikehaynes It should adjust the text size based on the iOS system setting. If we need another option on top of that, will need to wait until later. (Lots of stuff was moved to 3.1.)

it does for timeline but just sent feedback in TestFlight
New posts have very small text
Replies have slightly bigger text
Timeline is based on iOS settings
(Not sure if replies have all the markdown stuff either yet?)

@eshwarnag It doesn’t directly post to Mastodon from the app, but instead the Micro.blog backend can copy any post to Mastodon via the cross-posting settings.

how are the Markdown shortcuts supposed to work? After pressing one, should the insertion point get moved between the two asterisks or underscores? Or, do I need to manually move it?

@kevrodg Right now the buttons assume you’ve selected the text you want to make bold or italic, and then it will just wrap the text. We need to adjust this for when text isn’t selected.

If I don’t have any text selected, when I press the double asterisk button the app adds four asterisks to the body of my post. Is it a wanted behaviour?
Personally it seemed more correct to insert only two asterisks, write the text I want to render in bold, and then press the “**” button again to close the tag.
This is a screenshot I took from version 3.0 (310):

ooh; really forgot about the TF version of this. Will jump in on this to offer future feedback
