301–310 of 414 posts
Didn't last long? > sci-hub.hns/ could not be resolved by HNS.to. Please try another Handshake resolver..
[1] https://twitter.com/NamebaseHQ/status/1348707701744922625?s=...
Earlier quoted context omitted.
Handshake has taken a lot of lessons from previous attempts at alternative blockchain DNS roots like NameCoin. Here are some ways its different: - Handshake names are not *.bit domains like NameCoin they're actually top-level domains. This is because Handshake's purpose is not to decentralize domain names per se but too decentralize the root zone and create a more secure root of trust than Certificate Authorities [1]…
They're not top-level domains until most people's clients resolve them as such. They're off to the side in a niche name space that most people don't know about, and to which you have provided a brittle gateway that doesn't even present them as top-level. ... and they have a million other little niche name spaces to compete with to reach the point of serving as "top-level domains". I can create my own alternate name s…
This article (really it's more of a press release from the interested parties) seems to confuse the role of DNS from the role of certificate authority, making it hard for me to understand what they're talking about. These days sometimes the same entities provide both SSL certificates and DNS, but they are different services. > Handshake is “is effectively a decentralized domain name server,” Roquerre said. Instead of…
The article has a few technical mistakes in it (I've found most publications do that when it comes to a technical subject I'm familiar with...), but in short Handshake is an alternative decentralized DNS root hosted on a blockchain. It aims to replace Certificate Authorities as the root of trust by pinning TLSA keys directly on the blockchain instead of relying on trusted parties for verfication.
Its an alternative DNS, with a method to use that alternative DNS as a way of authorizing ssl certs too?
It'd be funny if hns.to got taken down for providing a path to Sci-Hub. At the root, the problem is trying to use the highly centralized legacy DNS system for purposes contrary to the wishes of those who control that system. To be "uncensorable", you need to change clients to use something other than DNS to resolve names. Anyway, the property you usually want to abandon for global names is "human-meaningful". Just us…
It's on Brave Browser's roadmap to resolve handshake DNS directly.
Earlier quoted context omitted.
Great question. All Handshake names are registered with HNS through the auction process. Say you bid 1000 HNS on a name and I bid 900 HNS. You'd win that name and pay 900 HNS (the second highest bid price. Importantly, that fee doesn't go to Namebase or any other entity — the coins are burned on-chain so they go to no one.
uhhh, so I'm looking on the website right now, and it wants a scan of my passport or photo ID for the privilege of buying a virtual cryptocoin, that can be used for purchasing domain names almost nobody can currently resolve, which vanishes into thin air after the purchase? am I getting that right? "Purchasing HNS with USD is currently limited to those with a US passport or ID."
This article (really it's more of a press release from the interested parties) seems to confuse the role of DNS from the role of certificate authority, making it hard for me to understand what they're talking about. These days sometimes the same entities provide both SSL certificates and DNS, but they are different services. > Handshake is “is effectively a decentralized domain name server,” Roquerre said. Instead of…
I think what they meant is that with decentralized DNS, it is possible to replace certificate authorities by using DNSSEC + DANE RFC6698[0], but I agree the way it's mentioned is confusing. [0] https://tools.ietf.org/html/rfc6698
Replacing cert authorities with something DNS-based (or alternative decentralized DNS based) doesn't actually seem relevant to the problem they are highlighting, of sci-hub's DNS records being removed by private or government actors making it harder to find sci-hub... no?
Earlier quoted context omitted.
The article has a few technical mistakes in it (I've found most publications do that when it comes to a technical subject I'm familiar with...), but in short Handshake is an alternative decentralized DNS root hosted on a blockchain. It aims to replace Certificate Authorities as the root of trust by pinning TLSA keys directly on the blockchain instead of relying on trusted parties for verfication.
So it aims to replace both DNS (a way of looking up IP address for a hostname) as well as certificate authorities (a way of knowing if the SSL cert being used by your connection is 'good')? Its an alternative DNS, with a method to use that alternative DNS as a way of authorizing ssl certs too?
This article (really it's more of a press release from the interested parties) seems to confuse the role of DNS from the role of certificate authority, making it hard for me to understand what they're talking about. These days sometimes the same entities provide both SSL certificates and DNS, but they are different services. > Handshake is “is effectively a decentralized domain name server,” Roquerre said. Instead of…
Handshake [1] is the next generation of DNS, as opposed to the ICANN controlled legacy system. It is more decentralized since a single actor does not control the system. You cannot be de-platformed without the consensus of the community and a fork, as opposed to a decision made by a single or small group of actors.
> Or does it also serve as a certificate authority somehow?
Since you can verify a certificate against a DANE TLSA record which is retrievable from a DNS zone with DS records stored on chain, the CA is no longer required for trust -- only cryptography. Checkout the paper which goes into far more detail [2]. The entire system actually incentivizes the Internet to become more secure -- which is pretty exciting!
> Is it actually more decentralized than DNS
It's more decentralized than DNS in that the root becomes the blockchain instead of ICANN. This project simply finishes the beautiful DNS ecosystem, which was already decentralized, other than the root.
Now we are all root, democratically.
This article (really it's more of a press release from the interested parties) seems to confuse the role of DNS from the role of certificate authority, making it hard for me to understand what they're talking about. These days sometimes the same entities provide both SSL certificates and DNS, but they are different services. > Handshake is “is effectively a decentralized domain name server,” Roquerre said. Instead of…
It perpetuates that problem of ICANN DNS becoming a "business" instead of solving it. (ICANN DNS domain names were originally free.) The potential for censorship is only one problem of ICANN DNS.
Also, this project introduces a new problem of wasting energy on mining tokens.
Earlier quoted context omitted.
Reddit has conveniently left him out of their about page, despite being a cofounder: https://www.redditinc.com/ About Aaron: https://en.wikipedia.org/wiki/Aaron_Swartz
According to the Wikipedia page, he did not join Reddit until 6 months after Reddit launched. He was fired a year later. There is also a tweet from 2011 saying he was not a co-founder: https://twitter.com/alexisohanian/status/93374221685755904
He made a webapp, and partnered with reddit founders to maybe merge things but AFAIK conflicting (technical and non technical) visions made the next step impossible.