Chat logs of #funderscore for Thursday, 2024-09-26

00:04 *** Quits: Juest/ef (~Juest@rev190-105-167-002.pccp.net.ar) (Read error: Operation timed out)

00:25 *** Joins: danct121/h (~danct12@hackint/user/danct12)

00:25 *** moist/h sets mode: +v danct121/h

00:29 *** Joins: Juest_ (~HxChat@rev190-105-167-002.pccp.net.ar)

00:29 *** irc.andrewyu.org sets mode: +v Juest_

02:21 *** Quits: danct121/h (~danct12@hackint/user/danct12) (Client Quit)

02:24 *** Quits: hax[xor] (~hax[xor]@oper/netadmin) (Client exited)

02:24 *** Quits: hax (root™@netadmin.irc.andrewyu.org) (Ping timeout: -240 seconds)

02:25 *** Quits: DuckServ (\_o<@services.irc.vitali64.duckdns.org) (*.net *.split)

02:26 *** Joins: DuckServ (\_o<@services.irc.vitali64.duckdns.org)

02:26 *** fun.irc.runxiyu.org sets mode: +o DuckServ

02:26 *** Joins: hax[xor] (~hax[xor]@oper/netadmin)

02:26 *** irc.runxiyu.org sets mode: +ao hax[xor] hax[xor]

02:43 *** Joins: danct121/h (~danct12@hackint/user/danct12)

02:43 *** moist/h sets mode: +v danct121/h

03:34 <[R]/h> https://fdc.nal.usda.gov/api-guide.html <-- neato

08:14 <danct121/h> f_[x]: what's a local channel?

08:15 <danct121/h> i noticed there's '&' '!' '+'

08:25 <JAA/h> # is a regular network-wide channel. & is a local server channel. ! has something to do with netsplits. + is an unmoderated channel. # and & are part of the original RFC and should exist pretty much on all IRC networks. ! and + are far less common.

08:28 <danct121/h> can you name a network that supports '!' and '+'?

08:29 <JAA/h> Nope. None that I'm on, I think.

08:31 <danct121/h> wow

08:31 <hax[xor]> sure I can name one! rx even "supports" username-is-channel (in both directions). (in a very broken sense, due to the plentiful protocol violations involved)

08:32 <hax[xor]> s/username/nick/

08:32 * JAA/h is wholly unsurprised.

08:33 <JAA/h> I'd check netsplit.de, but I'm pretty sure CHANTYPES is broken there.

08:35 *** Danct12 is now known as #danct12

08:37 *** hax[xor] is now known as #hax[xor]

08:37 *** #hax[xor] is now known as hax[xor]

08:40 <danct121/h> https://netsplit.de/networks/w3.org/

08:40 <danct121/h> looks like w3c irc network supports +

08:51 <danct121/h> a little question

08:52 <danct121/h> looking at netsplit.de i noticed many irc networks also run irc on different ports

08:52 <danct121/h> i guess that workaround firewalls?

08:53 <danct121/h> i do know that some firewalls blocks IRC ports by default due to malware using irc as c&c center

08:53 <danct121/h> but that's probably the past

08:53 <hax[xor]> also useful for running multiple on the same host

08:53 <hax[xor]> (with the same address, of course)

09:02 <danct121/h> added support for the two rarest channel prefix

09:02 <danct121/h> just because i can

09:07 <JAA/h> Rarest? So . and ~? (I have never seen these anywhere except in lists of channel types.)

09:07 <JAA/h> They're specific to some particular ircd, IIRC.

09:08 <JAA/h> Yeah, KineIRCd.

09:09 <danct121/h> i personally would stay close with ircdocs and the rfc as possible i can

09:09 <JAA/h> ! and + aren't in the modern IRC horse. :-)

09:10 <JAA/h> They are technically in RFC 2811, but nobody uses the 281x RFCs.

09:11 <danct121/h> i did read rfc 2811, that's why i asked about these channel types

09:12 <danct121/h> and also w3c irc network uses '+', so it exists and is being used

09:12 <JAA/h> The problem with RFCs 281x is that they tried to document the state of IRC but then also added stuff on top and are just all kinds of weird.

09:12 <JAA/h> So yes, ! and + exist, but not because they're in 2811; they're in there because they already existed.

09:14 <JAA/h> The advice I've been given by seasoned veterans in IRC software and standard development has been to forget that RFCs 281x even exist.

09:14 <danct121/h> well then

09:15 <danct121/h> i guess i should just stick with ircdocs horse?

09:16 <JAA/h> Yeah, that's the best description of how IRC actually works nowadays.

09:17 <danct121/h> got it

09:18 <danct121/h> it's just a switch case anyway so eh.

09:18 <danct121/h> doesnt hurt to add the last two.

09:18 <katia/ef> how do irc work

09:18 <danct121/h> idk

09:18 <danct121/h> you tell me.

09:19 <katia/ef> i open the irc and there is little people in it

09:37 <danct121/h> updated the echo example with the new features

09:38 <danct121/h> split.

11:04 <f_[x]> JAA: EFnet has &channels, IRCnet has !channels

11:05 <f_[x]> But yeah only # and & are usually to be seen - # is a network-wide chan and & server-wide

11:06 <JAA/h> Ah yeah, IRCnet, right. Not sure I've ever even connected to it.

13:29 *** Quits: danct121/h (~danct12@hackint/user/danct12) (Quit: WeeChat 4.4.2)

14:17 *** Quits: tweezers (~tweezers@103.108.229.52) (Connection closed)

14:18 *** Joins: tweezers (~tweezers@103.108.229.52)

14:22 *** Quits: tweezers (~tweezers@103.108.229.52) (Connection closed)

14:22 *** Joins: tweezers (~tweezers@103.108.229.52)

14:26 *** Quits: tweezers (~tweezers@103.108.229.52) (Connection closed)

14:27 *** Joins: tweezers (~tweezers@103.108.229.52)

14:29 *** Quits: tweezers (~tweezers@103.108.229.52) (Connection closed)

14:30 *** Joins: tweezers (~tweezers@103.108.229.52)

14:44 *** Quits: tweezers (~tweezers@103.108.229.52) (Connection closed)

14:44 *** Joins: tweezers (~tweezers@103.108.229.52)

15:26 *** Joins: tester3 (~tester@tor/onion)

15:28 *** Quits: tester2 (~tester@tor/onion) (Ping timeout: 240 seconds)

15:33 *** Quits: tweezers (~tweezers@103.108.229.52) (Connection closed)

15:33 *** #danct12 is now known as Danct12

15:34 *** Joins: tweezers (~tweezers@103.108.229.52)

16:19 <f_/ef> Danct12 Why do you need to check CHANTYPES

16:19 <f_/ef> I mean why do you need to check channel prefix at all

16:19 <f_/ef> If you really need to, just parse ISUPPORT CHANTYPES instead of hardcoding

17:44 *** Joins: Juest__ (~HxChat@rev190-105-167-002.pccp.net.ar)

17:44 *** irc.andrewyu.org sets mode: +v Juest__

17:47 *** Joins: Juest/ef (~Juest@rev190-105-167-002.pccp.net.ar)

17:47 *** f_|aop/ef sets mode: +o Juest/ef

17:50 *** Quits: Juest_ (~HxChat@rev190-105-167-002.pccp.net.ar) (Ping timeout: 240 seconds)

17:50 *** Quits: Juesto/ef (~Juest@rev190-105-167-002.pccp.net.ar) (Read error: Operation timed out)

18:59 *** Joins: Juest_ (~HxChat@rev190-105-167-002.pccp.net.ar)

18:59 *** irc.andrewyu.org sets mode: +v Juest_

19:02 *** Joins: Juesto/ef (~Juest@rev190-105-167-002.pccp.net.ar)

19:02 *** f_|aop/ef sets mode: +o Juesto/ef

19:02 *** Joins: hax (root™@netadmin.irc.andrewyu.org)

19:05 *** Quits: Juest__ (~HxChat@rev190-105-167-002.pccp.net.ar) (Ping timeout: 240 seconds)

19:08 *** Quits: Juest/ef (~Juest@rev190-105-167-002.pccp.net.ar) (Ping timeout: 630 seconds)

19:20 *** Joins: Juest__ (~HxChat@host-190-210-32-19.iplanisp.com.ar)

19:20 *** irc.andrewyu.org sets mode: +v Juest__

19:23 *** Joins: Juest/ef (~Juest@rev190-105-167-002.pccp.net.ar)

19:23 *** f_|aop/ef sets mode: +o Juest/ef

19:27 *** Quits: Juest_ (~HxChat@rev190-105-167-002.pccp.net.ar) (Ping timeout: 240 seconds)

19:27 *** Joins: Juest_ (~HxChat@rev190-105-167-002.pccp.net.ar)

19:27 *** irc.andrewyu.org sets mode: +v Juest_

19:28 *** Quits: Juest__ (~HxChat@host-190-210-32-19.iplanisp.com.ar) (Ping timeout: 240 seconds)

19:29 *** Quits: Juesto/ef (~Juest@rev190-105-167-002.pccp.net.ar) (Read error: Operation timed out)

19:43 *** Quits: hax[xor] (~hax[xor]@oper/netadmin) (Quit: e)

19:43 *** Quits: hax (root™@netadmin.irc.andrewyu.org) (Ping timeout: -240 seconds)

19:44 *** Joins: hax[xor] (~hax[xor]@oper/netadmin)

19:46 *** Joins: Juesto/ef (~Juest@rev190-105-167-002.pccp.net.ar)

19:46 *** f_|aop/ef sets mode: +o Juesto/ef

19:49 *** Quits: Juest_ (~HxChat@rev190-105-167-002.pccp.net.ar) (Ping timeout: 240 seconds)

19:50 *** Quits: Juest/ef (~Juest@rev190-105-167-002.pccp.net.ar) (Read error: Operation timed out)

20:01 *** Quits: hax[xor] (~hax[xor]@oper/netadmin) (Quit: e)

20:01 *** Joins: hax[xor] (~hax[xor]@oper/netadmin)

20:02 *** Quits: DuckServ (\_o<@services.irc.vitali64.duckdns.org) (*.net *.split)

20:02 *** Joins: DuckServ (\_o<@services.irc.vitali64.duckdns.org)

20:02 *** fun.irc.runxiyu.org sets mode: +o DuckServ

20:03 *** Joins: Juest/ef (~Juest@rev190-105-167-002.pccp.net.ar)

20:03 *** f_|aop/ef sets mode: +o Juest/ef

20:10 *** Quits: Juesto/ef (~Juest@rev190-105-167-002.pccp.net.ar) (Read error: Operation timed out)

23:13 *** Quits: hax[xor] (~hax[xor]@oper/netadmin) (Client exited)

23:30 *** Joins: hax[xor] (~hax[xor]@oper/netadmin)

23:31 *** Quits: DuckServ (\_o<@services.irc.vitali64.duckdns.org) (*.net *.split)

23:31 *** Joins: DuckServ (\_o<@services.irc.vitali64.duckdns.org)

23:31 *** fun.irc.runxiyu.org sets mode: +o DuckServ

23:50 *** Quits: hax[xor] (~hax[xor]@oper/netadmin) (Client exited)

23:50 <[R]/h> https://web.archive.org/web/20240926212028/https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/index.html

23:51 *** Quits: f_/ef (Unk@195-15-242-30.dc3-a.pub1.etik-cloud.com) (*.net *.split)

23:51 *** Quits: f_[x]/ef (~fun@scarlet.mboa.dev) (*.net *.split)

23:51 *** Quits: katia/ef (znc@2001:41d0:a:14d8:ca75:ca75:ca75:ca75) (*.net *.split)

23:51 *** Quits: f_|aop/ef (~haha@195-15-242-30.dc3-a.pub1.etik-cloud.com) (*.net *.split)

23:51 *** Quits: fol/ef (fire@static.96.98.78.5.clients.your-server.de) (*.net *.split)

23:51 *** Quits: Juest/ef (~Juest@rev190-105-167-002.pccp.net.ar) (*.net *.split)

23:51 *** Quits: aop/ef (aop@vps-9bde1a96.vps.ovh.net) (*.net *.split)

23:51 *** Quits: Noisytoot/ef (noisytoot@not.eris.berkeley.edu.pl) (*.net *.split)

23:51 *** Quits: JAA/ef (~JAA@ns531958.ip-192-99-9.net) (*.net *.split)