🇳🇱
Oh no I am falling down a black hole.....
@FailForward it will only render as we see it on QOTO on a few instances, it uses the miskey format for quotes so misskey instances will see it rendered properly and a few other instances.
@Matt should still see it as a link attached to the post though so it will still "work" for him in a sense.
Yes with so many flavors on the fediverse that is true. The problem is that it is also willful from some developers.
All the stuff I added I tried to use standards as much as they exist. The issue is that some developers intentionally want to break consistent rendering for their own vision, so it isnt a bug it is a "feature" in their mind.
Take the markdown stuff, it converts the markdown into html tags so rendering should be consistent across all clients without any need for a client to do anything to support it. However Gargron, and thus vanilla mastodon, specifically invisions a no-rich text scenario. They felt rich text was offensive to many users. So they go out of their way to strip it out and remove it, actually taking extra steps to **break** from the standard. He had considered making that feature optional but ultimately rejected it as the developer who implemented it got frustrated with the repeated rejection of his PR and i think the community gave him a hard time about it so he dropped the feature kind of out of spite for how he was being treated.
So sadly consistent rendering is something that is impossible to really garuntee. I think qoto probably handles and renders the most standards that are out there really, we handle rich text, and quoting and math latex (though thats buggy and i need to fix it soon)... we pretty much handle it all.
@freemo @FailForward @Matt I think as we are a science based instance then the nice rendering is important esp with the LaTeX support.
