@paulfree14 @mistressemelia Have you considered running a #tor hidden, and #i2p service. Self-authenticating endpoints, *practically* uncensorable. Also... everyone knows how to use tor browser, so user adoption is easy!
@mistressemelia @paulfree14 a tor hidden service would protect you from DNS hassles. Users go and grab the tor browser bundle and just use that. ".onion" addresses are well known to be associated with #tor, and the Tor project has loads of mind share and documentation. For example I'm a big fan of http://uj3wazyk5u4hnvtk.onion .. pirate bay is blocked on many #UK ISP ... #meh! I wasn't suggesting that your primary point for engaging with users be a tor hidden service, but having a resilient censor resistant service sounds ok ? Obviously deploying onions has its risks, but they are mostly fixable https://riseup.net/en/security/network-security/tor/onionservices-best-practices
@gcupc I agree with your human rights violation. However... it's very common to find it in Bring Your own Device #BYOD situation in corporate or education. Where the user will be told to install an additional CA to use the network. /cc @paulfree14 @mistressemelia
@mistressemelia @paulfree14 the hash of the public key for the site, is looked up in a DHT, to get the routing information, same as a bittorrent magnet link finds the file. But with some anonymity layers thrown in too. It's super interesting crypto/P2P design. Another cool project #i2p has lots of similarities https://geti2p.net/en/
@mistressemelia @paulfree14 for sure. However once the address is published it can never be removed. We can print the onion on t-shirts and spray paint on walls. It will always work.
@zoowar it is a problem... without a central source how does one know how to trust anything. I guess DNS does solve that. I was engaged with #monkeysphere once using PGP WoT to cross validate x509 https certs. http://monkeysphere.info/