Commit Graph

30 Commits

Author SHA1 Message Date
Vecna 10ff088b5a Resolve some TODOs 2024-04-26 15:25:56 -04:00
Vecna ec4dc5ca29 Re-evaluate past days in case we got new reports since last evaluation
It would be better to track which bridges got new reports and only re-evaluate those.
2024-04-26 15:11:31 -04:00
Vecna 43228e18c9 Encrypt negative reports 2024-04-16 01:11:47 -04:00
Vecna 45e71f32e8 Pass date for analysis, compute age correctly 2024-04-15 15:21:35 -04:00
Vecna 1a8b64080d Refactor Analyzer trait 2024-04-15 13:19:56 -04:00
Vecna cba8aea553 Pass confidence to analyzer 2024-04-12 12:52:30 -04:00
Vecna 5c6a076289 Begin work on cleaning up old nonces 2024-04-12 12:50:40 -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 bc35163084 Add tests for reports 2024-03-29 16:12:48 -04:00
Vecna 1ccd676e5c Store bridge data with key 'bridges', guess and report blockages 2024-03-23 23:16:20 -04:00
Vecna 12e699f979 Track bridge info by country first, then date 2024-03-23 21:40:00 -04:00
Vecna 3ef9c04141 Add functions to verify reports, update db 2024-03-23 17:43:18 -04:00
Vecna 8ea6940397 Listen for reports
Downgrade hyper, listen for new reports, TODO: test
2024-03-22 23:42:22 -04:00
Vecna 58ab310a40 Switch REQUIRE_BRIDGE_TOKEN back to constant for now 2024-03-15 13:24:00 -04:00
Vecna 5935d3d78c Rename bridge_info::BridgeInfo to disambiguate 2024-03-15 11:32:17 -04:00
Vecna 4f5bec56ad Add distributor enum so we know where to send NRs
For now, I'm not adding this to PRs because PRs are very Lox-specific
2024-03-14 18:09:24 -04:00
Vecna 4f88df6171 Create struct for bridge info which must be externally provided 2024-02-28 15:26:22 -05:00
Vecna c1b058ce4e cargo-fmt 2024-02-26 18:01:07 -05:00
Vecna 3a6423d2ba Space things out for better readability 2024-02-25 17:42:30 -05:00
Vecna cde22fef67 Use bridge-stats-end if available, refactor db to counts of reports 2024-02-25 17:38:37 -05:00
Vecna 28233ec8a5 Use map for negative reports 2024-02-21 15:15:39 -05:00
Vecna 08cfacbf85 Code for processing extra-infos files 2024-02-07 18:36:40 -05:00
Vecna 1e44e16bb1 Check fields when deserializing user reports 2024-01-22 23:06:50 -05:00
Vecna 76dd724613 Add Lox proof for positive reports 2024-01-17 18:53:40 -05:00
Vecna 326d7e5560 Clean up enum definitions/shared behavior, add struct creation functions 2023-12-05 19:55:33 -05:00
Vecna 1f21eeeb53 Make bridge tokens optional 2023-12-05 18:05:44 -05:00
Vecna 086e1a6a70 Add hash of bucket as type of proof of bridge knowledge 2023-11-28 17:56:49 -05:00
Vecna e153d58fd2 Define initial data structures 2023-11-28 13:18:08 -05:00