# Top stories on Kiwi News, week 44 2026 Mon 26 October to Sun 1 November 2026 (this week so far, updated as votes come in) Page: https://news.kiwistand.com/weekly/2026-W44 The 2 top stories on Kiwi News so far this week (Mon 26 October to Sun 1 November 2026), ranked by upvotes, comments and clicks, with 0 comments in total. Most-shared sources: x.com. Summaries are AI summaries of the linked article. ## 1. @VitalikButerin: Okay with Kimi 3.1 leaving out top-end offensive cyber capabili - Kiwi News: https://news.kiwistand.com/stories/VitalikButerin-Okay-with-Kimi-31-leaving-out-top-end-offensive-cyber-capabili?index=0x6adef52a76eeec7d240f1b977d36a730bba2af973d76fd7996feb65aaee01a395840a7cc - Source: https://x.com/VitalikButerin/status/2114534202788225513 - Submitted by tim, 2 upvotes, 0 comments Vitalik Buterin says he is okay with Kimi 3.1 deliberately leaving top-end offensive cyber capabilities out of its training data. He argues that restricting use cases is much less harmful than restricting users, and that the world needs time to harden systems, check old code, and formally verify new code before powerful cyberattacks arrive. He warns that if this first wave of AI risk is handled poorly, it could lead to a dystopia of locked-down models, KYC gating on everything, intrusive surveillance, and citizens ranked by model access based on credentials and nationality. ## 2. Farcaster clients froze after a chain upgrade merged two hours - Kiwi News: https://news.kiwistand.com/stories/Farcaster-clients-froze-after-a-chain-upgrade-merged-two-hours?index=0x6adf18b4df6ebd34e1f983cec1abaf907b60c6e46cd1c4df05bb1e3431f99fb1ac016dd2 - Source: https://x.com/CryptoStatuette/status/2114044829193605587 - Submitted by misha, 1 upvote, 0 comments Farcaster clients froze after a chain upgrade whose final activation schedule was merged about two hours before it took effect, according to a Resistance HQ Diaries post on the @farcaster_xyz account. The author says they found several clients frozen while trying to check whether the "cockroaches" in the network's APIs had been dealt with, and they traced the cause through GitHub to the late-merged upgrade. The post notes a warning hidden in a PS about nodes that would stop working, and says the investigation into the frozen clients and "bend the knee" errors is ongoing.