00:02:21 | <nicolas17> | wtf |
00:02:32 | <nicolas17> | it's december already (UTC) |
00:02:34 | <nicolas17> | how did that happen |
00:29:08 | | etnguyen03 (etnguyen03) joins |
00:50:35 | | lukash98 quits [Quit: The Lounge - https://thelounge.chat] |
01:10:43 | | DogsRNice joins |
01:23:51 | | DogsRNice_ joins |
01:27:30 | | DogsRNice quits [Ping timeout: 260 seconds] |
02:42:30 | <qwertyasdfuiopghjkl2> | I read through the discussion, and I agree with what thuban and TheTechRobo said. I'm not good at wording things (and also not a programmer), but it seems to me that a significant issue is that people who could (and want to) help out with the coding stuff aren't able to do that because the tracker is not open source/ci is broken/etc, so it'd make sense to prioritize solving those problems first |
02:42:30 | <qwertyasdfuiopghjkl2> | ish because they seem to be a prerequisite for anyone else even being able to help with many of the issues. |
02:43:09 | <qwertyasdfuiopghjkl2> | (hmm, message splitting ate the dash?) |
02:43:15 | <qwertyasdfuiopghjkl2> | In the category of "making it easier for people to find/use the IRC", in addition to the already-mentioned rewording of the IRC rules page to be more friendly, I think it'd be good to add some kind of "How can I request that a website be archived" link to the front page of the wiki, since (surprisingly) there doesn't currently seem to be one. It could probably be added to the "Archive Team |
02:43:16 | <qwertyasdfuiopghjkl2> | recruiting" section or somewhere near there, so it's visible without having to scroll. |
02:46:44 | <qwertyasdfuiopghjkl2> | (there was probably more I intended to say, but I couldn't figure out how to word it and now I don't remember some of it) |
02:51:50 | | lukash98 joins |
03:02:07 | <Ryz> | qwertyasdfuiopghjkl2, think you should drop in some notes in a paper, stream of consciousness and stuff o: |
03:02:25 | <nicolas17> | I didn't read the massive IRC backlog yet |
03:15:51 | | etnguyen03 quits [Client Quit] |
03:16:35 | | etnguyen03 (etnguyen03) joins |
03:24:29 | <TheTechRobo> | Regarding the IRC rules, I don't personally have an issue with the rules, but I've never been a huge fan of the examples provided. Not because of the examples themselves, but because of what's around them. |
03:24:38 | <TheTechRobo> | To put it bluntly, if I was a new Archive Team member reading through the examples, and I saw "Anyway, enough talking to the retard" in response to someone who was just asking too many questions, I'd probably assume this wasn't a great community. |
03:24:47 | <TheTechRobo> | I'm not commenting on that exact conversation. Maybe it was warranted; I don't have any context. But IMO it's really not a great introduction to AT. |
03:27:41 | <TheTechRobo> | This is just my 2 cents, I don't expect anyone to take it seriously. That's just the impression that those IRC examples have given me. |
03:37:38 | | etnguyen03 quits [Remote host closed the connection] |
03:42:50 | | DogsRNice_ quits [Ping timeout: 260 seconds] |
03:43:06 | | DogsRNice joins |
04:31:41 | | zhongfu quits [Quit: cya losers] |
04:52:52 | | zhongfu (zhongfu) joins |
05:05:45 | <steering> | oh huh, that's cool, ovh gives you the option of an ipxe shell as rescue media |
05:33:51 | | DogsRNice quits [Read error: Connection reset by peer] |
05:43:51 | | Hackerpcs (Hackerpcs) joins |
05:50:32 | | quartermaster joins |
06:38:39 | | eroc1990 (eroc1990) joins |
07:10:05 | <DigitalDragons> | the biggest problem with AT I see right now is that the tooling is super fragile |
07:15:59 | <DigitalDragons> | when it works, it works really well! but it is confusing to learn and has a lot of longstanding workarounds |
07:18:32 | <DigitalDragons> | (like how ArchiveBot pipelines need to keep months of uptime, because if a pipeline stops the jobs can't be restarted again) |
08:02:07 | | midou quits [Remote host closed the connection] |
08:02:15 | | midou joins |
10:00:15 | | tzt quits [Ping timeout: 260 seconds] |
10:32:20 | <@arkiver> | i agree on the IRC rules yes, they should be changed to be more "friendly" - instead of the bit of an aggressive tone they have now. (but not outright deleted as was done before) |
10:35:36 | <szczot3k> | First of all - they should be in the topic :D |
10:36:13 | <szczot3k> | I was made aware of them because of this discussion (granted: They're like most of the irc channels rules, just passive aggresive) |
10:38:22 | <@arkiver> | i dont know if they should in the topic. maybe a reference at the most. |
10:39:52 | <szczot3k> | Rules that people are not aware of are kinda pointless. People taht join #archiveteam for the first time shouldn't be forced to jump onto wiki, and search for them |
10:40:08 | <@arkiver> | we're not forcing them |
10:41:12 | <@arkiver> | people can say whatever they want when they join on IRC - if it is then seen that it's all becoming very unproductive or counterproductive, the rules on the wiki can be referenced to |
10:43:19 | <@arkiver> | the rules on the wiki will be rephrased. as for information people about them, i think we're not going to do that in the topics, as we don't see much bad behavior lately. i would continue pointing people to the rules if necessary |
10:48:13 | <steering> | arkiver++ |
10:48:15 | <eggdrop> | [karma] 'arkiver' now has 41 karma! |
11:03:11 | | sralracer (sralracer) joins |
11:09:08 | | Shjosan quits [Quit: Am sleepy (-, – )…zzzZZZ] |
11:09:52 | | Shjosan (Shjosan) joins |
11:26:31 | | Froxcey quits [Remote host closed the connection] |
11:26:41 | | Froxcey (Froxcey) joins |
12:00:05 | | Bleo182600722719623 quits [Quit: The Lounge - https://thelounge.chat] |
12:02:48 | | Bleo182600722719623 joins |
12:12:32 | | Froxcey quits [Remote host closed the connection] |
12:14:29 | | kaz (Kaz) joins |
12:14:29 | | @ChanServ sets mode: +o kaz |
12:15:41 | | Froxcey (Froxcey) joins |
12:17:55 | | Froxcey quits [Read error: Connection reset by peer] |
12:17:57 | | Froxcey (Froxcey) joins |
12:19:51 | | Froxcey_ joins |
12:22:35 | | Froxcey quits [Ping timeout: 260 seconds] |
12:24:11 | | Froxcey_ quits [Read error: Connection reset by peer] |
12:24:13 | | Froxcey (Froxcey) joins |
12:26:40 | | Froxcey quits [Read error: Connection reset by peer] |
12:26:41 | | Froxcey (Froxcey) joins |
12:31:49 | | Froxcey quits [Remote host closed the connection] |
12:31:50 | | Froxcey (Froxcey) joins |
12:32:37 | | Froxcey quits [Remote host closed the connection] |
12:43:36 | <szczot3k> | immibis are you familiar with the Pumpkin of Shame? lmao |
13:05:17 | | driib quits [Quit: The Lounge - https://thelounge.chat] |
13:05:38 | | driib (driib) joins |
13:22:03 | | Froxcey (Froxcey) joins |
13:26:45 | | Froxcey quits [Ping timeout: 260 seconds] |
14:35:54 | | Froxcey (Froxcey) joins |
14:40:15 | | Froxcey quits [Ping timeout: 260 seconds] |
14:41:09 | | rewby quits [Quit: WeeChat 4.4.2] |
14:41:21 | | rewby (rewby) joins |
14:41:21 | | @ChanServ sets mode: +o rewby |
14:55:02 | | etnguyen03 (etnguyen03) joins |
15:07:15 | | T31M quits [Quit: ZNC - https://znc.in] |
15:14:37 | | T31M joins |
15:14:40 | | T31M is now authenticated as T31M |
15:19:55 | | katocala quits [Ping timeout: 260 seconds] |
15:20:07 | | katocala joins |
15:29:39 | | Froxcey (Froxcey) joins |
15:31:35 | | katocala quits [Ping timeout: 260 seconds] |
15:32:16 | | katocala joins |
15:32:35 | | th3z0l4_ joins |
15:34:30 | | th3z0l4 quits [Ping timeout: 260 seconds] |
15:59:47 | | etnguyen03 quits [Client Quit] |
16:02:30 | | th3z0l4_ quits [Ping timeout: 260 seconds] |
16:06:37 | | etnguyen03 (etnguyen03) joins |
16:24:06 | | Froxcey quits [Remote host closed the connection] |
16:25:58 | | Froxcey (Froxcey) joins |
16:28:05 | | Froxcey_ joins |
16:28:05 | | Froxcey quits [Read error: Connection reset by peer] |
16:59:49 | | sludge is now authenticated as sludge |
17:13:56 | | etnguyen03 quits [Client Quit] |
17:32:48 | <@JAA> | /*stdin*\ : 0.03% ( 1.88 GiB => 676 KiB |
17:32:51 | <@JAA> | Not bad... |
18:07:11 | | etnguyen03 (etnguyen03) joins |
19:23:47 | <steering> | I spent all night customizing a live CD image to boot with my SSH keys (and start sshd), and much of the morning getting OVH to boot it (aided by an apparent hardware failure on their side? lol). now, I'm rewarded with this. |
19:23:51 | <steering> | Progress: 0.7%, ETA 07h42m17s, 11 GiB written, speed 63.7 MiB/s |
20:17:38 | | szczot3k quits [Quit: The Lounge - https://thelounge.chat] |
20:22:05 | | szczot3k (szczot3k) joins |
21:07:00 | | BPCZ quits [Ping timeout: 260 seconds] |
21:07:51 | | th3z0l4 joins |
21:24:23 | | etnguyen03 quits [Quit: Konversation terminated!] |
21:38:46 | | etnguyen03 (etnguyen03) joins |
22:02:36 | | BPCZ (BPCZ) joins |
22:23:09 | | BlueMaxima joins |
22:52:02 | | HP_Archivist quits [Read error: Connection reset by peer] |
22:52:13 | | HP_Archivist (HP_Archivist) joins |
22:56:58 | | Exorcism quits [Quit: Ping timeout (120 seconds)] |
22:56:58 | | DigitalDragons quits [Quit: Ping timeout (120 seconds)] |
22:57:27 | | DigitalDragons (DigitalDragons) joins |
22:57:27 | | Exorcism (exorcism) joins |
23:46:07 | | etnguyen03 quits [Client Quit] |
23:52:44 | | etnguyen03 (etnguyen03) joins |