Retiring the Mozilla Location Service
The accuracy of [Mozilla Location Service ](https://location.services.mozilla.com/)(MLS) has steadily declined. With no plans to restart the stumbler program or increase investments to MLS we have made the decision to retire the service. In 2013, Mozilla launched MLS as an open service to provide geolocation lookups based on publicly observable radio signals. The service received community submissions of GPS data from the open source [MozStumbler](https://github.com/mozilla/MozStumbler) Android app. In 2019, Skyhook Holdings, Inc contacted Mozilla and alleged that MLS infringed a number of its patents. We reached an agreement with Skyhook that avoided litigation. This required us to [make changes to our MLS policies](https://blog.mozilla.org/services/2019/09/03/a-new-policy-for-mozilla-location-service/) and made it difficult for us to invest in and expand MLS. In early 2021, we [retired](https://discourse.mozilla.org/t/retiring-mozilla-stumbler/75206) the MozStumbler program. We are grateful for the contributions of the community to MLS to both the code and the dataset. To minimize disruptions and allow people time to make alternative arrangements, we have created a schedule that implements the retirement in stages. The retirement plan can be tracked in this issue. There will be five stages. 1. As of today (Mar 13th, 2024) we will stop granting new API access keys. All pending applications will be rejected. 2. On March 27th, 2024 we will stop accepting POST data sub
Posted by mostlygeek on Mar 13, 2024, 5:45 PM
Tags
Related issues
- Some good points here, and I definitely hate the "unalive" movement but like someone else said, it has gone beyond self-censorship to in-...
- It’s hard to take the article seriously when there’s no real discussion about how consciousness is defined and it takes Anthropic’s views...
- you know what i hate?
- > I honestly do not understand why any average person would buy anything else than a macbook today.
- Codex App frequently freezes/stutters on Windows 11 Pro despite sufficient system resources
- Add "Basic" and "Standard" plans
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (SaaS)
Some good points here, and I definitely hate the "unalive" movement but like someone else said, it has gone beyond self-censorship to in-...
It’s hard to take the article seriously when there’s no real discussion about how consciousness is defined and it takes Anthropic’s views...
you know what i hate?
> I honestly do not understand why any average person would buy anything else than a macbook today.
Codex App frequently freezes/stutters on Windows 11 Pro despite sufficient system resources
Add "Basic" and "Standard" plans
FEATURE: Multi-window support in Claude Code Desktop
Hi HN I built CookPal to solve a small but annoying problem for myself: I kept saving recipes from websites, TikTok, YouTube, and Instag...
Retiring the Mozilla Location Service
The accuracy of [Mozilla Location Service ](https://location.services.mozilla.com/)(MLS) has steadily declined. With no plans to restart the stumbler program or increase investments to MLS we have made the decision to retire the service. In 2013, Mozilla launched MLS as an open service to provide geolocation lookups based on publicly observable radio signals. The service received community submissions of GPS data from the open source [MozStumbler](https://github.com/mozilla/MozStumbler) Android app. In 2019, Skyhook Holdings, Inc contacted Mozilla and alleged that MLS infringed a number of its patents. We reached an agreement with Skyhook that avoided litigation. This required us to [make changes to our MLS policies](https://blog.mozilla.org/services/2019/09/03/a-new-policy-for-mozilla-location-service/) and made it difficult for us to invest in and expand MLS. In early 2021, we [retired](https://discourse.mozilla.org/t/retiring-mozilla-stumbler/75206) the MozStumbler program. We are grateful for the contributions of the community to MLS to both the code and the dataset. To minimize disruptions and allow people time to make alternative arrangements, we have created a schedule that implements the retirement in stages. The retirement plan can be tracked in this issue. There will be five stages. 1. As of today (Mar 13th, 2024) we will stop granting new API access keys. All pending applications will be rejected. 2. On March 27th, 2024 we will stop accepting POST data sub
Comments (0)
No comments yet. Start the discussion.