Conversation
Notices
-
Embed this notice
the issue in having anything else than commonmark/markdown (like KaTeX or MFM) seems to be accessibility (it's also a pain to port on many clients, translating spinny text on Husky is... yeah)
\hspace{1em} does not translate well
**hello _gort_** does, because even if you don't have markdown support, if you see the source, you still understand it almost as well
i want to see more things like that in markups, though, it would be very nice, but that is a difficult task
-
Embed this notice
@helene Are headlines supported in markdown, in notes?
-
Embed this notice
@7 yeah, at least in Pleroma, though Pleroma-FE does not make h1, h2, ... tags larger
-
Embed this notice
@helene I was wondering about that. Good to know, thank you.
-
Embed this notice
@helene But I specifically want delimiters that encode the text in-between to base 64. Every app should do 64this64 → dGhpcw==. It is absolutely necessary and I use it in everyday talk :acat_deranged:
-
Embed this notice
@helene @7 i think that is supported but only when it comes from blog stuff, not regular instances
though it would be nice to display them but (again) i believe these tags are stripped by backend, like tables :(
-
Embed this notice
@duponin @helene </3
Is it a conflict with hashtags? I haven't tried in a while but I remember at one point hashtags being weird with markdown on in pleromafe.
-
Embed this notice
@7 @helene hashtags are known to be buggy with Markdown
but nah, that’s unrelated, stripped tags are for safety reason