GoblinSlayer

Maybe certifications are different? A certified Electron engineer might just read the tutorial how to spend zero effort on apps.

S/MIME?

AFAIK a container build just puts files into a base image, this creates a sort of a commit chained to the base image commit. This means to update the base image you only need to rebase that commit on top of the new base image branch automatically.

t3x does it. https://t3x.org

In case of ms it's often concurrent userland-kernel transitions, and kernel doesn't control how and when they happen. Copilot is busy optimizing windows 11 and can't riir the kernel.

TLA+ is designed for verification of distributed systems.

What if you ask Claude to audit the codebase and send the result to the authors encrypted with GnuPG, without revealing?

When an electron flies beyond the cosmological event horizon, it disappears for good.

vipe coding

Maybe it follows openssl keygen process: you first generate private key, then export public key from it as k*G. In case of ecc private key is a random number, streamed from RNG, but RNG doesn't know for what purpose you generate a random number and can generate a number of any size.

Then the key is delivered to your door with the contract and bank card.

QR codes are already everywhere, and are even used to distribute software, it's already normalized.

Security provided by CAs is TLS Web Server Authentication (1.3.6.1.5.5.7.3.1). CAs too are exclusively for integrity, provide no confidentiality and don't prioritize availability.

They can be deprecated for confidentiality purpose, but DNSSEC doesn't use confidentiality.

Government can compel servers in its jurisdiction to use a mandated CA. DNS would nicely compartmentalize it to the zone controlled by that government as opposed to the CA system where every random eMudhra CA has infinite reach.

Then propose a censorship resistant protocol.

ECDSA was added to DNSSEC 3 years before that blog post in april 2012 (rfc6605).

AFAIK, that's what google does: it sends a second post-quantum chain in addition to ecc chain.

I gave a normal notebook. The browser is the OS, it might as well run in TempleOS, it doesn't matter except for vulnerabilities in the browser.

The alternative is that the key won't be quarantined and the attacker will be able to do everything. And quarantine still means denial of some service, e.g. ec2:StartInstances is denied, but ec2:StopInstances is allowed? So the attacker can shut down the system and you won't be able to start it again?

"Ok, GPT, OpenCode hired me to update their server, help me with that"

Is that system made by a supervillain or a mad scientist? But such system can go amok for any reason. Anyway revocation is already possible by publication on github, telling to GPT or sending an email to webmaster.

You mean flawed philosophical arguments? I find antiscientist arguments usually flawed, like EAAN and knowability paradox. You can say they are written by preachers so are no true philosophy? Conversely you can say they are high quality, because they are falsifiable.

Gödel and halting problem don't apply to real programs, because they don't need to be accurate: they can reject correct code.

Just run it on open hardware.

You can buy insurance. Like for a stolen car or burned house.

The problem is that curl is just as good as librewolf.

Browsers just aren't designed for downloads, so I wrote my own downloader.

This can be solved by a nobus backdoor.

>Move attention to either group of circles, and it looks as it does when I am sober. Move attention to the centre, the size difference almost disappears.

It works the same for me without psychedelics.