It's not an on/off kind of thing, MTE is a set of ARM extensions. Either the api to use them is clearly documented or, as in the pixel 11's case, Google started to not document their implementation.
We know this matches their plan to obscure the AOSP code to eventually lock out anyone else from using their base.
GOS is not in a position to reverse-engineer api calls on what was formally documented hardware.
Instead, Google rewrote critical core Android system daemons using Rust. Like the keystore, Bluetooth stack, DNS resolver, and others. I believe using Rust essentially makes MTE unnecessary.
No. Rust being "memory safe" doesn't mean rust apps can't abuse speculation or buffer under/overruns.
The point is that the post makes it sound like using a Pixel 11 under Android results in less security than before, but for most people there is no change since they never used MTE anyway.
Read the BlueSky posts, Google didn't force app devs to opt into MTE, so no one did.
Google probably decided that since hardly anyone used MTE anyway on earlier Pixel devices, they could use the space in the chip for other uses.
"Space in the chips"? Again, see the Bluesky posts.
Google is very clearly shifting over to a completely walled garden, because, same as Apple, it isn't about the hardware performance and capabilities, it's about control.
These articles are meant to be read, that's the premise of posting them.
Flatpak is a mature project and the best option that exists on GNU/Linux today, but its security and sandboxing features still trail behind those of well-funded proprietary platforms such as Android and iOS.
without traffic, that's just doesn't work well enouhg
Yeah, that's fair enough for most of us.
Openstreetmap data isn't nearly as complete as google maps, to be sure. However, like a number of other FOSS and community-driven apps, there's always something I need to either live without (and in my current rural setting, that is traffic data), or I work around it.
One thing comaps is really good at is recording GPS tracks out-of-service, which google maps SUCKS at.
Ordnance Survey looks great! Too bad I'm not in Britain.
The internet isn't just for robots, you know. We still have to read with our own eyes.
Communication is a two-way street. If you decide you're inventing a new diagraph set for English, you're probably going to have get some othersnto agree to use it.
It's not an on/off kind of thing, MTE is a set of ARM extensions. Either the api to use them is clearly documented or, as in the pixel 11's case, Google started to not document their implementation.
We know this matches their plan to obscure the AOSP code to eventually lock out anyone else from using their base.
GOS is not in a position to reverse-engineer api calls on what was formally documented hardware.
No. Rust being "memory safe" doesn't mean rust apps can't abuse speculation or buffer under/overruns.
Read the BlueSky posts, Google didn't force app devs to opt into MTE, so no one did.
"Space in the chips"? Again, see the Bluesky posts.
Google is very clearly shifting over to a completely walled garden, because, same as Apple, it isn't about the hardware performance and capabilities, it's about control.