Drunken Bishop (2023)
re.factorcode.org77 points by todsacerdoti a day ago
77 points by todsacerdoti a day ago
It's been a while but I can't get past the first image. I keep wanting to kill the orcs and grab all those spellbooks and gems, while keeping a wary eye on the elemental. (Although since this is obviously the Elemental Plane of Air, my ascension kit should let me handle it easily enough.)
How universal are roguelike character mappings? Is there some central bit of knowledge that all the developers refer to to decide whether 'b' should be a bear or a beholder?
These links are not loading for me but hopefully it's just some network hiccups on my end:
The Art of Unix Programming: http://www.catb.org/~esr/writings/taoup/html/
GNU Coding Standards: http://www.gnu.org/prep/standards/standards.html
Standard list of long options: http://www.gnu.org/prep/standards/standards.html#Option-Tabl...
Short options from -a to -z: http://www.catb.org/~esr/writings/taoup/html/ch10s05.html
...so this is the "serious" version of what you're describing.
I love being able to see the keys that are generated.
Years ago I made a high res greyscale version of the drunken bishop:
https://raw.githubusercontent.com/justintrupiano/RSA-Randoma...
I see the theoretical need for such fingerprint displays, but I can't imagine noticing that the display for one of the computers I work with has changed. Maybe if I printed them all out and posted them around my monitor...
I've found setting an alias like `alias ssh='ssh -o VisualHostKey=yes'` makes these fingerprints appear on every connection, creating muscle memory for how they should look. When something changes, it immediately feels "off" without needing to remember specific patterns.
I wonder if this would work better if it played a little jingle on every connection, rather than showed a picture.
These visualisations are so bland I can’t tell them apart. I mean, if looking at two side by side than sure, but if I look at them like every other day at best I can’t tell if anything has changed.
The visualisation makes it hard to see changes near the end of the string, which makes it a bad visualisation for verifying cryptographic hashes.
With cryptographic hashes, partial collisions are easier than full collisions, but still difficult.
But yes, it's unfortunate that Drunken Bishop provides different amounts of protection for bits in different locations. Ideally the protection would be equal among all the bits.
I am at a loss for words. This is simply an amazing read. Thank you for supplying me with this information.
