It wouldnt do it when i tried to super-script2 the TM after the already superscripted 🚫 in a recent post title, nominally to my exceedingly mild chagrin. I cannot underempasize the mildness of said chagrin…
Strike through and sub/superscript never comes across for me on Firefox and Windows.
I get it now
huh ~I can’t get this one to work~
doesitneedtobelikethis ?
this?I don’t think I’ve used superscript or subscript on Lemmy. Kinda didn’t know they existed. And now I want an excuse to use them… So I’m just going to make this comment…
Edit: I’ve been on Lemmy for over two years. The “new user” icon makes me sad. RIP lemm.ee.
Lemmy uses CommonMark spec.
Some clients have diferent parsers, which will allow one for different formatting, but they should stick to the default.
Some users complained about supporting headings in titles so I think that’s one that makes sense to explicitly disable for post titles.
It depends on the client
Some apps / frontends support it and others don’t
Never thought of super/subscripting an emoji😎👽
Edit: 🤔 what happens if I try to subscript a superscripted emoji?
Edit2: wheeeee
Edit: 🤔 what happens if I try to subscript a superscripted emoji?^
this:
Never thought of super/subscripting_an_emoji_😎_~👽~
but spaces break the superscript so you have to use something else for it
testEh.
In a post title, tho (Upvoted immediately ahhh)
