News for hackers. Stuff that matters.
Re:Why I’m done with Chrome by tananaev on Sunday September 23, 2018 @10:12PM (#18054555)
I'll add my very recent negative experience with Google. I have a couple of apps on the Google Play that use Firebase analytics and crash reporting. This weekend both apps were removed by Google without any warnings. The issue was that apps were in "Violation of Usage of Android Advertising ID" because by default Firebase collects Advertising ID. I don't really need Advertising ID in my app or my analytics and there is a way to opt out [1], but I think the way Google handled this is just wrong. Collecting information that most people probably don't care about and then removing apps without notice for basically their own default configuration.

[1] https://firebase.google.com/support/guides/disable-analytics

Re:Why I’m done with Chrome by Daniel_sk on Monday September 24, 2018 @02:11AM (#18055409)
We (software agency) had the same problem, a simple app with just basic Google libraries was violating their own privacy rules.
Re:Why I’m done with Chrome by the_new_guy_29 on Monday September 24, 2018 @03:31AM (#18055699)
Any examples of those rules and how they were violated?

Im just curious

Re:Why I’m done with Chrome by Daniel_sk on Monday September 24, 2018 @03:38AM (#18055723)
Some more details - https://www.reddit.com/r/androiddev/comments/9gqr6y/anybody_.... The emails from Google Play are never very specific so you can only guess what's wrong :-).
Re:Why I’m done with Chrome by zavi on Monday September 24, 2018 @03:14AM (#18055647)
You should appeal if what you're saying is indeed true. You're supposed to use advertising ID for any ad-related tracking - if you use something more sensitive instead (like IMEI) then you'll get taken down.
Re:Why I’m done with Chrome by Angostura on Monday September 24, 2018 @04:25AM (#18055927)
GDPR issue?
Re:Why I’m done with Chrome by bad_user on Monday September 24, 2018 @01:15AM (#18055187)
> Collecting information that most people probably don't care about

I care about that information and I’m glad they removed your apps, maybe now you’ll start taking privacy more seriously.

Re:Why I’m done with Chrome by tananaev on Monday September 24, 2018 @02:54AM (#18055564)
I think you misunderstood my comment. I don't want to collect that information. All I need is anonymous crash stacks and possibly some general statistics (number of users on various app versions and Android versions). Google was collecting extra information without me even being aware of it, until they removed my apps for the store. I want to collect as minimum information as possible for me to effectively maintain the apps. I have no use for personal information or any identifiers. But Google probably wants it and that's why Firebase collects it by default.
Re:Why I’m done with Chrome by patates on Monday September 24, 2018 @04:58AM (#18056051)
> Google was collecting extra information without me even being aware of it

I think the point is that you should be aware of it. It is your application after all. Yes, what Google does is weird, but the app developer needs to be more careful in general what 3rd party code they load.

On the other hand, I understand you. Probably you do your due diligence when you load some random dependency but you (like everyone else) used to expect better from Google. Not anymore I guess.

Re:Why I’m done with Chrome by Aeolun on Monday September 24, 2018 @05:51AM (#18056303)
I mean, if you use a google library that uses a specific google feature, it’s kind of fair to assume that it’s not a violation of their privacy policy.
Re:Why I’m done with Chrome by patates on Monday September 24, 2018 @09:40AM (#18057549)
You don't get to act clueless if one of the libraries that you added to your application collects data without asking the user. I already said what Google does is weird.
Re:Why I’m done with Chrome by gaius on Monday September 24, 2018 @01:42AM (#18055274)
The issue is that Google are shipping something with a default configuration that violates their own policy, then blaming the user of it