Remix.run Logo
rickdeckard 11 hours ago

This is quite a mixed set of topics mangled together, which is a pity because IMO a cleaner separation would be more beneficial to get the point across.

1. The Ad data-collecting platform TV-manufacturers are operating, what data they collect and how they use it.

2. The vulnerabilities of the OS in a SmartTV, and the potential issues to exploit them for malicious purposes.

3. The general behavior of the device when connected to your network, with features like voice control, App control, Smart Home etc. enabled, and how it may expose information about yourself.

All the points and scenarios in the video might be valid, but they are not sufficiently grouped into one of the above categories.

Instead, it just mixes them all together to imply that its all the same, weakening the whole investigation.

--

The plain example: Using voice-input for a web-search on the TV [0], make long pauses and observe how it keeps populating the prompt-UI with everything you say. This is a matter of #3 above, accusing a malicious intent already on such a trivial implementation topic is harming the whole story

[0] https://youtu.be/6IFVTcM28KA?si=oVqX6NtkxPmqh6R-&t=2951

PinkSheep 9 hours ago | parent | next [-]

You posted a Youtube link with a share ID tracker in it: ?si=oVqX6NtkxPmqh6R-

shevy-java 11 hours ago | parent | prev [-]

I find your "summary" much harder to read and understand, though.

I prefer the original article and the net-benefit of a google-linked video to explain things that already were properly explained, is rather small, at best, in my opinion.

rickdeckard 10 hours ago | parent [-]

> I find your "summary" much harder to read and understand, though.

Sorry, my grouping of topics isn't supposed to replace the entire research-session.

It's merely my observation after watching the actual "investigation video" that they mixed together lots of stuff they discovered into the larger conspiracy that everything is secretly spying on the user to feed a huge Ad-profiling database.

> I prefer the original article and the net-benefit of a google-linked video to explain things that already were properly explained, is rather small, at best, in my opinion

The article was made FROM the video and takes the wrong conclusions and summaries from it. If you want to form an opinion and are a bit technically savvy, you should watch the video instead.

For example: The video actually shows that all audio that is logged was only processed after voice-input was explicitly started on the device, either via the enabled wake-word or by starting voice-input in the web-search UI. The TV continues to show the text-input UI to the user while its transcribing the voice. This is not malicious, this is the expected behavior from user-perspective.