The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
blog.includesecurity.com
The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
1–10 of 114 posts
Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#2Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#3Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#4Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#5wss://proxyjs.brdtnet.com:443
This hostname resolves to AWS Global Accelerator IPs
There is some irony that both the scrapers and the websites being scraped are probably hosted on AWS, while playing an elaborate cat-and-mouse game pretending that they weren't.
Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#6I find Cloudflare to be more unethical than Bright Data.
If the divide was data center vs residential IPs, fine, but thanks to Bright Data and friends, residential IPs are getting suspicious as well, so I guess the next step is full-on client verification then...
Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#7I never connect any “smart” device to wifi. If it doesn’t work without connectivity, I don’t want it. I use my TVs as display devices. They have HDMI-in and that’s it.
Thankfully, the blast radius of this is nothing without connectivity.
Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#8Imaging having the police show up at your door because they've figured out that you're trafficking child porn, when the actual culprit is someone that is using your TV as a proxy to trade child porn.
Re: The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy
#9I find Cloudflare to be more unethical than Bright Data.
Both are causing a dynamic that will lock down the internet evermore for everything straying slightly from the corporate-approved line. If the divide was data center vs residential IPs, fine, but thanks to Bright Data and friends, residential IPs are getting suspicious as well, so I guess the next step is full-on client verification then...