A major problem with managing unemployment from AI might be people's inflexibility. Anecdotally, I know someone living off their wife's parents for several years while searching for a specific position and salary.
“UBI” is obviously nowhere near the panacea many of you seem to think it is. The median left-leaning Westerner isn’t angry at Elon Musk because he can buy a million times more groceries than them. They aren’t upset with Palantir because Peter Thiel can afford to eat a thousand burgers to their one. This whole thing is in large part post-material. It’s the hierarchy & subordination they’re uncomfortable with. They feel their dignity is being trampled and their autonomy progressively diminished – rightly or wrongly they feel politically disenfranchised and stripped of a say over the future. Offering a guaranteed food budget and a pod to spend the night in return for further disempowerment is incredibly tone-deaf and should be expected to provoke more, not less, outrage.
Workshop Labs is joining @thinkymachines.
We believe there's a path for AI to make humans matter more. We couldn’t be prouder to join Thinking Machines to see this work through.
https://t.co/Ne2vrVYthh
I tenatively believe it would be good if all AI companies had a policy of doing external deployment before internal deployment, because the largest risks are from internal deployment and external deployment improves visibility.
Large internal/external gaps seem dangerous. 1/
@AddieF38654@UnslothAI Third: how we made post-training and inference happen so privately that even we can’t your data.
Very excited about this! Hopefully it becomes an industry standard
https://t.co/o8VnqZFanN
@alth0u@luke_drago_ The original implementation also doesn't train the experts. This is a huge hit to actually gaining new capabilities, though may be sufficient to remove safeguards. Imo, the 50x slowdown is enough to make it ~unworkable. Feedback loops look like a day+ rather than 30 mins
@alth0u@luke_drago_ Idt spending more can get around serial speed bottlenecks, except for by implementing faster training code (which could happen but is a higher bar)
@alth0u@luke_drago_ Independent from the risk or lack thereof of releasing training code, I'm excited to see the results for Kimi. I think everyone's out of the loop on what various capabilities of open source models are, with and w/out elicitation, and risk-relevant ones seem pretty pertinent
@alth0u@luke_drago_ The original implementation also doesn't train the experts. This is a huge hit to actually gaining new capabilities, though may be sufficient to remove safeguards. Imo, the 50x slowdown is enough to make it ~unworkable. Feedback loops look like a day+ rather than 30 mins
@ZoeyLi20@WorkshopLabs Megatron/NeMO it requires a multinode setup and with kimi-k2.5, it's set up for full parameter training rather than LoRAs. it's possible to modify it, but I'd guess it would be even more painful
Introducing Trellis for Kimi K2 Thinking.
It's post-training code that's 50x faster than the best single-node open-source version and 2x cheaper than training APIs.
After safety testing, we're open-sourcing it, giving builders the best tools to customize a frontier model.
🧵
@hezhao_z@WorkshopLabs But from a quick glance, I also thought it's likely possible to speed up compress_model especially in cases where there's many modules/parameters in the model (like MoE's). Happy to chat if it would help!