00:10:40<Guest>klea: the idea for implementation [wa/i]s (some of this i added right now) || 1: a config file that can be edited by trusted AT members | 2: code to the warrior is added to routinely pull this file (like the warriorhq check for AT's choice) | 3: the warrior parses the file and determines what project to pull and run
00:11:11klea nods
00:11:21<Guest>there could be a "ArchiveTeam's choice" and a "ArchiveTeam's choice (Hybrid)" with the hybrid one being whats above and the non-hybrid being "just stick with one project that AT selects, do not switch between"
00:11:54<Guest>but the hybrid would be recommended (remember people like defaults) because it helps AT switch between projects at a more fine tuned level
00:12:26<@JAA>The topic (from #eyewas) is how to distribute warriors across projects.
00:12:45<Guest>yes thats what im talking about
00:13:01<Guest>the config file determines how warriors are split between projects
00:13:05<@JAA>Yes, adding context for future log readers/searchers.
00:13:26<klea>may i dump some messages?
00:13:43<Guest>oh ok
00:13:47<Guest>yes sure
00:13:49<klea><Guest> WAC would be really useful right now: https://irclogs.archivete.am/archiveteam-bs/2025-12-10#l3197bade
00:13:49<klea><Guest> (redirect all ips within [insert list of asns] to telegrab)
00:13:49<klea><Guest> or a "if x status code has been recieved repeatedly for y amount of time, redirect to z project"
00:13:49<klea><Guest> theres tons of ways it could be configured, but i think further discussion goes to -bs
00:13:49<klea><klea> i think there's a little problem
00:13:50<klea><klea> for that idea, at least with how the AT setup is structure
00:13:50<klea><Guest> #-bs ?
00:13:51<klea><klea> the container can't decide to redirect itself, and warrior isn't designed to accept a change to this project temporarily option
00:13:51<klea><@JAA> #warrior probably
00:13:52<klea><klea> i thought #warrior was specifically for warrior only stuff, and from what i've understood there's people not using warrior but still querying the warrior endpoints
00:13:52<klea><@JAA> klea: The automatic project thing only exists in the warrior.
00:13:53<klea><klea> oh, i thought some people were running watchtower and some custom code designed by them that pulled the warrior config file, but i guess not.
00:13:55<klea>eggdrop: ping
00:13:59<klea>!ping
00:13:59<eggdrop>klea: pong!
00:31:10Max_G joins
00:59:12Shard795915 quits [Client Quit]
00:59:49Shard795915 (Shard) joins
01:54:11Shard795915 quits [Ping timeout: 272 seconds]
01:56:48Shard795915 (Shard) joins
03:37:22sec^nd quits [Ping timeout: 256 seconds]
03:38:33sec^nd (second) joins
03:55:43Guest quits [Quit: Guest]
03:56:05Guest joins
03:56:15Guest quits [Client Quit]
03:56:27Guest joins
04:09:05nothere_ quits [Ping timeout: 272 seconds]
04:39:32nothere joins
04:53:04DogsRNice quits [Read error: Connection reset by peer]
05:04:38Kotomind joins
05:09:15beardicus quits [Ping timeout: 272 seconds]
05:09:30beardicus (beardicus) joins
06:01:42nexussfan quits [Read error: Connection reset by peer]
08:10:30<@arkiver>agreed
09:34:37nathang2184 quits [Ping timeout: 272 seconds]
09:42:36nathang2184 joins
10:20:11Shard795915 quits [Quit: Ping timeout (120 seconds)]
10:20:27Shard795915 (Shard) joins
11:49:32quartermaster quits [Quit: Connection closed for inactivity]
12:00:00Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
12:02:45Bleo182600722719623455222 joins
13:41:37Shard795915 quits [Ping timeout: 272 seconds]
13:42:50Shard795915 (Shard) joins
14:59:45Woodie joins
16:28:46DogsRNice joins
17:04:17DogsRNice_ joins
17:08:05DogsRNice quits [Ping timeout: 272 seconds]
19:12:13Kotomind quits [Ping timeout: 272 seconds]
21:11:57Webuser333414 joins
21:15:15Webuser333414 quits [Client Quit]
23:19:10nexussfan (nexussfan) joins
23:58:33Yakov quits [Quit: Ping timeout (120 seconds)]
23:59:18Yakov joins
23:59:35Webuser260902 joins