Hi, On 05/19/17 14:34, Hanno Schlichting wrote: > On 19. May 2017, at 14:01, Zeeshan Ali (Khattak) <[email protected]> wrote: >> On 18 May 2017 at 18:53, Jan-Tarek Butt <[email protected]> wrote: >>> But I will take a deeper look into geoclue maybe we can also integrate >>> communicating with openwifi.su. Maybe we can merge the openwifi.su datas >>> into MLS as well. >> >> The last part would make the most sense but I'm pretty sure: >> >> * this has been already considered and not acted on (don't recall the >> reasons). > > The problem is openwifi.su uses the ODbL license for its dataset, which has a > share-alike requirement in it.
Right, merge is maybe not possible, But I can build the new API like also forwarding all new incoming data as well to MLS. This should be done without licences problems. I prefer working together between both services. It will be very nice for openwifi.su. > Our legal understanding is that it violates European privacy laws to release > a dataset, which contains the combination of a BSSID and a lat/lon position. > This combination is considered personally identifiable information. please could you show me the privacy laws or any references? I didn't find much while googling. :) > If we were to integrate the openwifi.su dataset into our own, we'd be > required to also release our derivative combined dataset under the Odbl. That > in turn would mean we'd violate privacy laws. right, we don't want to bring you changing your licence concept. We just would like work close with MLS because of same concept and idea. > This is not legal advice to anyone else and if you only operate in a single > country, the situation might be different. If you are small project the > chance of you being sued is also a lot smaller. But given that Google was > sued and lost over this, we need to be careful. All right, I see the most problems are in licences and laws.. that is not really my part. But maybe we can find a good solution together :) >>> Yes, sure I know what you mean. But it is the only service which works >>> without authentication and SSL. > > > Regarding SSL, at Mozilla we very much consider location data to be privacy > sensitive. Sharing such privacy sensitive data over a non-encrypted channel > is not an option for us. > > As for authentication, geoclue as a library ships with a built-in API key, so > not every user has to get a key. These keys merely help us to attribute > traffic to the various clients and act a lot more like an extended user-agent > header. Since we are providing this service for free, they also give us a way > to shut down access from one client library, without affecting everyone else. > We never had to do so, but if someone where to abuse our service, we'd have a > way to single out one client, rather than shut down the service for everyone. > We specifically don't want to have an API key for a single device or user, as > that would allow us to track an individual. Something we really don't want to > be able to do. I see, I fully agree with you, but about the SSL part I it is not possible to get SSL on our routers between batman-adv mesh networks protocols and other stuff 4MB flash is not really SSL friendly... If wee find a good solution to build a communication between the openwifi.su backend and MLS we definitely can use SSL because the backend will run on a server were ssl is not a problem. To give a better view how it should worke: the routers will comunicate with the openwifi.su server to solve SSL problems and don't spamming your APIs. The openwifi.su backend will send the data to MLS (if we find a way :P ). The idea on the end of the GSoC project is to integrate the locating service in an open wireless framework from the Freifunk organisation in Germany. Than around ~30K routers will use that services in hole Germany. https://www.freifunk-karte.de/ cheers Tarek
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
