Chat logs of #funderscore for Sunday, 2024-09-29

01:16 <rx> hax[xor]: if you go with password hashing, go with argon2

01:30 <hax[xor]> rx: is there any reason I'd actually need to follow GDPR here really? I could make some stuff optional and such, with the downsides involved of the varying methods

01:32 <rx> hax[xor]: users connecting from the EU

01:33 <hax[xor]> rx: does that actually get to apply if neither servers nor hosts are in the EU?

01:33 <rx> yep

01:33 <rx> if we serve EU users

01:33 <hax[xor]> rx: sounds like a great idea™ to make everyone follow the local laws of the users' local country

01:33 <hax[xor]> like, what if some country states that serving IRC stuff is illegal? yay!

01:35 <rx> hax[xor]: they would block our service

01:35 <hax[xor]> really, it's literally out of their jurisdiction to enforce their laws on someone not even related

01:36 <hax[xor]> that'd be a fair option

01:36 <rx> yep

01:36 <rx> i guess

01:36 <hax[xor]> so yeah it'd be "risk EU users not being able to connect if the EU decides to care"

01:36 <hax[xor]> if not following gdpr

01:36 <hax[xor]> which yeah is an issue for here

01:37 <rx> yeah

07:06 *** Joins: tweezers (~tweezers@103.108.229.68)

08:10 *** Quits: tweezers (~tweezers@103.108.229.68) (Ping timeout: 240 seconds)

08:16 <f_> hax[xor]: irc.andrewyu.org was originally in EU, too

08:16 <f_> Now it's in canada I think

08:16 <f_> no idea about runxiyu.org

08:16 <hax[xor]> canada or us, idr which, and no idea on runxiyu.org

08:16 <hax[xor]> I think they were both in the same region though

08:17 <f_> > Motd --   packages written by hax[xor] and runxiyu as well as a chat bridge.  This

08:17 <f_> > Motd --   server is located in Canada.  See <https://irc.andrewyu.org/> for guides.

08:17 <hax[xor]> and I don't get cross-continent latencies to it anyways

08:17 <f_> Might need to reword the motd tbh

08:17 <hax[xor]> so it can't be off the americas

08:17 <f_> my server is located in Europe, too

08:18 *** Joins: tweezers (~tweezers@103.108.229.68)

08:18 <f_> and I do want to link it to rx

08:18 <f_> one day...

08:46 *** f_ sets mode: +qo f_[x] f_[x]

08:53 <rx> It used to be in Germany

08:54 <f_/h> rx yup

10:32 <Danct12/h> hi f_

10:32 <f_/h> hi Danct12

10:32 <f_/h> How are things going?

10:34 <Danct12/h> f_, good

10:34 <Danct12/h> u

10:34 <Danct12/h> ?

10:34 <f_> good good

10:35 <rx> macOS's calendar.app decided to segfault on me

10:35 <Danct12/h> 17:35:32 up 36 days, 23:08,  2 users,  load average: 0.38, 0.28, 0.34

10:35 <f_> rx: yay!

10:35 *** f_ sets mode: +ao rx rx

10:36 <Danct12/h> warning: amd-ucode: ignoring package upgrade (20240703.e94a2a3b-1 => 20240909.552ed9b8-1)

10:36 <Danct12/h> warning: lib32-nvidia-utils: ignoring package upgrade (555.58.02-1 => 560.35.03-1)

10:36 <Danct12/h> warning: libxnvctrl: ignoring package upgrade (555.58.02-1 => 560.35.03-1)

10:36 <Danct12/h> warning: linux: ignoring package upgrade (6.10.3.arch1-2 => 6.10.10.arch1-1)

10:36 <Danct12/h> warning: linux-firmware: ignoring package upgrade (20240703.e94a2a3b-1 => 20240909.552ed9b8-1)

10:36 <Danct12/h> warning: linux-firmware-whence: ignoring package upgrade (20240703.e94a2a3b-1 => 20240909.552ed9b8-1)

10:36 <Danct12/h> warning: linux-headers: ignoring package upgrade (6.10.3.arch1-2 => 6.10.10.arch1-1)

10:36 <Danct12/h> warning: nvidia-dkms: ignoring package upgrade (555.58.02-1 => 560.35.03-3)

10:36 <Danct12/h> warning: nvidia-settings: ignoring package upgrade (555.58.02-1 => 560.35.03-1)

10:36 <Danct12/h> warning: nvidia-utils: ignoring package upgrade (555.58.02-1 => 560.35.03-3)

10:36 <Danct12/h> warning: opencl-nvidia: ignoring package upgrade (555.58.02-1 => 560.35.03-3)

10:39 <f_> eh

10:49 <Danct12/h>      #               Uptime | System                                     Boot up

10:49 <Danct12/h> ----------------------------+---------------------------------------------------

10:49 <Danct12/h> ->   1    36 days, 23:22:09 | Linux 6.10.3-arch1-2      Fri Aug 23 18:27:07 2024

10:49 -eggdrop/h- [karma] '----------------------------+-------------------------------------------------' now has -1 karma!

10:54 <Danct12/h> i show my presence you run away and fear the ghosts

10:58 <JAA/h> >  10:58:31 up 2655 days, 16:37

10:59 <Danct12/h> that's a server somewhere, isnt it

10:59 <JAA/h> Yup

11:00 <JAA/h> It'll be a sad day when I have to shut it off.

11:00 <Danct12/h>     up   566 days, 22:12:05 | since                     Thu Aug 18 18:39:23 2022

11:00 <Danct12/h>   down   206 days, 01:09:00 | since                     Thu Aug 18 18:39:23 2022

11:00 <Danct12/h>    %up               73.343 | since                     Thu Aug 18 18:39:23 2022

11:01 <hax[xor]> step one write bug-free kernel

11:02 <JAA/h> Yeah, loots of mitigations had to be deployed to keep it up. It's been fun.

11:03 <f_/h> ----------------------------+-------------------------------------------------++

11:03 -eggdrop/h- [karma] '----------------------------+-------------------------------------------------' now has 0 karma!

11:51 <f_/ef> hmm senpai has a /ban command

11:51 *** f_/ef sets mode: +b f_|aop!*@*

11:51 <f_/ef> ah

11:51 <f_/ef> doesn't kick?

11:51 <f_/ef> https://todo.sr.ht/~delthas/senpai/163

11:51 <f_/ef> uhhhh

11:51 *** f_/ef sets mode: -b f_|aop!*@*

11:53 <rx> Why would you want a kick?

11:53 <rx> but fine

11:53 <f_/ef> rx: because when I ban someone I want to kick them as well?

11:53 <rx> not always how I do things

11:54 <hax[xor]> kickban != ban

11:54 <f_/ef> but eh, I always used manual `/mode +b` and `/kick`.

11:54 <rx> hax[xor]: I would prefer it to be called /bankick

11:54 <f_/ef> hax[xor] Yeah, maybe there could be a /kickban command insteads

11:54 <hax[xor]> rx: true

11:54 <hax[xor]> ~~or we should just comply with naming and add race conditions~~

11:55 <f_/ef> you can always /kick and then /mode +b..

11:55 <f_/ef> Some do it that way

11:55 <rx> f_/ef: Race condition :P

11:55 <hax[xor]> ^

11:55 <f_/ef> of course

11:55 <f_/ef> for example:

11:55 <f_> hax[xor]: do you still have autorejoin configured?

11:55 <hax[xor]> though they've all got race conditions

11:56 <hax[xor]> f_: yeah

11:56 *** hax[xor] was kicked by f_ (you're banned!)

11:56 *** Joins: hax[xor] (~hax[xor]@oper/netadmin)

11:56 *** irc.runxiyu.org sets mode: +ao hax[xor] hax[xor]

11:56 *** f_ sets mode: +b hax[xor]!*@*

11:56 <f_> ^ see?

11:56 <rx> hax[xor]: Meh, bankick doesn't really have a race condition

11:56 <rx> Or is there something I'm unaware of?

11:56 *** f_ sets mode: -b hax[xor]!*@*

11:56 <f_> while:

11:56 *** f_ sets mode: +b hax[xor]!*@*

11:56 *** hax[xor] was kicked by f_ (you're banned!)

11:56 <f_> this works

11:56 *** f_ sets mode: -b hax[xor]!*@*

11:57 *** Joins: hax[xor] (~hax[xor]@oper/netadmin)

11:57 *** irc.runxiyu.org sets mode: +ao hax[xor] hax[xor]

11:57 <hax[xor]> for instance: ban someone!ident@host_a, someone!ident@host_a disconnects, someone!ident@host_b connects and joins, kick someone

11:57 <f_> hax[xor]: does that ever really happen?

11:57 <rx> Ah

11:58 <hax[xor]> it's really just a race condition with kick itself though

11:58 <hax[xor]> but the ban adds to the interval

11:59 <hax[xor]> anyways, bankick > kickban, but both can misbehave

12:00 <rx> hax[xor]: IMO UIDs should be exposed to the client protocol

12:01 <rx> hax[xor]: Would still be an issue if a server restarts though

12:01 <hax[xor]> UCIDs are also a problem

12:01 <hax[xor]> pretending UCIDs don't collide without a server restart is also a problem

12:01 <rx> Welllll

12:01 <rx> Yes

12:01 <hax[xor]> unless you want to enact forced server restarts

12:01 <rx> What's your recommendation

12:01 <hax[xor]> unsure

12:02 <hax[xor]> "base it on HaxIRCd mesh protocol"

12:02 <rx> "doesn't exactly solve the issue"

12:02 <hax[xor]> it does, since that protocol is going to have to put up with and not break with my insanity :P

12:03 <hax[xor]> the "minor" issue is that it doesn't exist yet

12:03 <hax[xor]> f_: also, don't bother with inviting me to here

12:04 <hax[xor]> I'm likely to not notice the invite till long after it's irrelevant and it never really had an effect :P

12:05 <hax[xor]> likewise if you want me to join some new channel, pinging me about it is the more effective way of getting me to notice

12:05 <hax[xor]> SAJOIN would be good if it wasn't for weechat acting undesirably with it

12:08 <hax[xor]> speaking of which

12:08 <hax[xor]> there's probably desyncable stuff with server reconnects

12:08 <hax[xor]> with inspircd's protocol

12:09 <hax[xor]> sever restarts rather, but maybe both

12:15 <hax[xor]> actually, it's probably even abusable to get some services to set your metadata accountname to someone else's, so R:<acc> stuff all breaks :P mostly untargeted and there needs to be enough latency and a restarting ircd that has both you and the target and maybe some other factors

12:17 <hax[xor]> but you can theoretically catch a `METADATA <UID> accountname runxiyu' or such on the lines while the server restarts, making it apply to whoever gets the UID in time for it to arrive on the server

12:19 <hax[xor]> anything on the side where the METADATA arrived before the netsplit+reconnect would stay in sync, anything on the other side would desync

13:18 <f_/ef> https://www.mibbit.com/

13:18 <f_/ef> > On the 30th of August, Mibbit will be shutting down.

13:18 <f_/ef> We're in september, Mibbit is still up.

13:24 <Noisytoot/ef> rx: UIDs should not be exposed to the client protocol because they do not have to exist

13:24 <Noisytoot/ef> I wrote a third-party unrealircd module that adds a letspiss.net/id client tag with the UID/SID of the sender

13:25 <Noisytoot/ef> https://raw.githubusercontent.com/pissnet/pissircd/refs/heads/piss60/src/modules/third/id-tag.c

13:47 <f_> Noisytoot: Do you not have access to your ZNC anymore?

14:32 *** Joins: Elestren (bot@andrewyu.org)

14:32 *** f_ sets mode: +h Elestren

14:32 <f_> ?

14:32 <f_> Elestren: messageparser add \\o/ "echo \o/"

14:32 <Elestren> f_: The operation succeeded.

14:32 <f_> \o/

14:32 <Elestren> \o/

14:33 <f_> Elestren: messageparser add test "echo Test failed successfully"

14:33 <Elestren> f_: The operation succeeded.

14:33 <f_> test

14:33 <Elestren> Test failed successfully

14:33 <f_> replicating vdoIRC's stuff with Elestren

14:33 <f_> DuckServ might go one day

14:34 <f_> Elestren: funderscore ??

14:34 <Elestren> he sucks

14:34 <f_> Elestren: what is<REPLY>I wish I knew :^)

14:34 <Elestren> f_: Error: "what" is not a valid command.

14:34 <f_> Elestren: what is <REPLY>I wish I knew :^)

14:34 <Elestren> f_: The operation succeeded.

14:35 <f_> Elestren: what

14:35 <Elestren> what is <REPLY>I wish I knew :^)

14:35 <f_> Elestren: del what

14:35 <Elestren> f_: Error: "del" is not a valid command.

14:35 <f_> Elestren: delete what

14:35 <Elestren> f_: Error: "delete" is not a valid command.

14:35 <f_> Elestren: help Factoid

14:35 <Elestren> f_: Error: There is no command "factoid".

14:35 <f_> Elestren: help Factoids

14:35 <Elestren> f_: Error: There is no command "factoids".

14:35 <f_> Elestren: list Factoids

14:35 <Elestren> f_: Error: 'Factoids' is not a valid plugin.

14:35 <f_> Elestren: list

14:35 <Elestren> f_: Admin, AutoMode, ChanTracker, Channel, Config, Ctcp, Filter, MessageParser, Misc, MoobotFactoids, Network, NickAuth, Owner, QuoteGrabs, RSS, Services, Unix, User, and Utilities

14:35 <f_> Elestren: list MoobotFactoids

14:35 <Elestren> f_: factinfo, listauth, listkeys, listvalues, literal, lock, most, random, remove, and unlock

14:35 <f_> Elestren: remove what

14:35 <Elestren> f_: Error: The command "remove" is available in the MessageParser, MoobotFactoids, and RSS plugins.  Please specify the plugin whose command you wish to call by using its name as a command before "remove".

14:35 <f_> Elestren: MoobotFactoids remove what

14:35 <Elestren> f_: The operation succeeded.

14:35 <f_> Elestren: what is <reply> I wish I knew :^)

14:35 <Elestren> f_: The operation succeeded.

14:35 <f_> Elestren: what

14:35 <Elestren> I wish I knew :^)

14:35 <f_> Elestren: what is this?

14:35 <Elestren> f_: Error: Factoid "what" already exists.

14:35 <f_> Elestren: what is this

14:35 <Elestren> f_: Error: Factoid "what" already exists.

14:36 <f_> Elestren: what  is this

14:36 <Elestren> f_: Error: Factoid "what" already exists.

14:36 <f_> Elestren: what  this

14:36 <Elestren> f_: Error: "what" is not a valid command.

14:36 <f_> Elestren: what ??

14:36 <Elestren> I wish I knew :^)

14:36 <f_> Elestren: messageparser add hi "echo greetings!"

14:36 <Elestren> f_: The operation succeeded.

14:36 <f_> Elestren: messageparser add welcome "echo greetings!"

14:36 <Elestren> f_: The operation succeeded.

14:36 <f_> Elestren: messageparser add hello "echo greetings!"

14:36 <Elestren> f_: The operation succeeded.

14:36 <f_> Elestren: messageparser add Hi "echo greetings!"

14:36 <Elestren> f_: The operation succeeded.

14:36 <f_> Hello

14:36 <f_> hello

14:36 <Elestren> greetings!

14:37 <f_> hi

14:37 <f_> Hi

14:37 <Elestren> greetings!

14:37 <Elestren> greetings!

14:37 <f_> Elestren: help

14:37 <Elestren> f_: Use the 'list' command to list all plugins, and 'list <plugin>' to list all commands in a plugin. To show the help of a command, use 'help <command>'.

14:37 <f_> Elestren: list

14:37 <Elestren> f_: Admin, AutoMode, ChanTracker, Channel, Config, Ctcp, Filter, MessageParser, Misc, MoobotFactoids, Network, NickAuth, Owner, QuoteGrabs, RSS, Services, Unix, User, and Utilities

14:37 <f_> Elestren: list ChanTracker

14:37 <Elestren> f_: addpattern, addregexpattern, addtmp, affect, b, cautoexpire, cbad, ccap, cclone, ccycle, cflood, check, chl, cnick, cnotice, cpmode, crepeat, detail, do, e, edit, editandmark, extract, getmask, i, info, isbad, isvip, k, lspattern, m, mark, match, modes, ops, overlap, pending, q, query, r, rmmode, rmpattern, rmtmp, summary, ub, ue, ui, undo, uq, vacuum, and weblink

14:37 <f_> Elestren: set

14:37 <Elestren> f_: Error: "set" is not a valid command.

14:37 <f_> Elestren: list Utilities

14:37 <Elestren> f_: apply, countargs, echo, ignore, last, let, sample, shuffle, sort, and success

14:38 <f_> Elestren: list Config

14:38 <Elestren> f_: channel, config, default, export, help, list, network, reload, reset channel, reset network, search, searchhelp, searchvalues, and setdefault

14:38 <f_> Elestren: config

14:38 <Elestren> f_: (config <name> [<value>]) -- If <value> is given, sets the value of <name> to <value>. Otherwise, returns the current value of <name>. You may omit the leading "supybot." in the name if you so choose.

14:38 <f_> Elestren: list config

14:38 <Elestren> f_: channel, config, default, export, help, list, network, reload, reset channel, reset network, search, searchhelp, searchvalues, and setdefault

14:38 <f_> Elestren: config list

14:38 <Elestren> f_: (config list <group>) -- Returns the configuration variables available under the given configuration <group>. If a variable has values under it, it is preceded by an '@' sign. If a variable is channel-specific, that is, it can be separately configured for each channel using the 'channel' command in this plugin, it is preceded by an '#' sign. And if a variable is a network-specific, it is preceded by a ':' sign.

14:38 <f_> Elestren: config chantracker

14:38 <Elestren> f_: Error: 'supybot.chantracker' is not a valid configuration variable.

14:38 <f_> Elestren: list ChanTracker

14:38 <Elestren> f_: addpattern, addregexpattern, addtmp, affect, b, cautoexpire, cbad, ccap, cclone, ccycle, cflood, check, chl, cnick, cnotice, cpmode, crepeat, detail, do, e, edit, editandmark, extract, getmask, i, info, isbad, isvip, k, lspattern, m, mark, match, modes, ops, overlap, pending, q, query, r, rmmode, rmpattern, rmtmp, summary, ub, ue, ui, undo, uq, vacuum, and weblink

14:39 <f_> Elestren: q #funderscore leah

14:39 <Elestren> f_: (q [<channel>] <nick|hostmask>[,<nick|hostmask>] [<years>y] [<weeks>w] [<days>d] [<hours>h] [<minutes>m] [<seconds>s] <reason>) -- +q targets for duration; <reason> is mandatory, <-1s> means forever, empty means default

14:39 <f_> Elestren: q #funderscore leah Uh

14:39 *** Elestren sets mode: +b m:*!*@2001:8b0:b95:1bb5::100

14:39 <f_> oh that works

14:39 <f_> Elestren: uq #funderscore leah

14:39 <Elestren> f_: nicks not found or hostmasks invalid or targets are not +q

14:39 <f_> Elestren: uq #funderscore *!*@2001:8b0:b95:1bb5::100

14:39 *** Elestren sets mode: -b m:*!*@2001:8b0:b95:1bb5::100

14:40 *** f_ sets mode: +q Mb

14:40 *** f_ sets mode: -q Mb

14:40 *** f_ sets mode: +b m:Mb*!*@*

14:40 *** f_ sets mode: -b m:Mb*!*@*

14:41 <f_> Elestren: config supybot.plugins.ChanTracker.floodMode

14:41 <Elestren> f_: Global: q; #funderscore @ rx: q

14:41 <f_> Elestren: config supybot.plugins.ChanTracker.floodMode "b m:

14:41 <Elestren> f_: An error has occurred and has been logged. Check the logs for more information.

14:41 <f_> Elestren: config supybot.plugins.ChanTracker.floodMode "b m:"

14:41 <Elestren> f_: The operation succeeded.

14:41 <f_> Elestren: config supybot.plugins.ChanTracker.floodMode

14:41 <Elestren> f_: Global: b m:; #funderscore @ rx: b m:

14:46 <rx> https://git.sr.ht/~runxiyu/cca/commit/ca0a3636d71ef244d3b4a1e945d10b2c8431b7ac

15:18 *** Quits: tweezers (~tweezers@103.108.229.68) (Ping timeout: 240 seconds)

17:14 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Ping timeout: 260 seconds)

17:17 *** Quits: Noisytoot (noisytoot@oper/netadmin) (Ping timeout: 240 seconds)

17:19 *** Joins: tweezers (~tweezers@103.136.147.199)

17:20 *** Quits: Elestren (bot@andrewyu.org) (Killed (f_ (Fix yerself)))

17:20 *** Joins: Elestren (bot@andrewyu.org)

17:47 *** Joins: Noisytoot/h (~noisytoot@dn42/person/Noisytoot)

17:47 *** moist/h sets mode: +o Noisytoot/h

17:50 *** Joins: Noisytoot (noisytoot@oper/netadmin)

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

18:55 *** f_|aop/ef sets mode: +o Juesto/ef

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

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

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

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