Matt Hamilton retweeted
Major IT systems start failing 18 months after drugged up silicon valley dipshits convince everyone to ditch their experienced coders for a machine that doesn't know how many Rs are in "strawberry".
Everyone: "Must be a cyber attack"
Matt Hamilton retweeted
The Departments of Dumb and Dumber #seanduffy #markwaynemullin #politicalcomedy #politicalsatire #omg
Matt Hamilton retweeted
Replying to @olivialarinaldi
A complete overhaul by an administration that can't even rehab a reflecting pool without F'ing it up beyond recognition?
Matt Hamilton retweeted
If Jensen had molested kids on an Israeli honeypot island like a normal billionaire instead of banging adult chinese honeypots, all of this couldve been avoided.
Proof of Work and Proof of Stake use the Nakamoto fork choice algorithm.
With practically low halt likelihood in exchange for lower safety. It prefers to continue closing blocks even when it's not safe. Liveliness over security.
On the XRP Ledger the fork choice is done via the preferred ledger algorithm. It prefers to halt producing new blocks when it's not safe to do so. Security over liveliness.
That's a key aspect i particularly like about our consensus algorithm, security thought is deeply embedded.
Matt Hamilton retweeted
An OpenSSH bug that took 46 years to ripen!
1980
UNIX puts * in the password field of system accounts. The idea is simple: it’s not a real hash, so it can’t be brute-forced and you can’t log in with a password.
2012
The musl libc developers decide that returning NULL from crypt() on failure is dangerous - programs often forget to check it and crash with a segfault. So they return an error string instead.
Guess which one?
The same asterisk: *.
Three weeks later they add a length limit: passwords longer than 256 bytes burn CPU. Anything longer is rejected. And since it’s an error, crypt() returns *.
2016
OpenSSH fixes a timing attack (CVE-2016-6210). If a user doesn’t exist, the server still hashes the password with a fake/borrowed salt so an attacker can’t tell valid usernames by response time.
2022
Alpine Linux changes the locked root password in /etc/shadow from ! to * so SSH keys work properly on cloud images.
… and the loop closes!
You connect over SSH as root (whose shadow entry is *).
You type any password longer than 256 characters (e.g. 300 As).
crypt() hits the length limit → returns * → OpenSSH compares it with the value in the database → that value is also * → you’re in as root.
That chain took 46 years (!!!) to complete.
Every individual change was reasonable. Together they produced a perfect * == * authentication bypass (CVE-2026-123158, nicknamed *sshole). Fixed in OpenSSH 10.6p2 and Alpine packages.
🚨 Critical OpenSSH flaw allows passwordless account access using any password over 256 characters
sshhole.com
A newly disclosed vulnerability dubbed *sshole has been discovered in OpenSSH installations using musl libc, potentially allowing attackers to bypass authentication and gain access to accounts that should reject password logins entirely.
The flaw affects certain configurations of Alpine Linux, OpenWrt, Buildroot, and Yocto where PAM is disabled and password authentication remains enabled. Under specific conditions, attackers can authenticate to locked accounts using arbitrary passwords between 257 and 1,024 characters.
The researcher demonstrated that affected Alpine Linux cloud images could allow attackers to gain root privileges through a passwordless administrative account.
OpenSSH 10.6p2 addresses the issue. Administrators are urged to update immediately or disable SSH password authentication until patches can be applied.
Matt Hamilton retweeted
Four Bittensor subnets pushed the AI frontier in just 24 hours.
On the latest Novelty Search, @const_reborn highlights major advances from @MacrocosmosAI, @trishoolai, @reliquary_ai and @chronollm across decision models, AI safety, decentralized training and historical LLMs.
Teams from ChronoLLM, REAX and Reliquary also join to discuss their latest research and results.
Full episode in the first comment
Matt Hamilton retweeted
Bittensor’s open competition just produced a world-leading AI decision model.
REAX 1.3 has the highest score among 270+ entries on the Decision Index hosted on @huggingface, ahead of leading models from Perplexity and Fastino.
🥇 REAX 1.3 is #1 on the Hugging Face Decision Index.
We produced the best decision model in the world.
274 models. One top spot. Built on Bittensor $TAO.
Four weeks ago, Subnet 92 didn't exist. Then the miners went to work: an open competition, two selected miner models, one post-production run.
Now REAX 1.3 sits at the top of Decision Index 0.4.1 with a Full score of 74.0.
This is what decentralized AI looks like when it ships.⚡
Live today on a Jev-compatible API
decisionmodels.io
huggingface.co/spaces/multim…
Matt Hamilton retweeted
Another Bittensor release which shouldnt go silently. This is a full top to bottom model, pre-trained on Teutonic (3) and then post trained in a competitive environment to reach coding performance above Qwen's flag ship 9B model.
These models are small sure, put these performance metrics are not, and the thing to watch here is alignment -- the team was able to aim a laser cannon at intelligence production and punch through SOTA weight class.
Every day something new. Congrats @reliquary_ai
Matt Hamilton retweeted
A Bloomberg journalist thinks ChatGPT might have just changed how this election turned out.
Matt Hamilton retweeted
The irony being that the more likely outcome from this war Trump started is a regime change in the US, not Iran.
Matt Hamilton retweeted
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math.
It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training.
We call this Weight-Space Programming: frontier LLMs can now natively read/write neural network weights! 🧵
Blog: rikiyat.github.io/blog/weigh…
Readers added context they thought people might want to know
LLM was given weights explicitly as text in prompt and used code/forward passes (per authors' logs) to ablate Qwen looping direction, a known thinking-mode issue per model card. Primarily fixed repetition in that mode, not general 'natively' improving weights/math.
rikiyat.github.io/blog/weight-sp…
github.com/RikiyaT/lm_und…
huggingface.co/Qwen/Qwen3.5-0…
huggingface.co/RikiyaT/Qwen3.…






























