• 0 Posts
  • 28 Comments
Joined 2 months ago
cake
Cake day: March 10th, 2026

help-circle

  • One thing that people often forget is TVs / stream boxes and Alexa/google assistants.

    Smart TVs all have microphones that are recording (for “voice commands”) and the same with the remotes for stream devices (though probably not unless asked because of battery life), also google and Alexa’s are constantly always listening. They are simply spyware devices that parse everything you say and hand it to advertisers, insurance, governments, etc…

    Phones also suffer from the battery life problem, so jury is still out on whether they listen to you because constantly recording audio would degrade battery life quite a bit (though maybe it is factored in). Phones absolutely do share location data and any phones discovered on the same WiFi network or in the same location if that data was available and from there will share entire search history of devices on the same network (well, that is on the data center end, phones likely just send what devices and for how long they were together). From there it is quite easy to advertised based on search history, unencrypted text data, etc…

    For example in OP, OP had likely searched around about cars and checked out manufacturers websites and such before meeting with the parents (unless they were going in completely blind to dealerships), so it would have shared exactly the cars that they were looking at and linked it to the parents for advertising.

    Still fucked, ethically wrong and legally grey, but “listening” is a bit of an inefficient way to do it, generally.


  • Can you provide one or elaborate on it?

    Embedded developers have tried all manner or wizardry to simply track speed, not even position based just on an accelerometer/gyro, but the sample rate error drift is so large that putting a GPS module in there is 100x more accurate for deriving speed.

    I would be interested to see how a browser, which almost certainly doesn’t get the full serialized data, is able to track just based on that which the wearables industry have been trying for decades with bad results.




  • Yes, but also on the hardware level.

    I don’t know enough about OS programming to know if it is the architecture or the (closed source, as mentioned) CPU design itself that is more difficult to implement.

    Looking at the MCU space, even with a known architecture (like ARM), each processor has to be individually implemented in software and firmware which is a ton of work, and the only people who necessarily know how are the processor designers unless it is open source. But take that with a big block of salt, because I have never done it, just looking at industry practices.