• 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.

If the average user

Proceeds to describe a task average users never perform.

And no, you having been a smart child doesn’t excuse you being an obtuse adult.

It’s not about business optimization, it’s about not having to defer to someone’s knowledge from the position of power.

AI bubble makes so much sense when you start looking at it this way.

I can often implement 80% of a new feature without ever running the code.

I really love how they then go and invent their own TDD acronym to justify this. Types are proofs, and they replace a whole category of borderline superficial tests with useful assertions, but claiming that you implement a <random number>% of a feature when you haven’t once verified it is… a reason I regularly cuss at code and remain employable. Keep it up.

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.

Considering that git doesn’t need federation, and email is the grandfather of federation, sourcehut has a working version of it this very moment.