Kab1r

But then sales taxes are fees, no?

Best library name.

I don't think formally verifying my showing that the model is correct is good enough anymore. You must prove that your implementation refines the model.

I've been building a TLA style Temporal Logic library for Verus (using LLMs). My experience so far is that LLMs are surprisingly useful at generating the mechanical proof scaffolding (when they're not occasionally trying to cheat with `assume(false)` statements), but they are not a substitute for knowing what property you actually want.

I have written complex proofs for distributed system using verus which are certainly not expressed by clippy

And some websites consume the entire history that a browser displays in that menu

I've had this a couple times too

I think CXL, perhaps more specifically cxl.mem on edsff, is a more relevant replacement for DDR, that most have also not seen

An anthropic the only provider with an IL6 approved frontier model?

Yes please take as many of the ≈10^12 unique email addresses I have used in the last year.

As opposed to the rest of the world who believe you must let yourself be murdered /s

Is there a good reason (other than licensing and Linux as an alternative) I shouldn't use Windows Server 202X as a Desktop OS?

S3 launched as the first public AWS service.

Didn't SQS launch publicly earlier than S3?

RAID or do regular off-site backups.

RAID is not a backup! Do both.

Does anyone know if this is the same vulnerability that ASUS leaked in a beta BIOS?

Being grateful for a miserable life marginally improving does not negate otherwise unavoidable prolonged suffering.

If the change is targeting a rust edition it's being treated as a feature/improvement not as a compiler bug. If there isn't a spec that explicitly says that this is expected behavior (and as far as I know there isn't a concrete spec for the rust language) it should be instead treated as a backwards compatible bug fix

I would call this a compiler bug

Grace Hopper already includes Arm based CPUs (and reference motherboards)

I fell in love with pattern matching the first time I used Haskell. Having the feature is great, but I really don't like the syntax used here.

Am I the only one that really dislikes the syntax choices here?

Either this or they worship Progress and Poverty like a lost religious text

Is this just searching certificate transparency logs?

If only it worked on ARM

Last time I opted out of facial recognition when re-entering the US, I got put through an additional baggage and security scan with my passport literally locked in a box.

I tried Ly maybe a couple years ago, but I ran some issues. I've had great luck with greetd+tuigreet. The UI is quite similar as well.

I have used iodine, which though isn't the easiest to setup works on every airline I have tried, to bypass airline Internet firewalls. DNS packets are one of the few things they don't seem to even try to filter. I wouldn't be surprised if you could just run wireguard over UDP/22.

I'm not sure if GitHub is the right place for chromium mirrors. When you upload to GitHub, you are agreeing that the code is licensed to GitHub under certain conditions (in addition to the license specified in the repository).

Really? I don't think I've ever had a YouTube video take longer than 30 seconds to load on a good Internet connection

the default storage options did not support ReadWriteMany for Block and Object Storage, which were necessary for using my database Postgres.

Postgres does not require ReadWriteMany volumes.

To better understand this, when I created multiple replicas, the same database could not be accessed by all the replicas. Only one at a time could access the database.

Assuming you mean multiple replicas accessing a single postgres database, this should not be a problem. I can't think of any networked database that prevents multiple clients from concurrently connecting. Postgres even has MVCC to allow multiple concurrent changes to the same record.

The architecture diagram towards the end of your blog post shows multiple subdomains, each with their own database. Each of these should be using their own RWO volume, not a single ReadWriteMany volume; that's a good way to cripple your ability to scale.

CNPG is my preferred way to manage postgres clusters on Kubernetes.