Conversation

Notices

1. Embed this notice
   faried nawaz (fn@p.node.pk)'s status on Wednesday, 23-Aug-2023 00:47:43 JST faried nawaz

   • Fedilab Apps

   @apps i might be wrong here, but it seems like when you make a markdown post with fedilab, it uses the mediaType of text/plain. is that correct? shouldn’t that be text/markdown?

   i can enter markdown natively in pleroma, using its default frontend. here’s the difference i see in the db:

   pleroma:

   "source": { "content": "```\r\ntired: bitcoin\r\nwired: nvidia h100\r\n```", "mediaType": "text/markdown" }, "content": "<pre><code>tired: bitcoin\nwired: nvidia h100\n</code></pre>",

   fedilab:

   "source": { "content": "fedilab test\n\n*italic*?\n**bold**?", "mediaType": "text/plain" }, "content": "fedilab test<br><br>*italic*?<br>**bold**?",

   husky also supports markdown:

   "source": { "content": "_relax_\n\n~~okay~~", "mediaType": "text/markdown" }, "content": "<p><em>relax</em></p><p><del>okay</del></p>",
   • Embed this notice
     Fedilab Apps (apps@toot.fedilab.app)'s status on Wednesday, 23-Aug-2023 00:47:42 JST Fedilab Apps

     in reply to

     @fn
     You have to enable extra-features in settings for that.

   • Embed this notice
     Fedilab Apps (apps@toot.fedilab.app)'s status on Wednesday, 23-Aug-2023 03:27:59 JST Fedilab Apps

     in reply to

     @fn
     For posting in Markdown with a Pleroma instance, you have to select Markdown when submitting the message. Then Pleroma transforms it in HTML.

   • Embed this notice
     faried nawaz (fn@p.node.pk)'s status on Wednesday, 23-Aug-2023 03:28:00 JST faried nawaz

     in reply to

     • Fedilab Apps

     @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 markdown

     when 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.

     1. the second one should show up italicized in fedilab.
     2. 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.

   • Embed this notice
     Fedilab Apps (apps@toot.fedilab.app)'s status on Wednesday, 23-Aug-2023 03:31:04 JST Fedilab Apps

     in reply to

     @fn
     Fedilab supports markdown as it is in plain text, not what is transformed by instances.