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

Check this out, guys, It's the coolest thing by far I have seen build-on holesail.

nostr:note10em22c0rr0cjwd5ndy7rl76u8m2z6my2t7y0qpyfhvv5crg4g9nsqhkx03

Reply to this note

Please Login to reply.

Discussion

ELI5?

Explain it like I’m 5.

I want to hear if this is what I actually think and exactly how you’d interact with it, and also that would probably help people scrolling past it too.

This is a web front end tunnel that talks to a peer swarm in the background basically like a proxy server? Am I getting that right?

Basically, it starts a SOCKS5 proxy in the background that will automatically handle connecting with holesail/hyperdht connections, you wont have to connect to a key every time in terminal, the proxy will automatically do it on the go for any app for browser.

For example, doing .hyper in the browser will load a holesail connection from .

It is pretty sick, nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr I see it is MIT, I might add it to holesail someday

Please feel free to add it to holesail or copy and take over the project. I'm not going to have time to add features or maintain it

My goal was to build a proof of concept that would allow any app to connect to hyper nodes without needing to be written in NodeJS or integrating hyperdht

Also there might be a way to roll this into a mobile app like Orbot. since I'm pretty sure Orbot is doing the same thing on mobile

nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev SOCKS5 is what every app (browser, bitcoin wallet, etc...) use to interface with Tor. they don't directly talk to the Tor network but instead talk through a proxy that in turn talks to Tor

This SOCKS5 proxy allows any app that supports routing traffic through proxies to connect to .hyper domains, which are just the pubkey key of any hyper node

Thanks, I was also thinking something like Orbot for mobile devices. This is a solid suggestion and will improve holesail a lot.

Orbot!