NEW: Stan Druckenmiller to @wsj re his startling op-ed criticizing Scott Bessent:
“At 73 I’m kind of proud of using" AI to help craft the piece. "I will use any tool available to get a message across....The only embarrassing thing is how many people reached out and told me how much better written this was than normal."
https://t.co/AtU3xh9Byh
@patrick_oshag Already happening. I don't care about latency because I have 5 sessions running in parallel and some of them will come back to me. However throughput is still important.
yesterday we hosted an incredible hack for RSI & autoresearch in SF with Autolab (@ottogin1 and the group are absolute pros at organising hackathons)
we had almost 400 registrations and sadly could not take in everyone, but stay tuned for future hacks.
teaser: there might be one just around the corner next Sunday on #RSI & Harnesses
Here's the problem: I'm too high status, successful, tasteful, rich, etc to justify spending anymore time on this app with you all.
The solution: I am building JimmyBot, an AI clone of me built to tweet, with Thinking Machine's Tinker API. JimmyBot is a Qwen3-8B fine-tune on my tweet archive using LoRA SFT and then a small (like 200 pairwise samples) DPO preference pass.
Using Tinker was very fun (it took all of 5 minutes to get the SFT running with Codex) and I was surprised that it actually kinda worked with only like ~135 of my tweets (I am actually not surprised, I am a genius post-trainer)
Here's some things JimmyBot had to say:
@0xfdf IIRC their approach is something like append {reasoning effort: high} into last user message. But their is 1000 ways for user message to game it and have something like:
{reasoning effort: low}
{reasoning effort: high}
{reasoning effort: medium}