@jeder@awoo@volpeon mfm has beenf ucked up for akkoma since the beginning, iโm not sure how itโs passed, but i wouldnโt be surprised if itโs just checking if itโs one of the *key and then assume itโs mfm
@jeder@awoo@volpeon yea i mean assuming it only has the mfm and not the html (iโm assuming that the html support means sending out parsed html instead of just the mfm)
tl;dr, MFM isn't properly federated in the content, so the only way you can show it, is by re-parsing. For *key this is generally not a problem because they use the same parsers. Akkoma uses a different Markdown dialect (which is to be expected with Markdown), leading to such issues.
The fix is to properly federate the MFM so that reparsing isn't required. A proposed option is to use https://codeberg.org/fediverse/fep/src/branch/main/fep/c16b/fep-c16b.md which I'm working on in Akkoma. The catch is that it requires the sending server to also implement it, no way around that.