People are publishing their slop projects as if they intend on maintaining them, but they clearly aren’t capable or willing to actually maintain them.
This is my #1 problem with it. Just put it on github and call it a day. Don’t act like its production ready at all. The #2 issue is namespace pollution.
$8 mil is pocket change for the investors. It’s like eight dudes all giving their bro $100 for his art project.
The HOMES mnemonic is now SHAME.
(I’m sure some lib on bluesky figured this out before me)
The Gates Foundation had strong objections to releasing the covid-19 patents. I’m sure they had some sort of rationale that wasn’t "this would set a bad precedent for M$ patents.
Yeah when will those expired GPUs hit the resell market? Or are they going to grapes of wrath them.
They are making the chips, building the data centers and collecting the data. None of those are the missing piece. The missing piece is being able to actually turn a profit from that entire pipeline.
MPD and pick your client.
Its a datacenter not a golf course. They’re going to bulldoze the entire lot anyways.
FWIW universal healthcare is not single payer. Its nationalizing healthcare providers and doing away with health insurance entirely. Which is better than any single payer plan IMO. Hospitals have never really been successful profit generating ventures.
The entire health insurance industry would be deleted along with all the jobs and stock value it produced. And yeah fuck’em but there’s going to be knock on economic effects from deleting an entire industry.
“More easily configurable” would be more accurate, because there’s less things that could get in your way. The system is designed to make it as simple as possible from a developers perspective.
That wouldn’t have fixed the AUR incident because the attacker updated the PKGBUILD which is roughly the same as the nixfile. And there are no packages provided by the AUR, just PKGBUILDs. You always build the package yourself locally.
Official packages are already vetted so they don’t need user scoping. They could just enforce user scoping in the AUR and use the provides array for resolving conflicts. Its not a perfect solution but there’s no such thing as perfect security, just better security.
Also having an AUR helper that properly containerized the build step would be an even bigger improvement.
Arch is deliberately minimal making it a good base system in the same way Debian or Fedora is. It’s smaller, simpler, updates faster than the others and is far more configurable. It is however not built for the average user and most distros built on top of it that try to make it more “usable” are IMO pretty dangerous ideas. I think the only derivative i’ve tried that was good was SteamOS because they made it Atomic like nix or silverblue.
None of this really has to do with the AUR. That was always labelled as “use at your own risk”. And to their credit they caught and addressed the attack within a day of it happening. Still, hosting user PKGBUILDs and leaving it to individual users to audit them is not a secure solution, its just punting on the responsibility.
npm: Node Package Manager.
AUR: Arch User Repository.
Bazzite is based on fedora not Arch so you don’t need to worry.
There’s also QtWebEngine, WebKitGTK+ and all the tui browsers.
Its a common courtesy that if you publish something on the AUR, then you actually think people would use it and you plan to maintain it. You don’t bother pushing some half baked afterthought to the AUR. Leave it on github. Otherwise you’re just squatting a perfectly good AUR package name.