Newest at the top
2024-04-28 22:14:28 +0200 | <yin> | that why i sometimes like chatgpt |
2024-04-28 22:14:27 +0200 | _ht | (~Thunderbi@28-52-174-82.ftth.glasoperator.nl) (Remote host closed the connection) |
2024-04-28 22:13:49 +0200 | <tomsmeding> | yin: so that sounds surprisingly accurate, down to the ambiguity |
2024-04-28 22:13:28 +0200 | <[exa]> | ah c'mon we've had rooms in 28000 BC |
2024-04-28 22:13:26 +0200 | <yin> | i asked chatgpt to list all message types in the IRC protocol and it listed NOTICE twice: under User Communication as "send a message that does not trigger automatic responses" and under Miscellaneous as "used for various notifications and alerts" |
2024-04-28 22:13:24 +0200 | <tomsmeding> | fair point |
2024-04-28 22:13:08 +0200 | <tomsmeding> | s/those/that/ |
2024-04-28 22:13:07 +0200 | <yushyin> | matrix has 'rooms' afaik? |
2024-04-28 22:13:04 +0200 | <tomsmeding> | "still using those old radio terminology?" |
2024-04-28 22:12:43 +0200 | <tomsmeding> | tell that to a zoomer discord user |
2024-04-28 22:12:34 +0200 | <tomsmeding> | funny |
2024-04-28 22:12:17 +0200 | <mauke> | I think it's from IRC |
2024-04-28 22:12:08 +0200 | <tomsmeding> | is the use of the word "channel" on matrix, discord, slack, etc. from irc, directly from radio, or unrelated? |
2024-04-28 22:11:53 +0200 | <mauke> | and they used to be numeric |
2024-04-28 22:11:37 +0200 | <mauke> | it's why we speak on "channels" |
2024-04-28 22:11:33 +0200 | <tomsmeding> | perhaps the names were chosen when servers had like 20 people on them |
2024-04-28 22:11:29 +0200 | <mauke> | I mean, IRC started out by emulating CB radio |
2024-04-28 22:11:06 +0200 | <tomsmeding> | that would be something |
2024-04-28 22:11:03 +0200 | <tomsmeding> | lol |
2024-04-28 22:10:58 +0200 | <mauke> | instead of the whole server |
2024-04-28 22:10:43 +0200 | <mauke> | it is only sent to the specified target :-) |
2024-04-28 22:10:08 +0200 | <tomsmeding> | nothing PRIV about a PRIVMSG |
2024-04-28 22:09:26 +0200 | <mauke> | NOTICE ME, SENPAI |
2024-04-28 22:09:22 +0200 | <tomsmeding> | both names are bad actually, NOTICE and PRIVMSG |
2024-04-28 22:09:08 +0200 | <[exa]> | yin: why do people read documentation. :D |
2024-04-28 22:09:07 +0200 | <tomsmeding> | precisely |
2024-04-28 22:09:02 +0200 | <monochrom> | Because "meaningful" names. People look at the name "NOTICE" and start having their own ideas. |
2024-04-28 22:08:35 +0200 | <yin> | makes no sense |
2024-04-28 22:08:32 +0200 | <yin> | why do some clients broadcast them then? |
2024-04-28 22:08:08 +0200 | <mauke> | according to the RFC, NOTICEs are just regular chat messages that are ignored by bots |
2024-04-28 22:07:56 +0200 | <yin> | notices used to go in my aforementioned special window until it started getting spammed by some bot |
2024-04-28 22:07:45 +0200 | <[exa]> | tomsmeding: s/yahb2/yahh2/ compliance fixed |
2024-04-28 22:06:46 +0200 | <ncf> | oh shush |
2024-04-28 22:06:46 +0200 | <tomsmeding> | I suspect it wouldn't go over well if I'd have yahb2 send notices |
2024-04-28 22:06:44 +0200 | <[exa]> | I always thought about notices as a kindof OOB data. "Read this before you get b&" or so. |
2024-04-28 22:06:25 +0200 | <monochrom> | In general, humanity is fundamentally broken, and everything breaks as expected. |
2024-04-28 22:06:17 +0200 | <yin> | i used to broadcast them, but because some bots started using them i stopped doing i |
2024-04-28 22:05:59 +0200 | destituion | (~destituio@2a02:2121:340:2456:fffe:d0f:7737:dd1) |
2024-04-28 22:05:40 +0200 | <yin> | i have configured notices to appear exactly the same as messages except for color |
2024-04-28 22:05:29 +0200 | <monochrom> | By and far, most clients. It is why bot writers stopped using NOTICE. |
2024-04-28 22:05:15 +0200 | <ncf> | aah so if you send a NOTICE to someone with the format [#channel] text then weechat displays it in that channel |
2024-04-28 22:05:09 +0200 | justsomeguy | (~justsomeg@user/justsomeguy) |
2024-04-28 22:04:50 +0200 | <mauke> | s/has a/as a/ |
2024-04-28 22:04:43 +0200 | <mauke> | but some clients instead treat NOTICE has a more important message than PRIVMSG (instead of less important), and beep and alert you about it |
2024-04-28 22:04:25 +0200 | <tomsmeding> | notices appear very differently in my client |
2024-04-28 22:04:23 +0200 | destituion | (~destituio@2001:4644:c37:0:6086:64f4:a213:b80d) (Ping timeout: 268 seconds) |
2024-04-28 22:03:56 +0200 | <mauke> | the only difference is supposed to be that NOTICE should not be processed by bots (and trigger further actions) |
2024-04-28 22:03:55 +0200 | <yin> | i'm not sure if i agree with it myself, but one positive side effect is that notices prevent feedback loops |
2024-04-28 22:03:35 +0200 | <mauke> | the protocol has two messages-sending primitives, PRIVMSG and NOTICE |
2024-04-28 22:03:26 +0200 | <ncf> | ChanServ sends a PvNotice, whatever that is |