Coder's Log

Just wanted to announce release 2.5.0 of Geoclue that includes the changes I mentioned in my last blog post . Also, while I'm at it, I wanted to highlight the "call for help" at the end of that post by repeating it here again. I apologize of repeating to those who already read it but a friend pointed out that it's likely going to be missed by many folks: The future of Mozilla Location Service When Mozilla announced their location service in late 2013, Geoclue became one of its first users as it was our only hope for a reliable WiFi-geolocation source. We couldn't use Google's service as their ToC don't allow it to be used in an open source project (I recall some clause that it can only be used with Google Maps and not any other Map software). Mozilla Location Service (MLS) was a huge success in terms of people contributing WiFi data to it. I've been to quite a few places around Europe and North America in the last few years and I haven...

After I started working for Collabora in April, I've finally been able to put some time on maintenance and development of Geoclue again. While I've fixed quite a few issues on the backlog, there has been some significant changes as of late, that I felt deserves some highlighting. Hence this blog post. Leaving security to where it belongs   Since people's location is a very sensitive piece of information, security of this information had been the core part of Geoclue2 design. The idea was (and still is) to only allow apps access to user's location with their explicit permission (that they could easily revoke later). When Geoclue2 was designed and then developed, we didn't have Flatpak . Surely, people were talking about the need for something like Flatpak but even with those ideas, it wasn't clear how location access will be handled. Hence we decided for geoclue to handle this itself, through an external app authorizing agent and implemented such an agent ...

So the Location hackfest 2014 took place at the awesome Mozilla offices in London during last weekend. Even though some of the important participants didn't manage to be physically present, enough people did: John Layt (KDE) Hanno Schlichting (Mozilla) Mattias Bengtsson (GNOME) Jonas Danielsson (GNOME) and some participated remotely: Bastien Nocera (GNOME) Garvan Keeley (Mozilla) Unfortunately Aaron McCarthy of Jolla couldn't attend remotely either as he lives in a very incompatible timezone (AU) but we had a lot of productive discussion with him through email that still continues. Some very fruitful discussions we had: Why Mozilla doesn't make wifi data it gathers for its location service , available for everyone to download? Hanno explained in great detail how making this data available would seriously compromise privacy and even safety of people. One good example given was someone getting out of an abusive relationship and not wanting to be traceable by the...

I just rolled out Geoclue 2.1.1 ! Since my last post with Geoclue update, there has been lots of changes. You can find a list of all the changes here but here are the highlights: Modem geolocation: If you got a 3GPP modem, geoclue will now be able to use that to locate you (with neighborhood-level accuracy) using opencellid.org . Additionally if your modem has GPS capability, geoclue can use that as well and as you know GPS is the most reliable geolocation source. One issue with GPS currently is that it takes a while before it can get a lock on and reason for that is that we currently have no support for A-GPS . I'll be talking with Aleksander Morgado during the weekend about how we can add that support but if I've understood correctly, it will need more work in ModemManager than geoclue now that it has all these other sources. Geoclue locating me using 3GPP source WiFi geolocation: In my last relevant blog post, I mentioned that we'll be implementing this ...