cross-posted from: https://lemmy.dbzer0.com/post/24292207
beaconDB is a drop-in replacement for MLS, which uses the same format request that’s used by Mozilla’s Ichnaea.
The source code is available on Codeberg: https://codeberg.org/beacondb/beacondb
You can contribute to the project by using an app like NeoStumbler (GitHub) or Tower Collector (GitHub) to submit location reports. NeoStumbler does Wi-Fi, Bluetooth and GSM, while Tower Collector can only do GSM cell towers. Both are FOSS and available on F-Droid.
It is also recommended by the GrapheneOS project: https://grapheneos.social/@GrapheneOS/112759509558471713
https://grapheneos.org/articles/positon-location-service
Just keep in mind that it’s still in relatively early development, which is why it really needs contributions.
I’ve been using this for the past week with microg to provide my network location. Works pretty well for me and also allows submission of new data.
The numbers seem to grow every time I look at them.
How do you use it with microG? Is there a NLP location plugin that uses it?
https://github.com/beacondb/beacondb-unifiednlp
It’s almost the same as the MLS UnifiedNLP backend, as beaconDB uses the same Ichnaea request format. Only the endpoint URL is changed.
Seems to be working nicely. It’s indeed a drop-in replacement for Mozilla NLP plugin, just with the added ability to customize the endpoint.
If anybody else needs to check their NLP plugins, the My Location app can show location fixes individually per location source.
I’ll start using the NeoStumbler app to contribute back to the API – hopefully it’s well optimized and won’t be eating too much battery.
I use microg 0.3.2. They removed the old NLP implementation in 0.2.8 I think. This new version has MLS implemented, but I you can set a custom URL like beacondb.
I first read it as “BaconDB”… Read into that what you will…
