@beacondb
I voted yes, but there is still the concern about people using the data dumps to target vulnerable routers which was not explained in the poll, but the data can be obtained from commercial sources.

This poll is a choice between keeping beaconDB only as a MLS-alternative for geolocation, or turning it into a larger free (as in freedom) and collaborative network database, like a FLOSS WiGLE.

There is still some research to be done about how to protect moving AP (access points) and contributor data, but publishing dumps not often (like every 2 months) would probably fix the second problem, but I would say it need to be thought after the result of this poll.

At least for now, as Apple already provide the same data in a scrapper-friendly way (it's easy to scrape with a low-end laptop), I would say it's not a real concern. If Apple decide to fix their server (which would be easy, by requiring the SSID of the visible AP in the location request, which would break the compatibility with old devices), the question would perhaps be different.

We can stop publishing dumps (or only obfuscated dumps) after Apple block the scrappers (which would create a new fork publishing dumps), because we wouldn't publish any new data (for example, @GrapheneOS is planing to distribute Apple dumps accessible on the Internet for offline geolocation).

Sorry for the long post.

@ianp5a @FediTips Pachli does have an option called "Reverse timeline order" under "Lab experiments", but I'm mainly using Moshidon for the design.
Another useful feature of Pachli is saving the point in your timeline where you exited the app (so you don't have to catch up everything at once).

I can't understand why such a basic feature is not considered as a standard on most apps.