• @[email protected]
    link
    fedilink
    English
    11 year ago

    Good morning, Thanks for your explanation. I am curious towards your phone book analogy because a phone book is like a ledger of information and creating a decentralized ledger is the main tech behind blockchain (which ive always understood as being more about the technological promise rather then virtual currencies). In my personal theory having a blockchain adress book of domain names sounds realistic. Is the problem that it would only work for those connected to it (so completely seperate from the current internet) or is there another technical challenge.

    Ive found handshake which is supposedly backwards compatible with current dns system but it uses a p2p system and coins to vore: https://handshake.org/ What are your thoughts on it?

    Also good night. Cause while you just woke up i’ve been delaying to go to bed.

    • @[email protected]
      link
      fedilink
      English
      11 year ago

      Have a good night!

      In my personal theory having a blockchain adress book of domain names sounds realistic. Is the problem that it would only work for those connected to it (so completely seperate from the current internet) or is there another technical challenge.

      Well, while I normally tend to have a kneejerk visceral reaction to blockchain tech these days, this looks to be something that would actually make sense/benefit from a blockchain based system. I’m certainly intrigued by it, but a couple of issues I can already think of:

      • From a user perspective: As you’d mentioned, it would rely on people being connected to it already, and people already have a very difficult time with the onboarding process of Lemmy

      • From a developer perspective: You’d most likely need some sort of library to handle communicating over this protocol, since none of the major (or at this point, I’d assume any of the) operating systems won’t support this natively. This means that not only does the server side of Lemmy need something to handle this, but any client-side apps (whether on PC or mobile) would also need a way to handle speaking over this protocol

      • From a server admin perspective: I’m not too sure about this one, but I wonder what the resource usage would look like for a protocol like this? Right now, its very easy for instance admins to just pickup say a $5/very cheap VPS from <insert provider here> and get up and running. I feel like the resource overhead of the protocol alone would make this a bit more difficult to get started. That’s just my guess though.

      So handshake definitely looks interesting in general, but unless it really takes off and becomes incredibly mainstream (which I’d love to see - I’m all for decentralized tech) I think it would only result in more negatives than positives.