publiush's comments

This is cool! This is an extension version of the federalist [1] project I was working on earlier! This makes using federalist so much easier!

Way to go! Also, this is really cool that you did this!

[1] https://news.ycombinator.com/item?id=29513547

I think that there is a bit of a disconnect in those that work on systemd. I agree that a revert makes sense in this case. Most people who will suffer real catastrophic breakage are also NOT usually using rolling-release or bleeding edge systems. This does, in fact, give a small window of time to issue this revert without causing massive harm. I also don't really see much toxicity in this discussion, instead just people arguing points.

As per the earlier drama with some of the Handshake admins and developers trying to bully developers out, I have linked up with some of the other developers who have experienced the same thing from them. We have setup a new discord server (it's brand new).

Looking forward to chatting there!

I actually made a system called federalist [1] that uses mutable torrents. Hope you like it!

[1] https://github.com/publiusfederalist/federalist

I e-mailed him about it days ago.

By the way, are you familiar with Zooko's triangle?

It's been an on-going conversation that's been going on a few days.

If we're talking about the same person, he was the only one who actually encouraged what I was doing and even gave me the idea for Zooko.

However, the admins on their discord, were less than encouraging.

EDIT: As per the same person's advice, I'm going to start a new discord community without the toxicity.

I've decided to begin my own community. Those toxic admins can't control the blockchain.

I also just pushed zooko message [1]. This allows you to encrypt and decrypt messages using only your handshake name.

[1] https://github.com/publiusfederalist/zooko-msg

This is definitely a little bit of a different medium to twitter and likely the '1 post per block' limitation is great in this case. Think before you Zooko, as it's permanent and forever.

[Submission Statement]: Right now, there are a lot of sentiments as it relates to de-platforming on various platforms. I was able to implement a completely decentralized twitter-like microblogging system on top of a blockchain, so this inherits the immutability from the chain with it. Since it uses Handshake, the posts are also name-verified.

I named it in honor of Zooko, one of the original Cypherpunks. Cypherpunks write code.

Onward.

Right now it's in POC form, so it's just using a simple 'zooko:' prepend to identify Zooko messages (Zookos). Since it's completely decentralized on chain, it actually doesn't need ActivityPub or XMPP for help (all you need is the ability to download the chain).

Again, this is a security issue and doesn't in any way reduce the proven efficacy of cryptography. It's pedantic at best, and I am going to stop replying to your comments.

Happy new year.

I agree that the intentions were pure. That said, this isn't a product, but instead, a project with a specific goal of improving internet security by showcasing concepts to the HN community. The discussion within the thread, I think, is indication that it is helping to inch closer to that goal as more users on HN are made aware of the beneficial tools cryptography with Handshake provides.

> Are you implying people should feel free to create and obtain a new name on the blockchain using any random website? Also I do not see the list of popular GH names in the link you provided.

The popular names are in the names folder.

I wouldn't recommend obtaining a new name from any random website. I don't think I did so. I'm going to avoid continuing this thread as gaslighting isn't usually something one would wish to engage in, obviously on the receiving end, but on the creator's end too.

I hope you are able to find peace in the next year.

Happy new year to you.

The instructions you pasted are for claiming a name that was pre-reserved when Handshake launched [1]. This is different from creating and obtaining a new name on the blockchain.

[1] https://github.com/handshake-org/hs-names

This is solved with key management and security as opposed to with the fact on whether or not the technology has merit. Now, we're really moving goalposts. ;)

It's more of using specialized, purpose driven applications vs using a generalized swiss army knife of epic proportions.

Handshake was purpose built to work with traditional DNS while ENS is something entirely different. I think that's why Handshake is gaining more adoption in the traditional DNS sector as well, but whatever the case, I've opted to work with this technology based on a number of factors:

1. The ENS project is great for creating human readable Ethereum wallets. However, it doesn't seem that it was initially suited to be used for DNS and that this was later patched on.

2. ENS is centrally controlled by a federation of key holders [1] while Handshake is decentralzed.

3. In Handshake, you truly own the name.

4. With blockchain already inheriting many inefficiencies when compared to more traditional systems, ethereum, while very cool, tries to be too much and the bloat has led to extreme fees for interacting with the blockchain.

That being said, I'm keeping my eye out on all of the naming projects. It's something I'm very interested in.

[1] https://docs.ens.domains/frequently-asked-questions

This isn't a marketing message/post.

This is a Hacker project to explore improved ways of doing things with the new primitives of our collective technology base. In this case, owning your own identity with a decentralized identity system.

I think marketing posts are better suited for another forum, no?

I apologize for that. There was an assumption that most people were aware of the Handshake Naming system [1]. Handshake is a naming blockchain that's recently been gaining adoption quickly (Namecheap [2]) (Opera Browser [3]). Using this, you can control your name, which is your identity, on the internet. There's a lot of other cool benefits, but as it pertains to this project, it's the names, cryptographic proof of ownership of said names, and the cryptographic provability that the messages were written by the owners of said name.

There are many ways to get Handshake names, but the easiest ways are to use Bob (non custodial) [4] or Namebase (custodial) [5].

[1] https://handshake.org/

[2] https://www.reddit.com/r/handshake/comments/pt55vb/namecheap...

[3] https://twitter.com/opera/status/1476841607005622273

[4] https://github.com/kyokan/bob-wallet

[5] https://namebase.io