Hear ye, hear ye!
How it works:
When you subscript or superscript text, the font-size gets smaller and the line position is raised or lowered. This has diminishing returns, so in order to hack line position properly you need to counteract the size reduction with headings, so: h1, h2, h3, h4 etc.
h1 being the biggest heading obviously has the biggest size increase, which nullifies the previous sub or sup size reductions, so the line position can significantly deviate.
Copy/paste h1 and sub or sup tags as necessary to achieve your desired line position. Stack sub or sup tags together like ⌠sup⌡⌠sup⌡⌠sup⌡⌠sup⌡... to achieve diminishing returns which allow for fine poisitioning.
What FireFish meant about the tag closing was that you need a series of h1 and sub or sup tags to do this, and he needed so much that in order to save characters for the text post Character Limit he omitted their [/ tags] and enclosed the entire abomination in a left tag, which didn't change anything but it closed all of the heading and script tags, allowing the comment to load without them.
In order to get images to load side-by-side like with DANDAN's pfp, well, they align like that automatically, so long as more than one of them can fit in the post width.
That's autistic though, as demonstrated.
⌠left⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠h1⌡⌠sup⌡⌠sup⌡⌠sup⌡⌠sup⌡⌠h1⌡. . . . .
< Your quality content here >
⌠/left⌡