> The so-called web of trust is meaningless security theatre.
Ignoring your comment’s lack of constructive criticism, I’m going to post this meaningful implementation that an excellent cryptographer, Soatok Dreamseeker, is working on: [1].
You may also search for his posts in this HN thread, his nickname is “some_furry”.
Keyservers already “solved” this problem without needing federation because we only needed one keyserver anyway. Federating them isn’t going to do anything. Web of trust is a broken system that sounds super cool until you try to really use it. It has so many flaws that there’s really no way to revive it. Keybase tried to do something about it and also failed.
At that point you're just io bound, no? I can easily parse json at 100+GB/s on commodity hardware, but I'm gonna have a much harder time actually delivering that much data to parse.
I’m curious, why not? The amount of time and frustration saved seems insane, which seems to be a net positive, unless you can’t afford it of course (which is a good argument, but I’m not seeing any in your comment).
Because there are free and privacy respecting alternatives. I use DuckDuckGo, but you can also use meta-engines that anonymize traffic like SearXNG. None of these require accounts or payment methods that effectively de-anonymize you. Finally, if you really like Google for some reason but don't want the side effects, use an adblocker and a VPN.
After setting up dkim, dmarc, etc. I've had no problems in the past decade except for one person using aol. I told him that his email was broken and if he wanted to receive my email he needed to fix it. I don’t count such things as deliverabilty problems, but as receivability problems on the other end.
I’ve never sent any kind of bulk email and I suppose my host has a good IP. Everything I do depends critically on email deliverability, often to addresses I’ve never sent to before, so if I had a problem I would certainly know about it.
Yea that's a common theme of excuses for both Rust and Nix. Wrong though, because most anyone who can use a computer at all can learn the basics of Vim.
Seeing that flake.nix badge of complexity lets me know a project will be a nightmare to set up and will break every other week. It's usually right next to the Cargo.toml badge with 400 dependencies underneath.
To be honest I don't know what to say, you can use nix in many ways, and you don't even require to know the language.
The easiest entry-point is to just use it like a package manager, you install nix (which is just a command...) and then you have available the whole set of packages which are searchable from here: https://search.nixos.org/packages
nix-shell is just to download&add programs temporary to your PATH.
I don't feel that this is harder than something like "sudo apt install -y xxxxx" but for sure more robust and portable, and doesn't require sudo.
If at some point you want to learn the language in order to create configurations or packaging software, it may require to check a lot more documentation and examples, but for this I think it's pretty straightforward and is not harder than any other package manager like aptitude, homebrew or pacman.
Nix with Flakes never randomly break, I still have projects from 3 or 4 years ago that I can still run `nix build` and getting it running. Yes, if you try to update the `flake.lock` this may introduce breakages, but this is expected if you're pining `nixos-unstable` instead of a stable branch.
I’m not sure what you mean by “a nightmare to set up”. You install Nix on your current OS with the determinate.systems installer, and you enter `nix run github:johndoe/project-containing-a-flake-dot-nix-file` to try out the project and have the full reproducible build taken care of by Nix.
Sure, installing packages the proper way requires a little bit more setup (Home Manager, most likely, and understanding where is the list of packages and which command to build to switch configuration), but as trivial as other complex tasks most of us hackers are capable of doing (like using `jq` or Vim).
It can only apply shader(s) to the current frame I think. To produce the crt ghosting you'd probably need access to the previous frame (not an expert).
I've tried the shaders in the following repo with ghostty. They definitely work. I ended up keeping a cursor trail shader. https://github.com/0xhckr/ghostty-shaders
Yes, correct! If you check out https://ghostty.org/docs/config/reference, the iPreviousCursor is available, so it can be used against the iCurrentCursor to produce a fading effect. But I think the entire previous framebuffer isn't there (yet).
You say that like it’s a joke, but the huge wall of text did that for me. Unless I was being forced to take the test, I’d just have given up on doing it.
Ignoring your comment’s lack of constructive criticism, I’m going to post this meaningful implementation that an excellent cryptographer, Soatok Dreamseeker, is working on: [1].
You may also search for his posts in this HN thread, his nickname is “some_furry”.
[1]: https://github.com/fedi-e2ee/public-key-directory-specificat...
reply