thurstylark

Finally time to update manjarno.snorlax.sh again -_-

Oh my god, thank you so much for this. I have always had the hardest time finding these exact same requirements, and this is perfect. All metal construction and coexisting with keys has always been a priority for me, but it seems like everyone is inexplicably fine with copping out by just dangling their data on this flimsy little string tied to a brittle plastic case and I cannot understand it.

I'm not currently looking for one at this exact moment, but I will be returning here when I am. You're doing the lord's work out here!

There is a title he currently holds, and which deserves a higher rank by mere exclusivity's sake...

Impeached Former President

Some extra fun details from the staff discussions around this: Valve is not interested in control of the distro, but are mainly interested in funding work on projects that are chosen by Arch staff, and are already things that Arch staff wants to implement. The projects chosen are indeed things that Valve also want to be part of the distro's infrastructure, but the process has been totally in the hands of Arch staff.

I gotta say, it's been really cool to see Valve go through the process of considering OSS as not just a useful tool or worthwhile target, but as a robust collaborator.

First, they build and maintain their client on Linux, and build their games to run natively on Linux, learning that things aren't actually as difficult as it's commonly made out to be, and the things that are more difficult than they need to be can be fixed by working with and contributing to the existing community.

Then they consider building their own hardware, but try the half-way approach of building SteamOS on top of Debian, and depending on existing hardware vendors to build machines with SteamOS in mind, learning that there's a lot of unnecessary complexity around both of those approaches to that goal.

Then they learn how to develop and build 1st party hardware with the SteamLink and Steam Controller.

Then they put the lessons from the Steam Machine project into practice by dumping loads of time and effort into Proton, knowing that they won't have the market unless they can get Windows games to run on Linux in a reliable and seamless way.

Then they put all that knowledge and effort together to do the impossible: unite PC gamers of both Windows and Linux flavors under the banner of the SteamDeck, a fully gaming-focused, high-quality, and owner-friendly piece of kit that kicks so much ass that it single-handedly pulls a whole category of PC hardware out of obsurity and into the mainstream.

And what do they do with that success? Literally pay it forward by funding work on the free software that forms the plinth that their success stands upon.

Good on Valve.

It's not about actually caring about making minors safer on their platform, or caring about giving tools to guardians to help keep minors safer on their platform.

It is about having something to point to the next time Meta is called in front of a congressional subcommittee to discuss proposed regulations. Look, we did positive things to our platform in the name of protecting minors, and we did it voluntarily, despite what losses we saw in that demographic! We definitely can (and so totally do) put the control of those protections in the hands of parents, where it belongs! We don't need to be regulated, because we're doing it ourselves already!

I think it would be naive to think that they don't know this already. Not to say that I think you're making that argument, but that I think the losses are calculated against the benefit of the appearance of care that this move affords them. Sure, these new restrictions and tooling means that some parents will be more willing to allow their teens to engage with the platform, but there's no way that will outweigh the active user reduction in the targeted age range.

The real benefit is looking like they're doing stuff in a positive direction in the context of minors. I'm definitely expecting them to point at this move (and its voluntary nature) as an argument against future regulation proposals. Especially the part where they're ostensibly putting that control in parents' hands.

Oh, poor baby can't make money with an illegal business model. How awful.

That depends on which audio system you're running.

Since this can vary depending on your distro, the easiest place to look for that info is going to be your distro's documentation. That documentation may also include instructions for how to accomplish exactly what you want.

On top of this, your account gets penalized if you refuse to take an offered ride.

The complexity is the point. The less people willing or able to jump through all the necessary hoops to receive their healthcare through the system, the less money they have to pay out. Adding more complexity in the form of yet another opaque approval system adds many more hoops to get through, which is actually the entire purpose of that system. Deloitte knew this going in.

Yes, I have sympathy for the individuals who have to build this system, however I have absolutely zero sympathy for the company that put it into practice.

Yes, the medicare system is needlessly complex, however Deloitte decided to replace manpower with cheaper automation which had the side effect of saving them work by increasing rejections.

The world also happens to be complex. Enough so that both things can be true.

As a former rideshare driver: Fuckin' based.

-... . .- - / -- . / -

/ .. -