Postman logs detailed information on every single API request you make through its tool, including query parameters. If you use the templating syntax `{{some_secret}}` to fill in a query parameter, it sends the actual secret content of `some_secret` to Postman's servers. If you disable outgoing network traffic to this logging endpoint, the entire app will stop working properly.
I discovered this when investigating whether Postman is HIPAA-compliant (it is not).
My main point was that I wouldn't want my secrets to ever be sent to Postman under any circumstance (or alternately, stop calling them "secret"). A lot of the online responses were some variation of "why are you sending secrets in query parameters in the first place?" (I'm not). When I posted on Reddit, it escalated to targeted harassment by people who were obviously current/former employees at Postman.
I did send out an email blast to a bunch of CIOs/CSOs in my network which went a bit "email viral" through forwarding, and this ended up triggering a substantial amount of enterprise cancellations.
I am still dumbfounded what value Postman can make in capturing all the publics usage. Sure they could mine the data, but they cant exactly use it in any legal way so why bother ?
Excellent post. One thing that would be really interesting to see is the "ponder hit rate" (how often two engines pick the same move across a large set of test positions) between your custom Crafty engine and the lineage of engine development over the decade after 1996 (Fruit, HIARCS, Rybka, Stockfish, etc).
Fabien Letouzey released the Fruit engine in 2004, and within six months, HIARCS had its biggest Elo gain in over a decade. No future engine followed the same slow Elo growth curve after that. Similarly, after Vasik Rajlich released Rybka, it pulled 150 Elo ahead of everyone else on the same hardware. So the history of chess engine development certainly supports the theory that a better evaluator can make an exponentially stronger engine on equivalent hardware.
This is such a great idea. I didn't know about WebXR before reading your comment, and was delighted to see that this is a relatively easy thing to implement. I need to find some VR goggles to borrow so I can test this out, but I'll optimistically push out an update within the next day with the WebXR update.
Thank you!! I was also hitting performance issues, especially on mobile - I think the latest version has gotten it a bit closer to a smoother experience, but there is still a lot of low-hanging fruit on making this more fluid (especially the step transitions).
Yours is amazing work, and certainly a higher degree of fidelity than I was able to achieve with AI assistance. The initial motivation behind this was largely driven by curiosity around the rotor motion (the ratchet and pawl assembly), and then into how the wiring actually works. For my brain, I needed to press the keys a hundred times and watch the current flow before it started making sense.
I'm curious about how you worked out the inner dimensions and part placements so accurately. Thank you for providing this marvelous free resource!
I discovered this when investigating whether Postman is HIPAA-compliant (it is not).
reply