YT@AlexFP16 retweeted
llama.cpp v1.0.0 is now available
huggingface.co/blog/ggml-org…
YT@AlexFP16 retweeted
my spidey senses are telling me the labs are, as we speak, using unguardrailed versions of their unreleased models to systematically reverse-engineer ALL of the internet’s software, apps, and games, then feeding the reconstructed source code straight into their training pipelines while simultaneously building guardrails to ladder-pull the rest of us
Replying to @higgsfield_ai
@higgsfield_ai sent us a cease and desist last night, asking us to shut down our Open Source Higgsfield challenge.
Our read on why they sent it. When the apps people pay for can be rebuilt in the open in two weeks, that’s an uncomfortable thing for a closed platform to watch.
So here’s us reiterating our promise to every builder in the challenge and community, and we’re keeping it:
• The challenge stays open
• Final submissions close tomorrow, Oct 30
• Winners are announced Nov 6, with prizes paid as promised
You showed up for each other. We’re showing up for you.
If we win, we all win!
Comfy out 🫡
Last night, @higgsfield sent @ComfyUI a cease and desist (attached)
They want the Open Source Higgsfield challenge taken down within 48 hours.
Their argument is that our use of the Higgsfield name and that using their CEO's likeness is an infringement violation (man, the irony). Claiming that it makes the event look like Higgsfield is associated with it.
This couldn't be farther from the truth, which is that Higgsfield made a promise to open source its product and never did.
For the past two weeks, builders have been recreating popular closed apps as open workflows anyone can run.
So we asked our community to deliver where Higgsfield failed: apps in the open, built by the community, for the community. We've made it clear that the challenge is organized by ComfyUI and not affiliated with or endorsed by Higgsfield.
When we started Comfy, we made the community a promise. Our product stays open, free, and yours. We’ve kept it every day since, and one letter isn’t going to change that.
The challenge stays up. Comfy and open source will win!
YT@AlexFP16 retweeted
Security called me at 6:12 AM today.
"Patch every PHP server immediately."
I asked what happened.
"Two critical vulnerabilities. Remote code execution. No authentication required."
Cool.
How many PHP servers do we have?
According to inventory: 12
According to reality:
Nobody knows.
We found one running WordPress.
Three running old internal tools.
One under someone's desk.
Two inside vendor appliances.
A forgotten employee directory from 2016.
And a server named:
PHP-OLD-DO-NOT-TOUCH
Naturally, that one runs payroll exports.
Then we found a PHP 5.6 box.
I asked who owned it.
The documentation said:
BRIAN.
Brian left in 2019.
We called Brian.
He said:
"Oh wow, that's still running?"
Excellent.
By 8 AM, leadership joined the incident call.
CEO:
"Can hackers actually get in?"
Security:
"Potentially yes."
CEO:
"Without a password?"
Security:
"Yes."
CEO:
"Then why do WE need passwords?"
Not the lesson.
Finance asked if we could wait until the weekend to patch because downtime affects revenue.
Security explained that the alternative was letting strangers execute code on our servers.
Finance asked for a cost comparison.
At 9:17, someone suggested temporarily taking the vulnerable websites offline.
Marketing refused.
"Our campaign is live."
So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover.
We finally patched everything we could find.
Then our scanner discovered another PHP server.
Hostname:
TEMP-PHP-2014
Uptime:
4,512 days.
Nobody knows what it does.
Nobody owns it.
Nobody can shut it down.
But every time we block network access, the warehouse stops printing shipping labels.
Security has classified it as critical infrastructure.
It is running PHP 5.4.
The vulnerability has existed longer than half our employees.
The emergency patch took four hours.
Finding out what PHP actually runs took eleven.
The internet isn't held together with code.
It's held together with servers everyone is afraid to turn off.
YT@AlexFP16 retweeted
Cavemen Issues Dire Warning That The Wheel Is Going To Eliminate Countless Jobs
YT@AlexFP16 retweeted
110,409 downloads in 9 days. I still cant believe this number.
On 4 Oct I uploaded an uncensored Qwen3.8 Flash-Next GSQ-RCO for Strata. I thought maybe 200 people would try it. A few friends, some people from my replies.
It was 110,409.
And the best thing here is not mine. The weights are from ISTA-DASLab, they made the quants. The direction is from Huihui. The engine is Strata by @coldniko. My part is a 480 KB file and a weekend of measuring.
A lab in Austria, a guy who wrote an engine, a guy who found a direction, and me with 4 old cards in an apartment. None of us work together. Nobody asked for permission. Each one built on the open work of the others, and 110,000 downloads came out of it.
This only works with open weights. And it means there are a LOT more of us than I thought.
Thank you to everyone who downloaded it. Thank you @Alibaba_Qwen for the weights. I am just getting started.
Download it now: huggingface.co/alesha-pro/Qw…
YT@AlexFP16 retweeted
Replying to @nntaleb
Exactly what you said in bed of procrustes "Trust those who are greedy for money a thousand times more than those who are greedy for credentials."
YT@AlexFP16 retweeted
Where we see evidence that mathematicians are more interested in the welfare of mathematicians than the improvement of scientific knowledge.
YT@AlexFP16 retweeted
The most profound paper of my PhD so far. We truly did something special to make LMs play/explain chess, needing both architectural & algorithmic innovation (natural-language analogue of the Alphazero algorithm) + applicable to many other domains. Please read on and share!
1/10
YT@AlexFP16 retweeted
Dario has written that we need to “pace the frontier,” and Sam has agreed. People may be surprised by my response: go ahead.
You guys are the frontier. By any reasonable metric — market share, revenue growth, model capability — the two of you have a duopoly on frontier intelligence. You’ve also claimed the lead is widening because of recursive self-improvement.
I don’t see what you see in the lab. If the unreleased models are scary enough that you think you should slow down, I support your decision to be responsible.
But stop pretending you need anyone else’s permission. Stop pretending antitrust law has to be suspended so you can form a cartel. Stop pretending you need a regulatory approval process that supersedes product liability. Stop pretending METR is independent when it is intertwined with Anthropic’s investors and staff. Stop pretending you need those same evaluators to police competitors who aren’t even at the frontier.
Most of all, stop pretending the motivation to slow down is purely altruistic. You face massive product-liability exposure if your products enable a truly damaging cyberattack. The market already punishes models that behave in unpredictable or unauthorized ways. After the Hugging Face episode, it is simply good business for OpenAI and Anthropic to trade some raw power for reliability and predictability. Call it alignment if you want. It is also just giving customers what they want.
Pacing the frontier would also create breathing room for a more intelligent conversation about regulation than Bernie Sanders’ “shut it all down.” China is very unlikely to join a global agreement, as you know, and that has to be taken into account as well.
So go ahead and pace the frontier. You are the ones setting it. The easiest way not to build superintelligence is for you to agree not to build it. Demanding your preferred regulatory framework as the price of that will look like blackmail of the public and the political system. So just do it.
If you do, you’ll buy goodwill for the next conversation. If you don’t, we’ll know this was just another bid for regulatory capture — or an election-season psyop.
































