Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geofence areas where to not create reports #255

Open
1 task done
Mikaela opened this issue Sep 29, 2024 · 3 comments
Open
1 task done

Geofence areas where to not create reports #255

Mikaela opened this issue Sep 29, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@Mikaela
Copy link

Mikaela commented Sep 29, 2024

Description

I would like to specify locations within X (kilo)metres of which NeoStumbler wouldn't generate reports and thus it wouldn't submit data to wherever I was submitting it.

Suggested implementation

I don't know, some sort of menu where to add locations and possibly display a map to show the concrete area. See e.g. Google Maps offline download zones?

Additional information

New request

  • I have checked that a similar feature hasn't been requested yet
@Mikaela Mikaela added the enhancement New feature or request label Sep 29, 2024
@spaetz
Copy link

spaetz commented Sep 30, 2024

Ideally with a fuzzy border, otherwise you get e.g. a nice clear circle of non-observations which reveals the center of your geofence.

@mjaakko
Copy link
Owner

mjaakko commented Sep 30, 2024

Ideally with a fuzzy border, otherwise you get e.g. a nice clear circle of non-observations which reveals the center of your geofence.

Very good point. This feature will need some planning

One idea would be to randomly discard a portion of data collected inside the defined area. Then there wouldn't be an obvious gap in the data nor a hotspot which could reveal your location

@tcpipuk
Copy link

tcpipuk commented Nov 4, 2024

I'd say it'd be reasonable to add a hard border as a first implementation then evolve the feature over time, especially as most of the services I've tried (e.g. beacondb.net) don't currently identify individual users to assist identifying dead zones.

From a privacy standpoint, including a basic version of the feature would be much better than having nothing, then there's lots of other possible ways to go in the future, like fuzzing time as well as distance to decide when to pause generating reports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants