Re:Show HN: Lohost – Distributed, decentralized, anonymized ...
by gmarland on Thursday January 06, 2022 @01:19PM
(#29827500)
This was a project I worked on over the Christmas break. It may not come through in the video but this is serving the webite straight from your computer, not backdoor uploading files.
Re:Show HN: Lohost – Distributed, decentralized, anonymized ...
by gmarland on Friday January 07, 2022 @02:56AM
(#29836302)
I can definitely see why you would say that! ngrok uses tunnels to connect to your computer, this uses websockets to load and serve the requested documents.
The reason for this is that I wanted this to be a distributed solution. You can shard up the different routes across as many computers as you like and the front end will route and patchwork it together at the front end.
Along with that you can run the client over any number of computers and they will act as backups for eachother. So, if you turn off one computer, one of the others will pick up the slack.
I'm not super familar with ngrok, but if it does all that then I guess, beyond the technology, there isn't a massive amount of difference :)
Re:Show HN: Lohost – Distributed, decentralized, anonymized ...
by itake on Friday January 07, 2022 @10:48AM
(#29840458)
ngrok doesn't have the distributed routing you're talking about, but (b/c its a tunnel?) it can forward non-http traffic (which I use to host a local proxy service to MITM debug mobile apps).
Re:Show HN: Lohost – Distributed, decentralized, anonymized ...
by gmarland on Friday January 07, 2022 @01:58PM
(#29843207)
the non http traffic is really really powerful. I feel like currently lohost is limited in serving static content too. its definitely something I would like to improve on in the future!
Here's a video showing it in action: https://youtu.be/DaK4d4Belwk
It's really just a fun project I wrote to see if it was possible.
Just so you know, I was able to build this under Arch Linux with dotnet-sdk 6.0.0.sdk100-2:
That's also good to know! I'll try and put together a Linux installer too :)
The reason for this is that I wanted this to be a distributed solution. You can shard up the different routes across as many computers as you like and the front end will route and patchwork it together at the front end.
Along with that you can run the client over any number of computers and they will act as backups for eachother. So, if you turn off one computer, one of the others will pick up the slack.
I'm not super familar with ngrok, but if it does all that then I guess, beyond the technology, there isn't a massive amount of difference :)