@sally@hfaust >the amount of effort it needs to go through to get this done, they would've got caught already and exposed by countless parties Yes, the proprietary masters have gotten caught and gotten exposed, but they don't have to care about that, as people simply refuse to believe it is happening.
The only people who have the irrefutable evidence are the ones who write the malware, under heavy NDA (and therefore have no motivation to expose themselves) - for everyone else, it's proprietary binaries that is difficult to even get a copy of (as such binaries are only distributed as direct-to-device updates and such devices are designed to be extremely difficult to extract the relevant programs from (you can't just dissemble an iphone and dump the NAND, as the whole NAND is encrypted and you're not allowed to have the key)).
It's like when the Snowden revelations came out and confirmed that the NSA had been doing things 10x worse than what people warned the NSA were likely doing - people just refuse to believe what's happening.
>It's not just the recording part that has to go through, it's the encoding all that audio and then send it through WLAN to whatever server Crapple wants to send it for process and storage. The audio itself does not need to be sent - the device now contains a sufficient advanced processor than can process the audio and possibly even transcript it on the device - and a bit of text and metadata is extremely small and with compression it could easily be transmitted over a mobile network unnoticed.
>it revealed nothing, with an idle phone left on a room with random audio of conversations there was barely any network activity involved, only random pings at servers via ICMP to verify there's still connectivity Why would scanning what goes over a Wi-Fi network pick up what goes over the mobile network?
Has the ICMP payload been checked? (good luck differentiating between a randomly selected ICMP payload and compressed+encrypted text transcript+metadata).
Also, iPhones have the ability to send data without a mobile network or a Wi-Fi AP - it's called "airdrop" - which could quite easily be used to make a meshnet to transmit small amounts of data (and how would anyone notice?).
>There's also the fact that encoding audio and sending it through WLAN consumes a ton of battery, unless you're doing the encoding through hardware, that is. Yes, the iphone has hardware acceleration for audio codecs. At a pathetic bitrate that is still good enough for speech, not much battery would be consumed.
>it's even more wasteful to encode raw PCM16 audio into a lossy format and then send it to some server, specially in real time. As I pointed out, it does not need to be in real time.
The devices have sufficient storage that a days worth of audio could easily be encoded and slowly sent via ICMP packets when the device is being charged (which most NPCs do daily).
>Every single person I've heard making such claims turns out they searched about the thing earlier on through a web browser on a device with their accounts logged in Every single person I've personally heard making such realization did not search about the thing.
Obviously there is other ways to get targeted advertising.
>In a couple years where disgustingly proprietary hardware will be so fast and so efficient at handling proprietary garbage printers such as LLMs and algorithms, all of this might become a reality Proprietary hardware is now fast enough that it's the current reality, no matter how much you deny it.
@eric For LGPLv2.1 libraries, they are required to ship the source code on a "medium customarily used for software interchange.", which can be a DVD or a flash drive etc, but can't be a floppy disk (as floppy disks are no longer used for software interchange).
@eric They aren't really following the license terms, as the written offer is for "open source code" and the LGPLv2.1 is not an "open source" license, it's a free software one.