I guess this depends on how much of the fundaments they want to lay before public release.

Reply to this note

Please Login to reply.

Discussion

For example, the Keet UX for now is not very good, so I can't even recommend it to anyone except early tech adopters. So if I was them (hole punch team), I would make it bit better before releasing the code. Building stuff that don't require servers have a lot unique challenges, so it takes time.

For now I'm just watching and cheering them. Idea is very good, but pending execution.

There are also some privacy issues as well, that needs to be resolved. All communication is encrypted, but because its p2p, there is a suspicion that peers leak their IPs to each other. On the other hand, privacy on Nostr is total downer. Still a lot of work in this space needs to be done.

I understand, still I think a good way to improve code is to open up.

If there are vulnerabilities, there's not much to hack at an alpha stage, so it would be a good trade off to open source.

From what I heard, Paolo is doing a lot operationally, maybe he's busy.

I just remember he said they plan open source it. I agree with you, sooner you do it, better, at least from security stand point. But I guess there are trade offs. Dunno. Observing the project for now...

I am too. Aside keet are there any apps using holepunch?

They recently released Node.js replacement that can be used in this no-server model. It's called Bare.

https://pears.com/news/introducing-bare-actually-run-javascript-everywhere/

Just read about it, I didn't know about it. Thanks!