| 00:07:19 | | jtagcat quits [Quit: Bye!] |
| 00:07:37 | | jtagcat (jtagcat) joins |
| 00:13:25 | | vegbrasil joins |
| 00:18:05 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 00:36:08 | | BearFortress joins |
| 01:34:32 | | tzt quits [Ping timeout: 252 seconds] |
| 01:45:39 | | TokieSan_ joins |
| 01:48:04 | | TokieSan joins |
| 01:48:44 | | TokieSan__ quits [Ping timeout: 265 seconds] |
| 01:50:29 | | TokieSan_ quits [Ping timeout: 252 seconds] |
| 02:07:28 | | imer quits [Client Quit] |
| 02:08:13 | | imer (imer) joins |
| 02:16:37 | | tzt (tzt) joins |
| 02:16:53 | | diggan quits [Remote host closed the connection] |
| 02:40:12 | | imer quits [Client Quit] |
| 02:43:25 | | imer (imer) joins |
| 02:59:14 | | tzt quits [Ping timeout: 252 seconds] |
| 03:01:00 | | tzt (tzt) joins |
| 03:25:24 | | TokieSan quits [Ping timeout: 265 seconds] |
| 03:46:01 | | Elizabeth quits [Remote host closed the connection] |
| 03:46:11 | | elizabeth joins |
| 03:46:44 | | elizabeth is now authenticated as Elizabeth |
| 03:56:35 | | elizabeth quits [Client Quit] |
| 03:56:38 | | Elizabeth joins |
| 03:57:40 | | Elizabeth is now authenticated as Elizabeth |
| 03:58:10 | | Elizabeth quits [Client Quit] |
| 03:58:12 | | Elizabeth (Elizabeth) joins |
| 03:58:55 | | Elizabeth quits [Changing host] |
| 03:58:55 | | Elizabeth (Elizabeth) joins |
| 05:02:26 | | vegbrasil joins |
| 05:06:54 | | vegbrasil quits [Ping timeout: 265 seconds] |
| 05:53:31 | | vegbrasil joins |
| 05:54:49 | | g0tmk quits [Remote host closed the connection] |
| 06:00:34 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 06:16:58 | | g0tmk joins |
| 08:23:34 | | Dango360 quits [Ping timeout: 252 seconds] |
| 08:23:41 | | Dango360 (Dango360) joins |
| 09:13:18 | | T31M quits [Client Quit] |
| 09:13:37 | | T31M joins |
| 09:14:46 | | T31M is now authenticated as T31M |
| 11:28:42 | | vegbrasil joins |
| 11:33:29 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 11:54:53 | | diggan joins |
| 11:57:24 | | systwi__ (systwi) joins |
| 11:58:14 | | systwi quits [Ping timeout: 252 seconds] |
| 12:13:41 | | diggan quits [Ping timeout: 265 seconds] |
| 12:21:22 | | vegbrasil joins |
| 12:22:47 | | diggan joins |
| 12:30:07 | | vegbrasil quits [Ping timeout: 265 seconds] |
| 13:07:41 | | IDK quits [Quit: Connection closed for inactivity] |
| 13:14:04 | | vegbrasil joins |
| 13:18:32 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 13:32:18 | | vegbrasil joins |
| 13:37:18 | | vegbrasil quits [Ping timeout: 265 seconds] |
| 13:43:48 | | vegbrasil joins |
| 13:52:05 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 14:01:17 | | vegbrasil joins |
| 14:04:44 | | beario_ quits [Ping timeout: 252 seconds] |
| 14:05:23 | | systwi__ is now known as systwi |
| 14:06:24 | | Pichu0102 quits [Ping timeout: 252 seconds] |
| 14:06:27 | | Pichu0202 joins |
| 14:08:14 | | vegbrasil quits [Ping timeout: 265 seconds] |
| 14:12:37 | | vegbrasil joins |
| 14:21:14 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 14:34:35 | | geezabiscuit quits [Quit: ZNC - https://znc.in] |
| 14:52:07 | | vegbrasil joins |
| 14:53:47 | | geezabiscuit joins |
| 14:53:47 | | geezabiscuit is now authenticated as geezabiscuit |
| 14:53:47 | | geezabiscuit quits [Changing host] |
| 14:53:47 | | geezabiscuit (geezabiscuit) joins |
| 14:56:26 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 15:26:32 | | diggan quits [Ping timeout: 265 seconds] |
| 15:35:26 | | diggan joins |
| 16:31:18 | | geezabiscuit quits [Ping timeout: 265 seconds] |
| 17:07:02 | | geezabiscuit (geezabiscuit) joins |
| 17:58:43 | <dave> | Hopefully not a FAQ I missed: why does the warrior VM image have a hard max of 6 for concurrency? I ask because for the reddit project, empirically I can sustain 8 concurrent (spread across 2 VMs) without tripping rate limits, and it'd be nicer to lump that into a single VM and dedicate the other to a different project. |
| 17:59:05 | <dave> | I can most certainly track down the number in software and bump it, but obviously don't want to do that without understanding why it's there in the first place |
| 18:01:58 | <@JAA> | dave: Because the warrior is mostly intended for people who just want to help without having to think about it or interacting with it much after the initial setup. Too many people would just crank it up to the maximum, so when we switch the default project, they get banned from the target site immediately. |
| 18:02:27 | <@JAA> | If you know what you're doing and want more control, use the project images instead. They have a limit of 20. |
| 18:03:07 | <dave> | Aah, makes sense. Okay, I'll go spin my own thing and (carefully) crank the limits then, thanks |
| 18:07:21 | <fireonlive> | have fun! https://www.youtube.com/watch?v=3-3Yok5D3Aw |
| 18:09:18 | <dave> | lol, well that's today's soundtrack sorted |
| 18:10:07 | <that_lurker> | That blazing on the speakers, sweat dripping, incrasing the concurrency by 1 and getting ip banned |
| 18:12:06 | <dave> | just like building CNC machines: torque down the bolt until it shears off, then back off a quarter turn |
| 18:14:01 | | vegbrasil joins |
| 18:18:40 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 18:49:14 | <fireonlive> | :D |
| 18:49:32 | <fireonlive> | lmao |
| 19:05:50 | | g0tmk quits [Remote host closed the connection] |
| 19:31:51 | | g0tmk joins |
| 19:33:37 | <g0tmk> | you guys are awesome, thanks for building all this infrastructure. I'll be running a Warrior indefinitely from now on. Only wish I knew about it sooner |
| 19:37:14 | | vegbrasil joins |
| 19:41:32 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 19:42:25 | <@JAA> | The best time to start running a warrior was 10 years ago. The second best time is now. :-) |
| 19:43:00 | | vegbrasil joins |
| 19:47:23 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 20:00:31 | | vegbrasil joins |
| 20:05:00 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 20:08:30 | | vegbrasil joins |
| 20:16:32 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 20:32:21 | | vegbrasil joins |
| 20:39:28 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 20:39:29 | <dave> | arright, spun up self-updating project containers and the projects I could find that are still active are working away. Is there a good way for me to (infrequently) poll what the team's choice project is, so I can get an alert if a new important project pops up? |
| 20:40:15 | <dave> | My plan B is just leave a warrior VM running on low concurrency in parallel with the extra project images. |
| 20:44:04 | <diggan> | dave if you set env var SELECTED_PROJECT to `auto`, it'll use whatever project Archive Team deems to be the most important |
| 20:44:44 | <@JAA> | You could monitor `auto_project` in https://warriorhq.archiveteam.org/projects.json . |
| 20:44:57 | <@JAA> | Or in fact the projects list. |
| 20:45:41 | <dave> | Got it, thx |
| 20:51:26 | | vegbrasil joins |
| 20:59:16 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 21:07:00 | | fireonlive quits [Client Quit] |
| 21:07:46 | | fireonlive (fireonlive) joins |
| 21:13:06 | | vegbrasil joins |
| 21:20:49 | | vegbrasil quits [Ping timeout: 265 seconds] |
| 21:47:00 | | Muad-Dib quits [Remote host closed the connection] |
| 21:47:17 | | Muad-Dib joins |
| 22:21:27 | | vegbrasil joins |
| 22:28:32 | | vegbrasil quits [Ping timeout: 252 seconds] |
| 23:56:56 | | geezabiscuit quits [Ping timeout: 265 seconds] |