-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use term StakeShuffle across the docs #1152
Comments
Update verbiage on CSPP/StakeShuffle with more recent developments. Adds terms CoinShuffle++ and StakeShuffle to glossary. Adds video tutorial for privacy mixing on "How To" page. Addresses decred#1151 and decred#1152.
Update verbiage on CSPP/StakeShuffle with more recent developments. Adds terms CoinShuffle++ and StakeShuffle to glossary. Adds video tutorial for privacy mixing on "How To" page. Addresses decred#1151 and decred#1152.
Update verbiage on CSPP/StakeShuffle with more recent developments. Adds terms CoinShuffle++ and StakeShuffle to glossary. Adds video tutorial for privacy mixing on "How To" page. Addresses decred#1151 and decred#1152.
After recent discussions, it must be clarified that this issue is about using term "StakeShuffle" in more "user facing" and "simplified" places (introductions, entry points that we share to newcomers), and it should be used as a synonym to "Decred Privacy", i.e. all elements involved. CoinShuffle++ must still be mentioned where appropriate to give it due credit, along with other involved tech. I think the right places to mention CSPP is anywhere where we need to break down what StakeShuffle is made of, some "advanced" pages, and places that talk specifically about configuring the CSPP server used. |
So it turns out that CoinShuffle++ is just one part of the equation. So far I've learned that
Recent marketing discussions suggest several people are happy with the StakeShuffle term to capture all of the above and being less user-unfriendly at the same time. It was used in the press release and picked up by some news outlets (just google it). We'll be using it in Decred Journal too, unless a better term shows up and gains support.
Whatever the final term is, the incorrect usage of CoinShuffle++ is already out of the bottle. But at least we can fix some dcrdocs pages.
Places to update:
Privacy / CoinShuffle++
(mkdocs.yml)The text was updated successfully, but these errors were encountered: