It's all an elaborate scheme by the ISRG: compete all the commercial CAs out of existence, and then charge A MILLION DOLLARS for a certificate renewal. I've seen this movie before.
What's the "old boy network" thing here? This looks like a sales outreach event. It's connecting enterprise startups that want to do pilots with enterprises that will consider pilots.
There are genetic traits correlated with virtually anything, including things that can't possibly be mechanistically linked to biology, so those correlations are saying less than you'd hope they would.
Just because smart people tend to have fewer children (because, for instance, they delay it due to schooling and career demands) doesn't mean genes for intelligence are necessarily being selected against.
There's several reasons why this might not be the case, including that our premise is simple heritability and not genetic determinism, which is a different concept. I get where you're coming from now though.
People beat around the bush but the heritability of IQ is extremely high, modern studies put it around 80%. So if one group has an IQ of 140 and another of 100, it'd imply about 32 of those 40 points are generally able to be explained by genetic factors. For some contrast that tends to be around, or a bit above, the estimated heritability for height.
And so you'd see that easily in a single generation. It'd be akin to if tall people (or short people) began removing themselves from the gene pool in significant quantities. You'd immediately (well at least once people reached their adult height) see a significant increase or decrease in average heights.
This isn't true; 80s and 90s-vintage twin studies put it around 80%, but those numbers have been slashed; even hereditarians don't stand by them anymore. Molecular genetics results (contested by hereditarians, in fairness) situate it closer to 15-30%. David Bessis has a good piece about this.
And that's before you get to the slippery definition of what "heritability" means. It does allow you to use the words "explained by genetic factors", but in a very specific way, one in which the number of hands you have isn't similarly explainable, but how much TV you watch is.
That's quite a meaningless statement. Molecular genetics is in its infancy and so you're appealing to absence lack of evidence, which exists for most of everything, as evidence of absence - quite nihilistic! A quick search similarly suggests rates as low as 10% for the heritability of (non-European) height based on molecular genetics, undoubtedly for the same reasons.
And we've already had this conversation and in spite of your obsession with bias confirming 'blogs written by very smart people' - the heritability of TV watching is zero. Actually lol looking this up, it turns out there has indeed been a study done on this [1], as part of a study on the heritability of sedentary behaviors in general. And yeah, it's zero.
You are right that the number of hands you have is not heritable, but is only because heritability is defined as the percent of variation in a trait, between populations, that can be explained by genetic factors. When basically everybody has two hands, there is no variation, so there is no heritability to measure. It'd be like discussing the heritability of hair color if everybody had black hair. It's not some sort of clever insight or retort, though I'm certain your blogs framed it as the wittiest thing ever.
This comment doesn't actually say anything. I get that you're unhappy with the comment that I wrote? But that's all I get from it.
The one specific claim you make here, that height has heritabilities measured at around 10%, is false. In fact, the comparisons between the steadfastly high heritabilities of simple physical phenotypical traits like height and complex behavioral characteristics is a big part of the current scientific conversation about behavioral genetics.
But you’re seeing huge effects in three years, not a generation.
The report notes “The change in mean scores that can be explained merely by the changing composition of the student body, however, never exceeds a few points.”
So for Portugal for example about 10% of the drop might be attributable to immigration. But the other 90% to something else.
The West is still mostly in the denial phase, so nothing is really being done, yet. As such, the effect is ongoing. The Flynn Effect (and its reversal) are measured in impact per decade. And numbers that seem small at first aren't necessarily so. For instance a 3 point decline per decade doesn't initially seem like much until you consider that IQ generally has an artificial mean of 100 with a standard deviation of 15. So 3 points per decade is 20% of a standard deviation per decade! That's enormous.
In the past an IQ of 85 was considered mentally retarded. This was changed in 70s to make normal intelligence 'more inclusive.' That's another way of stating that 85 is still the best threshold for mental retardation. So a reverse Flynn Effect of 3 points/decade means you're talking about going from perfectly average to mentally retarded in 5 decades.
And for many things, the effect will not be linear. If we take a test there's likely to be an exponential pattern where somebody of a certain IQ will get an answer correct e.g. 99% of the time, somebody a bit below 80%, somebody a bit below that 40%, and then somebody a bit below that will basically never get it correct beyond the point of statistical noise. Pair that with likely increased variance when looking at individual and relatively small societies, and it's fairly easy to imagine sharp swings being completely viable.
Forget whether you "roll your own" or not, userspace RNGs are a bad idea. The advice to rely on getrandom or urandom is as much about the superior security properties of a kernel RNG as they are about whether you'll fuck up AES somehow.
Linux kernel crypto code has resulted in security issues, e.g. CVE-2026-31431.
The advantage of using a cryptographically secure stream cipher [1] is that we only need about 128-256 bits of good entropy to generate an arbitrary large number of secure random numbers, across multiple systems (e.g. MaraDNS has a native Windows port where /dev/urandom randomness is instead done with proprietary Windows API calls). It can even give us some level of protection on systems where the OS level random API is compromised: Some people are wary of RDRAND because they think Intel might actually use an insecure PRNG for the numbers, and Coldcard Bitcoin seed generators were compromised a little over a month ago because their version of /dev/urandom was completely insecure on some of their devices.
I don't grant the premise that per-transaction urandom reads are likely a meaningful expense to begin with but on modern Linux getrandom is a vDSO anyways. Even before the vDSO, getrandom was fast.
The application domain where this tends to get brought up as a problem is in large-scale simulation. I have no opinion about whether getrandom is fast enough for simulation, but here we're talking about cryptographic random numbers, not simply high-quality random numbers. If you want to use something like PCG for your simulations I won't dunk on you.
In addition to the overhead of a /dev/urandom read(), since my programs run in a chroot() sandbox, there’s the possibility that the file descriptor to /dev/urandom will no longer function—since chroot() is not part of POSIX, there’s no rigorous standard on how chroot() is supposed to behave with a given operating system.
getrandom() is another possible solution, but the problem with getrandom() is that it’s also not part of the POSIX spec, and my program needs to compile in an anally POSIX compliant system: While my programs use chroot() and setgroups(), both of which aren’t part of the POSIX spec, it has a configure time option to disable both chroot() and setgroups() so everything will compile as long as the underlying system follows POSIX.
The reason for this strict compliance with POSIX is because the changes to the C compilers (gcc and clang) between 2022 and 2026 made previous versions of MaraDNS have issues compiling everything, and, indeed, with these C23 changes to C compilers, unpatched djbdns no longer even compiles with a modern compiler. I changed everything to work with the new C23 spec, then I changed the compile flags to compile with a strictly compliant C99 compiler, but to get that to work, I had to make the program strictly POSIX compliant (with the exceptions of chroot() and setgroups()).
This way, should MaraDNS not compile in the future (remember: The post-C23 changes broke a lot of programs that used to compile just fine), it’s a bug with the compiler not following C99 and/or POSIX, and not a bug with MaraDNS.
Hence, my homegrown secure pseudo random number generator, so I can make strong random numbers while remaining POSIX compliant (we seed the PRNG before entering the chroot() sandbox). Of course, /dev/urandom is also not part of POSIX, but it’s on pretty much any modern *NIX, and trying to open /dev/urandom is not going to raise compile-time errors.
I don't think trading resilience for POSIX compliance is a good call, and I don't think "strong random numbers" is at all the right way to think about this problem.
reply