Also since this is custom DNS resolution I dont think we need to convert to bech32 🤔
Well jokes on me because this code actually works, I just never finished it enough to fully test it
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
Discussion
Technically no, although there is no way to know if browsers or other apps have restrictions on domain length. could be even some libraries restrict it to 63 char
Even Tor .onion and I2P domains are encoded to be less than 63 char