To do multi-user correctly it will take them rearchitecting a few things. Here's what I'd image is currently required:
Game artifacts would need to move into a common area to prevent duplication (or utilize a COW filesystem)
Game compat data will need to move under the user home directory and not immediately live with the other artifacts like it does now
A new login screen will need to be created that actually switches between system users (will need to use some password separate from an account password for offline use)
Some extra state tracking may be useful. Switching back and forth between desktop and game mode will prompt the account switch menu but some data can be stored to make it remember who the current active user is...
Most of the tools to do this are already present but it'll take some time for someone to coordinate it and the fact that the product has made it this far without such a feature speaks to it's demand. Hopefully someone takes a look at it though because it really shouldn't be that bad.
Works pretty well, but you may find you have to set up multiple output entries and tags to filter out the useful parts of a post. That and html entries sometimes don't get parsed correctly so you'll end up with tags in what should be a parsed content string.
I don't know man, I've always liked the idea of a project outliving me. Though for the sanity of future engineers I hope that is not the case. Today's solutions are usually just tomorrow's problems.
The only place I've seen ruby used extensively is in environments with a lot of regular expressions and string manipulation. Still not entirely sure why I've only seen it used there. The regex tools in ruby are nice but they aren't nice enough to justify a language switch in my opinion...
Part of the problem is the game of telephone drops the cell chemistry related to the method almost immediately leading to general consumers applying it as a blanket rule for all batteries
Yep. Battery chemistry is a real pain in the ass. Every few years someone spins a wheel and determines the next big thing that everyone needs to do to prevent batteries from dying early. For a while people were told full cycles were healthy for avoiding cell memory. Now more sporadic cycles are being peddled.
Use the device as you need it. If you complete a full cycle, cool; if not, that's fine. Just don't let the damn thing completely die and don't keep it permanently on charge. Those are the common things most people do on accident that can really screw up a cell.
The most useful quote to those familiar with the linux boot process:
“An attacker would need to be able to coerce a system into booting from HTTP if it's not already doing so, and either be in a position to run the HTTP server in question or MITM traffic to it,” Matthew Garrett, a security developer and one of the original shim authors, wrote in an online interview. “An attacker (physically present or who has already compromised root on the system) could use this to subvert secure boot (add a new boot entry to a server they control, compromise shim, execute arbitrary code).”
If an attack needs root then it doesn't matter. Your box is toast anyway. If you're using http boot without verification then you should have seen a MITM attack coming.
We use your Personal Information for a number of purposes, which may include the following:
[snip]
To display advertisements to you.
To manage our Affiliate marketing program.
There will be times when we may need to disclose your Personal Information to third parties. We may disclose your Personal Information to:
[snip]
Third-party service providers and partners who assist us in the provision of the Services and Website, for example, (a) those who support delivery of or provide certain features in connection with the Services and Website (e.g. Stripe, a payment services provider; Sendgrid, an email delivery service; HubSpot, a CRM platform, and Sentry, a crash reporting platform); (b) providers of analytics and measurement services (e.g. Google Analytics, ProfitWell etc.); (c) providers of technical infrastructure services (e.g. Microsoft Azure, Google Cloud, and Amazon AWS); (d) providers of customer support services (e.g. Zendesk); (e) those who facilitate conduct of surveys (e.g. Hotjar); (f) those who help to advertise, market or promote our Services and Website (e.g. Mautic, Facebook Ads, Google Ads, Linkedin Ads, Reddit Ads, and Microsoft Ads);
The above leans heavily on the idea that the political spectrum is a loop and swaying to either side too heavily incurs bias that eventually warps the initial intention
I'm not seeing this on Arch Linux right now so it may be a Deck specific regression