↓Skip to main content

HTTP/HTTPS/SSH/TCP tunnels as a service

·2 mins
  • Generally, it’s a nice idea for someone to implement and learn a few new things. I, on the other hand, can imagine how the application will look like end-to-end and I am fairly confident I’ll be able to build it. So, it won’t be challenging for me.
    • It may have been if I could do end-to-end encryption. However, I don’t know how to do that and I will keep looking for that.
  • The problem has been solved many times over already. (See this for a giant list of existing projects: there are projects in Go, Rust, Javascript, Python etc.) If I were bringing something new to the table, that’d be interesting but I can’t think of anything right now. (There probably isn’t too much scope anyway.)
  • One idea is to just build something, no matter what. However, I also think I needn’t pick the first idea that pops up in my head.
    • I can always come back to it in future if I want.
    • I should keep exploring. I remember reading somewhere about the 1:10:100 approach where you think of 100 ideas, try 10 and focus your attention on just 1 of those. This idea is probably one of the 90 which I won’t explore further.
    • I won’t learn anything new and won’t contribute anything new which isn’t already there. It’d be different if any of the two weren’t true.