Seemingly only in Japan, though.
Yeah it would be nice to get Movies Anywhere or something fully on board. All the movie studios are sitting on 3D movies already, they just need to make the app(s).
Steam only being 32-bit isn’t improving compatibility, it’s being lazy. You can write code that works on both architectures for the best performance and compatibility across all PCs, like Chrome, Firefox, MS Office, etc.
Every other major application and service on Mac has ARM-native builds now, there’s not really an excuse for Valve. It’s especially silly when much of Steam is running through a Chromium engine, not machine code or anything else that might be difficult to port.
There’s a difference between Valve deciding to not make Mac games anymore and Valve leaving the Mac Steam client a slow and laggy mess on newer Macs. The former only affects people who want to play Valve games, the latter affects a lot more people.
Valve has avoided many of the same anti-consumer moves as other tech and gaming giants, likely due to its smaller size, status as a non-public company, and the long-time leadership of Gabe Newell and other executives. Valve won’t stay that way forever—the company is not immune to the pressures of capitalism, and there are already examples of anti-consumer behavior.
Valve is not immune to enshittification, and it has already happened on some level with minimal current Mac support, facilitating gambling through item trades, etc.
I mostly use Mastodon, but I 100% get it. The onboarding process is much easier with centralized services (no need for analogies to email), and more importantly, you’re not at risk of losing half your follows/followers when server admins have a pissing match. As long as those friction points exist, there will be a market for centralized platforms.
I’m okay with Threads federating because there are a some people I know who won’t use Mastodon but will use Threads, and I would like to talk to them without downloading Threads. That’s probably true for most of the people supporting it, or they just think it should be up to individuals instead of the admin making unilateral decisions about who you’re allowed to talk with.
Threads joining would also introduce a far wider group of people to Fedi that isn’t just “nerds who like Linux and/or programming”, which is the bulk of people using Mastodon (and Lemmy, for that matter) right now. I’m not really concerned about EEE because there will always be a huge chunk of people using the FOSS platforms.
If I am on Mastodon, there is nothing that Threads can collect from me that they can not get already. My posts are public, Meta or anyone else doesn’t need permission to look at them.
The only risk is if I am sending direct messages to someone on Threads from Mastodon, then obviously Meta has a copy. ActivityPub is not E2E encrypted, you shouldn’t be using it for private communication at all, the threat model is the same between Threads and any other Mastodon server.
Public Mastodon posts are already indexed by search engines.
How about users make decisions for themselves and block Threads if they want?
Minecraft Legends doesn’t have a broken camera that makes you fall off cliffs constantly ¯_(ツ)_/¯
Super Tux Cart is always a good time
I had some fun going in 2018 with friends, but it definitely felt like a theme park with lines everywhere for demos. Maybe there’s room for something to take its place focused on those demos or community events, rather than announcements that most visitors couldn’t attend anyway.
When you’re in Chrome or another browser, there’s an install option in the main overflow (three dots) menu.
I made a PWA that can quickly remove tracking variables called Link Cleaner. If you install it through Chrome or another Chromium browser on Android, it shows up as a share target, so you can share links to Link Cleaner and then share again to the intended target.
Or just an RSS reader, every channel has an RSS feed
I did say the element zapper was missing. uBO Lite is using the same default filterlists as uBO, which includes some trackers: https://github.com/uBlockOrigin/uAssets
There are malicious extensions found in the chrome web store pretty frequently, and if I was making one, I would definitely use the API that lets me man-in-the-middle all network requests. So google’s statement that 40% or whatever of malicious extensions use that API seems plausible to me.
You could definitely make the argument that Google should just do a better job of reviewing extensions, but that alone also wouldn’t be a 100% solution. Google definitely messed up with the original rule limits, though. If chrome is more optimized then surely it must be able to handle just as many (if not more) rules than uBO.
Not really, even the cheap phones have large screens now. There’s no correlation anymore between price and screen size, the cheap phones just have lower quality panels.