The original issue is proposing letting the user assign the debug service to a specific interface, one of which would presumably be loopback. This article is about the proposal from a developer that it should only ever be assigned to wlan0, which would break a lot of apps.

Letting applications bypass permissions with this feature is the exact usecase they don't want to lose. If anything, I don't see them being against the original proposal possibly restricting non-loopback access, which would enhance security.

▲

izacus 5 hours ago | parent [-]

It would break exactly 0 apps because none of the apps should be using this API to access your private data and phone call audio.

	▲	microtonal 4 hours ago \| parent \| next [-]
		So why do Google Play Services, etc. have full privileged access to a phone, including private data and phone call audio, but the user doesn't? It is tech feudalism - you don't own anything anymore, you just get to live on the digital land of a bunch of ~trillion dollar companies. At least, that is the goal. IMO either everyone gets access at the user's discretion or Google has to sandbox their own GMS services as well.
	▲	TeMPOraL 4 hours ago \| parent \| prev \| next [-]
		Why? What other APIs should my apps (or the apps I explicitly want to authorize for this purpose) use to access my private data and my phone call audio?
	▲	subscribed 37 minutes ago \| parent \| prev [-]
		So what official API call recorder app can use?