Yeah! Let me show you ant colony simulators. What we have here is something called Dwarf Fortress.

We told them to go fuck themselves. We retain lawyer specifically in case we have legal concerns, and the way we use their products, price jack up would be so extreme that it’s entirely worth risking it while we migrate away.

Too late ~

Article is from 2015, but nevertheless very cool.

Never change, Lemmy.

I’m not sure this is a shower thought but agree with you completely. Potential harms are far greater than the potential benefits.

User Fault FD “UFFD” support for enhancing the write-watches performance.

I’m too stupid to know what any of this means, but it bothers me so much that the title doesn’t say what it is.

Hey, at least the bots are ostensibly doing something useful.

Politics over science every time. Good job Florida.

Maybe you’ll learn that it isn’t what they put in the water that’s making you gay. Maybe you should, ya know, maybe not with the extreme conservative views.

I’m glad that they have the guts to deal with this massive distraction. In the States, school is more about free childcare than learning, so I understand it but disagree that phones are allowed.

Chuck Schumer: like cheap suit.

Yet another reason to hate Oracle software, not that we needed another reason.

Fuck you I’ve got mine!

True, and the applications are targeting children. Perhaps they’re praying on a user who will grant permissions without asking questions, of which there are many.

Do you have a mechanism to work around the OS permissions model that broadly works across handsets?

I can find you a buyer for that info and we’ll split 40/60. Dead serious. Cash, and no questions. Just prove that it works.

FUD. Apps cannot listen to the microphone without going through the OS first. I call FUD or share with me this magical OS-bypassing code. Compromising the OS at such a fundamental level on a recent Android version is almost certainly beyond their capabilities. I am more likely to believe the content that inspired this article is more aimed at investors and is blatantly making false claims, and that such claims from the privacy policy are generic disclaimers.

Further, have you ever tried to get an app to consistently run in the background on purpose? It’s an enormous PITA when you actually want this to happen. Android apps do not typically run in the background at all unless they have again special permissions to bypass background restrictions. The OS strongly prefers to pause and eventually kill apps to save battery rather than permit background activities to occur unless they fall into specific categories and then only at specific times to optimize the battery usage.

If an app asks to run in the background all the time, bypass battery restrictions, and you grant it microphone access explicitly, the problem is no longer Android. The problem is the user being stupid by granting access against their own interests. And even then, it’ll still trip the microphone indicator.

It amuses me how banks are so anal about the environment their apps run in, but I can open my bank in any browser with god-knows-what plugins installed on whatever OS of my choosing and just because I’m using a browser suddenly it’s totally fine and meets all security requirements.

As long as the user owns the TPM and has full control over it, I don’t see a problem. I paid for that hardware. I want to use it. There are already tools that can talk to it. It’s just not fully implemented and integrated into the system in a secure fashion. Indirectly, you kind of point out why there hasn’t been as much motivation to provide these features because they’re associated with the user giving up control, but it doesn’t have to be this way. The hardware can work for me if the support were there.

With the right support, it can even be combined with the password. This lets me enforce that the drive only unlocks in this machine, with this password, and only with the software that I set. That’s certainly more secure than how most distros do FDE today. It covers more use cases and enables a much stronger threat model.

Wow, removed and banned. Based on the comments this must have been highly inappropriate.

One major obstacle is third party drivers, specifically Nvidia, that forces building and signing your own kernel modules. It can be done, but it’s certainly more complexity than distributing signed binary drivers from the distro. I think Ubuntu has preliminary support for TPM-backed FDE, but only if you aren’t using such drivers. It doesn’t work in combination.

I don’t want to sign my own modules. I want them to shipped signed, so the key isn’t expected to be on my machine. If I were doing kernel development work, I’d have disabled secure boot entirely anyway.