I believe you can thank Taylor Hawkins for that. I know he was her tour drummer, but I'm pretty sure he wrote drum parts during his time with her, as well.
So that file can go anywhere you want, but ~/bin is a good spot (or ~/.bin if you like a tidy home folder). You can name it whatever you want, but I'd personally name it steam.sh. And then in the Buddy settings, use that file as your new Steam binary.
There's a host app that runs on the host machine alongside Sunshine that reads your Steam library, and the Deck plugin adds an icon on each game's banner on your Deck. When you click the icon, the plugin communicates with the host app and then automatically starts a Moonlight/Sunshine session that then starts up the game you were on. You only have to add one "app" to Sunshine and set up the MoonDeckBuddy app on the host, and then you have streaming for your entire library available.
I could go in-depth, but really, the best way I can describe my docker usage is as a simple and agnostic service manager. Let me explain.
Docker is a container system. A container is essentially an operating system installation in a box. It's not really a full installation, but it's close enough that understanding it like that is fine.
So what the service devs do is build a container (operating system image) with their service and all the required dependencies - and essentially nothing else (in order to keep the image as small as possible). A user can then use Docker to run this image on their system and have a running service in just a few terminal commands. It works the same across all distributions. So I can install whatever distro I need on the server for whatever purpose and not have to worry that it won't run my Docker services. This also means I can test services locally on my desktop without messing with my server environment. If it works on my local Docker, it will work on my server Docker.
There are a lot of other uses for it, like isolated development environments and testing applications using other Linux distro libraries, to name a couple, but again, I personally mostly just use it as a simple service manager.
tldr + eli5 - App devs said "works on my machine", so Docker lets them ship their machine.
I haven't had a deletion request come around yet, but I've had the pict-rs documentation in my back pocket just in case. My instance allows NSFW, so I made sure I knew how to do this before deploying.
I agree with the author, though, it definitely shouldn't be so hard to delete images. Hopefully the Lemmy devs tackle these issues quickly.
I like Ruby most of the time, but honestly, I'm not surprised at "sometimes" behavior from the language created by someone who, when asked for the formal definition of something in the language, said he's "not really a formal kind of guy."
My ISP says my IP is technically dynamic, but it hasn't changed once in the 6 years I've had their service. But that's for the best, since they're the only choice for symmetrical gigabit and their only option for static IPs is for business accounts.
So I continue to trust that they won't change it. Fingers crossed.
I find that I need to restart VSCode occasionally for reasons similar to this. I write C# daily, and sporadically VSCode will just completely lose track of all namespaces and everything is now a syntax error.
In addition to what's been mentioned, Bazzite also updates the kernel and graphics drivers more often than SteamOS, so yes, while things are slightly more likely to break every now and then, there are some decent performance gains to be had.
I love Bazzite, but I wish they would fix the no audio after wake on the OLED. I encountered it often while running the testing release, so I went back to SteamOS to wait for a stable release with the fix. Imagine my disappointment when they released a new stable version with the bug still present. :(
I believe you can thank Taylor Hawkins for that. I know he was her tour drummer, but I'm pretty sure he wrote drum parts during his time with her, as well.