faried nawaz@apps i’m sorry, there is something that doesn’t seem right about this. i went to settings > extra features, and turned the extra features on (i left the post format as text/plain). then, i went to an earlier post of mine and replied to it twice, once with the post format as text/plain, and once as text/markdown. i posted, in order:
*italic* as plain *italic* as markdownwhen i view the posts in fedilab, the first one shows up properly italicized, but the second one doesn’t. when i view them in pleroma-fe (or husky), the order is reversed – the first one isn’t italicized, but the second one is.
in the db, the first one:
"source": { "content": "*italic* as plain.", "mediaType": "text/plain" }, "content": "*italic* as plain.",the second one:
"source": { "content": "*italic* as markdown", "mediaType": "text/markdown" }, "content": "<p><em>italic</em> as markdown</p>",i think there are two issues here.
- the second one should show up italicized in fedilab.
- if fedilab can parse the first one as markdown when it’s displaying it to the user (even though the media type is text/plain), it should probably also post it to the server as text/markdown when the user creates it – it could guess that, or ask the user perhaps?
can i get you to please try husky, the tusky fork that supports markdown? it shows an “M” button to switch to markdown, and it seems to work as i’d expect. it’s on f-droid and the play store. i believe husky doesn’t try to guess the type from the content.
All GNU social JP content and data are available under the