[01:13] *** cechk01 has joined #warrior [03:04] *** JesseW has joined #warrior [03:37] *** JesseW has quit IRC (Leaving.) [03:49] *** JesseW has joined #warrior [04:26] *** Fletcher_ is now known as Fletcher [05:06] *** bwn has joined #warrior [05:36] *** cybersec has joined #warrior [05:36] quick question, for anyone able to answer [05:37] is warrior limited to 6 items at a time due to a drop-off in speed vs. quality, or something of that sort? [05:37] I've been working on the URLTeam project for most of the day and noticed that warrior is using a minimal amount of bandwidth while running 6 items [05:37] my internet would probably be able to handle upwards of 20 items, but would this hamper me in any way? is there a reason for the six-item cap? [06:03] the reason for 6 is lost to time, but 6 ends up being a good size for projects with what was an average-size item [06:04] the warrior shouldn't be monopolizing your connection; that's the point [06:07] it is also possible to run the urlteam scripts outside the warrior via https://github.com/ArchiveTeam/terroroftinytown-client-grab [06:08] however, that requires significantly more effort and assumes Linux or OS X [06:58] ah okay, that makes sense to me [06:59] is there a suggested limit on scripts to run? I'd hate to accidentally DoS someone if I'm running 10 instances of the urlteam script on my linux box [06:59] or even worse, accidentally DoS the tracker or something [07:13] check with Atluxity. They're currently throwing a ridiculous amount of power at the tracker (because, at their work, they were told, "here's a bunch of boxes -- stress test them for a few months, and let us know what goes wrong", and they decided to do so by contributing to ArchiveTeam) so they should have a good sense for what can go wrong when you do that. They're not in this channel, but you can ask them in #archiveteam (or #archiveteam-bs) [07:13] cybersec: ping [07:13] oh cool, thanks for the information [07:13] that's nice of them to contribute those resources too [07:14] yep :-) [07:30] cybersec: here's why Atluxity talked about thier setup: http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-11-02,Mon&sel=236#l232 [07:30] wow, that's pretty awesome sounding [08:37] *** JesseW has quit IRC (Leaving.) [08:51] *** deathy___ has quit IRC (Ping timeout: 252 seconds) [08:53] *** deathy___ has joined #warrior [08:59] *** bwn has quit IRC (Read error: Operation timed out) [09:36] *** bwn has joined #warrior [11:03] *** Infreq has quit IRC (始めましょう！) [15:47] *** sep332 has quit IRC (bye) [15:50] *** sep332 has joined #warrior [15:50] *** svchfoo1 sets mode: +o sep332 [16:34] *** Start has quit IRC (Quit: Disconnected.) [16:52] *** JesseW has joined #warrior [17:10] *** Start has joined #warrior [17:11] *** JesseW has quit IRC (Leaving.) [17:14] *** nertzy2 has joined #warrior [17:39] *** Start_ has joined #warrior [17:42] *** Start has quit IRC (Ping timeout: 252 seconds) [17:44] *** nertzy2 has quit IRC (This computer has gone to sleep) [18:39] *** Start_ has quit IRC (Read error: Connection reset by peer) [18:42] *** Start has joined #warrior [18:50] *** bwn has quit IRC (Read error: Operation timed out) [19:08] *** Start has quit IRC (Quit: Disconnected.) [19:24] *** bwn has joined #warrior [19:32] *** Start has joined #warrior [20:28] *** aaaaaaaaa has joined #warrior [20:44] *** Start has quit IRC (Quit: Disconnected.) [20:48] *** Start has joined #warrior [22:16] *** Start has quit IRC (Quit: Disconnected.) [23:02] *** aaaaaaaa_ has joined #warrior [23:02] *** aaaaaaaaa has quit IRC (Read error: Connection reset by peer) [23:27] *** aaaaaaaa_ is now known as aaaaaaaaa