News for hackers. Stuff that matters.
Re:Android May Soon Restrict On-Device ADB by light_hue_1 on Saturday July 25, 2026 @04:44AM (#49045755)
Every single time any story has the words "Google developers" in it, they're behaving like arrogant, disconnected, anti-consumer jerks. From constant GCP breakage, to not acknowledging obvious Android bugs, to intentionally braking Chrome. It's a stark contrast to behind the scenes interactions with them.
Re:Android May Soon Restrict On-Device ADB by lII1lIlI11ll on Saturday July 25, 2026 @05:20AM (#49045965)
Yeah, my favorite one is how Chrome users are not smart enough to handle case-aware web-page search toggle. Although to be fair their Chrome team is very arrogant even by Google standards.
[dead]
Re:Android May Soon Restrict On-Device ADB by lII1lIlI11ll on Saturday July 25, 2026 @05:17AM (#49045949)
You keep spamming variations of this comment without explaining how could apps actually bypass security without several steps that the user needs to take in order for it to work. Are you just farming down votes for some weird reason or will you finally get to the technical details instead of one-sentence snarks?
Re:Android May Soon Restrict On-Device ADB by izacus on Saturday July 25, 2026 @08:14AM (#49046938)
The linked bug explains exactly how. The fact that you angrily slam downvotes when you hear something doesn't like doesn't make it "farming", just like rage and rants and bizarre accusations of conspiracy in this comment thread won't change the underlying issues that this is going to fix.
Re:Android May Soon Restrict On-Device ADB by wolvoleo on Sunday July 26, 2026 @01:24AM (#49054987)
If it's a bug then the bug needs to be fixed. If the auth process works as intended it's hard enough to make it not something you could do by accident.
Re:Android May Soon Restrict On-Device ADB by TeMPOraL on Saturday July 25, 2026 @05:54AM (#49046182)
You forgot to ask yourself whose interests are being secured, and who/what is the threat being secured from.

Security is not an unqualified good. It's just mechanism of control.

Re:Android May Soon Restrict On-Device ADB by izacus on Saturday July 25, 2026 @08:12AM (#49046928)
The users.
Re:Android May Soon Restrict On-Device ADB by TeMPOraL on Saturday July 25, 2026 @02:51PM (#49050443)
As the threat being secured against, yes.
Re:Android May Soon Restrict On-Device ADB by userbinator on Saturday July 25, 2026 @05:18AM (#49045956)
I'm sure Google considers users having freedom to be a "severe security issue." /s
Re:Android May Soon Restrict On-Device ADB by inigyou on Saturday July 25, 2026 @04:13PM (#49051079)
this without the /s
Re:Android May Soon Restrict On-Device ADB by kitsumed on Saturday July 25, 2026 @01:18PM (#49049506)
If I didn't word it like that (I'm the author) the "reddit mob" would have exploded the thread. That's the last thing I want. I want valuable feedback there, for now its somehwat working.

Most of the users who saw the post on reddit didn't even open the blog post anyways, according to analytics.

Re:Android May Soon Restrict On-Device ADB by nikanj on Saturday July 25, 2026 @05:19PM (#49051704)
Exhibit A: https://issues.chromium.org/issues/40093420

Decades of people desperate for a fix, utter stonewall from Google

Some PM somewhere decided that autocomplete belongs on all your fields, and who are you, the poor site developer, to disagree?

Re:Android May Soon Restrict On-Device ADB by wolvoleo on Sunday July 26, 2026 @01:04AM (#49054899)
I don't think the developers are bad, the problem are the top dogs that are telling them what to do.