Noticed that the way #Mastodon sanitizes HTML coming from other instances flattens out block quotes in addition to removing other #formatting.
(Totally separate from the quote-toot debate.)
If I follow someone on WordPress or GoToSocial or Calckey etc. and they include an indented quote, when it shows up in Mastodon, it'll look like the quote is just another paragraph.
That can totally change the meaning of the post!
Found an open issue on GitHub:
https://github.com/mastodon/mastodon/issues/15311
(Totally separate from the quote-toot debate.)
If I follow someone on WordPress or GoToSocial or Calckey etc. and they include an indented quote, when it shows up in Mastodon, it'll look like the quote is just another paragraph.
That can totally change the meaning of the post!
Found an open issue on GitHub:
https://github.com/mastodon/mastodon/issues/15311
HTML sanitizer can change meaning of posts entirely · Issue #15311 · mastodon/mastodon
A private post in my home feed apparently contained a blockquote, which was stripped by the sanitizer and converted to a regular paragraph. This changed the meaning of the post entirely, since it w...GitHub
Posts from @kelsonv@gts.keysmash.xyz
in reply to Kelson's Sorta Old Account • • •For instance, the first paragraph in this post isn't actually written by me, it's a quote from the original GitHub issue from two years ago. Writing this on GoToSocial it's trivial to indent it (and if you look at this post on its own site, you should see it correctly!) and it doesn't make sense for me to have to think about how many of my followers might be on software that actually breaks my posts!
(The missing italics in the second paragraph are less of a problem, but they would be nice to see them go through.)
Kelson's Sorta Old Account
in reply to Posts from @kelsonv@gts.keysmash.xyz • • •FiXato
in reply to Kelson's Sorta Old Account • • •Example: Another thing where falling back to the original markdown would be an improvement, is lists: