Packets that are reported as "seen" by more than one reporting node are more likely to have been successfully sent on the mesh.
A hourly or nightly job that counts how often an individual packet is seen as just an int counter on the packet table would let us drop more aggressively on the seen table without losing the counts.
It also would allow us to choose to not count packets which were not seen by X nodes when doing trend analysis.
Packets that are reported as "seen" by more than one reporting node are more likely to have been successfully sent on the mesh.
A hourly or nightly job that counts how often an individual packet is seen as just an int counter on the packet table would let us drop more aggressively on the seen table without losing the counts.
It also would allow us to choose to not count packets which were not seen by X nodes when doing trend analysis.
<!-- github-sync-id:3471898156 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Packets that are reported as "seen" by more than one reporting node are more likely to have been successfully sent on the mesh.
A hourly or nightly job that counts how often an individual packet is seen as just an int counter on the packet table would let us drop more aggressively on the seen table without losing the counts.
It also would allow us to choose to not count packets which were not seen by X nodes when doing trend analysis.