if you want to stop your TV from spying on you, but don't want to get banned, follow these steps 1. Use less censored models, like GLM 5.3 or abliterated qwen. From OpenRouter, Venice, abliteration etc 2. Make sure your TV and pc/laptop are on the same laptop 3. Install a coding agent on your PC, like cursor or opencode 4. Enable developer options on your tv, enable USB or ABD debugging, and find your TV's ip 5. tell your agent to clone github.com/Gathin23/cleanyou… or dumb TV's repos, then paste the prompt from the repo. 6. Agent will connect to TV via adb connect <TV-IP>:5555, make a backup, then disable ads, data collections, and bloatware. 7. after agent's done, it will install a clean launcher and give a restore script. after that you disable debugging on your tv. this method will work on android or google TV, Fire TV/OS etc. rooting is harder on Tizen and webos but possible. or use DNS blocking with Pi-hole, NextDNS, AdGuard etc to block ads/spywhere This is how you avoid getting blocked on openAI, but of course always do your own research.

this is pretty evil and clever. so if your samsung TV model doesnt have a microphone, it will look for connected devices with one, such as a soundbar or a connected bluetooth device. this gets shipped off to bixby.

A couple interesting rumors made the rounds at ApeFest about Mudwater. 👀 I know Series 1 has only been out for 5 days, but hear me out. 🎴 Series 1: BAYC history and lore. Potentially the smallest circulation and most limited retail distribution. 🎬 Series 2: Rumored to tie into the upcoming BAYC anime, with both activations potentially feeding off each other. If Series 1 succeeds, could we see a bigger production run and wider retail distribution? Very early speculation, but an interesting possibility to consider while Series 1 is just getting started. Rumor 2 in second tweet 👀👇

In April of 2025, eMudhra (an Indian Certificate Authority), published 8 intermediate CA keys which were so weak that a small child could guess the numbers in a few seconds. One of the private keys was, literally, 4. Just… 4. This massive problem was not made public until October 17th of this year, when it was discovered by an anonymous guy on the Internet who goes only by “Wayne” (like “Cher”…. but… “Wayne”). What this means in practical terms: It has been trivially simple, for the last year and a half, to create fake “secure” HTTPS certificates. (One person even created a fake HTTPS certificate for a Google.com subdomain.) It took Mozilla 3 days, after learning about this (from “Wayne”), before they updated their certificate list (which many open source projects — including curl and Python — rely upon). As of this moment, many systems are still vulnerable (including macOS).

Apparently there’s a patch for the critical PHP vulnerabilities but a few things that are alarming. 1) Many websites that use php with sensitive information are simply abandoned. There will be no upgrade. That means they’re going to get pwned and leaked. That’s a LOT of the internet 2) This requires active participants to upgrade their sites that even know about this vulnerability. If you’re on X you’re at the tip of the tip of the spear. Most people don’t know about this. 3) Anthropic says that this is ONE of SEVERAL critical vulnerabilities that they have found. Which means there’s more chaos coming. TLDR: A large portion of the unmaintained internet is about to be pwned and god help us all or something like that.

Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.