- Quoted phrase in the opening sentence
- Opening quote: “here's the beta, I'll release the code in a few weeks”
- Quoted phrase in the opening sentence
- Opening quote: “facts”
Has a single researcher come out and backed up this story?
> who just personally bought 37,000 acres of Swedish forest land, presumably in preparation for some form of AI-related geopolitical fallout
Ultra rich guy put some land in his investment portfolio. What a shocker!!
- Ordinary term used more than once in the same comment
- “I don’t know.” appears 2 times
“Omg did you know that AI researchers are taking up smoking because they think AI will cure cancer??”
Oh really, which researchers?
“I don’t know.”
How many of them? One or many?
“I don’t know.”
What company do they work for?
“I don’t know. But I’m sure it’s Anthropic.”
How do you even know this?
“I saw it on someone’s TikTok.”
So if there are zero verifiable sources why do you believe this?
“Because it sounds fun, and confirms my biases. Now I’m going to forward this to a hundred other people or I’ll have bad luck.”
This is a meaningless example but this is true for so much more.
but there is something at least a little interesting about the notion that people working in the nuclear space they thought they might be saving the world - because in some sense, they... did?
I've always felt like the fact that no nukes have ever been dropped (in war) after 1945 was a pretty huge success story for the human race. We invented this insanely powerful weapon and, despite the typical pattern of humanity, we managed to solve one of our biggest "coordination problems" effectively enough to not use another one for 80 years (and counting).
I don't know that I'd extend this analogy to the AI labs, I'm not necessarily implying that they're all right about "saving the world," I just think it's worth noting that there was a contingent of people out there trying to save the world from a real threat and who seem to have - at least for now - succeeded.
- Quoted phrase in the opening sentence
- Opening quote: “we fixed some of the the excessive performance regressions that we introduced in 3.0”
Context: https://cryptography.io/en/latest/statements/state-of-openss...
People are saying the pace will settle down once LLMs find and fix all the bugs. Okay, sure, if you want to believe that sort of thing, but that still leaves the much shorter time window, and that's not going to go away anytime soon.
If you're on the side of the industry where your job or hobby involves breaking things, this is all very exciting. But if you're on the side of the industry where your job is to prevent things from being broken, then it really sucks.
I lost a full day yesterday because some big players discovered a thing, told other big players about it, "oopsed" enough public information to let everyone else know about it, and then left everyone else to figure out what to do with almost no information to act upon.
This cycle has happened several times this year now. If you're on the short list of big hosting providers, you get advance notice of what's coming and early fixes; if you're not, sucks to be you, hope you didn't have any plans today.
For people like me, this is just yet one more way LLMs are making my life materially worse.
My experience with AI-code is that it's extremely defensive and good at minimizing 'obvious' mistakes.
Are we comparing to old models generating code? Or mythos-class models?
- Quoted phrase in the opening sentence
- Opening quote: “Dutch government hacked into Jared Kushner's phone”
The GRU double-agent proved that the GRU had compromised Kushner's phone. Subsequently, Dutch intelligence themselves independently attempted to hack Kushner's phone.
"In The Hague, the MIVD hacking team tried to reverse engineer the Russian penetration of Kushner’s iPhone." [...]
"The Dutch team had been trying to pick the phone’s door lock, so to speak, when it occurred to them that the Russians may have found an unlocked window to gain entry instead. Their hypothesis was correct. By early 2018, the MIVD had found a vulnerability in the iPhone that gave them access." [...]
"when Kushner used the phone, they could see his screen. Almost as soon as they got inside, the intelligence service began capturing every image of Kushner’s screen as he used it, filing their own cache of surveillance on their internal computer servers."
Also (edit):
The part of the story I actually care about is two governments hoarding an iphone zero day, and using it to secretly hack iphones. I condemn it.
Digital privacy is important to me. I think that all humans should have it. Feel free to disagree. Jared Kushner is a human.
So again, I condemn this extrajudicial activity, which undermines the digital security and privacy of everyone.
But that doesn't make it a failure. In the era where we have:
a) an AI hype cycle where the benchmark of "successful product" is ChatGPT, Claude Code, etc. b) a social media environment that only rewards the most-engaged content
It's easy to declare something "fell off" because it didn't immediately revolutionize how everyone does their daily work.
But by that measure, nearly everything is a failure, even if it creates great businesses. That's especially true for infrastructure that runs in the background.
really early to call it "the fall of jev"
Perhaps the title could be updated to mention that it was the app that was reverse engineered? If the title had been "I reverse engineered a board game's app", that would have saved me from getting the wrong impression about the article.
Podman has never been commercialized.
Docker's difficulties in commercializing were self-inflicted. Enterprise and open source teams were culturally siloed and as a result the enterprise products were not "native". There was a lack of focus and a "checkbox" approach to building product. There was no singular "dictator" who could enforce a coherent product design and vision, and it showed. etc.
However Moby was a poor choice for a skunkworks project, it involved mostly communications and project management, which requires consistency and scale. Overall it was poorly executed because I failed to build enough support internally ("Solomon's at it again, let him do his thing"). Here I am trying to explain it on Twitter after the keynote, using a picture of a hand-drawn diagram, because nobody in marketing or product was assigned to help. https://x.com/solomonstre/status/855918630915133440
I think the goal of Moby was fundamentally correct: we were trying to replicate the Red Hat model, with well-scoped upstream components (linux -> runc, containerd..) integrated into a commercial product (Docker -> RHEL), with a faster-moving community project in between (Fedora -> Moby).
This was a way for us to clarify that Docker was a product, with a community of users, and Moby was an open source project, with a community of contributors. This clarity was very much needed, because different communities were projecting very different expectations on the brand "Docker", and these expectations conflicted with each other.
In a way, Moby aspired to be what CNCF ended up becoming - the "big tent" where the broader community meets to hammer out the general shape of the container stack. It seems obvious now that a single company can't be the sole authority over such a vast scope. But in the first years of Docker, we really did have that level of influence, because we literally invented the market, and brought the community together in meetups and an ever-growing Dockercon. It's only when Google and Red Hat pushed Kubernetes and CNCF, that our influence over the stack started to wane. Maybe it was for the better, I don't know if we would have been up to the task as designers and engineers. But at least there would have been a consistent design, with a Linus Torvalds figure willing and able to say "no" to stupid and redundant features. For a while I played that role - but then I was replaced by SIGs and committees.
Another explicit goal was to facilitate contribution. We thought Go syntax was "vanilla" enough to attract a broader set of contributors than a more niche, opinionated language like Erlang, Haskell, Clojure etc. I think that also worked out well - Docker was known for attracting many contributors, many of them making their very first open source contributions. We even ran special meetups to help people become contributors, that was fun.
That day is forever engraved in my memory... Off the top of my head:
I signed up for a lightning talk expecting an audience of 10-20 people, for a confidential demo of our unfinished project that we had so far only showed in 1-1 demos. Imagine my surprise when I learned Pycon does lightning talks on the main stage!
The previous speaker didn't show, so I started early. In the recording you can hear me joke that perhaps I should get his time allocation too - the MC was not amused.
I went over time and had to speedtalk through the end.. The MC once again was not amused and practically shoved me off stage :-D
We had a small sponsor booth at the even, where our small marketing team was prepared to pitch our product (DotCloud) but was thoroughly confused when a horde of people showed up after the talk, to ask about "Docker" - which as far as they knew was the founder's side project.
I drove down to Santa Clara on my newly acquired motorcycle - my very first trip on the freeway. I remember telling myself, "today is the day to take all the risks!"
I worked at Docker from 2014-2019. The most important part is actually written in C.
[I wrote a whole comment here about to explain how the hack works because I was too fixated on how technically incorrect "written in Go" is. Then I went back to read the rest of the article only to see that the paragraph immediately after this kind of explains it in its own way! Let that be a lesson to always finish reading the article before posting about it.]
What’s funny, though, is that since it was “just” a lightning talk, it didn’t even make it into the roundup of notes I sent to my team after PyCon. But a mere year later, Docker was how my team (and seemingly everyone else) ran projects locally.
Any interesting memories from that day in 2013? From your perspective, what happened in the year that followed that caused docker to be adopted so widely? Were there other key moments or turning points?
Docker in its earlier incarnations was based on openvz, which predates lxc. The lxc project was initially a kernel development project: a collection of kernel patches to add container support. The userland tool was just a companion. When it became apparent that these patches would "win" the race to be upstreamed even though openvz was much more mature, we switched our tooling to lxc. The patches matured over time, but the userland tool (what we now know as "lxc") was finicky.
The original open-source release of Docker wrapped lxc for low-level container operations. But it was just too unreliable and we swapped it out for an in-house Go implementation called "libcontainer".
As for "commercializing": Docker was famously bad at commercializing anything, we open sourced so much (maybe too much) and still people complained that we were not open enough.
- Quoted phrase in the opening sentence
- Opening quote: “5 different linux kernel features in trenchcoat”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “5 different linux kernel features in trenchcoat”
- Quoted phrase in the opening sentence
- Opening quote: “what's weird about it?”
Everything in that list feel natural when you know how things evolves over many years. Maybe it is just me getting older and less curious.
I remember my first time trying to use a container was about 2015 on a beach cafe's wifi in Bocas del Toro, Panama. You can imagine how it went...
After a brief hiatus though I was back to it and since then it's been a core part of many a local dev stack and even production stack (compose) I've set up. I recall the magic moment for me being when I first realised you could mount src to use all your local native dev tools while completely virtualising everything else, including and especially whatever combo of runtimes and dependencies you need.
It was just a lightbulb moment, like it entirely solves 'works on my machine', setting new people up on a project, it just seems like how software engineering ought to work and once you have experienced it it's difficult to go back.
I'm curious, as its creator are you still using it, or as someone who can clearly look ahead to experimental ways of doing things are you on to the next thing whatever that may be? If so, what is it? :-)
None of these things can be transposed today, so I guess I can't answer...
For what it's worth, my current project (dagger) is written in Go.
You may have already answered this somewhere, so feel free to tell me what to search for or if you have a link to hand, that works too :)
Some people will push back that agent development is "natural language programming" but I don't think that's right. I think in that case the agent is the one programming, and the programming still always happens in a deterministic language like Rust/Python/Typescript/etc. Maybe that'll change, but to me at least the other way would be a disaster.
The best exception I know of though, is definitely the Inform 7 language which is for writing text adventures[0]. It has a lot of fans, and I've never gone deep with it, but seems to do a pretty elegant job or marrying up natural language and programming together in a unique way.
Either way, definitely a must-check-out for any language-geeks interested in natural language programming.
I've realized that the agent doesn't write 'good' code, instead my vague understanding of what I expect makes me think it does. When I look at the AI code, I see that there are more nuances and decisions that needed to be taken before writing the code. One would say that a spec would suffice, but then I remember TLA+, developed by Leslie Lamport to help developers think critically about their programs/algorithms. Sitting down and formally writing what I want to do helps me better understand the problem and come up with a real -not vaguely defined- solution.
Most self-forming human societies are high-trust and more loyal to each other than to truth (as the models have so eloquently regurgitated). Look anywhere from the hunter-gatherer tribes to villages to small towns. I have traveled my small, poor country extensively and the only place the fundamental idea of altruism had to be "consciously invented, built and protected" was in the big cities. In the rest of the places, it came to them as naturally as hunger. We've found skeletons from thousands of years ago that indicate that the whole society came together to care for the disabled individual for nothing in return, leading them to live as long as a modern disabled person with healthcare might.
Societies become low trust driven by specific factors: resource scarcity, something forcing a lot of different groups of people into the same area without integration. This is not a defense of humanity. I'd say the case of the returned wallet is more an example of class-loyalty than general human altruism. Humans have an instinct for exclusion of the non-conforming.
But the idea that civilization has to be invented and maintained is a debunked, regressive, even dangerous idea in that this line of thinking was used to justify a lot of atrocities historically.
Difference between the countryside and the city I guess.
I did a 3-month walking pilgrimage in Belgium & France this summer. I had very little money and a tent and walked along quiet roads. Several people offered me a room for the night. (I was surprised, I don't know if I'd offer a stranger that) Many came out with food, snacks, fruit when they saw me resting near a church etc.
I used an app as well that allows camping in someone's garden ("Welcome to my Garden"). A few times I arrived to setup my tent and the owner had to leave for an appointment/event. They left me the keys to their house and told me to make myself at home until they returned(!)
The Crowd: "Yes! We're all individuals!"
Brian: "You're all different!"
The Crowd: "Yes! We're all different!"
A man in the crowd: "I'm not."
The Crowd: "Shhh!"
> it does not know
Define "knowledge" in a non-circular way.
There's a certain type of knowledge that machines definitely can't have - experiential - but conceptual knowledge doesn't inherently require subjective experience or a biological substrate.
> the only thing it does is reproduce patterns more or less abstract in function of the pressure you put on certain representation during training time.
As for humans; just replace "training" with "education" and the likelihood of a certain output with the likelihood of a certain thought or response.
Amusingly (in this context), much of adult behavior is shaped by patterns reinforced during childhood.
- Quoted phrase in the opening sentence
- Opening quote: “human flaw”
- Quoted phrase in the opening sentence
- Opening quote: “takes”
Seems to me that the opinion being a consistent among LLMs show that it is in fact a constant in the training data, just not apparent. The idea that “humans would rather be wrong together than right alone” seems to ring pretty true to me. I would not be surprised after training on all human communication this pattern emerged.
Verification: Code does what it says.
Validation: Code does what Specifications say.
Specifications: Were hopefully correctly modeled to the Problem.
In IEEE terms:
> Verification: "Are we building the product right?" > Validation: "Are we building the right product?")
You can write mathematically flawless code that highly efficiently solves the wrong problem.
---
While I think formal verification is the future (essential for cybersecurity), it's not a silver bullet for the other 2 items, which are way more ambiguous. I think however they can all iterate on each other and improve the project overall, but it still depends on competent steering
If you have had experiences with good approaches for verification Validation & Specification framework, do let us know about them.
Likely, a proliferation of experimental languages all somewhat akin to Typescript for SQL with significantly more nuanced operators to tersely capture the same outcomes as imperative languages.
They’ll compile down to be able to run performantly for game development or even for the Linux kernel (as if Linus would ever agree lol) but also they’ll be able to run on distributed execution engines with effectively a shared memory space, etc.
Allows for significantly more terse artifacts. Lower chance of hallucination, fewer output tokens, fewer thinking loop iterations and concise enough for humans to review (for domains that need it).
On top of that, additional theorem like syntax to drastically limit the ability of functions, etc. likely some sort of higher level effect system for verification. Used for many things like “constant time compilation for crypto functions”, and also “ensure acid compliance” for writes and reads in a local context, and things like “ensure only once delivery” for functions on a distributed execution engine.
At which point every program will be formally verified by default. You could think of it as AdaErlangSQL+++
Some mathematicians have observed a similar pattern in the recent LLM proof drops, leading them to suggest that LLMs will hit a wall in mathematical capability just beyond the convex hull of human mathematics. The sort of proofs done in formal verification are a pretty interesting litmus test for LLM reasoning since the systems considered aren't necessarily on distribution (compare with math where the "systems" and structures worked with, and proofs about them, make appearances in thousands of individual books) so the advantages in broad domain knowledge pretrained LLMs have over humans doesn't really buy you much. IMO this observation from Anthropic/Theorem lends more credibility to the convex hull hypothesis.
[0] https://www-cdn.anthropic.com/files/4zrzovbb/website/6867ead...
I do think that GNU Taler is the better technical solution as the blind signatures and online model require less trust in the platform, while the Digital Euro requires untamperable hardware enclaves. So in an ideal world we would all standardize on GNU Taler and be happy.
Unfortunately, anything related to money is probably the place where trust paranoia is the least useful. In fact, widespread use of the Digital Euro will probably be the best proof for the security of the available hardware enclaves, similar to how Bitcoin is proof that SHA-2 is currently secure. Otherwise, somebody would make bank from counterfeiting in the few moments before the system crashes down.
The digital Euro has the real benefit to allow offline transactions. Both Digital Euro and GNU Taler have the psychological burden that you have to exchange "real money" for some kind of digital "monopoly money" which can get lost with no way to re-imburse you. (Which is the same as would happen with literal cash, but nobody will care about that.)
(Which is why I actually think both "digital cash" solutions will die out, with GNU Taler fading into obscurity, and Digital Euro being kept on life support as it is literally legal tender. And we will eventually all just be using Wero, which is just SEPA wire transfers in a trench coat)
That's... exactly what I would expect from putting a FOX News pundit in charge of the military.
My family has a long history of alcohol and substance abuse, I'm the first to be diagnosed and medicated for ADHD. If you're not medicated and have ADHD the risk of substance abuse is much higher, and there is a strong link to alcoholics being undiagnosed with ADHD.
I'm always scared of the long term effects of the medication, but without it I can't work or hardly even function.. I'm not sure of these benefits another user mentioned, but whatever they are is not worth the trade off at all.
- Ordinary term used more than once in the same comment
- “responsible disclosure” appears 2 times
This term came from an era where companies or projects were disrespectful and dismissive towards security researchers. Those orgs were generally bad risk practitioners, and they coined the term "responsible disclosure" to mean "you send us the info and we'll do whatever we want with it, for however long we want, etc".
Many security people (like me) prefer the term "coordinated disclosure" as a way to indicate a practice where both discoverer and patcher participate in a good faith, communicative, and timely process to get things fixed for the community.
The difference can be summed up like this: if I report vulnerability X to company Y, and company Y sits on it for 3 years, that is not responsible. It is more "responsible" (especially today) to report it to the public, so they can protect themselves in a non-official-patch way, because the likelihood of bad guys knowing about it and exploiting it are approaching near-certainty.
These terms are obviously not super scientific, but I try to point out the history whenever it comes up.
- Quoted phrase in the opening sentence
- Opening quote: “non trivial to exploit from just public requests”
- Quoted phrase in the opening sentence
- Opening quote: “take full responsibility”
(For clarity, I’m being facetious, but it’s a really meaningless and empty phrase to commit to the written record.)
According to the European Commission’s Emissions Database for Global Atmospheric Research (EDGAR), China and India combined (~35.5% of the human population) account for roughly 38% of global greenhouse gas emissions. Which is indeed an overshoot, albeit not of terribly epic proportions.
However, per-capita - on both a 100-year-effect and a 20-year-effect timeframe - the USA is easily the leader in emissions per person, and the USA also records the largest absolute increases ongoing.
The figures, which already take the variable potency/effect of different gas types into account, show annual per-person greenhouse gas emissions (in CO2 equivalent) of 17.3 Tonnes-per-person (USA), 11.1 Tpp (China), 5.6 Tpp (EU27), 2.2 Tpp (India) on the 100 year impact scale.
On the 20 year impact scale ("the amount 1 person releases in 1 year will trap the same amount of heat as XX tonnes of pure carbon-dioxide would"), which much better takes into account the balance of current agricultural practices etc, the USA = 21.5 Tpp, China = 15.8, EU = 6.8, India = 4.1.
The United States also recorded the largest absolute increase between 2024 and 2025 (+131.5 Mt CO2eq, or +2.2%), followed by Indonesia (+16.1 Mt CO2eq, or +1.2%).
So, any message which - when translated through the lens of practical reality - is essentially saying to the developing world "Please either tighten your belts, or be less populous" seems a very challenging expectation, if not outright-unviable by almost any other metric or ethic.
Data center demand right now has much more to do with private credit's demand for new deals, since the binge they went on around the pandemic led to the accumulation of a lot of bad debt and depreciating assets. Data centers are a tool for extracting money from insurance trusts and pension funds to prop up private credit and create debt-driven artificial "revenue" for the hyperscalers and Nvidia.
> You let people evade fares and then those people go onto stab people like Zarutska.
That has nothing to do with it. The guy that committed that murder wasn't going to be deterred by a ticket fee. But it is interesting that you should right away jump from the one to the other, effectively using the poor dead girl for your agenda. Crime and homelessness are complex problems some parts of which are easy to solve and some of which are much harder.
You can't simply jump from 'someone got murdered on public transport' to 'public transport can't be free'.
- Quoted phrase in the opening sentence
- Opening quote: “small crimes go unpunished”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “small crimes go unpunished”
If we've got a Lamborghini justice system, delivering amazing performance to people with a spare $250k and doing nothing for anyone else - some would say that's not the right price/performance trade off.
- Quoted phrase in the opening sentence
- Opening quote: “protecting those careers”
Source: I work with a top defense lawyer in Chicago
- Quoted phrase in the opening sentence
- Opening quote: “small change”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “small change”
Only my personal view but even 1000 LoC is not a "small change".
Near the end they include a paragraph claiming we should interpret this piece as being about more than self-interest and resistance to change, but it doesn't really feel like the piece offered a taste of what that "more" is.
The most thought-provoking part for me was considering that AI companies have used pretty much all available data for training while "they spend more and more money to create proprietary training data". That seems to break a sort of intuitive social contract - like, well you all used everyone's knowledge. Send yours back out too.
Grant from 3brown1blue released a video exploring the economics and mechanics that enable careers in math, in light of the AI company releases over the last couple weeks. Overall it was a lot more hopeful, and it didn't need to strain awkwardly like this piece to apply an ill-fitting historical framework like enclosure. Worth checking out: https://www.youtube.com/watch?v=LKrwhjOI8Nc
- Quoted phrase in the opening sentence
- Opening quote: “information commons:”
Springer would like a word
edit after reply:
> What was odd, the source said, was that the money in the account—hundreds of millions of dollars—had come from a bank in Azerbaijan.
Ahh, now the arrest of the former chief of Germany's BND, related to what seemed like a random country "Azerbaijan" is making a bit more sense?
The threat feeds we offer are in alignment with what the user expects and intends. Mandatory restriction of DNS resolution by a third party (not the user, not Quad9) is expressly what users do NOT want, regardless of the outcome. Once such restrictions are enacted and treated as normal, the channel for making demands will fill with a flood of "objectionable" names from every corner for every reason. Quad9 has already received demands from the French regulator to block sites which deliver adult content found to be objectionable to minors. We see an extremely slippery slope which has already moved out of piracy as the scoped intent which is this case in particular.
More to the point: prohibiting content via the DNS is a useless exercise when it is done out of alignment with the end users' goals - they will simply use some other recursive resolver (or their own) probably without the benefits of being oriented towards security and privacy. We have no monopoly on DNS resolution - there are thousands of others open to public use, and anyone can set up their own, for free, with no mandatory requirements by governments or regulators. This case (and any others like it) only drives out law-abiding organizations who are trying to promote better cyber hygiene and who want to keep the DNS as a single, un-splintered high-integrity pointer system.
- Quoted phrase in the opening sentence
- Opening quote: “bad”
Isnt this what gets all tech companies into trouble all the time. Something objectionable happens (ChatGPT helping someone bulid a bomb for instance) and we go like "Do better".
An editing pass to make the prose less "punchy" would be great.
- Ordinary term used more than once in the same comment
- “enhanched” appears 2 times
The call to action says "Copy prompt", not "Unlock prompt", "Sign in to copy", or "Get Creative to access prompts". I didn't even go past the signup to see if the prompts themselves are actually free and work without a subscription to your hosted MCP server. There's a GitHub link in the header suggesting an OSS tier, at the least. That repo may include "prompts" folders, but no prompts are there. The README doesn't even hint that this is a paid library of assets/prompts until the very end, with the misspelled "enhanched" sentence under the "Pro" header. The only prompts that appear to be in the repo (other than those that configure an agent how to use the paid and hosted MCP) are basic design guidelines.
Getting back to the website: your hero text directly invites users to "Try each example and copy its implementation prompt." Which immediately demands the aforementioned signup flow that I didn't bother completing.
All of that just turned me right off.
Your examples are nice, if a bit generic. But if you intended this to be a loss-leader for the more "enhanched" UI/UX skills, it isn't doing that job.
I think we need to keep pushing back against this idea that "now it's the AI coding era, everything gets coded with AI." Let's keep building things, especially passion projects carefully by hand and normalizing this. Lots of us are still coding without AI.
It would be like me practicing surgery 1 hour a week and saying "well surgery only has a very small place in my 80-hour work week" in response to flagrant failure of medical care.
If they go to the trouble of wrapping them, use real keys. Or don't do it.
Also, it's a big "human error" to not notice this for a year and a half.
- Quoted phrase in the opening sentence
- Opening quote: “and we would have gotten away with it, if it wasn't for those meddling kids”
Note that p,q (the primes you’re thinking of) are not actually required for decryption. They enable you to calculate d, the decryption exponent, and also enable decryption-time optimizations (exponentiation with d_p and d_q followed by CRT recombination), but that’s optional. In fact, p,q can be computed from n, e and d.
- Quoted phrase in the opening sentence
- Opening quote: “unforgeable”
- Ordinary term used more than once in the same comment
- “unforgeable” appears 2 times
Normally, the king would declare and sign a proc stating that anything signed by his secretary's "unforgeable" signet was to be respected as well. The secretary could delegate authority to others in turn.
Well turns out that one of the signets in the chain of trust was just a picture of a "four" that anybody could have forged, but nobody noticed because in all of the ceremony and stacks of parchment with wax seals, nobody actually checked if the signet was secure.
The statement can use whatever weasel words it likes, but the action pretty clearly says "we aren't mature enough as an organisation to handle this responsibility." Which would be quite the concern for me, if I were a customer for one of eMudhra's other product lines.
- Quoted phrase in the opening sentence
- Opening quote: “out of the affected CA's”
Adding "out of the affected CA's" is top PR weasel wording that will slip by non-technical people who read this.
Congratulations to those who wrote or prompted this statement.
- Quoted phrase in the opening sentence
- Opening quote: “There were no end entity certificates issued out of the affected CA’s.”
This seems like a weird statement given that anyone can issue certificates out of the affected CAs.
- Quoted phrase in the opening sentence
- Opening quote: “will sharpen focus on... trust services other than SSL/TLS”
Is there some reputation left to salvage here that I'm not aware of? Who would trust them?
- Quoted phrase in the opening sentence
- Opening quote: “Kovan viikon ilta”
Not that interesting. They are doing it illegally. And there is a pattern of builders of AI data centers ignoring the local law.
It makes it news. It makes it relevant and actual.
What do you find so "interesting"?
- Quoted phrase in the opening sentence
- Opening quote: “All games are essentially rentals”
Among all gaming platforms, it’s only behind DRM free storefronts like itch.io and GOG.
Unlike PS5 or XBOX, not all switch 2 games require downloads or day 1 patches.
For example I tried to investigate some CVE's on older android roms and it downright was refusing it. It was okay when doing it on... Microsoft and to submit a microsoft bug bounty but android was no go.
For the most part, the actual accusations are false. This submission was an earlier version of pgrust 0.4 called pgrust 0.4-preview. We just open-sourced a newer version called pgrust 0.4-beta yesterday, and you can fully audit it here[0]. Rather than contest the accusations on GitHub, we figured it would be easier to complete pgrust 0.4 and open-source it to show that we're being honest. You can also verify what I'm saying yourself against the 0.4-preview binary we submitted to ClickBench here[1]. I don't have a way to prove this is the exact binary submitted, but if ClickHouse provided the SHA of the binary they tested against, it would match.
The three main accusations boil down to: 1) We used handwritten code optimized against each query in the benchmark, 2) We cached the results between query runs, and 3) We didn't support queries outside of the 43 ClickBench queries.
First, we did not use handwritten queries. The code Alexey pointed out does not run during the benchmark. The design of 0.4 relies on a JIT compiler that compiles your SQL to a Lisp-based intermediate representation that we call Gravity IR that we then convert to x86 and ARM assembly. While developing 0.4, I wrote handwritten code against the IR for benchmarking purposes. The idea was that if queries written in our IR are fast, and we can compile good enough IR fast, then our new query engine will be fast. This is also the reason the directory those "kernels" are in is called "irprobe" - it was a probe of our IR to make sure it was fast. Our 0.4-preview submission went through the pipeline: SQL query -> Gravity IR -> assembly.
Second, the "result-cache" Alexey observed is the result of a cache we use to cache which predicates match which strings in our dictionaries we use for dictionary compression. Alexey wasn't aware of this cache and assumed we were just caching the query results. On ClickBench you are allowed to use caches like this that hold intermediate data[2]. ClickHouse has its own cache similar to this called the Condition Cache[3]. In our newest submission, we were upfront about all the caching we do and how to disable each cache[4].
The third claim that we didn't support other queries outside of the 43 ClickBench queries is partially false, but does have some ground to it. As I said before, pgrust 0.4-preview was an early version of pgrust 0.4. Once our new JIT compiler supported enough SQL to handle the ClickBench queries, we decided to submit it to ClickBench. AFAIK, ClickBench has no rules about how much SQL you need to support. On top of that, we did ship that we did ship 0.4-preview with our old query engine. It would have been a two-line change to fall back to it and support a much broader set of queries outside what our new engine could support. Those queries would still be fast, but not quite as fast as our new engine was. Our new 0.4-beta release does now support all Postgres SQL (minus some bugs around CTEs and MERGE)
To sum up, pgrust 0.4-preview was an early build of pgrust 0.4 while it was in development. It was a real query engine and actually executed queries. I acknowledge that we submitted it prematurely, when it supported a narrow set of SQL, and we should have ensured broader SQL coverage before submitting it. With our new submission that solves these problems, and we're hoping for pgrust to be reinstated. If there's anything off about the submission, please point it out and we're happy to fix it.
[0] https://github.com/malisper/pgrust/releases/tag/v0.4-beta
[1] https://pgrust.com/downloads/archive/2026-09-clickbench-snap...
[2] https://github.com/ClickHouse/ClickBench/blob/main/README.md
[3] https://clickhouse.com/docs/concepts/features/performance/ca...
[4] https://github.com/ClickHouse/ClickBench/pull/2751