Commit Graph

9 Commits

Author SHA1 Message Date
Vecna 36395181d3 Improve analysis
We seem to get better results when we scale bridge IPs down to multiples of 1 instead of 8 and only mark bridges as blocked if they differ in the 'bad' direction by at least one standard deviation from the mean.
2024-04-18 22:27:57 -04:00
Vecna 43228e18c9 Encrypt negative reports 2024-04-16 01:11:47 -04:00
Vecna bd4bc1b7b8 Test stage 1 analysis 2024-04-15 15:34:29 -04:00
Vecna c5a05be6d8 Test dropping NRs with repeated nonces and DB storage before processing 2024-04-12 12:26:36 -04:00
Vecna c82e604e3d Include nonce in negative reports 2024-04-12 02:38:35 -04:00
Vecna e1588aac0e Don't persist extra-infos files to disk, just process and store results 2024-04-06 12:02:53 -04:00
Vecna a679c13e4f Store bridge data by fingerprint and store set of fingerprints
We had been storing all the data as a huge map under the key 'bridges' so that we could iterate over all keys in the map as a way of iterating over all bridges. This caused the database to grow way too big, so we don't do that anymore. Now, we store each bridge's data with the bridge fingerprint as the key, and we store a set of bridge fingerprints under the key 'bridges'.
2024-04-06 01:09:43 -04:00
Vecna b915aea094 Add date to proof of bridge knowledge in negative reports 2024-04-04 22:55:07 -04:00
Vecna bc35163084 Add tests for reports 2024-03-29 16:12:48 -04:00