> We're talking about code that users can modify themselves to solve their own problems. That's it. I don't need to hear about the struggle.
That's exactly the kind of attitude that this discusses.
You create something that solves your problems, you put it up on GitHub, free, and open... Suddenly it turns out others have the same problems you did, your software solves them.
It starts ok. People are nice. But as it gains traction, a certain kind of toxic person becomes more and more common. The "YOU FIX IT NOW! I DONT KNOW" Kind of person.
You wake in the morning, look at your email, and it's a stream of being screamed at. That takes a toll.
All because you had an idea one time to build something that solved your problem you thought "hey I might just open source this".
> That's it. I don't need to hear about the struggle.
Let me tell you a solution for the "FIX IT NOW" types:
> This is an Open Source project that gets developed at the author's discretion. We provide paid work services for urgent fixes, cost is $500 per day with a minimum of 4 days.
Put that in the README, under a header that can be linked to in bug reports from entitled people. Worst thing that could happen is that the maintainer ends up earning a couple grand.
The thing is, mythos found those with multiple passes, thousands of passes... So using thousands of passes or perhaps the same budgets, yes, cheaper open weight models could potentially (and have) found the same/similar vulnerabilities.
Mythos screams of marketing hype, and nothing more. Opus 4.7 isn't really a meaningful upgrade in any sense, other than being more expensive.
Once you can see what something like Qwen3.6-35B-A3B can do... with just a FRACTION of the size of the larger models, You'll understand that the future is open weight models you can run yourself.
Same goes for companies, bringing inference onsite isn't hard, I'm actively building tooling to orchestrate it.
What is the failure state for a pass that doesn't find a real vulnerability? Do the models report no issues or hallucinate issues that aren't real? I'm trying to run open weight local models and finding them really impressive... Just also trying to understand the cybersecurity side of all this.
The status quo is insanely profitable for Apple and Cook is still going to be "engaging with policymakers around the world" so I don't think they'll deviate from malicious compliance and stalling tactics any time soon.
The perjury, contempt and referral for criminal investigation in the US carried no consequence, Japan and Brazil's regulations have been undermined by massive fees, as has the EU but they're afraid to fine them because of Trump. Except for the possibility of a $38 billion fine in India this strategy has been very successful for Apple: it's 5 years since the US ruled developers could use third party payments, 3 years since the DMA came into effect, and nothing has changed.
> 3 years since the DMA came into effect, and nothing has changed.
Not nothing. In the EU, there are settings now to set default apps for browser, email, navigation, contactless payments, calling and messaging, for example.
I've been running models on my homelab for a bit now, but none of the available options out there was what I wanted. I wanted something that I could command from the CLI, API, or Web, so have an agent go in and do work remotely via SSH or myself via a web interface.
I wanted the ability to know if models have been updated, and if backends (llama.cpp, ik_llama.cpp) have been updated, see what those updates are and choose to update. Also wanted the ability to switch betwen versions of those, so if I felt like there was a regression, or performance issue, I could roll back.
I've also published plugins for OpenCode and Pi so that model discovery is automatic too.
reply