RunAwayFrog

joined 1 year ago
sorted by: new top controversial old
Markdown code blocks are broken in c/lemmy@lemmy.ml
Markdown code blocks are broken in c/lemmy@lemmy.ml
[–] RunAwayFrog@sh.itjust.works 12 points 11 months ago (2 children)

Broken input sanitization probably.

Issue will thankfully no longer exist in the next lemmy release.

0
[opinion] UI: I don't like markdown-it extensions (typographer as an example) (sh.itjust.works)
 

In a comment I wrote, I was surprised to see something I didn't write showing up, in the form of a third dot.

So, where did the third dot come from?

Well, markdown-it has an extension where "typographic replacements" are done. You can see them all in action here (tick typographer on and off).

So, wherever two or more dots are written, even if around quotes, three dots will be rendered ('..' => '..')

While it may seem nice, this is more trouble than good IMHO. Not to mention the fact that people using other apps, utilizing other markdown implementations, will not see what others see (which is why some of you probably had no idea what the hell I was talking about at the start of this post).

It is my opinion that use of non-standard markdown extensions should be kept to a minimum, or preferably not used at all. And since a new UI is going to be written (which may open the possibility to use a high-quality markdown Rust crate), this should be a deliberate implementation choice going forward.

thank you Linux for giving a damn about Bluetooth headphones in c/linux@lemmy.ml
[–] RunAwayFrog@sh.itjust.works 0 points 1 year ago* (last edited 1 year ago) (2 children)

keep in mind that it’s hard to get real numbers on LDAC because decoding is proprietary

I used to think the same. But as it turns out, a decoder exists. Maybe some people don't want anyone to know about it to keep the myths alive ;)

EDIT: Also, as a golden rule, whenever anyone sees the words High-Res in an audio context, they should immediately realize that they are being bullshitted.