Android restricting ADB reignites the user autonomy debate

Reports that Android may soon restrict on-device ADB (Android Debug Bridge) access sparked a heated thread about the recurring tension between platform security hardening and user and developer control. ADB is how developers test apps, researchers audit devices, and power users automate their phones. Restricting it on-device would force reliance on a connected computer for debugging, which is a meaningful workflow change.

The pattern is one HN commenters named explicitly: a feature exists, it creates security surface area, and the platform removes it under the banner of security, catching both bad actors and legitimate users in the same net. The frustration isn't with security as a goal, it's with the framing that treats all non-default use as a threat model. Multiple commenters connected this to a broader 2010s-onwards trend of platforms consolidating control over what users can do with their own hardware.

The sarcastic comment ('finally my children will be secure and my bank account impenetrable') captured the sentiment well: the people making the argument for restriction and the people who will be inconvenienced by it are largely different populations.