RunAwayFrog @ RunAwayFrog @sh.itjust.works

Posts

3

Comments

66

Joined

2 yr. ago

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.

I only use(d) it in a specific way. For example searching for a sport club (non-dictionary) name, limiting the search to that sport's sub, and sorting by new).

For general search, a search engine would indeed probably work much better.

Problem found and solved according to Reddit Status btw, and confirmed by my own tests.

When have you ever found anything you were looking for with it?

Always.

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.

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.

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.

This should be de-stickied. The instance appears to be receiving zero maintenance (still on 0.17.4, enough said).

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.

Or “Hyphanet” as it’s now called.

wtf, I missed that news.

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

Yes. That was what I'm alluding to when I wrote:

that architecture didn’t see large scale success before, except in Japan

Perfect Dark is a major network in Japan. Freenet is a network most people in the globe are not aware of. Hell, Perfect Dark may have a larger Japanese user-base than Freenet's global one.

It's worth mentioning that the former leader of the Freenet project wasn't the most competent. Combine that with him spending years trying (and failing) to cater to the needs of imaginary dictatorships' defectors (anyone of them using Freenet instead of Tor is the imaginary part), instead of focusing on maximizing the reliability and performance of the network to help its actual users. So it's not just the ignorance of the masses that was at fault. The default FN user experience was often a horrible one. And users needed to ignore the officially-recommended microblog/forum applications, and even use a patched FN version, to get a decent performance out of the network.

Anyway, Freenet is the past and the present. And as I wrote in the parent comment, I hope a Freenet-like network would become a major success in the future, but I'm not holding my hopes up.

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.

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>:

  CSS

    
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;
}

  

And finally, quotes need a different background too:

  CSS

    
blockquote {
    background: #DDDDDD60;
}

  

Alright, for code blocks, this looks good enough for me:

  CSS

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

  

And <pre> with a <code> inside it needs a class so we can easily set a different background for it! (edit: or maybe just set a different background for <pre> regardless of content).

People really do have the memory of a goldfish.