HomeSearchPrevious dayNext day

00:28:33AlsoHP_Archivist quits [Ping timeout: 258 seconds]
00:51:06Arcorann (Arcorann) joins
01:02:33dm4v quits [Read error: Connection reset by peer]
01:04:30dm4v joins
01:04:33dm4v quits [Changing host]
01:04:33dm4v (dm4v) joins
01:07:54godane quits [Remote host closed the connection]
01:32:11onetruth quits [Ping timeout: 258 seconds]
01:42:28AlsoHP_Archivist joins
02:00:48driib5 (driib) joins
02:04:20driib quits [Ping timeout: 250 seconds]
02:04:20driib5 is now known as driib
02:41:33xkey quits [Quit: WeeChat 3.1]
02:42:06xkey (eyo) joins
02:47:21AlsoHP_Archivist quits [Read error: Connection reset by peer]
02:47:53AlsoHP_Archivist joins
02:48:42AlsoHP_Archivist quits [Read error: Connection reset by peer]
02:49:09AlsoHP_Archivist joins
02:54:13tzt_ quits [Ping timeout: 258 seconds]
03:01:41qw3rty_ joins
03:05:20qw3rty__ quits [Ping timeout: 258 seconds]
03:26:24tzt_ joins
04:00:12qw3rty__ joins
04:03:56qw3rty_ quits [Ping timeout: 250 seconds]
04:10:18DogsRNice quits [Read error: Connection reset by peer]
04:24:22katocala quits [Read error: Connection reset by peer]
04:24:43katocala joins
05:16:59AlsoHP_Archivist quits [Client Quit]
05:17:17HP_Archivist (HP_Archivist) joins
05:45:50HP_Archivist quits [Read error: Connection reset by peer]
05:46:14HP_Archivist (HP_Archivist) joins
06:47:12xkey quits [Client Quit]
06:47:54xkey (eyo) joins
07:14:28xkey quits [Client Quit]
07:14:44xkey (eyo) joins
07:28:18monoxane quits [Ping timeout: 258 seconds]
07:28:58fuzzy8021 quits [Killed (NickServ (GHOST command used by fuzzy802!~fuzzy8021@173-224-26-244.ptcnet.net))]
07:29:04fuzzy8021 (fuzzy8021) joins
07:29:56monoxane (monoxane) joins
07:36:16monoxane quits [Ping timeout: 250 seconds]
07:37:35monoxane (monoxane) joins
07:45:13LeGoupil joins
07:52:23tzt_ is now known as tzt
07:57:00tzt quits [Changing host]
07:57:00tzt (tzt) joins
07:57:07tzt is now known as tt
07:57:09tt is now known as tzt
08:46:22BlueMaxima quits [Read error: Connection reset by peer]
09:30:07<@OrIdow6>Wikidot script is slowly expanding, as they tend to do
09:58:14nothere quits [Quit: Leaving]
10:10:22nothere joins
10:40:50HP_Archivist quits [Read error: Connection reset by peer]
10:41:23HP_Archivist (HP_Archivist) joins
11:22:03IDK (IDK) joins
11:28:20<IDK>How do I call for help
11:31:19<IDK>I see some unusual activity on the bot
11:36:01Matthww quits [Client Quit]
11:36:07<Jake>archivebot or another project?
11:36:46<IDK>Archivebot
11:36:51<IDK>Jake:
11:37:20<IDK>Some web user is queueing up so much twitter task
11:38:30<Jake>Ah. I see. You'd need an op to do something there. Not sure if any are available.
11:39:00<@OrIdow6>What do you need
11:39:03<IDK>That webuser doesnt seem like to have any perms
11:39:07<IDK>#archivebot
11:39:21<@OrIdow6>Looking
11:39:43<IDK>Some non-voiced user is queueing so much
11:42:03<IDK>http://dashboard.at.ninjawedding.org/3
11:42:09<IDK>jesus christ
11:42:16<@OrIdow6>Looking through what some of these pages are
11:42:27<@OrIdow6>A lot of them seem related ot the game "rolbox"
11:42:57<IDK>hmm
11:43:21<IDK>OrIdow6 Can you abort?
11:43:34<Jake>i'd probably recommend that he slow down, current jobs should be fine?
11:43:48<@OrIdow6>Alright, at risk of angering JAA I'm going to try talking to them
11:44:03<@OrIdow6>And I mostly say that first part sarcastically
11:44:10<@OrIdow6>Yeah, I don't think these look too big?
11:44:37<IDK>I mean they would add up to like 20-30gb?
11:44:42<IDK>Doesnt look that bad
11:45:14<IDK>9g0wodvsxnhmjblrc0nng3aux and 5rajes2gvfmuek6gfr0taknxc are pretty big running task
11:56:08<@OrIdow6><OrIdow6> This isn't my area, for all I know your activity is a drop in the bucket, stick around if you want someone who knows to get online and tell you
11:57:11<@OrIdow6>If Webuser932 is still on when someone who knows the answer, please tell them
11:58:30<@OrIdow6>But AFAICT they are completely sincere
12:38:08yanmaani quits [Remote host closed the connection]
12:38:18yanmaani1 (yanmaani) joins
12:38:23Matthww joins
12:55:48yano quits [Quit: WeeChat, the better IRC client, https://weechat.org/]
12:56:07yano (yano) joins
13:40:58driib8 (driib) joins
13:44:44driib quits [Ping timeout: 258 seconds]
13:44:44driib8 is now known as driib
14:06:08Krownest quits [Read error: Connection reset by peer]
14:06:26Krownest (Krownest) joins
14:19:06<Ryz>Mm, this is why I always ask the non-voiced users that use socialbot to state their reasons - and I would prefer the voiced and OPped people to do so as well (maybe have an --explain for socialbot to make it easier)
14:21:13<Ryz>Would like to cut down the ambiguity at times
14:26:41<IDK>Ryz: there should be a guide on using socialbot in the channel topic
14:30:43yanmaani1 is now known as yanmaani
14:34:59<thuban>it might be useful to permit non-voiced users to use !explain as well (maybe just on jobs they submitted? i'm not sure how practical this is)--in the past i've had to ask for help because i !ao <'d but forgot to --explain and couldn't fix it, as it were, in post
15:40:11<@JAA>Thanks OrIdow6 :-)
15:40:29<@JAA>Ideally, socialbot would only accept commands from voiced/opped users, but that's not easy to add.
15:42:24<@JAA>thuban: Yeah, the 'on jobs they submitted' part is the hard one. You need to keep track of nicks and disconnects etc. to do that reliably. :-/ On the other hand, !explain is completely non-destructive, so it probably wouldn't hurt to just permit its use to non-voiced users in general.
15:44:15<thuban>i mean, arguably overwriting preexisting metadata with nonsense is destructive. but i agree that that might be the best choice
15:45:51<@JAA>Well, yeah, but it doesn't affect anything in terms of what AB produces and uploads to IA. The explanation isn't even included there.
15:46:17<thuban>right
15:54:41Arcorann quits [Ping timeout: 258 seconds]
15:55:50HP_Archivist quits [Read error: Connection reset by peer]
15:56:30HP_Archivist (HP_Archivist) joins
15:57:01HP_Archivist quits [Read error: Connection reset by peer]
15:58:10HP_Archivist (HP_Archivist) joins
16:13:50HP_Archivist quits [Read error: Connection reset by peer]
16:14:39wickedplayer494 quits [Remote host closed the connection]
16:16:19HP_Archivist (HP_Archivist) joins
16:25:32lennier1 quits [Client Quit]
16:26:40lennier1 (lennier1) joins
16:38:49Iki1 quits [Read error: Connection reset by peer]
16:39:50HP_Archivist quits [Read error: Connection reset by peer]
16:40:23HP_Archivist (HP_Archivist) joins
16:41:10Iki joins
16:45:50HP_Archivist quits [Read error: Connection reset by peer]
16:46:17HP_Archivist (HP_Archivist) joins
16:57:40wickedplayer494 joins
16:59:48AlsoHP_Archivist joins
16:59:48HP_Archivist quits [Read error: Connection reset by peer]
17:01:50AlsoHP_Archivist quits [Read error: Connection reset by peer]
17:02:22AlsoHP_Archivist joins
17:03:50AlsoHP_Archivist quits [Read error: Connection reset by peer]
17:04:17AlsoHP_Archivist joins
17:09:20AlsoHP_Archivist quits [Read error: Connection reset by peer]
17:09:49AlsoHP_Archivist joins
17:15:20AlsoHP_Archivist quits [Read error: Connection reset by peer]
17:29:16HackMii quits [Remote host closed the connection]
17:29:41HackMii (hacktheplanet) joins
18:46:33DogsRNice (Webuser299) joins
19:14:48FalconK quits [Ping timeout: 250 seconds]
19:15:01FalconK (FalconK) joins
19:43:13HP_Archivist (HP_Archivist) joins
20:09:59tzt quits [Ping timeout: 258 seconds]
20:16:51HP_Archivist quits [Read error: Connection reset by peer]
20:17:21HP_Archivist (HP_Archivist) joins
20:18:10LeGoupil quits [Client Quit]
20:36:39G4te_Keep3r joins
20:36:39<marked>how about allowing setting an explain message if never set
20:41:32<@JAA>That wouldn't help with socialbot because that sets its own explanation.
21:22:09tzt joins
21:24:13Sylirana quits [Read error: Connection reset by peer]
21:24:35Sylirana (Sylirana) joins
21:32:15HP_Archivist quits [Read error: Connection reset by peer]
21:33:20HP_Archivist (HP_Archivist) joins
21:39:18HP_Archivist quits [Ping timeout: 258 seconds]
21:58:29HP_Archivist (HP_Archivist) joins
22:26:27HP_Archivist quits [Ping timeout: 258 seconds]
23:09:41Sylirana quits [Ping timeout: 244 seconds]
23:10:08Sylirana (Sylirana) joins
23:14:55BlueMaxima joins

HomeSearchPrevious dayNext day