See also desktop notifications for websites
You install an application you are giving it permission to do practically anything it wants to do with your system, including find the location as often as it wants to.
Browsers have to ask you permission to show desktop notifications, or get your location, or anything else.
Not on macOS, AFAIK. You can add/remove permissions for that.
I pin the system disruption from this query squarely on the OS. It should make such determinations in the background and return whatever value it has, without starting up a new scan just for this query.
I can't believe they ever thought that'd be a good idea.
1. Google/Nest WiFi mesh APs being "too close" to each other (30 ft / 10 m), causing a periodic backhaul mesh collapse. There was no user-visible indication of this, it was completely locked away and only noticed by support. I ditched Google's junk and moved to Ubiquiti.
2. On macOS, ObjectiveSee's LuLu has nondeterministic packet loss that causes SSH connection resets and a whole host of other weird problems. It's totally untrustworthy and shouldn't be used by anyone until it's proven reliable.
Scanning for nearby WiFi access points with excessive frequency might be a dumb idea for other reasons (e.g. power consumption) but it should *not* interrupt the functionality of the current network connection.
If it does, that's a massive failure of the network card's firmware and/or OS drivers for it.
My guess would be that the card is changing frequencies/bands to scan other channels, and is slow to switch back to the channel of the currently-associated AP, or doesn't properly buffer network packets while doing so.
Under Linux, I don't think I've ever seen a case where WiFi scans appreciably affected a normal infrastructure-mode WiFi connection (whether from NetworkManager or triggered manually via `iw` etc).
So much for Apple's vaunted hardware/software integration
https://www.reddit.com/r/linux_gaming/comments/3xipom/how_to...
Right. I suppose I've been both lucky, as well as intentional in seeking out hardware with high-quality drivers when it was very important.
I'm just surprised that *Macs* have this issue, given that one of the alleged selling points for Mac is that it runs on a very limited set of hardware which is supposed to enable careful OS/hardware integration and testing.
Scanning works by tuning the radio to listen for a beacon sent by the AP every ~100ms on every channel (there are 11 2.4 GHz and ~22 5 GHz channels in the US). Since you're not transmitting, it should be low-power, but you have to tune the radio to each channel, so you can't communicate with your AP.
Yes, but good drivers can mitigate the latency hit by not scanning all the channels at once. https://blogs.gnome.org/dcbw/2016/05/16/networkmanager-and-w....
> Since you're not transmitting, it should be low-power,
Depending on the hardware/firmware quality, tuning to each channel can use a lot of energy. As for "not transmitting," this is true for passive scanning (generally preferable) but not for active scanning.
> but you have to tune the radio to each channel, so you can't communicate with your AP.
Right, but _if the OS and drivers are written properly_ (on both the client device as well as the AP ) they'll buffer unsent packets… the high latency during the channel changes is unavoidable, but the dropped packets and broken TCP streams are NOT.
> With a good driver scanning takes only a few seconds
A few seconds of not transmitting or receiving packets. This is in line with people having sudden several hundred millisecond ping spikes.
A few seconds of no real traffic is absolutely noticeable impact for constant, latency sensitive traffic.
You omitted the immediately following text: "*and the driver breaks the scan into chunks*, returning to the associated access point’s channel periodically to handle pending traffic."
A good driver will return to the AP's channel _during the scan_ so that there is never more than (say) 100 ms of latency even while the scan is ongoing.
I noticed that my WiFi had similar repeating lags .. about every 8-10s pings would go to a few hundred ms and then return to single/low double digits.
Long story short, the problem was with several MacOS components (and maybe some 3rd party software) requesting Location services to determine Mac’s position. To do that, among other things, Mac scans WiFi around you (probably for the names/SSID?) and to do that, the current WIFI connection is temporarily put on a back burner, resulting in a brief delay in traffic. The solution was to minimize location services.