41–50 of 128 posts
Great, what the world really needs is a hideously inefficient set of distributed DNS servers that are permanently eating 100% CPU to do their proof-of-work blockchain mining crap. The page hand-waves this away by claiming (with no good reason) that it will all be renewable energy. Just like bitcoin in China, right?
No, centralization exists because users don't care about the protocol. Users care about the brand.
It's way easier to use FB than it is to say "choose your hosting provider. Each one has a slightly different set of features. Then link with other people you care about, all of whom may be using different providers that you need to pay special attention to." With FB, I click "send a friend request" and then move on with my day. And that's just one example.
This has been tried. It's called Namecoin and it failed to get much traction. I suspect that using Bitcoin instead would improve adoption dramatically instead of creating yet another token. This can be done using sidechains or something similar.
ENS is running on top of ethereum just fine
I know the handshake devs/maintainers are active on here. I've heard explanations from y'all about how handshake tries to solve the squatter problem. As far as I understand those explanations: - Names are released at a trickle, meaning no one can buy all of them in one go. - Names have to be constantly renewed (it's not a buy-once-keep-forever scheme), and (correct me if I'm wrong), you can't buy 10 years out in adva…
- 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…
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 family could mean that they lose their emails very soon (worst case scenario where something bad happens to the technical person towards the end of the bi-annual period just before the renewal).
“You need to submit a transaction to prove you still have access to the private key” — “transaction”? “prove”? “private key”? There’s no way this is going to last if people use these domains for emails and mailboxes for their families. At least with the conventional system, it’s easy to note down simple instructions to go to a site, pay and renew. This system seems better suited for institutions that may be able to handle it (though it could be argued that even large companies fail in trivial ways, like it happened with a certificate expiry with Microsoft recently).
They've somehow managed to make the two least optimal choices of language possible. The full node daemon, hsd, is written in Javascript. A non type safe language with poor package management for consensus critical code. We also have a light client, hnsd, which is written in C A non memory safe and error prone language for client code people would run on their systems as root.
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.
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]';
};
This has been tried. It's called Namecoin and it failed to get much traction. I suspect that using Bitcoin instead would improve adoption dramatically instead of creating yet another token. This can be done using sidechains or something similar.
Earlier quoted context omitted.
Everyone can put self-signed cert on a blockchain. You need to prove that you control the domain. Easiest way to prove that is to ask your registrar. And if your registrar will sign this fact you don't even need to ask him. So you naturally will come to DNS and DNSSec. And all standards are already here: deploy DNSSec, put TLSA record and it's done. It's a solved problem, just not widely supported.
"prove that you control the domain"? isn't that the rub? sounds a bit circular to me at least. there doesn't seem to be any solid replacement for the existing centralized trust authorities. what am i missing?
This has been tried. It's called Namecoin and it failed to get much traction. I suspect that using Bitcoin instead would improve adoption dramatically instead of creating yet another token. This can be done using sidechains or something similar.
One of the issues with Namecoin is the issuance. You can register any name for a set price. This leads to easy squatting behavior and allows whales to buy up all the good names. Handshake built in mechanisms to improve the issuance of names (detailed in danShumway's comment) which is critical when you're working with the issuance of scarce, non-fungible assets. It's like drawing a comparison to bitcoin and bit gold.…
Earlier 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.