Qwen-3.8 vs Kimi-K3
Prompt: "SVG animation of a real tennis rally, two players going at it, physically accurate, follows real-world logic."
This one took me 2 hours to generate. Maybe that's on Qoder, not sure. Qwen-3.8 spent 40+ min just thinking and planning, then another hour writing the files and squashing bugs.
But the result? Genuinely clean. It's got sound, and a bottom bar showing live commentary, ball speed, rally count, and shot analysis.
Kimi-K3? No sound, and the stats bar is buggy. Doesn't update in real time.
Qwen-3.8 vs Kimi-K3
More posts
Just found a legit 0-cost local solution for Agent search &
crawling I’ve been playing around with this open-source project called wigolo lately. It lets you do full search, scraping, crawling, extraction, and research—all running completely locally. No API keys, no cloud services, nothing leaves your device. This means your agents can search the web and grab pages for free, without relying on Firecrawl, Exa, Tavily, Brave, Jina, or any of those other paid tools. Super clean for regular users too—no more messing around with API keys or environment variables. github: KnockOutEZ/wigolo
Alibaba dropped Qwen3.8. Only Fable 5 is ahead of it right now.
2.4T params. Open source. Biggest Qwen model they've shipped. Qwen3.8-Max-Preview is already live. You can use it on Token Plan, Qoder, and QoderWork. No benchmarks out there yet. I'll test it myself later and share what I find.
Claude appeal rejected.
Won't refund the subscription either. I'm half convinced the appeal email is itself phishing, because I'm pretty sure they log the IP. DHH came to Shenzhen recently and showed how he uses Claude Code over there. That's the safest way now, honestly: run Claude Code on an overseas machine, connect through Tailscale, never use it locally. So I need to rent an overseas box with a residential IP, and register and log into Claude there.
Sharing my current mobile only workflow.
Until late September it was the usual setup: parked in front of my laptop, terminal open, bossing pi around, fanning out subagents, then eyeballing diffs myself and filing the PR. Glued to the chair all day, every day. Late September I moved the whole thing to my phone, Hermes runs the show, pi takes the orders. My back is very grateful. Three weeks in, still no regrets. Stack: Hermes on flagship brains (gpt-6-astra / opus-5.5), pi on mid-tier (ds-v4.1-flash / sonnet / terra) with as few plugins as possible, the two talking over a2a. Hermes reads the issues, slices them into small tasks, spins up a worktree for each one, and dispatches a pi into it. When a pi finishes it pings Hermes, who decides: ship the PR or bounce it back for rework. I get back from a full day of being a tourist, or just wake up, and a dozen PRs are sitting there done. Pretty sweet. The catch is how black-box the whole thing is. My emotional arc has been a rerun of early vibe coding, except back then I at least read the diffs. Now even that goes to a flagship model. Boxes all the way down. If you don't have data anxiety, grok-bot and chatgpt-dot basically ship this out of the box, grok-cli and codex built in, native agent-to-agent comms. Downside: your code lives on their servers, everything's moderated, and one ban takes it all with it.
