00:13:50@Fusl quits [Ping timeout: 265 seconds]
00:15:31qwertyasdfuiopghjkl joins
00:35:05systwi quits [Read error: Connection reset by peer]
00:36:02systwi (systwi) joins
00:42:50tzt quits [Ping timeout: 265 seconds]
00:48:11<SoJa>Any chance of the warrior getting a "top 3" projects to work on? I have ample resources to run several warriors but as I've bounced around projects I often see tracker rate limiting(.ua), or getting API rate limited(reddit). It would be nice if I could specify "ArchiveTeam's Choice 1-3" and my warrior instances would work on 3 separate projects per IP.
00:48:46<SoJa>I understand I could simply statically assign projects, I guess once the statically assigned project reaches completion, does it go back to AT preference automatically?
01:48:25<TheTechRobo><SoJa> I understand I could simply statically assign projects, I guess once the statically assigned project reaches completion, does it go back to AT preference automatically?
01:49:07<TheTechRobo>I'm actually not sure about that one, but it does seem like it would be the case.
01:49:42<TheTechRobo>Also, if you have experience with Docker, rather than running multiple Warriors, you can also run projects individually. But that doesn't have the Archive Team's Choice option (although you _can_ install the Warrior as a docker image, that's actually what the virtual machine uses iirc).
01:51:48<SoJa>yeah I have a bunch of warriors running on docker, hence the issues I am seeing
01:52:38<SoJa>but yeah, I could run projects individually, but I want something I don't need to touch once it is setup
01:53:00<SoJa>the reddit API bans are particularly annoying since I only have 1 IP at home
01:55:14<SoJa>It was more of a wish, I realize the point of the warrior is to allow anyone to contribute to the projects and I am doing something unusual with it
01:55:29<SoJa>but it would be cool if a warrior could contribute to multiple projects I guess
02:28:25<TheTechRobo>yeah, I agree
03:13:57eroc1990 quits [Client Quit]
03:13:57@OrIdow6 quits [Client Quit]
03:14:50OrIdow6 (OrIdow6) joins
03:14:50@ChanServ sets mode: +o OrIdow6
03:15:24eroc1990 (eroc1990) joins
03:26:02tzt (tzt) joins
04:08:52tzt quits [Ping timeout: 245 seconds]
04:32:35tzt (tzt) joins
04:42:42tzt quits [Ping timeout: 265 seconds]
05:28:20Fusl (Fusl) joins
05:28:20@ChanServ sets mode: +o Fusl
05:37:29tzt (tzt) joins
09:01:24Iki joins
09:02:12Iki1 quits [Ping timeout: 245 seconds]
12:39:33kdqep (kdqep) joins
14:16:22TheTechRobo quits [Ping timeout: 245 seconds]
16:03:26TheTechRobo (TheTechRobo) joins
16:06:25kdqep quits [Client Quit]
20:37:53Pingerfowder quits [Quit: ZNC - https://znc.in]
20:39:31Pingerfowder (Pingerfowder) joins
21:27:34LeGoupil joins
21:27:58thetechrobo_ joins
21:28:03TheTechRobo quits [Remote host closed the connection]
21:28:03qwertyasdfuiopghjkl quits [Write error: Broken pipe]
21:28:14thetechrobo_ quits [Remote host closed the connection]
21:29:26thetechrobo_ joins
21:29:44thetechrobo_ quits [Remote host closed the connection]
21:30:56thetechrobo_ joins
21:31:13thetechrobo_ quits [Remote host closed the connection]
21:31:40qwertyasdfuiopghjkl joins
21:32:24thetechrobo_ joins
21:32:44thetechrobo_ quits [Remote host closed the connection]
21:33:14thetechrobo_ joins
21:56:13LeGoupil quits [Client Quit]
23:52:35qwertyasdfuiopghjkl quits [Client Quit]