• ssh to remote, forwarding some remote port to your local ssh port (-R)
• ssh from remote through the exposed port, starting socks proxy in the process (-D)
• use socks proxy explicitly or find some tool that can route the traffic into it

Similar approach can be used to establish VPN tunnel with no encryption (ssh already provides that), routing everything but your ssh connection through it.

• ssh to remote, reverse forwarding your VPN-over-tcp server’s listening port
• establish vpn connection on remote, route everything but your ssh connection through the newly established interface

It will be wasteful, but it will work.

Good point.

Gl.iNet is a great value router, but if you want to do anything really interesting, it won’t do.

I have Slate AX chugging along, and have been eyeing teklager boxes to do actual routing, with slate as an access point.

Same weird non-sequiturs chain that foobar2000 author uses.

They could’ve honestly said “I don’t wanna”, and that would be the end of it.

Please correct me if I’m wrong, but doesn’t this allow one to represent virtually any resource as a mail inbox/outbox with access through a generic mail app?

I’m working with a specialized healthcare company right now, and this looks like a way to represent patient treatments data as an intuitive timeline of messages. With a local offline cache in case of outages. Security of local workstations is a weak point of course, but when is it not…

Sorry, but you don’t get to claim groupthink while ignoring state of Apache when Nginx got released.

Apache was a mess of modules with confusing documentation, an arsenal of foot guns, and generally a PITA to deal with. Nginx was simpler, more performant, and didn’t have the extra complexity that Apache was failing to manage.

My personal first encounter was about hosting PHP applications in a multiuser environment, and god damn was nginx a better tool.

Apache caught up in a few years, but by then people were already solving different problems. Would nginx arrive merely a year later, it would get lost to history, but it arrived exactly when everyone was fed up with Apache just the right amount.

Nowadays, when people choose a web server, they choose one they are comfortable with. With both httpds being mature, that’s the strongest objective factor to influence the choice. It’s not groupthink, it’s a consequence of concrete events.

Turns out, I do need therapy.

By becoming a CTO and having an early retirement. Or not at all.

Either by making it segfault or you don’t.

I got a whole software developer career going out of my attempts to exit vim.