Not necessarily a mastodon app, but I’d love to see consistent application of markdown. The client I use doesn’t seem to support spoilers, and I’ve seen others that implement headings differently. It would be nice to have all clients implement it the same way.
(vanilla) mastodon does not have markdown, and content from other instances (marked up or not) get transmitted as HTML over the wire (and the mastodon API serves sanitized HTML to apps).
mastodon forks like glitch, and clones of the mastodon API like those on pleroma/akkoma and iceshrimp do serve the markdown source AFAIK, but unless OP’s looking to… idk, support MFM (which, on a non-web app would be difficult) I don’t really see the point in that.
I’ll look into adding markdown support but I’m not sure I’ve ever seen anything other than bare HTML come through the API. Tbh, the apps are probably just parsing the HTML. Got any examples with markdown in the posts?
Look into opening an account on an Iceshrimp instance like https://fedia.social, or an Akkoma instance like http://pleroma.envs.net. Their APIs are an extension on top of the Mastodon APIs (and both support Markdown and should expose them to apps). Sharkey also has some Mastodon API compatibility but it’s quite broken and might require some odd workarounds to get stuff working.
That said, for rich text, parsing the HTML will be more than enough for nearly all cases.
Not necessarily a mastodon app, but I’d love to see consistent application of markdown. The client I use doesn’t seem to support spoilers, and I’ve seen others that implement headings differently. It would be nice to have all clients implement it the same way.
(vanilla) mastodon does not have markdown, and content from other instances (marked up or not) get transmitted as HTML over the wire (and the mastodon API serves sanitized HTML to apps).
mastodon forks like glitch, and clones of the mastodon API like those on pleroma/akkoma and iceshrimp do serve the markdown source AFAIK, but unless OP’s looking to… idk, support MFM (which, on a non-web app would be difficult) I don’t really see the point in that.
I’ll look into adding markdown support but I’m not sure I’ve ever seen anything other than bare HTML come through the API. Tbh, the apps are probably just parsing the HTML. Got any examples with markdown in the posts?
Look into opening an account on an Iceshrimp instance like https://fedia.social, or an Akkoma instance like http://pleroma.envs.net. Their APIs are an extension on top of the Mastodon APIs (and both support Markdown and should expose them to apps). Sharkey also has some Mastodon API compatibility but it’s quite broken and might require some odd workarounds to get stuff working.
That said, for rich text, parsing the HTML will be more than enough for nearly all cases.