I do this for any inbound call, unless the caller id is someone in my contacts it can go to voicemail. If it's important they either leave a voicemail or keep trying, for repeated calls I will answer but with skepticism.
If they are in my contacts I will recognise their voice.
Not found any good proxy which works well with cisco VPN software. Charles and proxyman work intermittently at best and require disconnecting from the VPN and various such dances.
I used to send something like 250k a minute complete with delivery report processing from a single machine running a bunch of other services like 10 years ago.
But average latency is not the whole picture; tail latency is. For good tail latency and handling of spikes, you have to have a sizable "untapped" reserve of performance.
That's not really true though is it. I use it countless times a week to navigate from my current location to point x l, generally a postal code or POI.
At no point during this do I have to interact with alternative businesses or way points.
I agree that Google Maps does work as a navigation aid in certain environments (e.g. dense urban) and certain transportation modalities (definitely cars, to a lesser extent public transport, bike and pedestrian).
In my experience it's also useable as a general street/road map. It's clearly not a topographical map; I think it would be foolish and potentially dangerous to rely on Google Maps to, say, hike in the Alps. A standard topographical map would fit that use case much better.
P.S. I don't quite follow some of the complaints on this thread about the UX. For example, I always see the map scale in the bottom-right corner of the app. It is true that street names are not always written onto the map; however, clicking on a street gives me a popup with the name (not the most ergonomic UX, but it's not like the app is trying to hide the info, as some commenters are claiming).
If they are in my contacts I will recognise their voice.