00:00:51Wingy1 quits [Remote host closed the connection]
00:01:43Wingy1 (Wingy) joins
00:04:58<TheTechRobo>JAA: > When this capability is enabled, clients will be sent an AWAY message when a user sharing a channel with them sets, changes or removes their away state, as well as when a user joins and has an away message set. (Note that AWAY will not be sent for joining users with no away message set.)
00:05:05<TheTechRobo>Wouldn't that send a msg anyway?
00:05:27<@JAA>Well, no, it wouldn't send a PRIVMSG.
00:05:53<@JAA>It sends an AWAY line, and then the client can handle that accordingly, e.g. greying out the corresponding nickname or whatever.
00:06:02<TheTechRobo>Oh it sent a PM???
00:06:06<TheTechRobo>That's quite stupid
00:06:13<@JAA>This is a PRIVMSG.
00:06:21<@JAA>It's 'private' to this channel.
00:06:37<@JAA>(At least that's where I think the name comes from.)
00:07:10<TheTechRobo>So a message sent in a channel is a PRIVMSG?
00:07:12<@JAA>Any normal message you receive on IRC is a PRIVMSG, whether in a channel or via PM.
00:07:17<TheTechRobo>Ah
00:07:37<@JAA>There's also NOTICE, and you'd see that e.g. from ChanServ when joining this channel or a few others where it's configured.
00:07:41<TheTechRobo>So what would it send? Something similar to the "x has quit (Blahblah)"
00:07:49<@JAA>This is a notice.
00:08:20<@JAA>The away-notify thing sends a separate message type, AWAY.
00:08:29<TheTechRobo>that makes sense
00:08:36<TheTechRobo>Speaking of IRCv3
00:08:50<TheTechRobo>For some stupid reason, this 2021 distro ships with Xchat instead of hexchat or smth
00:08:56<@JAA>So it's a standardised way how people can signal their status, and clients that don't support it will simply not receive that message at all.
00:09:04<TheTechRobo>1. it sounds like a porn site 2. it's old af
00:09:08<TheTechRobo>JAA: Ahhhhhhh
00:09:35<@JAA>And those that do support it won't display it as a normal message but likely only update the nicklist display.
00:09:46<@JAA>At least typically, implementations vary obviously.
00:10:05<@JAA>XChat is what HexChat was forked from.
00:10:11<TheTechRobo>Ik
00:10:15<@JAA>It's *ancient*.
00:10:16<TheTechRobo>Still insanely old tho
00:10:28<TheTechRobo>Yeah, I checked the website. Last release was in 2010
00:10:46<@JAA>What distro is that?
00:10:55<TheTechRobo>Elive
00:11:35<pabs>elive should have hexchat available too, IIRC it is based on Debian, which has both
00:12:05<pabs>er, had both, xchat got removed before bullseye
00:12:06<TheTechRobo>pabs: yeah, but I'm too lazy to do all the reconfigs. it ships xchat by default, anyway
00:12:17pabs sigh
00:12:24<TheTechRobo>https://forum.elivelinux.org/t/xchat-vs-hexchat/517 <- forum thread from 2018 about adding it
00:14:57<@JAA>There's an open CVE for XChat from 2013...
00:15:17<@JAA>(Lack of certificate validation)
00:32:38<HP_Archivist>TheTechRobo: Nvm, I fixed it. Had to reinstall my Ubuntu config on Windows. Seems to be working again without error
00:57:39<HP_Archivist>Hm. No error, but the output while downloading/uploading in the terminal is full of random characters/syntax stuff. Nobody here uses tubeup on Windows?
01:00:41dm4v quits [Read error: Connection reset by peer]
01:02:56dm4v joins
01:02:58dm4v quits [Changing host]
01:02:58dm4v (dm4v) joins
01:37:45<HP_Archivist>e.g. maybe someone can help https://imgur.com/a/dXNrL2A
01:38:11<HP_Archivist>Seems to finish correctly but in previously using tubeup, it would not display like this
01:39:05<@JAA>Direct link because Imgur sucks: https://i.imgur.com/Hg1F8F8.jpeg
01:39:27<HP_Archivist>Ahh. Thanks JAA ^
01:42:35<HP_Archivist>Prior to tonight, that error I was getting looked like this which is on the list of bugs https://github.com/bibanon/tubeup/issues/172
01:43:02<HP_Archivist>That's now resolved and the output is all a bunch of nonsense (but still oddly uploads correctly)
02:02:20dm4v quits [Read error: Connection reset by peer]
02:03:12dm4v joins
02:03:14dm4v quits [Changing host]
02:03:14dm4v (dm4v) joins
02:20:46ddd quits [Client Quit]
02:20:54qwertyasdfuiopghjkl87 joins
02:22:04qwertyasdfuiopghjkl quits [Ping timeout: 244 seconds]
02:45:28paul2520 quits [Remote host closed the connection]
03:06:55qwertyasdfuiopghjkl87 is now known as qwertyasdfuiopghjkl
03:20:15HP_Archivist quits [Ping timeout: 258 seconds]
03:21:58ThreeHM quits [Ping timeout: 252 seconds]
03:23:50ThreeHM (ThreeHeadedMonkey) joins
03:53:06pabs quits [Quit: Don't rest until all the world is paved in moss and greenery.]
03:53:29monoxane quits [Read error: Connection reset by peer]
03:54:09monoxane (monoxane) joins
03:55:08pabs (pabs) joins
04:21:53qw3rty__ joins
04:25:48qw3rty_ quits [Ping timeout: 258 seconds]
05:27:21fuzzy8021 quits [Killed (NickServ (GHOST command used by fuzzy802!~fuzzy8021@173-224-26-244.ptcnet.net))]
05:27:28fuzzy8021 (fuzzy8021) joins
05:41:40fuzzy8021 quits [Read error: Connection reset by peer]
05:49:53fuzzy8021 (fuzzy8021) joins
06:03:41BlueMaxima quits [Read error: Connection reset by peer]
06:40:05Stiletto quits [Remote host closed the connection]
06:40:17Stiletto joins
07:01:18Stilett0 joins
07:03:22Stiletto quits [Ping timeout: 265 seconds]
07:03:44sec^nd quits [Ping timeout: 258 seconds]
07:08:29sec^nd (second) joins
07:29:52Wingy1 quits [Read error: Connection reset by peer]
07:30:52Wingy1 (Wingy) joins
07:34:25Wingy1 quits [Remote host closed the connection]
07:35:12Wingy1 (Wingy) joins
08:00:07britmob256364 quits [Quit: britmob256364]
08:40:20monoxane4 (monoxane) joins
08:42:56monoxane quits [Ping timeout: 265 seconds]
08:42:57monoxane4 is now known as monoxane
09:19:38useretail_ joins
09:19:38useretail quits [Read error: Connection reset by peer]
09:28:48qwertyasdfuiopghjkl quits [Client Quit]
09:32:12qwertyasdfuiopghjkl joins
11:28:08sec^nd quits [Remote host closed the connection]
11:28:31sec^nd (second) joins
11:53:00Wingy1 quits [Remote host closed the connection]
11:54:06Wingy1 (Wingy) joins
11:57:52monoxane quits [Ping timeout: 252 seconds]
12:05:44britmob2563647 joins
12:59:34Wingy1 quits [Remote host closed the connection]
13:00:31Wingy1 (Wingy) joins
13:07:39HP_Archivist (HP_Archivist) joins
13:46:54paul2520 (paul2520) joins
14:01:06<spirit>man, youtube ip-throttles like crazy if you go over some thresholds with youtube-dl
14:01:13<spirit>locked to ~60KB/s now
14:02:43Arcorann quits [Ping timeout: 258 seconds]
14:10:10Wingy1 quits [Remote host closed the connection]
14:11:01Wingy1 (Wingy) joins
15:32:14<h3ndr1k>I had that too some time ago. But it seems that there is a new JavaScript challenge in the website, which enables YouTube to distinguish between youtube-dl and a webuser.
15:32:14<h3ndr1k>I noticed that yt-dlp solved that problem and you can get normal speed using that.
15:33:04<h3ndr1k>Maybe give that a try
15:34:46<spirit>ah nice, thanks
15:34:56<spirit>i was wondering why browser streaming was fine
15:42:16<HP_Archivist>h3ndr1k: Any idea why I'm getting json dictionaries like in the imgur pic I posted above?
15:42:36<HP_Archivist>Tubeup videos are uploading to IA fine but the output is spitting out these json strings for some reason all of a sudden
15:45:55<h3ndr1k>I never used Tubeup. No idea
15:47:24<HP_Archivist>No worries
16:09:31Wingy1 quits [Remote host closed the connection]
16:10:24Wingy1 (Wingy) joins
16:24:43Wingy1 quits [Remote host closed the connection]
16:25:36Wingy1 (Wingy) joins
16:34:09Wingy1 quits [Remote host closed the connection]
16:35:21Wingy1 (Wingy) joins
16:55:26Wingy1 quits [Remote host closed the connection]
16:56:15Wingy1 (Wingy) joins
17:10:33HackMii quits [Ping timeout: 258 seconds]
17:28:50G4te_Keep3r4 joins
17:28:58G4te_Keep3r quits [Ping timeout: 252 seconds]
17:28:58G4te_Keep3r4 is now known as G4te_Keep3r
17:38:51HackMii (hacktheplanet) joins
17:39:14Wingy1 quits [Remote host closed the connection]
17:40:08Wingy1 (Wingy) joins
17:47:24LeGoupil joins
18:34:53HP_Archivist quits [Ping timeout: 258 seconds]
18:38:45HP_Archivist (HP_Archivist) joins
18:54:51Wingy1 quits [Read error: Connection reset by peer]
18:55:44Wingy1 (Wingy) joins
19:49:18HP_Archivist quits [Read error: Connection reset by peer]
19:51:58HP_Archivist (HP_Archivist) joins
20:03:26qwertyasdfuiopghjkl quits [Remote host closed the connection]
20:22:54AlsoHP_Archivist joins
20:26:26HP_Archivist quits [Ping timeout: 258 seconds]
20:28:11Wingy1 quits [Remote host closed the connection]
20:29:03Wingy1 (Wingy) joins
20:30:17AlsoHP_Archivist quits [Client Quit]
21:22:02LeGoupil quits [Client Quit]
21:59:14Stilett0 is now known as Stiletto
22:15:54Wingy1 quits [Remote host closed the connection]
22:16:48Wingy1 (Wingy) joins
22:30:54Wingy1 quits [Remote host closed the connection]
22:31:43Wingy1 (Wingy) joins
22:51:27BlueMaxima joins
22:53:22TheTechRobo quits [Remote host closed the connection]
23:00:54Wingy1 quits [Remote host closed the connection]
23:00:56Arcorann (Arcorann) joins
23:01:52Wingy1 (Wingy) joins
23:05:27driib7 quits [Read error: Connection reset by peer]
23:05:43driib7 (driib) joins
23:15:06Wingy1 quits [Remote host closed the connection]
23:15:58Wingy1 (Wingy) joins
23:46:40Wingy1 quits [Remote host closed the connection]
23:47:32Wingy1 (Wingy) joins
23:52:39HP_Archivist (HP_Archivist) joins