at the time of this writing we've got the visibilityTime set to 6000ms, && it seems like it's working fine, but we want to make sure we strike the right balance between the data feeling like it's an accurate representation of the devices around u at that moment ( so as u move through a city it's clearly changing ) but at the same time we don't want the time to be so short that a device right next to u seems to constantly be appearing/disappearing ( if for ex: the frequency at which it probes is less often than the visibilityTime ), some things to consider in finding a sweet spot:
what's the average time between a station's probe emissions
what's the average time between a network's beacon frame emissions
what's the technique used by aircrack under the hood for determining stations' connected to a network && how often is that data emitted/a acquired
at the time of this writing we've got the visibilityTime set to 6000ms, && it seems like it's working fine, but we want to make sure we strike the right balance between the data feeling like it's an accurate representation of the devices around u at that moment ( so as u move through a city it's clearly changing ) but at the same time we don't want the time to be so short that a device right next to u seems to constantly be appearing/disappearing ( if for ex: the frequency at which it probes is less often than the visibilityTime ), some things to consider in finding a sweet spot: