I'm ok with memorizing a static ip address if admin-sama wants to revoke progrider.org
Name:
Anonymous2015-06-24 23:31
why can't we make our own DNS replacement that respects privacy
Name:
Anonymous2015-06-24 23:45
>>3 Why don't you do some programming instead of worrying about that. We're all going to die eventually anyway, spend the time and energy you have programming.
Name:
Anonymous2015-06-24 23:45
why can't we make our own CA replacement that doesn't have a critical single point of failure that's accessible to the government?
SPOILER ALERT: The answers to >>2 and >>3 are the same.
Name:
Anonymous2015-06-24 23:46
>>3 Probably because storing dead niggers is an illegal practice.
Name:
Anonymous2015-06-25 1:17
>>2 >>3 Just use a hosts file. You can even sync it to a git repo.
Name:
Anonymous2015-06-25 2:40
welp time to shut down my websites
Name:
Anonymous2015-06-25 6:07
It's still safe to host a server with a static ip right? You can only WHOIS a domain name?
I know DNS is not secure, but it is still so bad that you can just have an access point with a hosts file that points www.banksite.com to a server in your house that serves a clone of the banking site in plain http and there would be no way for the user to tell the difference except for the absence of the lock icon in the url bar?
Name:
Anonymous2015-06-25 21:34
>>11 We would just designate someone to maintain the list and pitch in additions as they come by. The problem is keeping track of domain changes(the owner would usually do this), keeping away phishing, and having to update manually. But it would totally be possible. >>12 It's all about the lock.