CIRCLE WITH A DOT

@tante Personally it makes me feel a weird kind of sadness.

As if I was looking at someone who's been struggling to open a jar of pickles for 10 minutes but they've got too much pride to admit that they can't open it.

@serafine @puniko I was thinking more about the fact that infosec people just read whatever the news says and then do it in the most half-assed way possible.

For example they might set up logging on absolutely everything and have a flood of crap, because that's what they heard at a conference or whatever.

But it's the opposite of what you should actually do, you should log everything you need to detect something, and then make sure you can actually respond to the thing you need to.

But nah, just enable monitoring on 5 bajillion things and now you have a control panel with 200 flashing red lights 24/7, 90% of which are false positives and you don't have the people or knowledge to filter out the 10% you need to care about and then action on it.

@puniko I hate how much of the infosec industry consists of just checking checkboxes rather than actually understanding what you're securing or why

Finding out there's an SMR drive in your ZFS pool is the NAS equivalent of finding asbestos in your walls

Since the Macbook Neo is limited to 8GB due to how the A18 Pro is designed (Memory stacked onto die on chip). I wonder if that means a second gen Macbook Neo based on the A19 Pro would have 12GB of RAM as that's what all current products with that SoC use.

If they manage to bump the memory to 12GB with the next generation without increasing the price, the Neo's value proposition would suddenly become a LOT better

It could be something really stupid.

For example maybe one of the devices sends SBC audio at a lower bitrate and that makes most tracks sound a bit more bass-y or something. But if that's the case I dunno how to verify it, my speakers don't exactly have much of a UI to tell me what bitrate it's receiving

At first I thought I was going mad and this had to be some weird placebo-ish thing. But no. But when I leave the speakers are untouched and test both client devices with the same audio player (Finamp), same Android ROM, same Bluetooth codec and same audio file, for whatever reason they sound different. The only variable is the hardware, which shouldn't really matter when you never do a digital to analogue conversion.

Are there some real cursed hardware shenanigans going on here? Is there a difference in how the two SoCs compress bluetooth? Or is the audio -> SBC conversion done by some proprietary firmware blob and one of them contains some fucked hard-coded EQ?

I feel like I'm going mad, taking a lossless audio file, then playing it with the same app, and compressing it to the same codec using the same UI and shipping it off over the same wireless protocol should in theory yield the same result, no? Everything is (supposedly) happening digitally in software.

Do Android devices actually transmit differing audio over Bluetooth?

I'm confused because I have a OnePlus Pad 3 and a Fairphone 5, both running e/OS/. But for whatever reason when I connect them to my speakers over bluetooth, both using regular old SBC and volume set to 100% on device (without adjusting speaker volume) somehow the sound from my Pad 3 sounds darker and contains more bass, while my Fairphone sounds brighter and less bassy.

Like wtf, I always assumed that unless your Android ROM tries to do some crappy Dolby or Virtual "Surround" shenanigans it'd just take the same bits of PCM, compress them to SBC and ship them out over bluetooth. Why does it sound different???