Replicant

Hi,

I've been thinking about it, and I think it makes more sense not to support this anti-feature.

Most users are most probably not willing to give potentially very private information to the companies operating the phone lookup services, just to get a precise indication of where the phone number is located.

I think it would make more sense to disable that feature completely.

If some users really want it back, we could then try to think about which requirements (like not violating users's privacy) we should require in to accept a patch that can restore the feature.

Denis.

Denis 'GNUtoo' Carikli wrote:

Hi,

I've been thinking about it, and I think it makes more sense not to support this anti-feature.

Most users are most probably not willing to give potentially very private information to the companies operating the phone lookup services, just to get a precise indication of where the phone number is located.

Well, it makes sense to me too, personally. And it would also be much easier for me to just remove the anti-feature completely, compared to implementing a reset of the default settings.

Some users may still want to be able to use those services, though; I don't like the idea of cutting it off completely.

Also, consider that by resetting the default options to "off", the anti-feature would only be restored by an explicit action performed by the user in the dialer's settings GUI.
I think it is safe enough to just disable the option by default and let users chose to enable it explicitly if they wish so. This would both guarantee users' privacy and keep the opportunity to enable the service if any user wants it, without the need of an additional patch to bring it back in the future.
For a more complete solution, it's also possible to implement a graphical warning explaining the implied privacy concerns when the user tries to enable the anti-features.

Since we would like to build a release candidate of 6.0 0004 within the week and this issue blocks it, I suggest that we disable the feature completely since a patch that provides a more complete solution, like the one suggested by Fil, hasn't been written.