xthexder
I hadn't heard of this, and it makes me quite angry. Sooo many phones have Qualcomm chips in them, including every phone I've ever owned.
The amount of data they're collecting is unreasonable for what's actually required for A-GPS (the only actual feature this enables). And it's all completely invisible to users because they don't even include the Privacy Policy with the phones.
If I want to stop Qualcomm sending out a bunch of my data unencrypted over the web, I've got very few options, ~~all of which are: Buy a new Phone...~~
Edit: After more research on this, it seems this A-GPS request is still happening from the OS, which controls Wifi. /e/OS just didn't reconfigure the Qualcomm driver like GrapheneOS. This isn't a hardware or firmware backdoor or something like I thought initially. The article seems like an ad for NitroKey / NitroPhone, which is just a modified Pixel with GrapheneOS on it. I might look at GrapheneOS for my Samsung phone.
Can I split the rent with the ghosts?
To be fair, that game really isn't about shooting or even taking out enemies. Taking their gun only slows you down!
I should go play that again. It's got a great atmosphere (and soundtrack)
With some of the cats I've interacted with, letting them outside would probably be cruel itself. One is scared of the weirdest things, like string, and complete fails at even hunting bugs in the house. Not to mention the crazy heat waves we've been having that would definitely be a problem for an indoor cat with thick fur.
I'm not OP, but if transcoding is happening on user CPUs, it's theoretically possible to modify or inject stuff into the transcoded video. There'd need to be some way of validating a transcode matches the original, which is non-trivial.
A consensus algorithm could work, but that would massively increase the required compute. I'm not even sure things like NVENC vs CPU ffmpeg are deterministic in how tbey compress video. Different encoders could very likely end up with visually identical transcodes, but the hashes wouldn't always match.
Maybe someone else has a better idea for validating transcodes?
I think you're missing a critical part of how blockchains function: If Bitcoin was running on only 100 Mac Minis, there is nothing stopping someone buying 101 more Mac Minis, becoming dominant in the network and suddenly they can decide to just print their own bitcoins for themself.
The profitability of running Bitcoin miners is proportional to the market cap and the value of Bitcoin itself. For Bitcoin to remain stable, the total value must remain less than the cost of hardware to dominate the consensus algorithm.
Having never used Discourse before, I don't like that the default view is "Latest" and when you view "Categories" it only fits 1 at a time on screen for mobile, since it previews all the top posts still.
The MyBB instance Jellyfin has set up is much more user friendly if you're trying to get help with a specific thing.
People don't doom-scroll on forums like they do other social media, so I don't see the need to see all the latest "Why doesn't my Jellyfin work?" posts.