Chat logs of #funderscore for Monday, 2024-07-15

00:08 *** Joins: dip (3daa20ef2f@ip74-208-163-85.pbiaas.com)

00:09 *** Quits: Larsenv/h (~Larsenv@152.70.198.159) (Excess Flood)

00:09 *** Joins: Larsenv/h (~Larsenv@152.70.198.159)

00:35 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Ping timeout: 272 seconds)

00:39 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Ping timeout: 240 seconds)

00:56 *** Parts: dip (3daa20ef2f@ip74-208-163-85.pbiaas.com) ()

00:57 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

00:58 *** Joins: Noisytoot/h (~noisytoot@dn42/person/Noisytoot)

00:58 *** ChanServ/h sets mode: +o Noisytoot/h

01:12 *** Joins: dip (3daa20ef2f@2607:b500:423:bb00::1)

01:12 <dip> Test.

01:13 *** Parts: dip (3daa20ef2f@2607:b500:423:bb00::1) ()

01:44 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Ping timeout: 240 seconds)

01:45 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

01:46 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Read error: Connection reset by peer)

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

01:47 *** ChanServ/h sets mode: +o Noisytoot/h

02:37 <runxiyu> Um

02:37 <runxiyu> How is btrfs fragile?

03:05 *** Joins: dip (3daa20ef2f@2607:b500:423:bb00::1)

03:10 <dip> I tested BTRFS on Seagate Exos X16 Enterprise HDD. One day I got 49℃+ (seasons surely changed), apparently it lead to hectic random disconnects, "Power off retract count" grew like crazy, presumably the disk tried to lower the temperature this way, and BTRFS couldn't be mounted anymore after this. That occured twice on 2 different disks (I was slow to identify the cause).

03:12 <runxiyu> I only use btrfs on SSD's, so I can't tell

03:12 <runxiyu> I've had horrible experiences with Seagate drives

03:12 <dip> Formatted, switched to EXT4, checked all the disk's surface by S.M.A.R.T., all good.

03:13 <dip> SSD is where BTRFS belongs in my opinion.

03:13 <runxiyu> I used to use ZFS when I still used the large mechanical hard drives back in that apartment

03:13 <dip> Well, great you know how to setup, I don't.

03:14 <runxiyu> .c

03:14 <runxiyu> it's not that hard on freebsd

03:14 <runxiyu> a huge pain on linux though

03:14 <dip> Oh, FreeBSD, it's in the setup, I see.

03:15 <dip> I heard DragonflyBSD has an interesting alt FS like BTRFS/ZFS, called HAMMER2 or something.

03:18 <runxiyu> yeah

03:19 <dip> In any way, I keep filelists per month in a special folder, I add SHA256 to XATTR of files, have 1 block-long Parchive 2 (~0.5%) for bitrot recovery, and 8 different checksums plus filesizes and modification dates. All by custom tools.

03:19 <dip> Thus no corrupt file will go undetected.

03:21 <dip> The custom checksum maker reads a file once, makes the 8, then can SHA256 XATTR itself in RAM, send it into a BZIP2 file, check write OK, and then sign by SSH, PGP, HMAC. Integrity!

03:22 <dip> > I only use btrfs on SSD's, so I can't tell

03:22 <dip> All good?

03:29 <dip> Also while on the matter of archiving, take a look:

03:29 <dip> https://www.nongnu.org/lzip/tarlz.html

03:29 <dip> This is like RAR/7z but TAR, very handy.

03:34 *** Parts: dip (3daa20ef2f@2607:b500:423:bb00::1) ()

03:55 *** Joins: dip (3daa20ef2f@2607:b500:423:bb00::1)

03:57 <dip> Well, took a brief look at your site, couldn't find Article #17, checked the Internet Archive of it, found a link to Leah Rowe's article. That's a good article, thank you.

03:57 *** Parts: dip (3daa20ef2f@2607:b500:423:bb00::1) ()

04:37 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Ping timeout: 255 seconds)

04:41 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Ping timeout: 240 seconds)

04:45 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

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

04:46 *** ChanServ/h sets mode: +o Noisytoot/h

08:19 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Quit: ZNC 1.8.2 - https://znc.in)

08:19 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Client Quit)

08:24 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

08:24 *** Joins: Noisytoot/h (~noisytoot@dn42/person/Noisytoot)

08:24 *** ChanServ/h sets mode: +o Noisytoot/h

09:58 *** Joins: hax (hax@netadmin.irc.andrewyu.org)

10:03 *** Quits: luk3yx (luke@netadmin.irc.runxiyu.org) (Ejected, and the crewmates have won.)

10:04 *** Joins: luk3yx (luke@netadmin.irc.runxiyu.org)

13:21 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Ping timeout: 255 seconds)

13:25 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Ping timeout: 240 seconds)

13:26 *** Joins: Noisytoot/h (~noisytoot@dn42/person/Noisytoot)

13:26 *** ChanServ/h sets mode: +o Noisytoot/h

13:26 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

14:15 <f_/h> runxiyu: I didn't know you were on FreeBSD

14:15 <f_/h> I thought you used OpenBSD rather

14:33 <runxiyu> f_: I use FreeBSD for NAS

14:33 <runxiyu> f_: Because ZFS

14:33 <f_/h> runxiyuu right

14:33 <f_/h> oops

14:33 <f_/h> runxiyu: right

14:34 <runxiyu> and it's probably what I'd use if I ever switch to desktop BSD

14:34 <runxiyu> (maybe dragonflybsd? idk)

14:36 <f_> right

14:36 * f_ afk...

15:27 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Quit: ZNC 1.8.2 - https://znc.in)

15:27 *** Quits: Noisytoot/h (~noisytoot@dn42/person/Noisytoot) (Read error: Connection reset by peer)

15:27 *** Joins: Noisytoot_/h (~noisytoot@dn42/person/Noisytoot)

15:27 *** ChanServ/h sets mode: +o Noisytoot_/h

15:28 *** Joins: dip (3daa20ef2f@2607:b500:423:bb00::1)

15:29 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

15:36 <dip> The "fun" part is I do have scientific data that can help to write Article #17, but, I think it might be better to not rush that, see to what conclusions you'll come by yourself, you know, and then act if/when necessary.

15:37 <dip> For the record, I'm not 16, I'm from the 2nd half of the 1990s, the most I would say.

19:45 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Quit: ZNC 1.8.2 - https://znc.in)

19:47 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

19:53 *** Quits: Noisytoot_/h (~noisytoot@dn42/person/Noisytoot) (Ping timeout: 272 seconds)

19:56 *** Quits: Noisytoot (noisytoot@netadmin.irc.runxiyu.org) (Connection closed)

19:56 *** Joins: Noisytoot/h (~noisytoot@dn42/person/Noisytoot)

19:56 *** ChanServ/h sets mode: +o Noisytoot/h

19:56 *** Joins: Noisytoot (noisytoot@netadmin.irc.runxiyu.org)

20:23 <JAA/h> I can't take btrfs seriously until they figure out parity.

20:26 <hax[xor]> sounds like you should put btrfs on an applicable raid?

20:26 <JAA/h> I mean, yeah, there are workarounds, but it's still silly.

20:38 <dip> Folks, BCacheFS looks interesting, and it gets incl. in new kernels: https://bcachefs.org/

20:38 <dip> May consider for someday. :3

20:40 <f_> dip: Why do you keep leaving and rejoining on IRC?

20:40 <f_> Is it you closing your client?

20:40 <dip> For focus.

20:41 <f_> ah, but you lose chat history by doing so

20:41 <f_> Not that it matters much, it's all logged publicly, but still

20:41 <f_> (except #funderscore-sucks which is not logged)

20:46 <hax[xor]> sure it's logged *looks at ~/.local/share/weechat/logs/*

20:46 <hax[xor]> :P

20:46 <hax[xor]> (fine that's not public)

20:46 <dip> Logged publicly, exactly.

20:47 <dip> The "-sucks" one I do not mind.

20:48 <hax[xor]> and, 1) you could just mute your client or something and toss it into the background where you'll not be distracted by it?, 2) you could get f_ to set a relevant +H :P

20:48 <f_> we had +H to have InspIRCd send chat history upon join

20:48 <f_> I mean we had it set here

20:48 <f_> It's just wonky

20:49 <f_> so I unset it

20:49 <hax[xor]> set +N if you don't want it :P

20:49 <hax[xor]> user mode +N

20:49 <f_> Somehow even with +N I still got chat history sent to me

20:49 <dip> XMPP has that:

20:49 <f_> XMPP has MAM and MUC-MAM

20:49 <hax[xor]> sounds like your client is joining before setting +N

20:49 <f_> Perhaps.

20:50 <hax[xor]> or your bouncer isn't setting +N on reconnect or whatever

20:50 <dip> https://chatterboxtown.us:5443/upload/3daa20ef2fde5f7049901324bb81ce22ab837c96/osfOO7KzvNZuoRLZu3T5CSB1TC89Czei3XwLa7mt/Screenshot_20240715-205024_blabberim.jpg

20:50 <f_> soju doesn't support autosetting user modes just yet

20:50 <hax[xor]> well that would be why - it's not `even with +N`, it's `without +N` :P

20:50 <f_> so I just have it send a raw `MODE f_ +N` on connect

20:51 <f_> dip: well to me it looked like your biboumi wasn't properly configured to work as a bouncer

20:51 <dip> Maybe. I'm using a public one.

20:51 <f_> You can configure it with /ad-hoc <irc network>@<your biboumi instance>

20:59 <dip> Configure if I was the owner of Biboumi, I suppose.

21:00 <dip> Speaking of mute, we would be able to mute people selectively in the physical world by: https://dl.acm.org/doi/10.1145/3613904.3642057

21:00 <dip> That could save some folks from overwhelm.

21:00 <dip> *oversaturation.

21:03 <dip> Oversaturation is an absolute nightmare to be honest, especially when on a music fest.

21:04 *** f_| is now known as f_|tl

21:07 *** Quits: Riku_V (~riku@lynx.viitanen.xyz) (Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in)

21:09 *** Joins: Riku_V (~riku@lynx.viitanen.xyz)

21:28 *** Joins: CHANLOG (~logger@2001:1600:10:100::4b9)

21:29 *** Quits: Mb (~ircbridge@195-15-242-30.dc3-a.pub1.etik-cloud.com) (Ping timeout: 240 seconds)

21:31 *** Quits: FUN▬▬▬▬▬▬▬▋ (vdoSoju@services.irc.vitali64.duckdns.org) (*.net *.split)

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

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

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

21:31 *** Joins: FUN▬▬▬▬▬▬▬▋ (vdoSoju@services.irc.vitali64.duckdns.org)

21:56 <dip> I think I found the resolution: I'll use the far-away netbook for the account, so to you it should look always connected if that bugs you so much. OK.

22:03 <dip> Done.

22:24 <f_> that doesn't bug me

22:24 <f_> Just thought it might not be desirable for you

22:24 <f_> /sanick Mb_ Mb

22:24 <f_> oop

22:25 *** Mb_ is now known as Mb

22:34 <f_> oh I'm no longer op

22:34 <f_> thanks services-less rx

22:34 <f_> and me having forgot to set +w

22:34 *** f_ sets mode: +qo f_ f_

22:35 *** f_ sets mode: +w q:R:funderscore1

22:35 *** f_ sets mode: +w o:R:funderscore1

22:35 *** f_ sets mode: +w v:CHANLOG!*@*

22:35 *** f_ sets mode: +o CHANLOG

22:35 *** f_ sets mode: -o CHANLOG

22:35 *** f_ sets mode: +v CHANLOG

22:36 *** f_ sets mode: +w o:Noisytoot!noisytoot@netadmin.irc.runxiyu.org

22:36 *** f_ sets mode: +o Noisytoot

22:36 <f_> hax[xor]: how's NickServ going

22:53 *** Joins: f_|vdoXMPP (~f@195-15-242-30.dc3-a.pub1.etik-cloud.com)

23:00 <hax[xor]> hasn't changed yet

23:01 <hax[xor]> will probably get elf loading done first

23:46 <f_|tl> elf loading in NickServ??? hax[xor]