https://github.com/LemmyNet/lemmy/pull/4024

Broken input sanitization probably.

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

https://github.com/LemmyNet/lemmy/issues/3827

Would you have escaped them a priori?

Do you consider markdown-it’s typographic replacements common knowledge, and thus intuitively escapable?

Should lemmy apps be pushed to use markdown-it, in your opinion?

their live demo

I meant the markdown-it live demo.

I wrote a separate post about this.

While it may seem nice

No, it really doesn’t, its a horribly bad design choice.

I wanted to give some balance to my argument. I guess I was over-cautious with that one.

@dessalines@lemmy.ml

And btw, that’s '../lemmy' in the comment above with two dots. I didn’t write it wrong. The third dot comes from markdown-it (confirmed using their live demo)!!

Good, because I speak Rust, so, if there is an itch to scratch, I will scratch it, even though I’m not a UI guy.

I tried running the UI yesterday standalone and had ‘error loading’ message or something like that.

btw, mentioning needing ‘…/lemmy’ available in path, and needing the wasm target installed (via rustup target install wasm32-unknown-unknown) may help non-rustaceans in particular, if added to the contributing instructions.

Also, the UI was listening on *:1237, not just localhost, so maybe a WARNING regarding that is advisable, together with explaining the purpose behind leptos also listening to port 3001.

Will there be a way to run the UI in client mode only, without being attached to a running instance?

The codec is basic, uses decades-old tech, and was trivially REed.

Lemmy instance choice does not check out ;)

and for testing you get a wackload of SBCs and Bluetooth chips and test that

I asked because I wasn’t aware of any consumer buds supporting Opus. I wasn’t aware of PineBuds, thank you for mentioning them.

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.

After testing LC3Plus, Opus, and AAC personally for bluetooth, LDAC claims are BS

How did you test Opus for bluetooth?

latency is significantly better then AAC (tested against libfdk) and marginally better then opus

In case you didn’t know, you can use 10ms (or even 5ms) frames with Opus instead of the default (20ms). 10ms should roughly match LC3plus’s default latency while still retaining high quality.

LDAC claims are completely bullshit.

LC3plus is worse than AAC quality wise (to be expected). Lower latency is the only thing going for it. And that’s just because AAC is a very high-latency codec. Opus (as a format) would win on both fronts, although there could be issues with creating a high-quality encoder for it that is not too complex, and power-efficient.

People really do have the memory of a goldfish.

Don’t know if this will be relevant at all, but I’m almost hoping this will force Lemmy devs to abandon the obscure markdown crate they use for pulldown-cmark.

Using an obscure markdown implementation just because it supports spoiler tags always sounded like a silly decision to me!

I won’t be able to fully replace it, I’m afraid. Not before communities gain the ability for their posts to not show up in high traffic feeds.

Some subreddits I follow have this set, but this is not yet implemented in Lemmy if I’m not mistaken. So a workable move to Lemmy for them is not possible at this moment.