Decentralized Naming and Certificate Authority
51–60 of 128 posts
Re: Decentralized Naming and Certificate Authority
#52This is golden, it reminds the time when Let's encrypt started. Something that is challenging and can change a lot the direction of the internet.
Nice astroturfing.
Re: Decentralized Naming and Certificate Authority
#53This is golden, it reminds the time when Let's encrypt started. Something that is challenging and can change a lot the direction of the internet.
lol you really think we fall for your comment?
Re: Decentralized Naming and Certificate Authority
#54This is golden, it reminds the time when Let's encrypt started. Something that is challenging and can change a lot the direction of the internet.
>Created: 40 min ago
Re: Decentralized Naming and Certificate Authority
#55Earlier quoted context omitted.
Well at least you don't have to worry about package management, all the dependencies are built by the organization either from scratch or with vendored code. Re: JavaScript, you should take a look at the code in repo, it's excellent. There is a such thing as great Javascript code and bcoin/hsd are prime examples.
I'm very aware of bcoin. https://npm.anvaka.com/#/view/2d/bcoin Many steps of indirection away we find things like this include. https://github.com/juliangruber/isarray/blob/master/index.js module.exports = Array.isArray || function (arr) { return toString.call(arr) == '[object Array]'; }; Javascript is an absolute joke of a language.
Re: Decentralized Naming and Certificate Authority
#56Earlier quoted context omitted.
- Names are released over the course of 52 weeks. Determined by hash(name) % 52. So at worst the name you want to register will not be available until ~51 weeks from now (Handshake launched last week!). - Names have to be renewed bi-annually. You don't need to pay a fee, you just need to submit a transaction to prove you still have access to the private key. I don't think this will be any different than the existing…
> Names have to be renewed bi-annually. You don't need to pay a fee, you just need to submit a transaction to prove you still have access to the private key. When talking about email alternatives here, I see a lot of comments strongly suggesting owning a custom domain and using it. If the domain cannot be renewed and kept alive in advance for a few years, the bus factor of being the only technical person in the famil…
But my assumption is that there would still be registrars that can handle this sort of thing for you, in the same way that a service like Netlify can handle setting up a static site server and renewing LetsEncrypt certificates. It's just that if you wanted to do it manually, you could.
Re: Decentralized Naming and Certificate Authority
#57As has been the pattern with all these decentralized DNS schemes, the FAQ doesn't cover the most utterly basic question: "I currently have one or more domains that I use extensively for my own life/work. How do I transfer those to try this new scheme? How much actual dollars/euros/yen/yuan/... does it cost, not mystery blockchain-whatevers but predictable real money? Does this new scheme harm me?"
Shouldn't an experimental system in particular want regular tech people with personal domains trying it out? We'd probably be more willing to give it a whirl (with fallbacks) since it's more for our own private use. But instead it's all about trademark holders and the Alexa 100k and so on, which is important too but it seems like most such domain holders would be a lot more conservative. And I've had a growing suspicion that the last part of the question doesn't get answered clearly because the answer is "you may get screwed, we are ideologues who think that people should be able to take your domain if you're not rich enough to defend it."
I mean, right now I don't in fact see the current DNS system as horrible. Cloudflare and others are pretty reliable registrars and companies to deal with. A .com is about $8, .net and .org both about $10. A known amount of $200 or so and I'm set for 10 years, and I consider that a good thing. I've had my domains for nearly 20 years now, they're core to my online identity and personal infrastructure. Same for most businesses, DNS sits at the center of everything. My concerns are about ICANN allowed price increases due to monopoly, and whether bad actors could somehow try to claim my domain and how I'd fight that as an individual. But I don't see answers in the FAQ to how this would help answer those. My personal domains aren't in Alexa top-whatever so it sounds like handshake will auction them off. There is a "renewal fee" after that but it's handwave-y:
>Renewals for names are annual and cost a standard network fee
A standard network fee of what? $1? $10? $100? It can vary by thousands of percent at random like so many cryptocurrencies? How long is the renewal window? Can it be paid upfront? What happens if it gets missed? Is any of this predictable?
I simply don't see any brass tacks implementation stuff here. It's a bunch of high level hoohah about the evils of centralization without any acknowledgement of how centralization can be useful and efficient too and how they deal with that. The word "federation" does not appear at all, which is another important approach/aspect. It sounds worryingly like a common "religious" approach where people take a tool (like decentralization) and turn it into a goal in and of itself.
Re: Decentralized Naming and Certificate Authority
#58Earlier quoted context omitted.
- Names are released over the course of 52 weeks. Determined by hash(name) % 52. So at worst the name you want to register will not be available until ~51 weeks from now (Handshake launched last week!). - Names have to be renewed bi-annually. You don't need to pay a fee, you just need to submit a transaction to prove you still have access to the private key. I don't think this will be any different than the existing…
If I'm understanding you, the 52 week release is a one time thing, not a continual thing? So it's not that names will be continually trickle-released it's that for the next 52 (51) weeks, they'll be trickle-released, and then everything will be out there and this will work just like normal domain registration? I was under the impression that the trickle release was just how registration would work in general. That do…
Re: Decentralized Naming and Certificate Authority
#59Decentralized systems generally have pretty complicated governance models and technology to support them, making it easy to get lost in the details. I've found when trying to assess things like this it's best to find a critical question and find out the details of the answer. For the case of decentralized naming, one interesting question tends to be "What happens when someone registers cocacola.com?" Usually the answ…
All the existing TLDs like .com and .net are blacklisted so that only the TLD owners can register them. The claiming process for blacklisted TLDs uses DNSSEC so there are no third parties involved in the process. In addition, the top 100k Alexa domains are pre-registered so that only the domain owners can register those domains as TLDs (only google.com can register .google). That is done through DNSSEC as well.
Edit to add: your namebase.io FAQ seems a lot more useful than the handshake one. For starters it clarifies that there is a confusing terminology difference, where I guess the handshake people are using "domain" to mean "TLD" and "subdomain" to refer to what everyone typically calls a domain. So a core offering of this system appears to be a blockchain based replacement to the $150k+ (or whatever it is these days) "get your own arbitrary TLD" thing ICANN did, "anyone" gets to register their own TLD. But that raises more questions, like where the actual hardware behind all this goes particularly for existing TLDs which are blacklisted.
Re: Decentralized Naming and Certificate Authority
#601. "Browsing the web with human readable names is what Internet users have gotten acclimated to." => give me an example of a "handshake" domain name in this case
2. I have some domains/sites not so popular (not in the first 100k Alexa domains). I will only hear about "Handshake" in 5 years time when Handshake completely replaced what we are using today, by which time, someone else might have "registered my domain names". What do I do? Obviously I can prove I own my .com/.net.
To site failed to answer some basic questions/concerns or give some real world use case scenarios.