What might simplify your thinking about this is called “Semantic Versioning”.

You have a big codebase of all kinds of features, but at a certain time you want to release it to be able to differentiate between a point in time and release number so you can tell when a regression happens and address it.

Proton is released by version to be able to see this exact thing. They keep all the old versions available for users because they know that not every single point release will work for all games, and there will be regressions.

This allows users to be able to identify a stable working version of Proton for a specific game, and stick to it. If you try to upgrade for a newer release for some reason and find a problem, you can always go back to the previous working version and know for certain it will work without issues.

For your specific scenario, just check ProtonDB for games and see if people have posted tweaks and config combos for a specific game. Great resource for this exact reason.

It’s a dumbass AI-powered recommendation engine with an awful GUI. That’s about it.

As far as it being malicious, that’s really up to you.

It starts with the hardware first. You started well with tuning your CPU/MEM frequency settings, but that matters less if you’re running giant PSUs (or redundant), more drives than you need, and a huge number of peripherals.

Get a cheap outlet monitor to see what your power draw is and track it at the wall. I just got these cheap Emporia ones. I’m sure there’s more reputable ones out there.

Don’t go crazy with your networking solution if you don’t need them. PoE switches draw tons of power even when idle, and a 24-port switch is a huge draw if you’re only using 3 of them.

Consider getting a power efficient NAS box for backend storage, and low power Minipc for frontend serving instead of using a power hungry machine for all your network apps.

You can dive deeper into any angle thing, but these are the basics.

Well it’s the default, so something broke on your end.

1. It’s not a detection problem with the controller because it works in Steam
2. It’s not a Steam problem because steam-input seems to work fine.

Joystick calibration: depended what desktop you’re using. Just search up your DE and joystick calibration ". Might solve your issue.

Again: specs weren’t even posted before my comment, as I’ve said before.

There’s only so much reliability you can build into a simple home setup without it being a major loss on investment. In a datacenter situation, you’d have fault tolerance on all the network ingress: load balancers, bonded interfaces, SDWAN configurations…etc.

Unless you want 3 of everything you own, just do the basics, OR I guess consider hosting it elsewhere 🤣

Focus more on why the service is going down, and solve for that. Make it reliable by restarting automatically in the face of failures. A Reverse Proxy should be dead simple, and not change states between restarts, so it shouldn’t be dying in the first place. Having it restart on failures should be simple and reliable.

That behavior in Steam is normal. That’s the steam-input library mapping your controller for use in Big Picture Mode before starting a game. That means your OS detects the controller.

Are you using this on USB or Bluetooth? Did you get the native joystick calibration?

Hmmm, it does seem they’ve finally raised prices. Well that’s a huge bummer.

I can’t say the 3 options you posted are really good deals, but maybe that’s just the market in Australia. I’d check to see what the max RAM in those are and upgrade to at least 16GB though. It should still be cheap for non DDR5.

Anything can be a “server” in your use-case. Something low power at idle will not cost an arm and a leg to run, and you can always upgrade later if you need more.

Check the Minisforum refurb store and see what you can get for under $150.

Care to reference what you’re talking about?

Newp

Specs weren’t even posted when I commented, and you came back to try and H&M this comment 😂😂😂

Something 10 years old wouldn’t even have lanes available for that to work in any meaningful way at all.

Whatchu smoking, son??

It’s almost never worth it. 10 years have passed, everything uses magnitudes less power, and the bus on that thing wouldn’t even matter if you slapped something like an SSD into the PCIE (it won’t even have a slot for that).

Just recycle it unless you have a specific need for it.

1. dig , learn it, love it
2. Use a phone or other device outside your network to compare results from #1

They do no such thing.

The first link explains the protocol.

The second explains WHY one would refer to client and server with regards to Wireguard.

My point ties both together to explain why people would use client and server with regards to the protocol itself, and a common configuration where this would be necessary for clarification. Ties both of them together, and makes my point from my original comment, which also refers to OP’s comment.

I’m not digging you, just illustrating a correction so you’re not running around misinformed.

It wasn’t clear where OP was trying to make a point, just that the same host would be running running Wireguard for some reason, which one would assume means virtualization of some sort, meaning the host machine is the primary hub/server.

Uhhh, nooooo. Why are all these new kids all in these threads saying this crazy uninformed stuff lately? 🤣

https://www.wireguard.com/protocol/ https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/configuring_and_managing_networking/setting-up-a-wireguard-vpn

And, in fact, for those of us that have been doing this a long time, anything with a control point or protocol always refers to said control point as the server in a PTP connection sense.

In this case, a centralized VPN routing node that connects like a Hub and Spoke is the server. Everything else is a client of that server because they can’t independently do much else in this configuration.

Uhhhh…that is…not how you do that. Especially if you’re describing routing out from a container to an edge device and back into your host machine instead of using bridged network or another virtual router on the host.

Like if you absolutely had to have a segmented network between hosts a la datacenter/cloud, you’d still create a virtual fabric or SDLAN/WAN to connect them, and that’s like going WAY out of your way.

Wireguard for this purpose makes even less sense.

Why would you run a WG Client and WG Server on the same host? Am I reading that second mark wrong?