![](https://lemmy.blahaj.zone/pictrs/image/86f958b1-c407-43fc-bc06-8d9ea53753f9.jpeg)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Using Android as a base was honestly the most reasonable thing they did. No reason to reinvent the wheel. What they made with it is admittedly really shit, though.
Using Android as a base was honestly the most reasonable thing they did. No reason to reinvent the wheel. What they made with it is admittedly really shit, though.
Huh, I’ve been in that train. Sudden, random hit of Nostalgia.
Well, shit, there goes my vote.
you have an app called android podcasts
Never heard of that. There’s Google Podcasts, but Google discontinued it recently. I’d personally recommend AntennaPod, but there’s other alternatives as well.
I personally don’t value them differently, but I see your point.
The wonky ownership of these games is actually the reason I’ve been pretty much exclusively buying stuff on GoG for a few years. I don’t know their stance on inheritance, but at least the hypothetical grandchild won’t need perpetual access to the account to keep playing the games.
In the end, clear legislation is kinda the only thing that can resolve this mess.
Yeah, my point was, if they do try to enforce their policies, we could probably find a way to work around it. It’s probably cheaper and easier than for your heirs to test those digital inheritance laws in court.
What Stream support have sent that person is probably an accurate representation of what happens when you apply their policies as written. Write another article if they are seen enforcing it.
Luckily, SteamDRM is usually easy to bypass, so if that happens one could prepare accordingly.
If you wanna bet that AMD accelerators become a viable alternative while the bubble is still going, maybe bet on them. It’s all gambling, in the end.
All the new AMD Chips have had an integrated fTPM for quite some time. Dunno what else the problem could be. But as long as you don’t really need Windows, I’d go Linux.
Wenn irgendwer kurz davor ist, einen CO2 neutralen Verbrennen zu entwickeln, so wird diese Entwicklung nicht wegen des Verbrenner-Verbots aufhören. Falls es wieder erwarten zu einer solchen Entwicklung kommt, so kann man das Verbot immer noch zurück nehmen.
Because telling them “I’m not allowed to answer that question.” isn’t going to make them look it up themselves anyway. I mean, you could lie to them, but I can’t imagine that being a popular policy.
Even if the sentiment behind this wasn’t so horrid, this’d still be stupid.
If you wanna court the laptop oem market, windows is the safer bet.
Depending on how in-depth they co-operated with the windows for arm team, keeping some details confidential till launch might have also been easier that way.
Haven’t read into this too much, but I think the affected person that made this get attention was a solo dev that was prototyping a solution for one of his customers.
And the reason he raised a stink was because he had a huge bill, as the name he chose for his bucket was by chance the same an open source project used as a sample bucket name, so whenever someone deployed it without first customising the config, it was pinging his bucket and getting a 403.
Can confirm, my brother is a furry and on bluesky.
It has been many years since I’ve used an OS without full disk encryption, so I can’t really compare, but I have a Windows Partition for some proprietary software that doesn’t like Wine on my PC, and it is really smooth. Might be because it’s on a NVME SSD, though.
Well, it kinda does. If you choose to print your keys, you can use print to file and safe them to the encrypted drive, if you really want to for some reason.
Was that in question? I thought it was clear from the beginning that it does pretty much everything in the cloud.
Uh, I understand the sentiment, but the model doesn’t know anything. And it’s legit really hard to differentiate between factual things and random bullshit it made up.
I wouldn’t even say that. Even if they had a truly unique LLM that ran partially locally with a custom co-processor, Android might still have been a good choice. It’s just hard to beat an open source base that’s already compatible with most mobile hardware, and relatively easy to find Devs for.