crvdgc
Obviously, the author has deep engagement with the Chinese internet culture (the "junk food" part that I would avert), but the over generalization is comical.
Or maybe that's the point? The author is trying to be provocative? For someone with zero background of the Chinese internet culture, this could be a starting point (although an extreme one), but don't take this to represent the whole reality.
One example, the quoted book review of Three Body Problem draws the complete opposite conclusion that the aliens are Chinese. To anyone with actual Chinese culture context, they are obviously "Westerners".
<spoilers>
- Far more advanced technologies.
- The Trisolarians cannot lie, so that becomes the only advantage of humanity. -> Art of War
- The Trisolarians are blocking physical experiments to stop science and technology advancement. -> Entity list and export control. Huawei.
- The factions in human that supports the invasion. -> Evans hated humanity because of The Silent Spring, which is supposed to represent the Western self-guilt culture.
- The emaciated generation that failed at launching the mutually assured destruction device is an image of "Westernized" generation.
The overarching background of the book is a discussion of which direction that China should take after 1989 stopped the democratization process and drove the Western powers into hostility. The author Cixin Liu has a more or less social darwinism answer for that ("Dark Forest"). Not that he endorsed social darwinism, but that's the main theme of the book.
</spoilers>
1. They'll open source the alignment technology? For open weight models, it's the only possible way to pass the safety without an external guardrail triggering system (which would be the same to open and closed weight models).
2. They'll allow others (including CCP) to define part of the safety test? Otherwise, I can't imagine how the CCP would be onboard.
3. A "western" model passing the safety test can be trained with distillation? Or is that a "distillation attack" as well?
The fact that the parents had to make further efforts to go through their daughters death to warn others just feels wrong.
(comment itself: https://www.reddit.com/r/space/comments/1usdigz/comment/owna...)
The superpower thing turned out to be pseudoscience later. As a result of being lumped together, for a long period of time, AI was regarded as pseudoscience in China as well.
Although to be fair, during the same period, the US and the USSR were researching superpowers as well.
In addition to the normal value to value, type to type, and type to value functions, in comptime, you can write static value to type functions.
In full dependent type, you can in addition write dynamic value to type functions, completing the value to type corner.
So in terms of typing strength, plain Haskell < Zig < dependent type languages.
That being said, using a coding agent to direct fuzzying and find bugs in the Lean kernel implementation is the big news here. (After all the kernel's implementation is not proved.)
The moral of the story is to push for more verified code not less and try AI bug hunting.
They already did! https://github.com/orgs/community/discussions/65245
Even if that's not the case, I'd imagine attestation apps like banking apps would require some kind of identity verification in exchange for trusting Graphene's keys.
In principle it doesn't make sense to leave any escape hatch, but I guess as always, it boils down to economy.
You can have a separate core and kernel to run such code. They don't have to be powerful, but they'll need to be small enough to be verified by the said provider. For most of the code that doesn't need attestation, they can be executed on normal hardware.
The provider also has to convince the regulator or banks to trust them. However, if that's solved, the user should feel no difference between pure Android and alternative platform plus attestation.
- memory/yyyy-mm-dd.md
- MEMORY.md
- SOUL.md
> Ultimately if you have a mortgage and a car payment and a family you love, you’re going to make your decision.
Nothing is preventing the author from continuing to write code by hand and enjoy it. The difference is that people won't necessarily pay for it.
The old way was really incredible (and worth mourning), considering in other industries, how many people can only enjoy what they do outside of work.
The three high score patterns are interesting as well. "Conceptual Inquiry" actually results in less time and doesn't improve the score than the other two, which is quite surprising to me.
On the semantic gap between the original software and its representation in the ITP, program extraction like in Rocq probably deserves some discussion, where the software is written natively in the ITP and you have to prove the extraction itself sound. For example, Meta Rocq did this for Rocq.
For the how far down the stack problem, there are some efforts from https://deepspec.org/, but it's inherently a difficult problem and often gets less love than the lab environment projects.
From time to time, I enjoy the model guessing what I meant rather than what I wrote. For example, "Find the backend.py" can be auto-corrected into "find the app.py".