So people can visit and read the site with increased anonymity. In some places for some people, just visiting crimethinc.com could put them in real physical danger.
It would be great to provide a .onion address / hidden service for people to use if they need to.
I'd certainly prefer if our .onion address is something memorable and clean instead of random characters. .onion addresses have to be exactly 16 characters long before the dot.
crimethincABCXYZ.onion, for example.
You can use something like Shallot to generate public/private key pairs until the public key looks like the string of characters you want.
So people can visit and read the site with increased anonymity. In some places for some people, just visiting crimethinc.com could put them in real physical danger.
It would be great to provide a
.onion
address / hidden service for people to use if they need to.I'd certainly prefer if our .onion address is something memorable and clean instead of random characters.
.onion
addresses have to be exactly 16 characters long before the dot.crimethincABCXYZ.onion
, for example.You can use something like Shallot to generate public/private key pairs until the public key looks like the string of characters you want.
https://github.com/katmagic/Shallot
However, according to their performance table, it'll take basically forever to generate a full long address that's 16 characters.
It's obviously possible with enough compute resources. I just don't know if we'll ever have access to that.
Facebook has a vanity
.onion
address:https://en.wikipedia.org/wiki/Facebookcorewwwi.onion
Compare with ProPublica's:
propub3r6espa33w.onion
We could either go with a short quick to generate address like:
CWC[13 random characters].onion
Or work toward a very specific 16 characters, somehow:
crimethincXonion.onion
crimethincsecure.onion
I don't know where to start with this.