Google will expand age checks on Android worldwide till the end of the year
android-developers.googleblog.com
Google will expand age checks on Android worldwide till the end of the year
1–10 of 549 posts
Re: Google will expand age checks on Android worldwide till the end of the year
#2I don't understand why apps need to know anything about a specific age. If we have to go down this road, which I really don't, why can't we just simply have verification whether or not an age fits within a range better yet a category. Yes, age can still be inferred, for example, under 21 or over 21.
Re: Google will expand age checks on Android worldwide till the end of the year
#3I don't understand why apps need to know anything about a specific age. If we have to go down this road, which I really don't, why can't we just simply have verification whether or not an age fits within a range better yet a category. Yes, age can still be inferred, for example, under 21 or over 21.
The API behaves this way:
> To request a user's age range and sharing status, you call the Play Age Signals API (beta) from your app at runtime. The default age ranges the API returns are 0-12, 13-15, 16-17, and 18+, but you can receive custom age ranges.
https://developer.android.com/google/play/age-signals/use-ag...
But I don't find it any better. I don't see any viable reason to provide identification to my phone's OS. If a parent buys a phone for their child, they can already set up parental controls before handing it over.
I wish Motorola all the best with their GrapheneOS partnership.
Re: Google will expand age checks on Android worldwide till the end of the year
#4I don't understand why apps need to know anything about a specific age. If we have to go down this road, which I really don't, why can't we just simply have verification whether or not an age fits within a range better yet a category. Yes, age can still be inferred, for example, under 21 or over 21.
The API behaves this way: > To request a user's age range and sharing status, you call the Play Age Signals API (beta) from your app at runtime. The default age ranges the API returns are 0-12, 13-15, 16-17, and 18+, but you can receive custom age ranges. https://developer.android.com/google/play/age-signals/use-ag... But I don't find it any better. I don't see any viable reason to provide identification to my phone'…
You can also get GrapheneOS right now on Google-branded hardware, which is expensive but not enshittified.
Re: Google will expand age checks on Android worldwide till the end of the year
#5I don't understand why apps need to know anything about a specific age. If we have to go down this road, which I really don't, why can't we just simply have verification whether or not an age fits within a range better yet a category. Yes, age can still be inferred, for example, under 21 or over 21.
Because it's not about age at all. That's just ruse to get a lever to lock people out of their devices if they don't behave.
Re: Google will expand age checks on Android worldwide till the end of the year
#6Earlier quoted context omitted.
The API behaves this way: > To request a user's age range and sharing status, you call the Play Age Signals API (beta) from your app at runtime. The default age ranges the API returns are 0-12, 13-15, 16-17, and 18+, but you can receive custom age ranges. https://developer.android.com/google/play/age-signals/use-ag... But I don't find it any better. I don't see any viable reason to provide identification to my phone'…
You can also get GrapheneOS right now on Google-branded hardware, which is expensive but not enshittified.
True. Though I have mixed feelings buying new pixel from Google after all these actions.
Re: Google will expand age checks on Android worldwide till the end of the year
#7I don't understand why apps need to know anything about a specific age. If we have to go down this road, which I really don't, why can't we just simply have verification whether or not an age fits within a range better yet a category. Yes, age can still be inferred, for example, under 21 or over 21.
This isn't aimed at you specifically, but I think many technologists seem to innately misunderstand the slippery slope hypothesis which helps form the bedrock of American politics.
Too many seem to fall into the familiar problem-solving mode, ready to provide compromises or solutions while forgetting that once the infrastructure is in place, it can easily be modified later to undo the compromises which facilitated its acceptance in the first place. There is an inherent power asymmetry and it's not generally in favor of those building and using the infrastructure.
Re: Google will expand age checks on Android worldwide till the end of the year
#8Earlier quoted context omitted.
You can also get GrapheneOS right now on Google-branded hardware, which is expensive but not enshittified.
True. Though I have mixed feelings buying new pixel from Google after all these actions.
Then buy a used or open box one. There's plenty of people who try switching to Android and buy Pixels, but go back to their iPhones in a week.
Re: Google will expand age checks on Android worldwide till the end of the year
#9I don’t understand how are they even checking the age ??
Re: Google will expand age checks on Android worldwide till the end of the year
#10Age checks are inevitable sadly. No one would tolerate “adult” services and goods rendered directly to children without age check.
The main argument is that there is an assumption this data is not stored in the real world, which is only sometimes true. Some places like airports and some concerts, shows, bars, etc. scan identification with digital readers whose data is presumably retained. One reason for this is because fake identification is a thing so defense against this converges to the same solution as digital verification.
Imo best to spend energy thinking of the appropriate solution that minimizes privacy violation than conceptual fighting against the idea.