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

From a technical point of view, I’d rather Lemmy didn’t federate except with itself, and maybe possibly also with similar networks, but only as long as that doesn’t hold Lemmy back from doing its own thing.

Getting ActivityPub federation to work reliably between Lemmy instances alone is already proving challenging for developers.

From a personal point of view, I have zero interest in what I consider a shit paradigm of social communication. The “micro” lie in micro-blogging, as you quickly conceded, is long gone. The interface is horrible for effective exchange of well-thought ideas. The social networks formed are hypernormalized echo chambers of unhinged ranting faux intellectuals and champagne activists, usually led by a cult of personality or two who are tasked with making sure the one-upping posturing game continues forever.

When you are about to "micro"blog, presumably you will be writing something coherent enough that it relates to a certain subject of interest to a section of the public. It is also presumably meant to be viewable by the public since you’re not sharing it in a private group chat.

If that’s the case, there should be a community in Lemmy where those interested in that subject congregate. That community would either be low-traffic, then you can make your "micro"blog a post there breathing more live into it. Or it would be a high-traffic one, in that case a lounge/chat/MegaThread post should exist where you can chat with people interested in that subject, in an interface that actually facilitates good discussion.

Sort by “best” is coming to Lemmy, in case you didn’t know.

Imagine if media in Lemmy was all hosted in a distributed network filesystem like Iroh, where instances only function as inserters and exit nodes for that media.

This way, smaller instances can have a smaller cache corresponding to the media that was actually needed by it (recently). And independent peers can help by participating in the distributed file-system network without running instances themselves.

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.

Your information is a few years outdated. lineageOS neither comes rooted, nor does it offer a native way to root anymore. Magisk became a thing with a whole community around it. It’s an unlocked bootloader hider, root manager (and hider), and a system patcher, all wrapped up in one tool.

With Magisk, you give root access to the apps that need it, hide root ability from apps that require non-root devices (those apps do that by pretending to need root). Also, the Magisk app can rename itself, which is important as some apps check against the name itself.

The future challenge is with Google trying to force hardware identification (Apple style). I have not been following developments regarding that though, since as others mentioned, my X years old phone is still serving me perfectly, and I have no intention to upgrade any time soon.

And finally

Okay, finally finally this time. Full CSS with <code> alone also given a background, without breaking code inside <pre>:

li .comment-node {
    padding: 0.5ex;
    border: 0.1ex solid #80808060 !important;
    border-radius: 1ex;
}

li li .comment-node {
    border-left: none !important;
    border-top: none !important;
    border-radius: 1ex 1ex 1ex 0 !important;
}

pre, code {
    background: #EEEEEE;
}

pre {
    padding: 1ex;
    margin: 1ex;
    border: 0.1ex solid #80808060 !important;
    border-radius: 1ex; 
}

blockquote {
    background: #DDDDDD60;
}