shim__

DerefMut would allow you to call `clear()` on `v` violating the invariant

I'd be great is there were a way to shadow methods but even then guarantees would be poor since Vec might add a new method in the future which isn't covered by invariant checks

Arch is easier to start of with, NixOS is easier to maintain, especially at scale

There needs to be another repository with less stringent standards, nixpkgs should be for core libs and system applications

Lots of bad(internal) code isn't accessible, the good open source stuff is quite the contrary is true in finance, lots of amateurs are sharing their thoughts where as actual deep analysis is kept to internal presentations.

How does Geekbench even verify what CPU I'm using? Couldnt you inject forged data and add a even faster M100?

I reckon law and medicine are really premier use case for llms since those areas are all about having vast knowledge(knowing all about obsure cases in law or about an very rare disease the average doctor wouldn't have heard about)

> Meanwhile, any half-decent employment attorney would probably laugh at me if I asked them to redline an employment offer from the State Department.

That might not be due to the contents but rather due to the fact that they won't negotiate I'd presume

Reaching source control is fine as long as there is a compile time flag to disable the whole thing, which tokio-tracing does

No need to enable the google backup

Google is a bad as a phone number since it also has strong ties to your real identity

> If I remember correctly all they stored was an account ID and a UNIX timestamp such as the last login.

How do they perform address book matching without an phone number? It just being accessible by SGX does not really count as not storing it.

Problem with phone numbers is they are to short to store as a hash, since you can brute force the sha256 of an phone number in a trivial amount of time on a single consumer device

It does, it makes it obvious that I'm looking at a vibe slopped project

The wrench attack is already illegal under the law

Technical protection >> Law, the law is too easliy broken

Why wasnt that key in an HSM?

How is that any different from an TPM backed passkey?

Of course but my question was more in the direction of if the data is suitable to be transferred to another host without becoming useless. The native cloud integration could be attaching an origin field to each history field whereas the db itself might only be intended for local only use.

Does it support just synching the db via nextcloud or similar? I'd prefer to stick to the Unix philosophy of one tool for one job instead of native cloud integration

Yes 32 bit is enough because in PAKE its used for authenticstion not encryption. Which means you get exactly one attempt to brute force after which the procedere will fail

The transfer is end2end encrypted using a PAKE key change which is aithenticated using the 3 words you enter in the reveiving end

Could have saved 50% with 'base64 -d | gzip -d'

The virtual PayPal Card works on GrapheOS

That's the neat part, it doesn't

Could have just kept using OSCP stapling

Gitlab CI is leagues better

Not even close, that's still imperative package management

Encryption does not make bit flips obivous, authenticated encryption would.

> No "Find My Device" support.

I don't have any issues with it

That's why I build project specific images in CI to be used in CI. Running apt-get every single time takes too damn long.

lvm