$TBT out more runners @4.7 from 2.10

$WEAT vol is priced for a normal year. this isn't one stacked on the same crop: black sea supply still impaired, the fertilizer shock from the strait closure hitting next year's yields, labor enforcement changing farm economics, el niño peaking over australia's harvest in Q4, tariffs, and a food-quality problem nobody has priced at all that's five or six independent shocks. implied vol is priced like one of them has to be true

$WEAT big gap down in the morning and now hammering/above 50 MA daily

$NKE r/g after that downgrade this morning

$CORN look how beautiful this looks, filled the gap and shook off the weak hands and now should resume higher

$CBRS looks ready @OpticleTrade Size $210 calls for next week bought, trading 3400x

$TBT like I said folks in disbelief about yields rising

$TBT look at the move on this one so far...

$CBRS might finally be ready

$WEAT March 2027 $30s @.90

$GH continues to grind higher

$TBT folks going to be in disbelief soon

$WEAT $CORN $SOYB the whole commodity complex is at the same test right now $WEAT coiling above its breakout shelf after four inside weeks. oil at its own level. ags broadly re-accelerating off multi-year bases We're all gonna find out here how strong thse moves are imo (oil, ags, etc)

Interesting $FSLY finding from testing Meta Muse. Through a series of hundreds of tests, it appears that the $FSLY role with Meta Muse is greater than analysts have noted Over the past week, I created several test websites and ran 738 controlled tests to send traffic from Muse agents to my websites I set up analytics on my website, and I was able to track things like IP address, user agent, operating system, etc From the IP addresses, across the 738 tests, Muse sent traffic from: -Cloudflare: 37.0% -Fastly: 29.3% -Meta: 19.4% -AWS: 14.4% Cloudflare is not a surprise – as there has been a lot of analyst commentary about Muse using Cloudflare. Fastly, on the other hand, was a surprising result I ran many different situations and tasks to try to understand why, or when, Muse sends traffic through Fastly – or others. And when I looked deeper, Muse used Fastly for 100% of the tests when browser navigation was required (e.g., “go to my favorite restaurant’s website and find me the menu”). And when Muse was requested to navigate on a website (e.g., make me a doctor appointment), Fastly was used in 100% of tests Then in other situations, for example when an API is involved or a curl request required, Cloudflare was used in 100% of tests Lastly, when requesting Muse to search the web, Muse split traffic through Fastly, Cloudflare, Meta directly, and AWS

$TBT what a run so far but more to come imo

$WEAT think we hit my $31 tgt next