Week 2 of building docs for #Rhizo and back to an old challenge I haven't thought about in a few years: how do you write about common software industry terms that may come across as insensitive or offensive to some people?
Example of the week: blind signature https://en.wikipedia.org/wiki/Blind_signature
The audience is part people familiar with cryptography, and part experienced software engineers who aren't as familiar with it but want to learn.
Defaulting to the industry standard makes sense because that's what everyone calls it, but it feels bad - suddenly it's "blind this, blinds the token, signs blindly," etc.
Using an alternative term (hidden, disguised, obfuscated) may also alienate the audience who expects to hear about, well, blind signatures.
This matters to us because the app itself is also supposed to be accessible to a wide range of people, so the docs should be an extension of that.
What's the best approach here?
