mxey

Seems to me that “we ran the Jepsen test” is just something an LLM thought would sound good on a DB’s website.

It’s wild how bad it is. Not surprising for a vibecoded database, but why did they hire Kyle for a test, instead of first doing ANY testing themselves?

“isolated environments on shared hardware”

So, not isolated environments? The surprising thing is that they used the CPU cache instead of the just exploiting the hypervisor.

Oh, TIL!

How are agents helping you? What was the trouble with Postgres before?

Many CVEs have too high severity for what they describe.

“They can put SCTs in the cert, and still not publish to the logs, nobody is auditing the logs for every cert every browser sees”

I don’t think you can get the SCT from a log without the log publishing it? That would defeat the purpose.

“Certificates that support certificate transparency must include one or more signed certificate timestamps (SCTs), which is a promise from a log operator to include the certificate in their log within a maximum merge delay (MMD).[4][3] At some point within the maximum merge delay, the log operator adds the certificate to their log.”

The majority of existing software runs without a glitch? Are you being serious?

Who writes those tests and makes sure they test the right thing and everything?

That’s an interesting idea but not all locks are held for the duration of the statement. A lot of them take a less intrusive lock for the whole statement and take an exclusive lock for a very short time when they finish up.

Edit: Looking this up, I’m not sure this is correct.

> The WireGuard website claims ChaPoly is at least as fast as hardware-accelerated AES.

I haven’t used WireGuard but I have easily doubled OpenSSH performance by switching back to AES.

Since 10.7 it autosaves.

The Delete button is shown, and correct, for new files that have not been saved at all yet.