HomeSearchPrevious dayNext day

00:06:04jacobk quits [Ping timeout: 240 seconds]
00:06:24qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds]
00:41:28fuzzy8021 quits [Killed (NickServ (GHOST command used by fuzzy802!~fuzzy8021@173.224.25.67))]
00:41:35fuzzy8021 (fuzzy8021) joins
00:49:45<Doranwen>Ah well, I can only imagine someone had a bad day and was taking it out on me. *shrug*
00:50:11<Doranwen>Most of the people replying in both places were very nice and had some good suggestions so I've got a potential solution to try.
01:29:43thetechrobo_ (TheTechRobo) joins
01:53:38jacobk joins
02:04:03le0n quits [Ping timeout: 255 seconds]
03:03:54ThreeHM quits [Ping timeout: 255 seconds]
03:04:14ThreeHM (ThreeHeadedMonkey) joins
03:18:03michaelblob_ (michaelblob) joins
03:21:40michaelblob quits [Ping timeout: 265 seconds]
04:03:18Stiletto quits [Ping timeout: 255 seconds]
04:19:35Stiletto joins
05:21:04mutantm0nkey quits [Remote host closed the connection]
05:21:44mutantm0nkey (mutantmonkey) joins
05:27:27mutantm0nkey quits [Ping timeout: 255 seconds]
05:34:12le0n (le0n) joins
05:36:13mutantm0nkey (mutantmonkey) joins
06:25:05qwertyasdfuiopghjkl joins
07:05:21pabs quits [Quit: Don't rest until all the world is paved in moss and greenery.]
07:11:08pabs (pabs) joins
07:57:44BlueMaxima quits [Read error: Connection reset by peer]
08:00:27Arcorann quits [Ping timeout: 255 seconds]
08:08:46nikow3 joins
08:09:42nikow2 quits [Remote host closed the connection]
08:12:26Arcorann (Arcorann) joins
09:12:12Mateon2 joins
09:12:30Gereon6200 (Gereon) joins
09:12:37Chris50104 (Chris5010) joins
09:12:42Jake1 (Jake) joins
09:13:15balrog quits [Quit: Bye]
09:13:15Chris5010 quits [Client Quit]
09:13:15Gereon620 quits [Client Quit]
09:13:15Jake quits [Quit: Ping timeout (120 seconds)]
09:13:15Mateon1 quits [Remote host closed the connection]
09:13:15shoghicp quits [Excess Flood]
09:13:15Chris50104 is now known as Chris5010
09:13:15Gereon6200 is now known as Gereon620
09:13:15Mateon2 is now known as Mateon1
09:13:15Jake1 is now known as Jake
09:13:16qwertyasdfuiopghjkl quits [Client Quit]
09:13:27Stiletto quits [Remote host closed the connection]
09:13:31shoghicp (shoghicp) joins
09:14:03balrog (balrog) joins
09:17:56Stiletto joins
09:19:22dm4v_ joins
09:19:22dm4v quits [Client Quit]
09:19:36dm4v_ is now known as dm4v
09:25:11Iki1 joins
09:27:16Iki quits [Ping timeout: 240 seconds]
09:40:16Jake quits [Client Quit]
09:40:30Jake (Jake) joins
09:41:58Jake quits [Client Quit]
09:42:11Jake (Jake) joins
09:44:09<Jake>(sorry for the relogs. Some weird issue with service workers or something...)
11:03:35qwertyasdfuiopghjkl joins
11:26:28immibis_ quits [Ping timeout: 240 seconds]
11:27:28immibis_ (immibis) joins
12:28:46qw3rty_ joins
12:31:42qw3rty quits [Ping timeout: 265 seconds]
13:02:42Arcorann quits [Remote host closed the connection]
13:33:16jacobk quits [Ping timeout: 240 seconds]
14:15:38shoghicp quits [Remote host closed the connection]
14:15:55shoghicp (shoghicp) joins
15:03:00jacobk joins
15:34:02mutantm0nkey quits [Remote host closed the connection]
15:35:45mutantm0nkey (mutantmonkey) joins
16:12:24@OrIdow6 quits [Quit: Quitting.]
16:12:45OrIdow6 (OrIdow6) joins
16:12:45@ChanServ sets mode: +o OrIdow6
16:12:46CraftByte quits [Quit: Ping timeout (120 seconds)]
16:13:01CraftByte (DragonSec|CraftByte) joins
16:14:52jacobk quits [Ping timeout: 240 seconds]
16:19:49jacobk joins
16:26:15Stiletto quits [Ping timeout: 255 seconds]
17:15:25dm4v quits [Ping timeout: 265 seconds]
17:27:27tech_exorcist (tech_exorcist) joins
17:28:54dm4v joins
17:49:30sec^nd quits [Ping timeout: 255 seconds]
17:49:42mutantm0nkey quits [Remote host closed the connection]
17:50:14sec^nd (second) joins
17:50:45mutantm0nkey (mutantmonkey) joins
17:52:29<spirit>is there a searchable 4chan archive?
17:56:15jacobk quits [Ping timeout: 255 seconds]
17:58:27jacobk joins
18:19:39jacobk quits [Ping timeout: 255 seconds]
18:36:46<spirit>also, is there a good way to archive a whole twitter thread "tree"? i am in the middle of a weird shitstorm and would like to future proof it
18:41:44michaelblob_ quits [Read error: Connection reset by peer]
18:43:39michaelblob (michaelblob) joins
18:54:39tech_exorcist_ (tech_exorcist) joins
18:55:05tech_exorcist quits [Remote host closed the connection]
19:08:28Gaelan quits [Ping timeout: 240 seconds]
19:23:58Gaelan (Gaelan) joins
19:32:58<@JAA>spirit: snscrape can do it (as long as Twitter doesn't act up). Either via `snscrape twitter-tweet --recursive TWEETID` or through the search with `snscrape twitter-search 'conversation_id:TWEETID'` (where `TWEETID` is the ID of the first tweet in the thread). Reliability of either approach varies because Twitter's weird. The former used to be a bit more stable last time I tested it, but I know that
19:33:04<@JAA>tweet pages sometimes don't contain all replies, so it's still a mess. The search will obviously miss search-banned users' tweets and has a bunch of annoying bugs that also miss tweets.
19:33:34<@JAA>You'll probably want `--jsonl` (global option, so before the `twitter-*` scraper name) to dump it into, well, JSONL.
19:33:56<@JAA>Oh yeah, the recursive thing can be quite slow since it needs to retrieve the page for every tweet in the tree.
19:37:57<spirit>thx!
19:38:51sec^nd quits [Ping timeout: 255 seconds]
19:41:26sec^nd (second) joins
19:45:20jacobk joins
19:50:04jacobk quits [Ping timeout: 240 seconds]
19:50:33jacobk joins
19:51:23tech_exorcist_ quits [Remote host closed the connection]
20:19:05qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds]
20:25:39geezabiscuit quits [Ping timeout: 255 seconds]
20:39:41geezabiscuit (geezabiscuit) joins
21:16:03sec^nd quits [Ping timeout: 255 seconds]
21:20:00sec^nd (second) joins
21:43:04sec^nd quits [Remote host closed the connection]
21:44:59sec^nd (second) joins
22:18:36thetechrobo_ is now known as TheTechRobo
22:56:48Arcorann (Arcorann) joins

HomeSearchPrevious dayNext day