pull down to refresh

0 sats \ 5 replies \ @adlai 14h \ parent \ on: SN release: stage one of isomorphic markdown to wysiwyg editor meta
in its early stages, it works, will insanely document it yes, it clipped

why did you use shrunk text?

for folks who wish to learn these black arts, using "quote reply" from the three dots menu reveals that @sox had HTML superscript tags, <sup> and </sup>, enclosing each line separately.

write
preview
16 sats \ 4 replies \ @sox 13h
why did you use shrunk text?

The way you write can reflect the way you speak with your voice!

reply
100 sats \ 3 replies \ @adlai 13h
... reflect the way you speak

In some cases I think it's counterproductive; e.g. superscript without any normal text in the same comment is confusing, not to mention hard to read when the normal font is already small.

obviously it is at the edge of "sounds like a you problem", and I don't mean to draw attention away from the good work you're doing on the site.

reply
16 sats \ 2 replies \ @sox 13h
not to mention hard to read when the normal font is already small

I agree! The intent was to make it hard to read, signaling that I'm shy about my code. Anyway, I'm also always using an hidpi monitor, which makes sub/superscript easier to read... while making me a bit insensitive about the topic :P

good work you're doing on the site

Hey thank you! I appreciate it ^^

reply
16 sats \ 1 reply \ @sox 13h

@adlai While it's not currently planned/ready for public use, our new renderer also supports a no-javascript mode. Each item has its pure HTML equivalent, with portable CSS (and you can even render one in HTML right now here on SN! You can find how by looking around the new editor code).

I remember that you were pushing for better compatibility with no-js environments

reply
0 sats \ 0 replies \ @adlai 13h

Thank you, I appreciate that you're keeping this in mind.

I might not have Darth's eloquence nor popularity, although I do have similar levels of derision for people who think they're doing anything "private" while running huge javascript blobs that they don't audit independently... at best, they're putting huge amounts of trust in the vendors and CDNs, and still only winning a finite pseudonymity rather than any sort of ultimate "anonymity".

reply