• 0 Posts
  • 207 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle


  • You’re arguing two different points here. “A VPN can act as a proxy” and “A VPN that only acts as a proxy is no longer a VPN”. I agree with the former and disagree with the latter.

    A “real” host-to-network VPN could be used as a proxy by just setting your default route through it, just like a simple host-to-host VPN could be NOT a proxy by only allowing internal IPs over the link. Would the latter example stop being a VPN if you add a default route going from one host to the other?


  • Fundamentally, a host-to-host VPN is still a VPN. It creates an encapsulated L2/L3 link between two points over another network. The number of hosts on either end doesn’t change that. Each end still has its own own interface address, subnet, etcetera. You could use the exact same VPN config for both a host-to-host and host-to-site VPN simply by making one of the hosts a router.

    I see your point about advocating for other methods where appropriate (although personally I prefer VPNs) but I think that gatekeeping the word “VPN” is silly.


  • “It has effectively the same function as a proxy” isn’t the same thing as “it’s not actually a VPN”.

    One could argue you’re not really using the tech to its fullest advantage, but the underlying tech is still a VPN. It’s just a VPN that’s being used as a proxy. You’re still using the same VPN protocols that could be used in production for conventional site-to-site or host-to-network VPN configurations.

    Regardless, you’re the one who brought up commercial VPNs; when using OpenVPN to create a tunnel between a VPS and home server(s), it seems like it’s being used exactly to “create private communication between multiple clients”. Even by your definition that should be a VPN, right?





  • The idea is that it isn’t just operating the vending machine itself, it’s operating the entire vending machine business. It decides what to stock and what price to charge based on market trends and/or user feedback.

    It’s a stress test for LLM autonomy. Obviously a vending machine doesn’t need this level of autonomy, you usually just stock it with the same thing every time. But a vending machine works as a very simple “business” that can be simulated without much stakes, and it shows how LLM agents behave when left to operate on their own like this, and can be used to test guardrails in the field.



  • Wine literally stands for “WINE Is Not an Emulator”.

    That said, Proton is pretty transparent, you can just install any game off Steam right now and it’ll work 9 times out of 10 without you noticing that you’re using wine. I often can’t tell if I’m using proton or not and get surprised when I go into the game files for one reason or another expecting proton and am surprised to find a native Linux build. There has even been at least one time I’ve switched from a native Linux build to Proton because it ran better, and it was just one toggle.

    Why the resistance to wine? Did you have an issue while using it, or is it the principle of using a compatibility layer?



  • If there’s a port you want accessible from the host/other containers but not beyond the host, consider using the expose directive instead of ports. As an added bonus, you don’t need to come up with arbitrary ports to assign on the host for every container with a shared port.

    IMO it’s more intuitive to connect to a service via container_name:443 instead of localhost:8443