JoeCoT

If a wrestler’s really well liked it can be really hard to turn them heel, or even stay heel if they were heels in the first place. MJF and Swerve were basically forced into stopping being heels. Even the tradition of assaulting Tony Schiavone only gets boos for a couple weeks.

If you follow pro wrestling, if you go to small independent shows, there is almost always one guy in the front row, with a WWE belt, taunting wrestlers. Because you see, those wrestlers are nothing, and no matter how cool they are, whether or not they win the match, whether they win that indie promotion’s title, they’ll never be the WWE champion. And, sure, I guess? But not everyone cares about that. And even if the wrestler isn’t going to be WWE champ, they’re far closer than that guy is.

Common in the hobby of tabletop RPGs, or especially Larping, is Main Character Syndrome. People think that their character is the most important thing in existence. If things don’t go their way, they complain, claim cheating or bias. If the larp is setup for it they ask for appeals for the decisions and investigations against the person who wronged their character. They spend more time just arguing over what great things should happen (or what bad things should not happen) to their character than they actually do just … playing the game.

Harrison Ford and Ke Huy Quan (Short Round) in Temple of Dune. I want a little boy as an action hero while Harrison Ford provides occasional support.

I don’t know of a good way to route other application’s traffic through the VPN container with them being in docker containers, unless you use some intermediary setup. That’s why I have socks proxies routed through the VPN, so I can selectively put traffic through it. If the app supports a socks proxy you could do it that way. At the least you could use Proxychains to do so if the program does TCP networking.

So it’s always going to be used for technical things, but not necessarily development things. I use it for both.

For my home server setup I have docker setup like this:

1. A VPN docker container
2. A transmission (bittorrent client) container, using the VPN’s network
3. An nginx (web server) container, which provides access to the transmission container
4. A 3proxy socks proxy container, using the VPN’s network
5. A tor client container
6. A 3proxy socks proxy container, using the tor container’s network

Usually it’s pretty hard to say “these specific programs and only these should run over my VPN”. Docker makes that easy. I can just attach containers to the same network as my VPN container, and their traffic will all go over the VPN. And then with my socks proxies I can selectively put my browser traffic over either the VPN or Tor, using extensions like FoxyProxy. I watch wrestling through my vpn because it’s cheaper overseas and has better streaming options, so I have those specific sites set to route through my VPN socks proxy. And I have all onion links set to go through my Tor proxy.