Not audiophilic enough.

ffmpeg -i in.flac -ar 48000 \
            -af aresample=resampler=soxr:precision=28:cheby=1:dither_method=shibata \
            -c:a libopus -b:a 224k out.opus

Search is broken in Reddit right now (for me at least). Best part is, it doesn't always report an error, just pretends there are no results.

Oh, and Reddit Status doesn't know yet.

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.

Click the "more" button (three vertical dots), then the flag button!

Sort by "best" is coming to Lemmy, in case you didn't know.

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.

Funny you should mention that. I think iced as of four days ago can do this!

If I'm reading the release notes and Cargo.toml right, cargo add iced --no-default-features and you should be good to go, as tiny-skia will be used as a rendering backend instead of wgpu.

I do think it is the future of filesharing

In internet years, Torrenting is old. I2P is old. Even torrenting in I2P is old. Nothing about this is "the future".

Ideally, the future of file sharing would involve a fully/natively integrated anonymous network with content-addressable distributed filesystem.

But this will probably not happen, as that architecture didn't see large scale success before, except in Japan where at least some elements of this architecture are used in their popular P2P networks.

The I2P crowd themselves tried with Tahoe-LAFS, but that was never really a network, even aMule over I2P had more traction, and by traction I mean tens or hundreds of users, not thousands or beyond.

Ironically, the one content-addressable distributed filesystem that gained some attraction (outside Japan) is IPFS, which doesn't offer anonymity, or replication, or anything special really. Yet for some reason, some hype-susceptible techies liked it, together with the NFT crowd, a great fit.

The future of file sharing will depend on where most content will land where it will be easily accessible and quickly grabbable. How those networks will look like? Nobody knows.

Broken input sanitization probably.

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

While this is indeed paranoid and not well informed, I'm kind of appreciating... the GNU appreciation.

Makes a good change from all the hypernormalized Twitter/Mastadon non-coders, or self-proclaimed coders (the kind that uses terms like "imposter syndrome" every day), always bitching about how GNU was a mistake, and all it did was provide free labor for corporations, and how the FSF and Stallman are all kinds of bad and wrong.

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!

Blog announcement.

if you’ve been following us for a while you know we’re passionate about #Rust! 🦀

who's "us"?
following where?
is there a reason to particularly care about ᐸwhoever you areᐳ's passion for Rust?

^ only meant half-seriously to point to the silliness of microblogging to a discussion community.

Note: the ᐸᐳ characters are Canadian Aboriginal syllabics because Lemmy devs haven't fixed broken input sanitization yet.

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.

• Don't use "*" dep version requirements.
• Add Cargo.lock to version control.
• Why read to string if you're going to base64-encode and use Vec<u8> later anyway?

Lemmy instance choice does not check out ;)

I'm not talking about inherent brokenness that was always there.

There is a specific search with a non-dictionary word, and limited to specific sub, that always worked, but it's not working right now, returning zero results. Reddit search is fully broken right now (except for finding sub names if you don't limit the search to a sub).

Problem is still persisting btw. And Reddit Status still reporting no problems.

Defederation questions/requests should be made in private, at least initially. That is to avoid turning an instance, which may temporarily not be actively administered/moderated, into a hotbed of illegal posting.

As it stands, any concern troll can turn a random small instance, which may not have an admin around for two days or three, into a hotbed of illegal or potentially-illegal activity, simply by bringing attention to it with a public defederation request.

Even with the presumption of genuine concern, the effect and end result will be the same.

I constantly seem to include something from the docs, only to be told by the compiler that it does not exist, and then I have to open the source for the create to figure out if it’s hidden behind a feature flag.

As others mentioned, the situation is not perfect. And you may need to check Cargo.toml. Maybe even the source.

But as for the quoted part above, the docs should definitely indicate if a part of the API is behind a feature. Let's take rustix as an example.

Here is the module list:

Here is the view from inside a module:

Here is the view from a function page:

This is also true for platform support. Take this extension trait from std:

Now, it's true that one could be navigating to method docs in the middle of a long doc page, where those indicators at the top may be missed. But that's a UI issue. And it could be argued that repeating those indicators over and over would introduce too much clutter.

Because the audiophile is broke, and will have to listen to some music on a lowly device, but the craving for some placebo is still there.

EDIT: btw, the bitrate is missing a k in your command 😉