Why? Everyone knows about rubber-hose cryptanalysis. The whole point of cryptography is to reduce them to this.
If they want our information, they should have to become literal tyrants, send armed men after us and violate human rights in order to get it. Not push a button on a computer to tap into their warrantless global dragnet surveilance networks and suddenly have our entire private lives revealed to them on a computer screen.
Yes, people will fold if they are kidnapped and tortured. That's not news. Forcing them to stoop to that is the entire design. Once the situation has escalated to that level, you are justified in killing them in self-defense. Torturers don't make a habit of allowing their victims to live and testify about it.
It's really pretty stupid. Your encryption is there in case your laptop gets stolen. If you have people willing and able to kidnap and torture you to get your data, you have much bigger problems than the fact that they'll probably get it.
I don't know PBTR, but in other raytracers the trick is to create a single surface between the two materials and set the ior of that surface's material to the quotient of the iors of the materials o both sides.
That way the light will refract on the internal boundary as if it moves from the one material to the other.
Prerequisite is that you ened to be able to create non-manifold objects...
I have to figure that one out every time I do it ;-)
The resulting interface ior should be positive if you go from a less dense medium into a denser medium, so I guess the material you're going to goes on top.
(which matches what happens from air-> glass. ior air is more or less one, mior glass = 1.5 so from air to glass -> ior 1.5)
> -2020-2022 mandatory COVID vaccine ID, to be able travel and enter establishments
Imo this one was slightly different, because it was (at least where I live) a temporary emergency measure with an end date as a response to an active crisis.
But I agree that people can get blinded by security theater.
Haha, I have used AI in some parts of it - mainly the JSON part because I could not wrap my head around it for the life of me. But I am proud that 90% is self written!
In that case the json parse function might be a bit of a challenge. It should actually be pretty straight forward with the builder functionality you’ve got in there. Loop over the input and use a state machine (switch block with a state variable) keep track of what you’re doing. Oh and you’ll need to recurse or otherwise use a stack to keep the nesting levels correct. Ie objects that contain arrays or objects, arrays that contain arrays, etc.
I think the old HN ethos that I loved, on full display here, won't survive intact in the AI era. It'll have to change from "It is cool to try making <neat tool> in <non obvious language>". Such a project is now a prompt away, and there's light-years of distance between a carefully hand crafted version and something that is posted aspirationally by an AI.
Every agent I know of or use will always say they built "Production ready, secure, fast package for X" if you ask them to build that, but they rarely actually will. It takes enormous time and effort to actually do that, and any first iteration of "production ready" is definitely aspirational until it actually hits the real world and survives. I'm speaking from experience, fwiw.
I actually really liked the gaussian elimination part. It's a term you hear often and 'demystifying' it is good imho.
Only nitpick I have is that it's a pity you use only 1 and 2 in the example with the carbs. Because of the symmetry it makes it harder to see which column/row matches which part of the vector/matrix because there's only 1s and 2s and it fits both horizontally and vertically...
I think it's a good idea to make the distinction. But I don't think 'vibe engineering' is the term I'd go for.
To me `vibe engineering` sounds like shoddily AI-designed suspension bridges. But then maybe I'm just an old fart programmer who thinks 'software engineering' is a term made up by programmers wanting to be as cool as bridge designers...
The article is nice. The website is very nicely done. It's interesting in a 'because you can' sort of way.
But I shudder when I imagine a web where all page elements move with bouncyness.
edit: which is not to say you should never use it of course. Even the <blink> had some uses.