Pinned Tweet
“I wish it need not have happened in my time," said Frodo.
"So do I," said Gandalf, "and so do all who live to see such times. But that is not for them to decide. All we have to decide is what to do with the time that is given us.”
Arthur retweeted
This seems cope-coded but is totally correct
You recognize LLM writing not because of form, but because of topic.
Almost always, its because it treats the median opinion, common knowledge, and predictable behavior as authoratative in a way no normal person does
when the coders realize that their mid is a way different mid than the writer's mid
oh boi
my time has come
the humanities are finally coming back into focus after a 60 year reign of dumbass technocrats
This is why LLMs can’t write interesting and novel content, and won’t be able to for the foreseeable future
All knowledge work is now deciding what to work on and designing how to do it to AI agents
There is no doing it anymore.
One month into dating, her boyfriend’s startup was acquired by NVIDIA.
Our #1 SF Dating advice: Lock it in before the acquisition
Although the security breaches are awful, it is pretty gnarly and sci fi that fleets of AI’s are battling it out in cyberspace
It just keeps happening
🚨 BREAKING: LINUX IS NOW FACING TWO CRITICAL SECURITY VULNERABILITIES, AND THERE ARE NO OFFICIAL KERNEL FIXES YET.
Both rated 9.0/10 in severity.
One could allow hackers to take control of vulnerable servers WITHOUT EVEN LOGGING IN.
And the most alarming part? The flaws were made PUBLIC before patches were ready.
Here's what's happening:
→ TWO CRITICAL RCE FLAWS: Both affect KSMBD, Linux's built-in SMB file server.
→ NO PASSWORD REQUIRED: One vulnerability could allow unauthenticated attackers to execute malicious code on vulnerable servers.
→ KERNEL-LEVEL ACCESS: Successful exploitation could potentially give attackers control within the Linux kernel itself.
→ NO MAINLINE PATCH YET: Both vulnerabilities were publicly disclosed before official kernel fixes were available.
→ DISCOVERED BY AI: Trend Micro's AI-powered security scanner identified the flaws.
→ SERVERS AT RISK: Linux systems running the vulnerable KSMBD service need immediate attention, especially if port 445 is exposed.
First PHP. Then Node.js. Then GitLab. Then Python.
NOW LINUX.
And this time, the vulnerabilities are PUBLIC before the fixes are ready.
If you manage Linux servers, CHECK YOUR EXPOSURE NOW.
Readers added context they thought people might want to know
KSMBD is a rarely used optional in-kernel SMB server distinct from the common Samba implementation; it is not enabled or shipped by default on major distributions like RHEL, and the flaws affect only systems explicitly running it with port 445 exposed.
thehackernews.com/2026/10/two-cv…
threatlandscape.io/blog/ksmbd-zdi…
Do not use codex goal mode @yacineMTB is right
Burned 3 resets with no results, it’s head gets stuck in the sand
Claude Code’s new card system where it gives you an action item and one line summary instead of explaining things is absolutely terrible



















