I think the answer was to introduce a law which would force digital market places to clearly describe what users are paying for, for folks who weren't around during the controversial time when Steam and Xbox Live Arcade came out and can't grasp the concept; folks who didn't observe the reality before and after this shift.

Even though it was abundantly clear already, this is what the California law is all about.

If, with this clear explanation, you still want to merely get a license to use games via a service, you should be able to do it.

Valve isn't doing anything wrong: far from it. Steam is awesome and I understand that one day, it could all go away and with it, all the games I have access to.

I also understand that, at any time, Valve may decide that they don't want me to use Steam anymore, or that someone may hack into my account and I won't have access anymore.

Finally, I get that even now, things that I could do with physical games; I can't do with my Steam library (eg. Easily play a game on my Steam Deck while someone also plays another game on my desktop, or sell a game disc that sits on my desk).

I understood this when I reluctantly signed up to Steam to play Half Life 2 back in the day when it was a complete dumpster fire of a buggy mess of a service. But it has improved so much since then.

Hey, do you, but I don't see what the big deal is. We've already protested that Steam was a bad idea, and Valve was literally the devil, but it's actually turned out to be objectively more convenient than any alternative to play games, and it's no longer Valve forcing us to install Steam to play their games. Practically the entire industry has shifted, plus there are now alternatives (besides piracy) like GoG. Hopefully this law causes more competition in that DRM free space.

Yah. Makes more sense for Valve to spend their time improving Proton or working on their reference handheld device. A reference desktop device is a solution looking for a problem.

This is definitely a case of overloading a feature when they could just make multiple features.

I personally love the ability to easily switch the active Bluetooth device (so I love the new behaviour), but not everyone has this need.

They should just have added multiple quick settings tiles so we can all be happy.

They're completely different implementations of systems that steam video/audio/inputs.

Valve's is pretty buggy but has deep integration with Steam and allow NAT traversal, while Sunshine/Moonlight are way more reliable, have features that reduce latency but are pretty barebones as far as features: they just do streaming with no tight integration with what's being streamed.

And Sunshine is a reverse engineered version of Nvidia's game stream server, since Nvidia sunset Gamestream a few months ago.

Whoever made this has never used Google Cloud Platform.

And your ISP can still see which domains you’re going to if you use them as your DNS.

Just so you know, because TLS SNI is not encrypted and not yet universally obfuscated (adoption of this is pretty slow and one of the largest CDN providers had to pause their rollout last I checked), not-even-barely-deep packet inspection can be used to track the sites you visit regardless of your DNS provider or wherever resolution is encrypted. Just do a packet dump and see.

Also, if a website isn't fronted by one of the most popular CDN providers in existence, it can be possible to infer the sites you're visiting based on their server IP addresses.

Although this just shifts where tracking can occur, a VPN is the only reliable way to maybe prevent your ISP from tracking the sites you visit, if this is your desire.

You're not alone. Especially over the past few months, fonts on mobile seemed slightly off. The new design looks way better in comparison as the typography is consistent across the entire app.

I dunno. Just speculation (here's a grain of salt but) people may be sick of Nitro because of all the features that Nitro users are asked to pay more for. It's weird to remind people who are paying a subscription for an app that there's a store where they can pay more for stuff.

It's more down to trust and attestation than a technical implementation. Whoever makes an NFC payment system needs to prove to payment processors that the chain of software and hardware from the payment terminal to whatever proves you're the account holder (a card or a phone) can be identified. And, separately, the implementation needs to be audited.

This may sound like they're trying to make this horrible walled garden on the surface, but bank users expect their money to not get stolen. And if it is, they expect the bank to make that problem disappear. The bank can only provide these assurances if they control everything.

This is why they use hardware attestation and a chain of trust all the way through to the OS to identify the specific implementation of an NFC payment system. They want to know they can go after whoever created the buggy NFC payment implementation to recover the money or to least stop partnering with them.

Not a lot of FOSS developers would go through the trouble.

The more established term is a live service game: A game where development continues far beyond release with a trickle of content to keep players playing (and paying).

Yah. Fandom is an Adblock-required site. And even then it's pretty hard to browse.

Sync for Lemmy is a different app from Sync for Reddit. So the in-app purchases won't transfer. There's nothing to transfer.

tl;dr - Second option usually.

I think a huge part of shell programming (besides recognizing when anything more maintainable will do 😂😂😂) is trying to allow others who aren't as familiar to maintain what you've written. Shell is full of pitfalls, not the least of which is quoting and guaranteeing how many arguments you pass to commands and functions.

To me, the whole point of quoting here is to be crystal clear about where command arguments begin and end in spite of variable substitution. For this reason I usually go for the second option. It very clearly describes how I'm trying to avoid a pitfall by wrapping each argument to find in a pair of quotes: in this case, double quotes to allow variable substitution.

Sometimes it's clearer to use the first approach. For example, if the constant parts of one of those arguments contains a lot of special characters, it may make it clearer to use the first approach with the constant parts wrapped in single quotes.

But even then there are more clear ways to create a string out of other strings. For example, the slightly slower, and more verbose use of printf and a variable, and then using that variable as an argument...wrapped in double quotes since it could contain special characters.