Natanael

Malicious compliance is when you follow a order or law knowing that it will backfire on those who issued it.

“Lawfare” is a comparable term but not quite it (basically legal harassment campaigns).

This affects the view of posts via the bluesky servers, but not via mirrors or other servers

And the use of content addressing means you can be sure it hasn’t been modified

Several Android manufacturers have their own settings in the OS for battery longevity (automatic schedule based smart charging, or charging limits)

Don’t think it’s native in Android. Charging limits need support in the charging controller chip, plus driver support in the OS.

I use my backup headphones when my Bluetooth headset has run out of battery

Telegram has been under fire from the start, lol. 'we have math PhDs" 🤷

There’s also a big difference between published specifications and threat models for the encryption which professionals can investigate in the code delivered to users, versus no published security information at all with pure reverse engineering as the only option

Apple at least has public specifications. Experts can dig into it and compare against the specs, which is far easier than digging into that kind of code blindly. The spec describes what it does when and why, so you don’t have to figure that out through reverse engineering, instead you can focus on looking for discrepancies

Proper open source with deterministic builds would be even better, but we aren’t getting that out of Apple. Specs is the next best thing.

BTW, plugging our cryptography community: !crypto@infosec.pub

Looks like the same dev from reddit

https://www.reddit.com/r/crypto/comments/1iumxl3/how_far_can_i_push_closesource_code_towards_being/

Depends on where the exact cause is. Sometimes it’s fixable in another layer (like a compatibility patch in wayland) if all the data is still there, but it really should be fixed in the driver

It’s usually a driver issue as in limited support for your specific graphics card, where some features are implemented differently from other models and not covered in full by the open source drivers

This is an issue with translating the graphics buffer to the screen, it’s a driver issue. There’s differences in the graphics APIs used by older and newer games, sometimes not every version is tested for a given driver / graphics card combination, so stuff like older OpenGL games might not work the same as a newer one running on Vulkan (or which Proton can translate to Vulkan)

What else do you have installed? KDE Connect?

Yup, don’t be sole owner if you can’t afford a lawyer to make sure you get a good deal

And you can have a union even in a co-op (would mostly help if the majority / appointed leaders make decisions that break some rules, think enforcing safety rules and such)

The Nyquist-Shannon sampling theorem isn’t subjective, it’s physics.

Your example isn’t great because it’s about misconceptions about the eye, not about physical limits. The physical limits for transparency are real and absolute, not subjective. The eye can perceive quick flashes of objects that takes less than a thousandth of a second. The reason we rarely go above 120 Hz for monitors (other than cost) is because differences in continous movement barely can be perceived so it’s rarely worth it.

We know where the upper limits for perception are. The difference typically lies in the encoder / decoder or physical setup, not the information a good codec is able to embedd with that bitrate.

Newer fractional arithmetic encoding can get crazy

https://en.wikipedia.org/wiki/Asymmetric_numeral_systems

Why use lossless for that when transparent lossy compression already does that with so much less bandwidth?

Opus is indistinguishable from lossless at 192 Kbps. Lossless needs roughly 800 - 1400 Kbps. That’s a savings of between 4x - 7x with the exact same quality.

Your wireless antenna often draws more energy in proportion to bandwidth use than the decoder chip does, so using high quality lossy even gives you better battery life, on top of also being more tolerant to radio noise (easier to add error correction) and having better latency (less time needed to send each audio packet). And you can even get better range with equivalent radio chips due to needing less bandwidth!

You only need lossless for editing or as a source for transcoding, there’s no need for it when just listening to media

SMTP?

Except Opus. Beats it at most bitrates

You literally can not distinguish 192 Kbps Opus from true lossless. Not even with movie theater grade speakers. You only benefit from lossless if you’re editing / applying multiple effects, etc, which you will not do at the receiving end of a Bluetooth connection.

That’s more than a codec question, that’s a Bluetooth audio profile question. Bluetooth LE Audio should support higher quality (including with Opus)

Nobody needs lossless over Bluetooth

Edit: plenty of downvotes by people who have never listened to ABX tests with high quality lossy compare versus lossless

At high bitrate lossy you literally can’t distinguish it. There’s math to prove it;

https://en.wikipedia.org/wiki/Nyquist–Shannon_sampling_theorem

At 44 kHz 16 bit with over 192 Kbps with good encoders your ear literally can’t physically discern the difference