ichnaea

Sorry, but then I take this as the usual - GOS is attacking other projects, that I can easily see in all their socials, and the other projects have done nothing wrong. GOS always claims that the other projects attack them since years, and never shows any proof. And indeed, I still never have seen any attack against GOS. Seems like this won't change today. You or other readers can check https://github.com/mozilla/ichnaea/issues/2065 for a public display on how GOS attacks work when they are mixed into technical debates, how they destroy any chance of cooperation.

Reading the MLS retirement issue[1] it seems that multiple established organizations (e foundation, Graphene) are also interested in providing an alternative service. Does this mean that we're now in a situation where multiple open source location service providers are competing, or is this the only publicly accessible project in this space for now? This project is cool and all, but seems to just be a one person effort with not a lot of engagement on GitHub[2]. Are you in talks with other people with similar goals to expand and collaborate on the project? Having the backing of an existing developer community could really bring this to the next level. 1) https://github.com/mozilla/ichnaea/issues/2065 2) https://github.com/beacondb/beacondb Edit: the actual project seems to be on Codeberg[3], where there is a bit more engagement from others

No, that's sadly not true. With the stepping down having been cancelled and the recently repeated paranoid accusations in https://github.com/mozilla/ichnaea/issues/2065#issuecomment-... the present situation of GrapheneOS is far from good, it's an "absolutely do not use and do not recommend the project"-situation. This maintainer being active and continuing his bullying is way too risky for the users of the project (and the FOSS android ecosystem as a whole). But let's indeed let it be here, it gets OT for the ASUS topic. The GrapheneOS warning just had to be mentioned as it was related to the bootloader re-locking.

He just made it on-topic: https://github.com/mozilla/ichnaea/issues/2065#issuecomment-.... For real, that's acceptable to you?

The rather troubling part of this announcement in a GitHub issue is that this nugget comes out in a seemingly innocuous comment[1]: >> Firefox still uses MLS for `browser.region.network.url`; will that also move to Google Location Services? > This endpoint will be migrated to another service (classify-client) that will return the expected response. We'll adjust DNS entries when it's time to make that move so firefox won't see any difference. What exactly is this "classify-client" service? Note also this led me to discover for the first time that this is a thing[2]: > Geolocation for default search engine > In order to set the right default search engine for your location, Firefox will perform a geolocation lookup once by contacting Mozilla's servers and store the country-level result locally. This connection happens on the first start of

The server code is on GitHub, but I don't know offhand where the offline geolocation scripts are. The Stumbler app's map will show your phone's GPS position (blue dots) and Mozilla Location Service's estimate (red dots) so you can compare the difference. https://github.com/mozilla/ichnaea We store signal strength for possible future use, but our current location algorithms don't use it. Wireless signal strength is notoriously flaky. From some reports I've read, signal strength is more highly correlated with the user's orientation (i.e. is their body blocking the signal to the source) than with distance to the source.

We're going to put some more information there on why we don't publish wifi at this point. https://github.com/mozilla/ichnaea/issues/330 In a nutshell though, we don't know how to do this yet without creating a privacy nightmare.

Good question, I added a ticket to get this addressed: https://github.com/mozilla/ichnaea/issues/330 I wrote about some of the topics a while back. Not all of it is up-to-date but it gives the broader context: http://blog.hannosch.eu/2013/12/mozilla-location-service-wha...

FWIW, most if not all of the web stuff is on GitHub: https://github.com/mozilla mozilla.org: https://github.com/mozilla/bedrock crash-stats: https://github.com/mozilla/socorro marketplace: https://github.com/mozilla/zamboni geolocation: https://github.com/mozilla/ichnaea support: https://github.com/mozilla/kitsune MDN: https://github.com/mozilla/kuma

The docs should be fixed now. Thanks for pointing out the problem. <:) https://github.com/mozilla/ichnaea/compare/3a3ed20df078...4e... The location API depends on having wifi measurements in our database, which is still tiny compared to big players.

I work on this Mozilla project. If you have any questions, please ask! Mozilla's network "stumbler" client is installable from GitHub: https://github.com/dougt/MozStumbler/releases. The client code is at https://github.com/dougt/MozStumbler/ and the server code is at https://github.com/mozilla/ichnaea/.