SpaghettiCthulu

What benefit would there be to uninstalling those bundled apps entirely vs disabling them? It's a nice goal to aspire to, sure, but does it really matter?

You can trivially install another launcher without that search bar and disable nearly all bundled apps on Pixels. Show me how easy it is to remove all the ads and bloatware from Windows.

> "A complete rebuild was necessary to ensure the website meets modern security, usability and accessibility requirements for the millions of Australians who reply on it every day," a spokesperson said.

I guess those "usability and accessibility requirements" don't include being usable without JavaScript.

Unless you think the same backdoor is hiding in AOSP, you can just check the diff and some extra lines for context.

You really want an LLM hallucinating that everything is ok and turning your air back on? Or hallucinating that everything was always ok and not turning your air off in the first place?

Source?

> When you reach out to one of your recovery contacts for help, you will share a code with them. They will get an email or notification and can confirm it’s really you by verifying that code, helping you securely regain access to your account. While you should choose someone you trust, rest assured that your recovery contact will not have access to your account or any of your personal information.

What additional verification will be required to regain access to your account?

Would be safer to use GrapheneOS and distribute these apps on F-Droid, using a custom repo if the main one won't allow them.

It's not just Android. I've encountered frequent broken gradle caching when using Kotlin outside of Android and when using Fabric for building Minecraft mods. In my experience, the only solution is wiping the user-wide gradle cache. Maybe it's a gradle issue or maybe it's an ecosystem issue (i.e. gradle plugins not respecting Gradle's cache semantics). Regardless, it does not reflect well on Gradle that such issues are so widespread.

From TFA:

> The primary use case in mind for parker is on the machines with high core counts, where scalability concerns may arise. Once started, there is no communication between kernel instances. In other words, they share nothing thus improve scalability.