troquerre

One cool thing about NextDNS is that they also support the Handshake DNS protocol. It’s an alternative root DNS that supports new TLDs while maintaining compatibility with existing ICANN TLDs https://handshake.org

I meant how do they track the data? If they're just doing it manually that makes sense though it seems inefficient...

How did GitLab track and create this diagram? Is there a service that does it automatically?

I think Keybase pivoted to add more features besides the web of trust functionality. That said I think there's definitely potential in using Handshake as an identity solution. ie If I own my username on Handshake I can point github.username to my github, twitter.username to twitter, etc. It's pretty easy to do with redirects

Great post from Calvin. Every founder, even if they're the CTO, should learn at least the basics of selling. Having the whole team aligned on what moves the needle makes a huge difference. It's not enough to offload thinking about selling to the CEO just because it's not the CTO's primary responsibility.

Agree with the premise of the article. That's why I'm excited about Handshake (https://handshake.org), it's an experimental new protocol that's trying to shift the root of trust of DNS from CAs to a distributed blockchain. Outside of creating a more secure root for TLS, it allows anyone to own their domain name and makes it very difficult to block access from end-users. It's still very much in the early days of adoption but nextdns.io already supports it which is promising.

Funny you mention HTTPS certificates because there's a blockchain-based protocol that's trying to create a decentralized certificate authority. It basically aims to shift the root of trust from CAs to the blockchain https://handshake.org

Hi I'm the CEO of Namebase. You're right that's the best way to bid anonymously on Namebase right now. We're also going to add the ability to bid anonymously directly on Namebase. The account verification is only required for purchasing HNS which we need to do due to regulatory restrictions in the US.

Have you checked out Handshake? It's a new experimental protocol that's trying to decentralize DNS https://handshake.org

We use NextDNS to access Handshake domain names and it's been working great. The privacy features are great too, although email links sometimes don't work because of them (more of a feature than a bug imo).

Uncanny, I was looking for something exactly like this yesterday to upload screenshots automatically to Google Drive. Ended up using Dropbox's screenshot save feature but I'll switch to rclone instead.

Handshake can improve how security on the Internet works. There are also geopolitical reasons for why it's important: https://www.namebase.io/blog/meet-handshake-decentralizing-d... https://www.namebase.io/blog/you-can-make-a-difference

Took a minute to set up nextdns on my phone but surprisingly the site resolved like normal on iOS Safari after setup. There are more Handshake sites here too https://github.com/namebasehq/awesome-handshake

I’ve been wishing for a ScreenHero replacement for years. It seems odd to me that no one came out with a replacement earlier, but I’m super excited to try this out now!

Can anyone who's used both Netlify and Zeit comment on how the two compare? I personally use Zeit and I really like their interface. The work they've been doing with nextjs has also been very interesting.

There are some new attempts at creating DNS roots that aren’t managed by centralized organizations. Handshake.org is aiming to create a distributed root of trust for the DNS root and it’s been getting traction in certain circles.

Security is not binary, it's a spectrum based on cost. It's the same for censorship-resistance. If Handshake increases the cost of internet censorship for every country in the world, then it will have succeeded even if it's still possible for countries like China to censor it.

Agreed. Consumers don't care about about implementation details, they just want better experiences. I think this is what most decentralized services miss the mark on. There's an interesting new protocol called Handshake (https://handshake.org) that's trying to decentralize DNS. The main benefit is that it can improve security by shifting the root of trust in DNS from a certificate authority based system to a distributed network. If you think about traditional DNS, 99% of people using it (everyone on the internet) don't even know that it exists. For Handshake, I think it's possible that millions of people will use it and get the security benefits without knowing it's decentralized.

Cloudflare and Google's dns resolvers got a lot of adoption bc they provided a way for normal people to get around censorship, but they're inherently censorable bc they're run by centralized companies. There are new initiatives aiming to create a distributed dns layer which are promising like https://handshake.org.

I think China has demonstrated that countries are willing to do that.

Which country are you in/which countries do you see this happening in if you don’t mind me asking?

Hey Vinnl, would it be alright if I dm you? I think there’s a way to create your service using Handshake.org such that it can’t be shutdown.

For context, Handshake is a new project aiming to create a distributed certificate authority and naming system. Domain names on Handshake are very difficult to shut down, so you could have a sci hub domain on Handshake that continuously tracks the sci hub servers. Users would be able to always access sci hub from the same domain in this case.

On the domain name analogy, there are now decentralized DNS initiatives like handshake.org that are trying to make domain names truly distributed, which may make for a better analogy for solid. I agree that DNS in its current implementation is not well distributed as you've pointed out.

I completely agree. If I were them I'd do whatever is necessary to get the acquisition out of the spotlight and then claw back every promise over the next few years. I have very little doubt that this won't happen, unfortunately for .org and the internet...

PSA if you had over 15 followers on GitHub by August 2018 you were likely included in the Handshake airdrop. Basically they developed a way to give each dev in the airdrop 4662 coins each (worth a lot since current market price is $0.20[1]). These instructions walk through what the claiming process is like https://namebase.io/airdrop. [1] https://namebase.io

There have been a few comments about Handshake already. I agree that there needs to be a single DNS and not just an “alternative” bc that will fragment the namespace. I think Handshake has the potential to become the DNS that the world uses bc it’s compatible with the traditional system — existing TLDs are blacklisted and the Alexa top 100k have been reserved as TLDs for the domain owners. Given that ICANN isn’t opening the gtld program for 2-3 years and how fast things can grow on the Internet, I think Handshake can become the de facto DNS that everyone uses before there’s a possibility for conflict.

People are already purchasing TLDs for affordable prices. .coin sold for 200k HNS ($50k at market price) but there’s have been dozens of other TLDs registered for less than $10. Any alphanumeric name less than 63 characters can be registered so you can almost always find a good name that is affordable https://namebase.io/domains

Namebase didn’t create the airdrop. You can still claim your coins to a cli wallet if you want, and the cli wallet is pretty easy to use actually.

To be clear, Namebase didn’t create Handshake or the airdrop. We’re building on top of it but we’re a separate team. You can also claim your coins outside of Namebase if you want. The cli wallet is actually pretty easy to use.

Duplicate accounts were deduped, but you can try both options to see which method was used for your airdrop. https://namebase.io/airdrop has instructions for GitHub. For keybase, follow the instructions from the page but instead of using your ssh key log in to keybase.io, go to your profile and 1) click on your GPG key 2) click to show private key 3) add your keybase passphrase 4) copy the private key into a file called `secret.asc` 4) executed `./bin/hs-airdrop secret.asc GPG_ID ADDRESS` where `GPG_ID` was the id/name of the key