Sent1n3l

Go touch grass, what sort of positive beneficial value does this add to any conversation.

Your type make HackerNews more like Mumsnet full of feminine energy, gossip and character assassination avoiding a single logical thought or adding anything of technical value.

This asinine nonsense is like reading a 14 year old girls diary. Grow up.(And before you think going after my feels will help it won't chick, I know the above after laughing with my wife when we went back to hers.)

Post hoc nonsense, your position is that because GrapheneOS, its users and community understand the issue and explain it on an objective basis this results in your subjective view of the community being toxic because you don't like the answer and it's delivery.

None of your points above have any relation to each other nor does one explain another.

You concocted a weak argument to justify ad hominem and say 'community toxic'.

Well done in providing an example of vapid demogoguery.

Marketing team? You only need to market something if you're selling it. GrapheneOS isn't a product, people buy device brands not OS names. People don't buy OneUI they buy Samsung, they don't buy PixelOS they buy Google, they don't buy OxygenOS they buy OnePlus, people don't buy SteamOS they buy Steamdeck ad infinitum.

Great way to demonstrate you don't know the general public and think and speak only nerd.

That being said people DO buy Google Pixel for GrapheneOS and they WILL buy Motorola for GrapheneOS too.

That is the power of GrapheneOS that all the other BingaBoingoKonohaOS can only wish for.

What a weird angle to have a pop over.

Says people should take a critical stance on GrapheneOS while providing no actual basis other than 'my feels' 'I've got a tingling' or 'my stomach made an unusual noise when I thought about it' as their position to smear it.

If I was reading this critically I'd say you have an axe to grind and want to continue to show why HN is a useless source of news or content.

Known for ages...another issue that's been spoken about but instead of resolving the F-Droid team decided to brush it under the rug and misdirect people instead of addressing it.

"Overall, this case study highlights how F-Droid’s inclusion policy ultimately harms end users by forcing app developers to adopt potentially decrepit development tools and build processes in service of its regnant FOSS ideology."

Funny how this article is continually proved accurate and poignant: https://privsec.dev/posts/android/f-droid-security-issues/

Taken from the projects official Twitter they offer more than what is available by said toggle on stock:

They provide a nicer MTE implementation as part of hardened_malloc which uses the standard random tags with a dedicated free tag but adds dynamic exclusion of previous tag and current (or previous) adjacent tags. We also fixed Chromium's integration and will improve PartitionAlloc.

They also use it for their browser too using PartitionAlloc. Other Chromium-based browsers including Chrome don't use MTE since they don't really use the system allocators and have PartitionAlloc MTE disabled.

They are also continuing work on integrating more ARMv9 security features. MTE having the highest impact and being the most interesting of these features, but they're expanding usage of PAC and BTI. Android uses Clang's type-based CFI but not everywhere so BTI is still useful.