Loading video...

Video Failed to Load

Go Home

I almost stopped testing new models altogether. Not because they were bad. Because every call left a number climbing in the corner of my screen, and at some point I started watching that number more than I was building. A flat-rate backend fixed that for agent work. I swapped...

94,458 views • 4 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

For 6 months I woke up at 5 AM to catch Asian markets on Polymarket. During that time I lost my girlfriend, gained 8 kg, and got used to drinking coffee instead of breakfast Then I wrote an agent that monitors everything for me while I sleep. In the 1st month income went up 15% and I finally deleted the 5 AM alarm Turns out a half-asleep human trades worse than a 200-line script I thought discipline meant waking up early. In reality it was just stubbornness that cost me money and health. When I finally sat down to build the agent it became clear why Here is what is under the hood: 1. Sentiment analysis powered by Claude. Every 15 minutes the agent runs a feed from 40+ Asian sources: Reuters Asia, Nikkei, South China Morning Post, Yonhap 2. NLP tone classification. It compares sentiment shifts to open markets on Polymarket through the API, and if the news has already dropped but the odds have not reacted yet that is the entry window 3. Kelly criterion. A mathematical formula for position sizing instead of my usual "I will bet more, feeling lucky" 4. A hard stop at 5% of the deposit per trade so that 1 mistake cannot kill the entire account 5. A cooldown between entries so the agent does not stack up a cluster of correlated positions These are exactly the rules I was missing at 5 AM. I knew them perfectly well but consistently ignored them because on adrenaline and caffeine every bet felt like an "obvious opportunity" When I ran a backtest on my old trades it was genuinely painful: 60% of the bets I placed by hand in a half-asleep state would have been rejected by the agent for failing the expected value filter Those were the exact ones dragging the whole result down When I was building my agent I needed a benchmark. A wallet that already trades on similar logic so I could compare my results to someone else's Found 1 that works almost like a mirror of what I described: same Asian markets, same cold calculation without emotion. I still keep it bookmarked and periodically check how it handles the same situations: That is actually the wallet I started with when testing auto-copying through a bot before I launched my own agent. A useful thing if you want to see how a strategy works on someone else's example first and only then build your own:

Blaze

126,979 views • 7 months ago

Claude Code just found a secret North Korean virus called "CRIMSON-9" taking over iPhones, iPads, and MacBooks, and nothing has ever spread this fast… one person accepts a single Bluetooth file, and from then on it jumps to every Apple device nearby on its own, no tap, no download. It is already on 1.7 million of them. I am not a security expert. I can only tell you what one AI agent found on two phones in my house last week. My brother walked in from the other room, scared, holding a phone that was doing things no one asked it to. He had never touched it. I grabbed a second phone and filmed it, because I knew nobody would believe me. By the time I looked up it was finished. His phone was dead, locked, mocking him on the screen, and there was nothing left to save. Then it hit me that his phone and mine had been on the same network. So that night I ran Claude Code across every device I own. On my phone it found a connection I never made, quietly sending data to an address it traced back to North Korea. It flagged the pattern as something it had never seen before and tagged it CRIMSON-9. As far as it could tell, it started with one file my brother accepted over Bluetooth a week ago, something he thought was a photo. After that nobody had to tap anything. It moved by itself between devices that were simply near each other. Here is what Claude Code showed me on our phones. → it tagged the thing CRIMSON-9, talking to a server it placed in North Korea → it got in through one Bluetooth file, then moved between nearby devices by itself → it had copied our photos, our logins, and the codes our banks text us → then it locked the phone and reached for the next device in range If it can cross a room in one house in an evening, I do not want to picture a train car or an office. I asked Claude Code how to stop it, and it went through every device I own and shut every way in. Here is what I did. → turned Bluetooth off whenever I am out → turned off the setting that lets nearby devices connect without asking → set Claude Code to watch everything on my network and block any device it does not know → stopped my phone from trusting cables and computers it has never seen Now nothing unknown can reach my phone, my laptop, or my kid's tablet without my say. Claude Code blocks every connection it did not approve. My brother lost everything on his phone. I still do not know exactly what it was, but I know Claude Code caught mine before it got that far. The full step by step and the exact Claude Code setup are in the first comment. It takes ten minutes. Save this, and send it to anyone you want to keep safe.

goldtooth.exe

22,996 views • 1 day ago

BREAKING: Claude Code found 12,847 photos of my face on my iPhone that I never took. It looked like the phone was taking them every time I picked it up. From the club. From home. At a red light while I was driving. Almost every time I took the phone in my hands there was a frame. They were sitting in a system cache with timestamps and location data. None of them were in Photos. I plugged the phone into my MacBook and asked Claude Code to scan for any front-camera files that weren’t in my Photos library or Recently Deleted. It flagged Private/var/mobile/Library/Caches/com.apple.faceid. Over 12,000 files. Mix of infrared frames and regular front-camera images. Each one had a timestamp and GPS coordinates attached. I started scrolling. Most were from the last 14 months. Then I saw one from four seconds ago. I was still looking at the folder. Apple says the TrueDepth system turns the capture into a mathematical model inside the Secure Enclave and discards the image. On this phone the raw frames were still in the cache. Several of the processes that wrote to the folder belonged to system diagnostics. A couple of old apps with camera permission also had access to the same directory. I turned off diagnostics sharing and revoked camera access from every app that didn’t need it. If you want to check your own phone, plug it in, run a backup, and ask Claude Code to look for front-camera files outside the Photos library. The folder path above is where mine were.

Cooler

1,430,281 views • 3 days ago