01:12:32nulldata quits [Client Quit]
01:14:05nulldata (nulldata) joins
01:20:24nulldata quits [Client Quit]
01:21:57nulldata (nulldata) joins
02:44:26TheTechRobo quits [Remote host closed the connection]
02:44:26ScenarioPlanet quits [Remote host closed the connection]
02:45:17ScenarioPlanet (ScenarioPlanet) joins
02:47:59TheTechRobo (TheTechRobo) joins
08:15:32xendium joins
08:24:48<xendium>morning. is my understanding correct, that bit.ly is not actively scanned for a while? Seems like last downloadable archive is from 2021.
08:35:42<@flashfire42>Hi xendium I dont believe we have been actively scanning bitly for a bit but I will check and see if its active all the same
08:37:27<@flashfire42>And I am not game enough to switch it back on as it says it uses some custom code and I am not versed enough to know what that means
11:43:17decky_e joins
11:45:49decky quits [Ping timeout: 255 seconds]
13:01:52BearFortress_ quits [Ping timeout: 255 seconds]
13:26:48BearFortress joins
14:58:02AlsoHP_Archivist quits [Client Quit]
14:58:23HP_Archivist (HP_Archivist) joins
16:51:17<wickerz>What concurrency makes sense/is useful for this project (per IP)?
17:46:49thalia joins
18:04:40xendium quits [Client Quit]
20:50:11<@JAA>wickerz: Anything goes, the tracker will limit you. Higher concurrency than there are active shorteners (which varies, of course) is effectively useless, but you'll likely rarely see that many items actually run anyway. I'd probably just go for the max on a single container, i.e. 20.
22:46:25systwi quits [Ping timeout: 255 seconds]
23:03:45systwi (systwi) joins