Aperture Science, we do what we must because we can.
Aperture Science, we do what we must because we can.
Well, mine doubles as a convenient place to store my grilled cheese
Any reason you can’t use a locally hosted VPN? That would be my solution for something like this. Either use tailscale or use a wireguard VPN and a dynamic DNS service.
Later on I might consider adding some PiKVMs in order to be able to more safely reboot/troubleshoot/access BIOS.
deleted by creator
deleted by creator
deleted by creator
At least for desktop computers, you have the power switch on the back of the PSU. Assuming your PSU is actually ATX compliant and not some proprietary or otherwise non-standard bullshit.
That switch is inline with the AC input and will kill power to the device completely.
So, not graphic, just verbose.
pegging -v
I’m currently using this. It doesn’t appear to have a way to auto import a list of subscriptions. But it fits all of OPs other requests. It also has a jellyfin add on to import the videos into a library there with title and thumbnail.
They mention in the post that they have a list of official clients you can choose to donate to.
So, if there’s a client you use every day and that you love, consider finding it’s author in our list of official clients, and sending them a little something instead (or too).
It would probably be helpful if they included a link to that list in the post, though it is just one click from the projects homepage, and made it clearer that the list does include at least some subset of third-party clients. Though it would also be reasonable to infer that from the quote.
In either of those scenarios what power would the application developer have over the owner of the device? If the owner doesn’t like what the app is doing they’re free to remove it. There is no obligation to use that particular application to use the device for any purpose the owner sees fit.
AOSP is full open source mobile OS and uninstalling Google Chrome is as easy as uninstalling any other app and it can be replaced with any browser of the owners choice.
Similarly, SteamOS 3 is full Arch based Linux distro and uninstalling Steam is as easy as removing any package installed in Arch. Actually the immutable root file system does make it slightly more difficult, but it’s far from hard, and it can be replaced with a game launcher of the owners choice.
Proprietary software only becomes unethical when it is designed in a way that gives the device owner no option but to use it for their device to function as the owner desires.
Running SteamOS 3 on the Deck is like running AOSP on a phone with Google Chrome installed. You have an entirely open OS running a singular proprietary application.
In both cases you could pretty easily uninstall that app and replace it with something else.
I (obviously) hadn’t realized that. That’s awesome that valve has done that.
Though my point was more that there’s very little in SteamOS 3 that’s actually proprietary.
As for patching in drivers to a different distro for the Deck, for me that’s not a huge concern since I don’t own a Deck. I’d more so like to see Valve release SteamOS 3 for general use rather than only providing images for the Deck.
It looks like Bazzite is a good third-party option for that though, and I intend to try it out when I get home from traveling.
I wish an official SteamOS 3 existed with hardware support for anything other than the Deck.
Yeah, I’m pretty sure Steam and some of the drivers for valve developed hardware (like the controller) are the only closed source parts of SteamOS.
Wizards can definitely be femboys. Sir Ian McKellen still looks good in a dress.
The changed the driver model and broke compatibility with any device that didn’t get updated drivers. Which created a fuck-load of ewaste and unnecessary expenditure as people had to replace otherwise functional devices.
It also ran like absolute dog-shit even on PC’s that exceeded the recommended requirements by fairly significant margins.
And until Vista SP2 came out, it remained a buggy, broken, mess of an OS.
Also, given the promises Microsoft made about Project Longhorn (Vista’s cancelled predecessor) and the several years worth of delays Vista had Microsoft had no excuse for releasing an OS that was buggy, poorly optimized, and incompatible with most hardware more than two years old. Vista was supposed to release in 2003, it came out in 2007.
Windows 7 was what Vista should have been and what Windows should have stayed.