I dunno about all that. The state is pretty particular about these things.

That looks awesome unfortunately this is so a client can connect to a state database so it's not applicable here :(

I see what your saying. We were talking past each other a bit

I'm talking about automating the second part.

For example if I wanted to host my website or relay over hyperdht then I would use holesail --live 80

However anyone who wants to access it would have to bind it to localhost with a port they choose

That's fine if they are accessing it only once. But they would have to bind the port every time ( every reboot )

So that's what the HTTP proxy is for. It allows apps ( like browsers ) to proxy their traffic through a local server

Which means the HTTP proxy can intercept their requests and bind the ports automatically then forward the traffic through hyperdht to the correct node

Yes however i don't think most apps are going to integrate the binary. Just like how most apps don't come with a tor binary

I'm not saying holesails approach with using localhost won't work. Just that if we where able to build a proxy for holesail then any apps that work with tor would immediately work with hyperdht

Yes, but you have to manually connect the tunnels. Also apps have to explicitly integrate hyperdht or holesail in order to connect

If we where able to build a SOCKS5 or HTTP proxy for hyperdht then any app ( mobile apps, desktop browsers, etc ) could access hyper services since most already support proxies for Tor onion services

Life hack: you can control your attention, your opinions, and your feelings.

According to Mathias & Paolo the combo of C & JS that they use is actually much friendlier in terms of resource requirements if they can get beyond some of the ways in which they have to work around modern OS limitations. They are talking about building a pear phone too.

While there are a lot of caching improvements that need to be made Keet is actually really impressive even in its current form & it works fine on mobile. Holesail (Liveport) which also uses Pear appears to be very lightweight & reliable.

as it is right now, holesail is essentially a server, so it takes implementation on both ends.

you are wanting the zeus app to create the tunnel from the outside without any server side implementation?

So this app is using bare-kit to run a bundled version of app.js with nodejs that has access to the network interface so it can make TCP connections?

I'm trying to figure out how the JavaScript (hypercore) part of of this app is able to use TCP sockets since most of the time JavaScript is sandboxed

Also curious whats the reasoning for keeping the Android holesail app closed source when all the other holesail packages and tools where open-source from day 1?

#asknostr does anyone have a link to the holesail android app source code? I want to see how they got hyperdht running on android

Yes, along the line we intend to make money.

Soon when I post about the basic security issues and carelessness I discovered with the current port forwarding / static IP model, it will makes things clear why I am so admadent on the security part.

My observation and personal opinion.

IPv6 and NOSTR share a similar issue.

There is no financial incentive to push adoption of a protocol.

There is incentive to push the adoption of a solution, even a FOSS solution, as there is a commercial insensitive to do so.

Even with FOSS, there is potential sponsorship or the commercial opportunities arising from adoption of your product / service. nostr:note12fax0wzftn05759v366wn2dkwxxyxj4nxc0r3fluqs3adjgr4essc6rjv5

I will watch with interest the development of holesail. I currently use Tailscale and it works great, but I am aware of its limitations.

Good luck 🤞

Yes, as I said security is a separate, but equally important consideration, but we do have better options available today than we used to and more hardware and software compute power to deal with it.

I was an IP architect in a former life 1989 - 2002, so much more knowledgable about this than security, but I have some fundamental understanding of security and the current state of the technology and the opportunities available within this arena.

I will steer away from discussing security in detail as I have less knowledge of this area.

It works via the DHT, like BitTorrent. Basically it’s kinda like a broadcast network hunting for the other user.

So let’s say I connect to 8 random peers on my mobile. Then my hosting machine connects to 8 random peers. When we start up an instance we announce to our peers what our keys are and they add it to their DHT (big hash table of peers basically).

Then when I scan the QR of my hosting machine, I ping out to my nearest 8 peers for anyone who has seen the hosting key. If we share no peers in common, then they pass it on to the next set of peers that they are connected to, then through “6 degrees of Kevin Bacon” we eventually cross on a peer that has heard my request, and also heard the hosting machine’s key earlier. (This might realistically only need one or two hops, maybe the DHT of my nearest node already has the update from the host, but not necessary)

Then when I find my host via mobile (this is where I’m less certain about specifics) then both machines do a “hole punching” method where the host and the mobile both try to establish connections from either direction using any available port. Again, a kind of “guess and check” method not so unlike finding a peer with random broadcasting. Then the connection is established, keys exchanged, and viola, P2P direct encrypted connection for whatever you want to do.

There are probably more specifics that I’m missing, but as I understand it, this is the general idea. Hope this helps.

Agreed, I am discussing an ideology, not current reality.