@awoo@gts.apicrim.es this looks BAD on software that doesn't support that weird citation format

@root @awoo it was already wondering when seeing that for the first time how that would work on *key. the answer appears to be that it doesnt

@49016 @root but non-misskey users (minus those manually implementing it themselves) are supposed to shut up about missing MFM support? /lh

@awoo @root mfm has a very sane fallback though. the gts footnotes just do whatever and hope it works lol

@49016 @root "very sane fallback"

@49016 @root if it weren't for some of the alt text I wouldn't be able to understand some of the posts ​

@49016 @root also: the Markdown parser used by GoToSocial is "compliant with CommonMark 0.31.2" according to itself.

@awoo @root like, yes, but when it can be made compatible (e.g. the way that this one always highlights the word "house" in blue via MFM) still makes posts readable when viewed without MFM. having huge hashtags with unpronounceable names is not really a good fallback lol

@49016 @root oh those were supposed to be footnotes (with the ability to jump between the text and the footnotes (and where it got referenced)), but the lack of markdown footnote support is an issue on the other end :3

also if it reads those properly, those "hashtags" have the post ID in them, as well as -fn (footnote) or -fnref (footnote reference) followed by a colon and then the identifier for said footnote (either a number, or an arbitrary word).

and just because *key (and whoever decides to join along with the quasi-standard-but-also-not-really that is Misskey-flavoured Markdown) gets to implement very experimental things, doesn't mean that a beta software (like GoToSocial) isn't allowed to implement features of a proper standard for once. it's now misskey's turn to implement something, not others' turn to implement this mess that barely even works across multiple instances running similar forks from misskey.

@awoo @root the point it is making is that there's literally no fallback for implementations that sanitize the relevant html bits and that causes accessibility problems. mfm literally always sends a plain version alongside the mfm source so implementations that don't support it don't start doing whatever lol

@49016 @root then I guess Misskey is wrongly reporting to support this (or doesn't sanitise it correctly) since stuff like Mastodon can handle it just fine