My apologies, I think I misread the crux of the issue. Actually I think you are many issues brought up in this bug report: timezone vs. location, wasted page space, proprietary software, and an ambiguous regression. Is it that timezone and location are separate concerns? Timezone information you want public, but not your location?
I agree that timezone and location should not be tightly coupled. I think their coupling was a mistake.
I also agree that it is pointless showing you a map that you have implicitly deactivated to other users--the map cannot be used to set your location.
I think these are separate bugs if I my understanding is correct. The timezone/location rule may be a model change that is more difficult that the UI change to hide a map you cannot use.
My apologies, I think I misread the crux of the issue. Actually I think you are many issues brought up in this bug report: timezone vs. location, wasted page space, proprietary software, and an ambiguous regression. Is it that timezone and location are separate concerns? Timezone information you want public, but not your location?
I agree that timezone and location should not be tightly coupled. I think their coupling was a mistake.
I also agree that it is pointless showing you a map that you have implicitly deactivated to other users--the map cannot be used to set your location.
I think these are separate bugs if I my understanding is correct. The timezone/location rule may be a model change that is more difficult that the UI change to hide a map you cannot use.