On 04.08.2014, at 14:34 , Adrian Custer <[email protected]> wrote: > Has the requirement for API keys for uploads been turned on?
As stated on IRC already. Nothing has changed yet for data submission. > Also, does a single key get used for all instances of a stumbling application > or should a different key be used for different versions, notably when the > way the data are gathered changes? For data submission the api keys tell us from what source we get data and how much that is. For example we can distinguish MozStumbler github users from MozStumbler f-droid users. We don’t want to store the api key with the records, but use it to get a general idea of where we are getting data from. And respectively be able to make decisions on where to focus our efforts. As a secondary option, we could track the data source (what application, what version). We don’t do that yet. If we were to go there, I think that would be something we’d want to solve via the User-Agent header. We might also want to have a bit more data in that, like the major version of the client operating system. This could allow us to treat data from different sources differently. For example if we’d know or discover a client side bug in a specific app/version, we could write workarounds for that particular app. We only have an issue about this on the MozStumbler side at https://github.com/mozilla/MozStumbler/issues/287 > I can pass more details about my current plans for the app to whomever needs > to decide about issuing a key. Note though that the app is a Firefox OS app, > which therefore needs to be certified, which means that the app will never be > distributed through the marketplace but only as a hand installable artifact. > There will therefore never be many users of this app. If you still want an api key, sent me a private email and I’ll get you a key for the app. Hanno _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
