Comment 4 for bug 1450168

Hi Jamie, I think the privacy issue with the web cache is of a very different scale from the one you could get from collecting the map data. In the web cache you find visited websites, maybe with a lot of private information about the user. In the cache maps, on the other hand, the only information you can collect is a set of map tiles which might give some hint on where the user lives or has been travelling to, but even that with a lot of guesswork. I do see the issue, however.

There might be a solution, however: could we make give the apps the permission to only execute (traverse) the directories, and not read (enumerate) them?
In that way, it would not be possible for an app to get the list of the map tiles, while it would fulfil QtLocation caching needs (we know the file path of the tile we want to load, so we don't need read permissions on the directories).
Of course, an app could still try and read all the possible tiles one by one...

And if we go for the trusted prompt approach, what would be the action to be performed if the user grants the access? Would creating a hard link to ~/.cache/QtLocation from ~/.cache/<app>/QtLocation work?