This article goes into more detail about how these new measures will actually work compared to the blog post earlier this year from Google. Namely:

1. Enabling the OEM unlocking setting will no longer prevent FRP from activating.
2. Bypassing the setup wizard will no longer deactivate FRP. FRP restrictions will apply until you verify ownership of the device by signing in.
3. Adding a new Google account is blocked.
4. Setting a lock screen PIN or password is blocked.
5. Installing new apps is blocked.

In this post, we’ve discussed the technical details of how we are restructuring memory in Android to get faster, more performant devices. Android 15 and AOSP work with 16 KB pages, and devices can now implement 16 KB pages as a development option.

Save a few words. Make life easier. How can this possibly go wrong?

I have a large DVD collection containing lots of niche titles that don’t appear to be on any public tracker. I would like to share my love of these films with the world.

I have access to a server that’s online 24/7 with a symmetric link and no data cap. My plan is to use a docker container with a web transmission instance to seed all of my material through a VPN provider (for my own safety). My server was last rebooted 200 days ago; I intend to rack lots of uptime seeding with my server. I have technical skills and I can ensure I’ll have an open port to accept connections.

Questions: what steps should I take to protect myself in seeding these DVDs? Is there a guide or some recommendations you can provide to get the best quality out of the many hours I’m going to spend ripping? Is it possible to trace the DVD reader that made the rip? Are the cool kids still uploading torrents or is there a better technology I should be using?

Overall, I have plenty of content to share, but I don’t want to put myself at risk when I do.

Article refrains from drawing conclusions, instead presenting the data. Android is doing better at moving users to newer versions, but the overwhelming majority of users don't have the current Android OS version nor the previous version, combined.

Bullet points stolen from the linked article:

• Code suggests the satellite connectivity feature on Pixel devices could be called “Pixel Satellite SOS.”
• We’ve also found a clue suggesting that the feature will be offered for free for two years, which would match Apple’s current offer on the iPhone 14 and 15 series.

I want to share this post because I was disappointed to see this popular smartphone cracking tool works very well across Android versions and devices while iPhone enjoys relative security.

The graphic also shows premium devices specifically are vulnerable to their tools, so one cannot argue that the problem is funding or cheap devices getting owned because of dumb changes by the vendor -- premium devices fare not much better. Even Google controlling the hardware and the software of their Pixel line remains vulnerable to data extraction while the latest iPhone versions aren’t.

To me, this sounds like the state of Android physical security might be inferior. Why? What can be done to fix this? Perhaps is it because Android is more popular globally so they get more work targeting Android?

It could also be coincidental that at the time the documents leaked, the iPhone stuff was being finished up and there is actually not that much difference if you have an attacker who has lots of time and money.

EDIT: Removed wrong information. EDIT: Added more material for discussion.

So much pony on the canvas! Where are all you guys and gals coming from? MLP has always seemed fairly quiet on the fediverse, but the proof is in the pudding, apparently!

It warms my old, nerdy heart.