10,581 karma · joined May 25, 2019
This project is vehemently against AI usage of any kind, so I can trust that the contents of this post has been checked and written by someone who has read the code and knows what they are doing.
> The Linux io_uring interface allows the user to submit one or more I/O operations to the kernel, which are then processed in an asynchronous fashion without blocking the userspace process. Redox, being a microkernel, handles I/O in userspace scheme processes rather than in the kernel.
io_uring is incredibly fast for async I/O but is also a massive security disaster in the Linux kernel. As long as Redox is able to show a secure interface for async I/O the better. Likely part of their long term goals for the OS.
> While it has substantially improved over the years, IPC is still quite slow on Redox, and this is important to optimize as ring buffers can only offset this overhead to a certain extent. This has been a focus of our work to improve system performance.
I quite like this targeted and thoughtful approach for a wholistic improvement starting with ring buffers in redox. They need to compare the async executor benchmark results with Linux and continue from there for improvements.
> The optimization made here is that the kernel zeroes the vector registers if the caller and callee entered the kernel through syscalls, rather than saving/restoring (using vzeroall, ldmxcsr etc. as required for correctness).
Interesting approach for complete correctness over performance in this area and this tells me that they are not taking going to risk on overlying on rust's "guarantees" to help them prevent races or data reuse after free bugs in the Redox kernel.
One of the most technically sound and researched posts I've read, but unfortunately it has been buried under low effort slop posts on HN.
Don't even use GitHub then as that is also closed source as well as this.
Why?
> No cloud accounts. No 1GB Electron bloat. 100% Local-first.
This would make me want to use Postman (Electron) over this, since I know that this will absolutely be unmaintained in the a few years.
> TL;DR: GNU Savannah hosts Bash, Coreutils, and hundreds of other GNU projects. Using Hacktron, we found that an email address like a`touch${IFS}/tmp/savane-rce-proof`@attacker.example gave any registered user code execution on its backend. From there, we made our account a superuser, impersonated Bash’s maintainer, and confirmed we could add an SSH key with push access to the upstream Bash repository. An unpatched kernel gave us root access and access to a GNU backup server. We reported it to the FSF on May 11, 2026.
> Like much of the infrastructure free software depends on, it’s run by a handful of volunteers and FSF staff with limited resources. We wanted to put our resources to work there. Savannah runs Savane, a PHP application that is itself free software, so we pointed Hacktron at the source and audited it.
Imagine attackers reading that and ordering swarms of abliterated frontier models onto an open source project like that.
Many projects like the FSF do not use AI themselves maybe "by principle", but the attackers don't care and will unleash AI agents on to anyone as a backdoor target.
Given all that you have seen with the mass discovery of these security issues and hacks, there will be no choice from open source projects to conglomerates to use AI to protect themselves ahead of the attackers.
So non career politicians.
This is essentially a technocratic government that is left leaning. Just because they are academics, researchers, doctors, engineers and sociologists does not mean they cannot go corrupt themselves (it will). The EU itself is heavily corrupt as well.
We have also seen how corrupt a technocratic right government can get in the US. It will be no different to a left leaning one once money and promises are involved.
To give an analogy of what this is, this is like electing effective altruists from Anthropic with the difference being that they are using your money (taxes) instead of theirs and giving lots of promises for your vote.
If they are serious, they need to pass the world toughest anti-corruption laws while also significantly growing their own economy or borrowing economic policies from the least corrupt nations in the world such as Singapore and to exceed them.
> Student List has promised to fight corruption and establish meritocracy, accountability, and the rule of law.
While these are good promises, the problem is that this is the first lie that they have already made.
They better do all four of them without angering the electorate otherwise they can’t be trusted.
Imagine swarms of abliterated frontier AI models that reach >20,000 TPS. As I said before [0] you are going to have to hire specialized security engineers or technical bodyguards from the senior to senior staff level using AI agents to protect your entire business.
Otherwise you are cooked.
Someone will have to be the technical bodyguard that needs to thwart an attempted breach as quick as possible without causing an outage and that is the difference between a $45,000 breach vs a $450M breach. Enough to bankrupt a startup.
Using something like Cloudflare won't be enough this time.
Let the be a warning to those who want to slow down.
Let's say that the house of cards crashes down and takes the market with it who will shutdown, survive or have no choice but to get acquired for a 90% discount.
Some will be just alive long enough for the early investors to pull out enough before the market crashes.
After everything announced in GitHub Universe and with that to improve the reliability of GitHub overall, yet we have another incident afterwards.
It doesn't matter what GitHub does, only you can decide for yourself to self-host rather than going all in on GitHub and it continues to go down.
Predicted this 6 years ago and self hosting has aged perfectly well. [1]
This concept was hyped up (because DeepMind) for a while at the time and in reality it amounted to nothing. This is just the second reincarnation of a similar concept but with added extra saturated slop and hype on top.
Reality says otherwise, especially from those who run LLMs in production at a large scale. Hacks such as baking in the weights with tiny experiments doesn't disprove anything.
The same LLM boosters also continue to repeat one of the biggest misconceptions: "sEt TeMperaTurE tO zERo tO aChiEvE fUlL dEterMinIsm."
I agree. AI is useful to layoff thousands of employees as we have already seen, hacking companies and governments with agent swarms and also helping with accelerating cyber crime.
Now anyone including script kiddies can tell an AI agent to build an exploit to attack a website of their choosing the moment they find a vulnerability.
You cannot say it is useful (which it is) and it does not also accelerate and amplify all the negative consequences at the same time.
> Crypto has none except scams and get rich quick.
Stablecoins are quite useful for companies such as Stripe, Shopify, Square and others for payment of goods and one can send stablecoins around the world on the same day, 24/7 with extremely low fees.
Crypto is not the one that will cause the next financial crisis. That will be AI.
Thanks to the $3TN (and counting) debt that is now becoming a massive risk to the point where big tech companies are hiding it from their balance sheets [0] with Oracle and even CoreWeave being the most likely to default first. [1]
[1] https://siliconangle.com/2026/10/14/shares-of-oracle-neoclou...
One (emacs) gets millions in donations via the FSF and the other get little to no money or donations for being "free software" from the start despite both of them being "free software".
[0] https://github.com/herdrdev/herdr/blob/a57b97285c3308fbdcc16...
Claude Code was already malware, but with this attack you cannot trust the vendor either.
In the next 2 weeks, no one should download / install / update anything as I predict at least one developer's key for a GitHub, NPM, Crates.io or any other CI or login was leaked and the attacker will target those services to propagate their trojan to more victims.
Thank you for proving my point.
Yet another reason why it makes sense to never buying the first version of an Apple product [1], since previously:
> "But once again as I said before, don't buy the first version of an Apple product."
This was Apple's first foldable iPhone. If the price wasn't enough of a deterrent, then the defects should now be even clearer to wait until Apple fixes them in the next version.
[0] https://www.theguardian.com/technology/2026/oct/26/iphone-du...
More of what? I see many here using AI to build more of the same things in another language such as rewrites and then claiming that they are "productive", which is the problem of many engineers here.
Not that much risk taking if all what everyone is doing is just full blown rewrites and then abandoning it in a couple of months later and just wasting tokens for free.
If the result is to vibe code something for free and it makes no money and has no users then it is a waste of time.
That is not the question I am asking.
> But for Herdr specifically? Probably not.
So no then.
That is why they went for VC money since the author knew that donations weren't enough to maintain it in the open.
> There are tons of similar free alternatives and even vibe coding your own is very easy with all the open source code of both herdr and all the alternatives available.
Why would I waste tokens vibe coding something that would go unmaintained in 6 months (because it is "free") over a properly funded project that will last much longer than that?
The cost of maintenance is never "free".
Just like X did, and LinkedIn.
At this point, we seriously need to discuss whether if the major projects still written in C such as Linux, Chromium and even git can even handle the stream of now near infinite bugs being discovered with AI.
Attackers are already rapidly finding and building exploits for those vulnerabilities the moment they are discovered with abliterated frontier-level models.
These sort of vulnerabilities are far to common in those projects and in the future, it will be extremely unsafe for even experts to continue using C or C++ in any way.