0
0

Gab.com killed?


 invite response                
2021 Jan 18, 11:12am   302 views  9 comments

by Patrick   ➕follow (55)   💰tip   ignore  

% curl https://gab.com/
curl: (6) Couldn't resolve host 'gab.com'

Can't get to it from my browser or my server.

Were they killed by the oligarchy?

Comments 1 - 9 of 9        Search these comments

1   Patrick   2021 Jan 18, 11:14am  

#patrick@vafli:~/planner() 11:12:57% whois gab.com
Domain Name: GAB.COM
Registry Domain ID: 4274190_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.epik.com
Registrar URL: http://www.epik.com
Updated Date: 2020-09-01T16:41:30Z
Creation Date: 1998-12-08T05:00:00Z
Registry Expiry Date: 2023-12-07T05:00:00Z
Registrar: Epik Inc.
Registrar IANA ID: 617
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ELMO.NS.CLOUDFLARE.COM
Name Server: SUE.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
Last update of whois database: 2021-01-18T19:12:45Z
2   Tenpoundbass   2021 Jan 18, 11:14am  

I saw a message about 12pm said it was going to go offline at 1pm to install more servers.
3   Patrick   2021 Jan 18, 11:15am  

Oh, that's good then. Thanks!
4   richwicks   2021 Jan 18, 11:15am  

Patrick says
% curl https://gab.com/
curl: (6) Couldn't resolve host 'gab.com'

Can't get to it from my browser or my server.

Were they killed by the oligarchy?


They killed the DNS entry:

https://www.nslookup.io/dns-records/gab.com#cloudflare

$ nslookup gab.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
*** Can't find gab.com: No answer


That's it, we have to get rid of DNS entirely.
5   Patrick   2021 Jan 18, 11:34am  

richwicks says
we have to get rid of DNS entirely.





I agree, and here's one way to do it:

- Everyone creates a public/private keypair, maybe via ssh
- Everyone's public key is hashed to a set of four English words, like "correct.horse.battery.stapler" case insensitive
- Every request you send is encrypted with your public key so others know it's really from you.
- Every response you get is encrypted with your public key so that no one can snoop.
- Content will be searched for by user public key (say, this conversation thread is owned by me) using a distributed hash table
see https://en.wikipedia.org/wiki/Distributed_hash_table
- Content will not necessarily be on any one server. Anyone who surfs public content also thereby hosts a copy of it, as in bittorrent.
- Bittorrent protocol will be used for serving via UDP direct from your laptop or phone.

So we would also replace ssl at the same time, eliminating two points of centralized control.

It would require a modified browser, or some small server piece you run on your laptop.
6   Tenpoundbass   2021 Jan 18, 1:06pm  

It's back up
7   Patrick   2021 Jan 18, 2:38pm  

Yes!!!
8   ThatGuy   2021 Jan 18, 7:02pm  

Upfront this seems like a fantastic idea, just don't let it be compromised
9   Patrick   2021 Jan 18, 7:32pm  

ThatGuy says
Upfront this seems like a fantastic idea, just don't let it be compromised


Thanks!

Indeed one way to defeat it would be to distribute similar software that has been hacked. So I need to have a well-known public ssh key and get people to check that they are getting the original.

Please register to comment:

api   best comments   contact   latest images   memes   one year ago   random   suggestions