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

04:38 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Excess Flood)

04:40 *** Joins: Noisytoot/h (~noisytoot@dn42/person/Noisytoot)

04:40 *** moist/h sets mode: +o Noisytoot/h

07:01 *** Joins: exxxxkc/h (12ac0e80cc@disroot.org)

07:21 *** Parts: exxxxkc/h (12ac0e80cc@disroot.org) ()

08:30 *** Joins: exxxxkc/h (12ac0e80cc@disroot.org)

08:42 *** Parts: exxxxkc/h (12ac0e80cc@disroot.org) ()

09:00 *** Quits: runxiyu/h (~runxiyu@runxiyu.org) (Ping timeout: 256 seconds)

09:01 *** Joins: runxiyu/h (runxiyu@runxiyu.org)

11:58 *** Joins: [R]/h (~rms@184.70.74.110)

11:58 <f_/h> hey [R]

11:58 <[R]/h> Hey

11:59 <[R]/h> This channel wasn't in your /whois list :p

11:59 <f_/h> I'm probably +i

11:59 <f_/h> > The current user modes are: +Zi

11:59 <[R]/h> You aren't

11:59 <f_/h> I am

11:59 <[R]/h> Well, I got a massive list of channels from you anyways

12:00 <f_/h> oh somehow the channel is +s

12:00 *** f_/h sets mode: -s

12:00 <hax[xor]> pylink being pylink-y for spambot evasion?

12:00 <f_/h> thanks for letting me know

12:00 <[R]/h> No worries

12:01 <f_/h> hax[xor]: I actually +s'd the chan on OFTC and somehow PyLink bridged it to the other channels...

12:01 <hax[xor]> your -s got bridged too

12:01 <f_/ef> yeah...

12:01 <[R]/h> lol

12:01 <f_/ef> to EFnet.....which I do want +s on.......

12:01 <hax[xor]> lol

12:01 <hax[xor]> deop rxbridge before setting it on efnet?

12:01 <f_/h> that's what I'll do

12:01 *** f_/ef sets mode: +s

12:01 <hax[xor]> er right

12:01 <f_/h> there

12:02 <hax[xor]> well it's +s here again :P

12:02 *** hax[xor] sets mode: -s

12:02 * hax[xor] unsets it

12:02 <f_/h> thanks

12:02 <hax[xor]> rxbridge unable to -s it on efnet this time?

12:02 <f_/ef> it did

12:02 <hax[xor]> lol

12:02 <f_/h> sec

12:03 *** f_/ef sets mode: +s

12:03 <f_/h> hax[xor]: Unset it with your SAMODE powers

12:03 *** hax[xor] sets mode: -s

12:03 <[R]/h> I think +s, deop on effnet, -s, reop on effnet would be the least effort way to get this

12:03 <hax[xor]> done

12:03 <hax[xor]> yeah

12:03 <f_/h> That's what I did.

12:03 <f_/ef> now I need to reop it on EFnet

12:04 <aop2/ef> well I have an auto-op bot that takes care of auto-op on join

12:04 <f_/h> I don't care all that much about EFnet - it's just an experiment there

12:04 <f_/h> to see for how much time I can keep op

12:05 <f_/h> well I'll unbridge OFTC then

12:05 *** f_ changes topic to '[ <fireonlive> funderscore is a hoover max extract pressure pro model 60 ] Free Palestine · read https://moin.vitali64.duckdns.org/IRC · logs at https://irc.vitali64.duckdns.org/rx/funderscore/ · also on hackint and XMPP · have fun and be respectful to each other!'

12:05 <f_> LinkServ: remote ef unlink #funderscore

12:05 <f_> LinkServ: help

12:05 <LinkServ> PyLink provides extended network services for IRC.

12:05 <LinkServ> Available commands include: autoconnect, chandesc, claim, clearqueue, create, delink, destroy, disconnect, echo, forcetag, help, identify, link, linkacl, linked, list, load, loglevel, logout, mkpasswd, modedelta, purge, rehash, reload, reloadproto, remote, rpm, save, showchan, shownet, showuser, shrug, shutdown, status, unload, version

12:05 <LinkServ> To see help on a specific command, type help <command>.

12:05 <f_> LinkServ: remote ef delink #funderscore

12:05 *** Parts: weechat/ef (~weechat@144.172.70.127) (Channel delinked.)

12:05 *** Parts: Noisytoot/ef (noisytoot@not.eris.berkeley.edu.pl) (Channel delinked.)

12:05 *** Parts: aop/ef (aop@vps-9bde1a96.vps.ovh.net) (Channel delinked.)

12:05 *** Parts: aop2/ef (~haha@195-15-242-30.dc3-a.pub1.etik-cloud.com) (Channel delinked.)

12:05 *** Parts: fol/ef (fire@static.96.98.78.5.clients.your-server.de) (Channel delinked.)

12:05 *** Parts: JAA/ef (~JAA@ns531958.ip-192-99-9.net) (Channel delinked.)

12:05 *** Parts: corwin/ef (~someone@ghostwheel.bru.st) (Channel delinked.)

12:05 *** Parts: f_/ef (s-16abab34@195-15-242-30.dc3-a.pub1.etik-cloud.com) (Channel delinked.)

12:05 <LinkServ> Done.

12:05 <f_> oops

12:05 <f_> LinkServ: remote ef link #funderscore rx

12:05 <LinkServ> Error: Invalid channel 'rx'.

12:06 <f_> LinkServ: remote ef link rx #funderscore

12:06 <LinkServ> Joining '#funderscore' now to check for op status; please run this command again after I join.

12:06 <f_> LinkServ: remote ef link rx #funderscore

12:06 *** Joins: weechat/ef (~weechat@144.172.70.127)

12:06 *** Joins: Noisytoot/ef (noisytoot@not.eris.berkeley.edu.pl)

12:06 *** Joins: aop/ef (aop@vps-9bde1a96.vps.ovh.net)

12:06 *** Joins: aop2/ef (~haha@195-15-242-30.dc3-a.pub1.etik-cloud.com)

12:06 *** Joins: fol/ef (fire@static.96.98.78.5.clients.your-server.de)

12:06 *** Joins: JAA/ef (~JAA@ns531958.ip-192-99-9.net)

12:06 *** Joins: corwin/ef (~someone@ghostwheel.bru.st)

12:06 *** Joins: f_/ef (s-16abab34@195-15-242-30.dc3-a.pub1.etik-cloud.com)

12:06 *** ef.relay.fun.irc.andrewyu.org sets mode: +ooooooo Noisytoot/ef aop/ef aop2/ef fol/ef JAA/ef corwin/ef f_/ef

12:06 <LinkServ> Done.

12:06 <f_> I wanted to delink OFTC not efnet..lol

12:06 <f_> LinkServ: remote oftc delink #funderscore

12:06 *** Parts: Xion/oftc (~rms@184.70.74.110) (Channel delinked.)

12:06 *** Parts: Noisytoot/oftc (~noisytoot@0002a660.user.oftc.net) (Channel delinked.)

12:06 *** Parts: f_/oftc (s-16abab34@00030532.user.oftc.net) (Channel delinked.)

12:06 *** Parts: dujem/oftc (~dujem@172.86.78.46) (Channel delinked.)

12:06 <LinkServ> Done.

12:06 <hax[xor]> did it -s efnet when relinking?

12:07 <f_/ef> It did not

12:07 <hax[xor]> nice

12:07 <f_/ef> > #funderscore has modes +stn

12:07 <[R]/h> Chanserv could also possibly lock a channel mode

12:08 <[R]/h> So that +s could not be unset

12:08 <[R]/h> Depends on the impl

12:08 <f_/h> There's no ChanServ on rx

12:08 <f_/h> (not a real issue, +w autoop and NickServ do exist on rx)

12:08 <f_/h> and there's no ChanServ on EFnet (real issue)

12:09 <hax[xor]> you can also set mlock here, but pylink is a server so it would just bypass it

12:09 <[R]/h> Fair

12:09 <f_/h> PyLink is a server on rx-side *

12:09 <[R]/h> rx == runxiyu?

12:10 <f_/h> no(t really)

12:10 <hax[xor]> yes and also no :P

12:10 <f_/h> In this context rx is refering to the network

12:10 <f_/h> https://irc.runxiyu.org/

12:10 <f_/h> But yes runxiyu does use the nick "rx" on libera and rx

12:10 <hax[xor]> there's also a user nicked `rx` on `rx`, which is runxiyu :P

12:11 <[R]/h> Okay, I meant the runxiyu network mentioned in topic :p

12:11 <f_> yeah that's the network that's mentionned on the topic

12:15 <[R]/h> *nods*

12:27 <[R]/h> Reading runxiyu blog.  C doesn't NULL terminate strings, it NUL terminates them.  (Programming Languages entry)

12:28 <[R]/h> errno is indeed bad

12:28 <hax[xor]> C may null terminate strings, but it also doesn't have that as your only option

12:28 <hax[xor]> "hi\0bye" is still a perfectly-usable 7-element character array, as you can see with sizeof()

12:31 <[R]/h> Aye

12:32 <[R]/h> It still doesn't NULL terminate them though, no need for the extra 7 bytes of 0

12:32 <hax[xor]> eh?

12:32 <[R]/h> (or 3 if you're still running 32-bit)

12:32 <[R]/h> NULL is a pointer, NUL is a character.

12:33 <hax[xor]> char x = NULL; is still going to set a char to 0

12:33 <hax[xor]> but sure

12:34 <[R]/h> Right, but when discussing it, the actual terminator is NUL

12:40 <f_/h> [R]'s got a point

12:41 <f_/h> The actual char is NUL, "NULL" is supposed to be a pointer

12:41 <f_/h> Some libc's set "NULL" to 0 and such though.

12:43 <f_/h> https://ewontfix.com/11/ interesting blogpost about it

13:37 <Noisytoot/ef> It's not some libcs. The standard requires that NULL be 0.

13:39 <hax[xor]> Noisytoot/ef: 0 vs (void *)0 vs ...

13:40 <Noisytoot/ef> and null is the correct way to refer to '\0'

13:40 <Noisytoot/ef> A byte with

13:40 <Noisytoot/ef> all bits set to 0, called the null character, shall exist in the basic execution character set; it

13:40 <Noisytoot/ef> is used to terminate a character string.

13:41 <Noisytoot/ef> from https://open-std.org/jtc1/sc22/wg14/www/docs/n1548.pdf section 5.2.1 Character sets

13:44 <Noisytoot/ef> also 6.3.2.3 Pointers: An integer constant expression with the value 0, or such an expression cast to type

13:44 <Noisytoot/ef> void *, is called a null pointer constant.66) If a null pointer constant is converted to a

13:44 <Noisytoot/ef> pointer type, the resulting pointer, called a null pointer, is guaranteed to compare unequal

13:44 <Noisytoot/ef> to a pointer to any object or function

13:45 <Noisytoot/ef> and 7.19 Common Definitions <stddef.h>: The macros are

13:45 <Noisytoot/ef> NULL

13:45 <Noisytoot/ef> which expands to an implementation-defined null pointer constant;

13:46 <Noisytoot/ef> So NULL must be a null pointer constant, and a null pointer constant is 0 or (void *)0

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

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

15:05 *** fun.irc.runxiyu.org sets mode: +o DuckServ

16:02 *** Joins: exxxxkc/h (12ac0e80cc@disroot.org)

16:32 *** Parts: exxxxkc/h (12ac0e80cc@disroot.org) ()

17:54 <f_/h> RIP fireonlive :(

17:54 *** f_/h sets mode: -o fireonlive/h

17:54 <[R]/h> ?

17:55 <f_/h> Shouldn't that be self-explanatory?

17:55 <f_/h> He sadly passed away yesterday :(

17:57 -moist/h- f_ (funderscore) set flags -O on fireonlive

17:57 <f_/h> :(

17:57 <f_/h> in the short time I knew him, he was such a nice person

17:57 <[R]/h> Oh damn

17:57 <f_/h> he will be missed

17:57 <[R]/h> That sucks

18:00 <f_/h> I myself joined some of his channels .... they'll be so empty without him :(

18:02 <f_/h> https://irc.fireon.live/hackint/channels.html

18:02 <f_/h> ^ his IRC channels

18:49 *** f_[x]/h sets mode: +v fireonlive/h

18:53 <f_[x]/h> :'(

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

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

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

21:03 <[R]/h> https://runxiyu.org/blog/llpath/ <-- That opendir() example screams like 9p's walk() does.

21:05 <[R]/h> You connect, get a fid to the rootdirectory you attached to (think of a fid like an fd+).  You can then walk() that fid to create a new fid, optionally providing a list of directories (with an optional file at the end) to have that new fid reference the path.  You can then open(), create(), stat(), wstat(), or remove() that fid.

21:06 <[R]/h> Or you could walk() the new fid again to get yet another fid

21:11 <[R]/h> Then if you look at how libixp does its IxpLookup callback, it looks kind of similar

21:13 <[R]/h> IxpLookup can either get: an IxpFile* pointer, and a char * name, at which point it needs to return a single IxpFile* for name.  Or it gets an IxpFile* pointer, and null, and it needs to return a linked list of IxpFile* entries for that directory.  It gets called for each part of walk.  So walk('foo', 'bar', 'fie') will call IxpLookup three times

21:15 *** Quits: [R]/h (~rms@184.70.74.110) (Remote host closed the connection)

21:17 *** Joins: [R]/h (~rms@184.70.74.110)

21:47 *** Quits: runxiyu (runxiyu@oper/netadmin) (Ping timeout: 248 seconds)

21:52 *** Joins: runxiyu (runxiyu@oper/netadmin)