3,382 karma · joined July 28, 2011
Please use they/them pronouns when referring to me.
I can be reached via email to hnpub-c5b3 * ryanc * org
[ my public key: https://keybase.io/ryanc; my proof: https://keybase.io/ryanc/sigs/JVwG0IkvYj5Tur8NJGrivRLWeKzDetQdNyb488EQp_8 ]
ssh ansi.rya.nc
(currently shows Sneakers, complete with subtitles)
Has this person studied law?
I do not have a consent banner, and I do not believe that I need one.
You seem to be trying to say that "the fact that it was delivered proves it had a valid signature when it was sent".
That presupposes that the headers indicating when it was delivered are correct, or that it was delivered at all in the first place.
I don't think you understand the attack.
I sent Thomas an email admitting to something scandalous.
A few months later, Mallory pops the server Thomas's email is stored on, and extracts his mail spool.
Mallory wants to prove to a third party that the email is authentic and not a fabrication.
I know it's real.
Thomas knows it's real.
Mallory is pretty sure it's real.
Alice, a reporter for the Daily Bugle cannot verify it is real, rather than Mallory's forgery.
I can claim it's a forgery, and point out that Mallory could have made it up and generated the signature with the published key.
Now, I may have a problem if it were a crime rather than something merely scandalous because then Bob, an FBI agent, decides to subpoena some logs and maybe prove when it was sent, but even so, logs typically don't have message content or even a hash of the message content.
This would indeed be pants-on-head for UDP.
My vim configuration is moderately customized, and I regularly write code on systems I SSH into since my personal laptop is a Pixelbook.
The main things I rely on are syntax checking plugins.
I use ripgrep to find stuff in codebases, and when I'm working seriously I use an ultrawide monitor with plenty of screen space to have documentation I can glance at open.
I have a significant collection of small libraries I've written for common tasks, and often refer back to my own code across projects to figure out how to do things. Metaprogramming is something I do often too.
As another person said, thinking is my main constraint when working, not actually writing the code.
It should also be noted that I'm not primarily a "Software Engineer". I'm a Principal Security Engineer at a big tech company. If I'm working on actual code, it's generally "interesting", either a hard problem at work, or a personal side project. There tends not to be much boilerplate.
For TypeScript/JavaScript in particular, something like copilot would get in my way, as my style for this languages is extremely non-standard.
I'm not sure how much any of my coding habits have to do with it, but I regularly tear into unfamiliar codebases to fix bugs and add features, and I'm pretty good at orienting myself quickly, even in languages I haven't used before.
The first thing I did with Rust was add features to a data compression library without any prior exposure to the language...
A wealthy person should not be able to decide that they don't like some small minority and then influence public policy to enact policies which make them so miserable that some of them are driven to suicide.
When you refer to "males" and "females", and especially use terms like "low-quality female" you sound absolutely unhinged.
#18 is wrong, after the 15 comes 18, so 18 should be written in the blank space.
Bastards.
No problems with it, but critically I revoke the public key a few days before publishing the private key.