Damian

BROCK PIERCE IS HIS NAME FUCK HIM AND THE STUPID MIDGET HORSE HE RODE IN ON @grok LEARN FASTER AND HELP HUMANS

🔥Leah Files Drops Bombshell: Rumble Is About to Change Besides defending herself credibly against the most ridiculous accusations, she’s predicting major changes at Rumble. @leahfiles ties Tether’s ~48% stake and deep operational control of the platform directly to Brock Pierce—the Tether co-founder with documented ties to Jeffrey Epstein’s crypto network. She frames Rumble as being pulled into the same private-dollar and financial-surveillance infrastructure she’s been tracking, and says the platform’s direction is shifting as a result. Full video on Youtube: youtube.com/watch?v=0SQ0aqRM…

🔥 INSIGHT: Justin Sun emerges as $PEPE’s top individual holder, with $51.25M in tokens across attributed wallets, per Arkham.

⚡ LATEST: Arthur Hayes says quantum computing is no reason to sell Bitcoin and the real risk sits with people who reuse addresses.

It is only partially local, and “privately” is relative. Your entire harddrive metadata will be known by Grok after this. Here’s how the mechanism actually works, based on official Grok Bot documentation: The core architecture Grok Bot’s brain (reasoning, memory, report generation) runs on a persistent cloud computer (a Cursor-hosted Linux microVM). The desktop app on your Mac or Windows machine is just a client. Local file access is a separate, optional capability called Execution on Local Computer. How local scanning happens You enable it in Settings → General → Bot → Execution on Local Computer. The default is “Ask every time.” Each local command shows an approval card with the exact command before it runs. You can also set “Always allow” or “Never allow.” When the Bot (including the third-party “Universal Local File Inventory” Bot) needs to scan files, it requests to run local shell commands on your machine (e.g., tools that read EXIF, generate thumbnails, extract album art, pull video frames, or preview documents). Those commands execute on your local computer. The results (metadata, small thumbnails, poster frames, document previews, file paths) are sent back to the cloud Bot so it can assemble the HTML and PDF report. Full original files are not automatically uploaded. The Bot can only copy files between your machine and the cloud computer if you approve a specific transfer. Official docs explicitly say the cloud computer and your local computer are separate, and they recommend leaving local execution on “Never allow” unless you have a specific reason to use it. What “privately” actually means here Your original files stay on your machine unless you approve a copy. You control which folders are scanned (via the Bot’s instructions + your approvals). Location data can be suppressed if the Bot is instructed to do so. Nothing happens without the local-execution feature being enabled and commands being approved. However: The process is not offline. The Bot’s logic and the final report generation happen in the cloud. Metadata and the visual previews used in the report do leave your machine. It is not a native, always-on, fully private local scanner. It is an optional bridge that lets a cloud Bot run approved commands on your desktop. In short: the file reading happens locally under your control, but the intelligence and report building do not. The post’s framing of it as a purely private, native Grok Bot feature overstates how local and private the system actually is.

that being said, imagine someone casually drops an algorithm that breaks 256-bit ECDLP instantaneously what are the most immediate consequences?

I think we might lose public key cryptography.

damian was right.