Replying to Avatar hzrd149

Well jokes on me because this code actually works, I just never finished it enough to fully test it

nostr:nevent1qvzqqqqqqypzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyghwumn8ghj7mn0wd68ytnhd9hx2tcprfmhxue69uhkummnw3ezuargv4ekzmt9vdshgtnfduhsqgxprey4pqkdfqf90a0nyz2vls6x8ae6pt3k8rmf7dhkhmrwd7clsy0z7jdy

So without further ado I present to you Hyper SOCKS5 Proxy

This is a SOCKS v5 proxy server that can automatically connect to HyperDHT node and Holesail servers. This is cool because it lets any application that already supports SOCKS5 or HTTP proxies ( mainly web browsers ) to connect to hyper nodes

Let me show you can example

First we have to startup a http server and use holesail to make it available on hyper

Next, on a different machine we can connect to it using hyper-socks5-proxy and configure FireFox to use the proxy

https://v.nostr.build/3bcbJMX7XbaWMdfA.mp4

NOTE: besides this example ( tested on my LAN ) I have not tested anything else. but in theory it should be possible to host relays over hyperdht

The reason I had to convert the hex connection string ( hyperdht pubkey ) into a bech32 address was because the maximum length for a domain name is 63 characters. and the connection string is 64...

But encoding it to bech32 with a 4 character prefix makes it only 58. Its identical to how nostr npubs are encoded

Anyways here are the links to the code if you want to play around with it

https://github.com/hzrd149/hyper-address ( https://hzrd149.github.io/hyper-address/ )

https://github.com/hzrd149/hyper-socks5-proxy

https://github.com/hzrd149/hyper-http-proxy

This is also available on my custom umbrel app store. If for some crazy reason you want to run my untested code on your lightning node ( please don't )

https://github.com/hzrd149/umbrel-community-app-store

#pear #hyperdht #holesail #proxy #socks5

I watched the video but don't quite understand what's going on.

So you ended up with your browser being configured to use a proxy that gave it DNS resolution for .hyper URLs? How are these routed? The holepunch people are loud about it being P2P with no middle man but how do packages actually travel from the client to the server and back? I see you are using no ssl. Is your proxy encrypting with the .hyper URL's public key or something?

Reply to this note

Please Login to reply.

Discussion

In short, I don't know.

I only have a vague idea of how hypercore works. I've looked at some of code but I don't know enough about IP and networking to fully understand it

It does seem to use encryption when connecting to another hypercore node and it does seem to be able to make a direct P2P connection to another node ( at least a lot more than WebRTC can )

But I doubt this as private as Tor or I2P since they seem to be using NAT and holepunching to connect the machines. which probably exposes your IP address to other the peer

I simply built this on top of the `holesail` and `hyperdht` packages that seem to work really well from my testing 😀

with hyperswarm A establishes a connection to B using some dht nodes to help punch holes, then A and B negotiate a noise channel, from there you can send and receive anything, encrypted TCP

it's not pure p2p because you need someone to help with the holepunch and I imagine currently these helpful dht nodes are ran by the people behind the project

It is pure P2P, the nodes do not help in holepunching but to discover first few peers, a node is just a known peer. Anyone can become a node.

You need to look into Kademliya algorithem to understand how it all works.

I think you might be too dumb to continue this conversation, but holepunching requires a third party by definition so Ill leave it up to you to tell me who does it in this case

Perhaps you are too smart to understand, but I will try:

Unlike traditional and common holepunching methods, there is no requirement of a third party STUN server in Kademliya.

The peers themselves act as a stun themselves(kind of) and help in holepunching.

Check out Kademliya algorithem, it is truly peer to peer, there are no central nodes.