Feature request / location scopes

iudnu

thetraveller1 Is there a location spoofer you recommend in the meantime?

ToolTimeTim7

Want to add +1 in This.
Many apps do not really need precise location but reject unprecise location. As such apps react to unprecise location the same way as to rejected location, I assume unprecise location is a different API, so app developers would have to update their code to get less data - which most companies just won't do.
If you are looking for offers or contacts in your area (coupons, dating, ...) the city would be sufficiently precise, but it does not work. One very widespread example is the McDonalds app.
Especially for dating apps this is an issue, as by the nature of their service they know a lot about the users, so removing (precise) locations from this list would be beneficial. Some apps (maybe intentionally, maybe on api level only) even leak precise locations to other users which can help stalkers and other malicious persons.

Joy69

Where can one add to this feature and contribute?

This is essential on so many levels,

No app should get any type of personal information, names addresses, location, who we talk to, what we do,.. NOTHING

An app is just a program that's supposed to be useful indiscriminate of the user.
Privacy is a human right.

other8026

Joy69 https://github.com/GrapheneOS/os-issue-tracker/issues/4075 along with a reminder to anyone who may want a feature that's listed in the issue tracker to please not "bump" the issue saying things like "please add this feature, it's so important" or asking for an update on on the progress of implementing a feature. Feel free to indicate to the developers that you want the feature by adding a positive reaction like 👍.

wild-rain-distant-drum

other8026 Feel free to indicate to the developers that you want the feature by adding a positive reaction like 👍.

Do the devs even notice when an issue receives a thumbs up if they don't specifically open up the issue and look at the reaction count?

I see this kind of "bump" issue most commonly when projects don't have a clear roadmap, or if the roadmap isn't posted in an obvious place for people to find it.

de0u

wild-rain-distant-drum Recently the GrapheneOS project has discussed a staffing problem due to a geopolitical event, and meanwhile changes to Google's open-source logistics have added significant friction to the development processes of GrapheneOS (and other AOSP forks). And the project has announced negotiations with a phone manufacturer, hopefully leading to GrapheneOS running on devices from a second manufacturer.

Overall my sense is that right now the project does not have idle developer time such that they could manage and act on large-scale input from the community on how to prioritize features that there isn't time to work on. If that is correct, "I want this too!!!" postings can do nothing but slow down development.

Meanwhile, the issue trackers show priorities, and it is possible for members of the community to help debug and fix code.

Please note that I do not speak for the GrapheneOS project.

« Previous Page