Changes

Google Voice Hacking

233 bytes added, 21:48, 16 May 2019
/* Miscellaneous Help */
The following lines were added (+) and removed (-):
This does not correct the change in behavior staring in 2018, prior the incoming caller's # always displayed when using voice.google.com via Chrome on a PC and the above setting only pertained to how the incoming call was displayed on a mobile phone that the call was forwarded to.  Now the setting applies to both.  Why in the hell would I want to see my own number on the PC. It is obvious to anyone that they are logged into that particular GV account when on the PC.  It is on the mobile phone the distinction should be optional.  Where is the logic Google?  Stupid.This does not correct the change in behavior staring in 2018, prior the incoming caller's # always displayed when using voice.google.com via Chrome on a PC and the above setting only pertained to how the incoming call was displayed on a mobile phone that the call was forwarded to.  Now the setting applies to both.  Why in the hell would I want to see my own number for all incoming calls on the PC? It is obvious to anyone that they are logged into that particular GV account when on the PC.  It is on the mobile phone the distinction should be optional.  Where is the logic Google?  Stupid. It would not be necessary to install the Google Voice bloatware app on the mobile phone to compensate for the ill behavior if Google would correct the situation restoring functionality to previous conditions.
Bureaucrat, administrator
16,192
edits