this post was submitted on 28 Jun 2023
304 points (98.4% liked)

Asklemmy

43950 readers
558 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments

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 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.