{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

I keep getting asked to support writing rich-text-formatted posts in (we already read them just fine). I finally wrote down, in this comment on this Github issue, a short essay outlining all my concerns with doing so:

github.com/hometown-fork/homet

Some of this is problems with Markdown, while some of this is problems with interoperability regarding any rich text rendering at all.

4
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Matt Schneider

@darius really great thoughts, and honestly a frustrating example of how the general accessibility of markdown just wouldn’t work out, and could ultimately make things less accessible with key context vanishing unpredictably for users on other servers :(

0
2y
Max

@darius Definitely a class of problem that needs wider Fediverse adoption for safe usage. Lovely chickens and eggs

There almost needs to be an RFC process for this that includes more than just Mastodon, but also has key members from upstream Mastodon at the table

Out of curiosity, this seems the most active upstream issue on it that I see: github.com/mastodon/mastodon/i

Don’t see any clear maintainer discussions and love the bog down into subset of Markdown semantics

0
2y
Ben Zanin

@darius really good writeup. Thank you for sharing that.

0
2y

@darius

This is how I do it in RSS.

I include both the rendered version and the markdown version of the text if it's available.

The default is the rendered version because there aren't many apps that are looking for the markdown version, but my apps are.

Here's a blog post that explains.

scripting.com/2022/07/19/15223

1
2y
Replies