05:27 <testuser[m]> Hi

10:23 <phoebos> https://github.com/bhk/scam

10:23 <phoebos> > a scheme implemented in GNU make

10:23 <phoebos> wow

10:24 <testuser[m]> Bruh

15:11 <phoebos> noocsharp: https://sourceforge.net/p/isync/mailman/message/37395245/

16:11 <noocsharp> thanks, will send patch

16:15 <noocsharp> i believe i also have several other outdated packages

16:23 <phoebos> :)

16:23 <testuser[m]> :(

16:24 <phoebos> i only pinged you bcs 1.4.4 fixes two CVEs

16:24 <phoebos> :p

16:25 <noocsharp> unfortunately dilyn hasn't applied the update i send for mupdf a few days ago so not sure how soon he'll apply this one

16:26 <phoebos> dilyn: tut tut

20:39 <natris1979[m]> Holy cow. That lisp. I'll never understand why people torture themselves like that

21:30 <illiliti> https://github.com/golang/go/issues/49383

21:30 <illiliti> king is cancelled from now

21:34 <cem> illiliti: yeah, it's quite unfortunate that google owns go

21:35 <cem> requiring a google account for it is plain stupid

21:38 <phoebos> that is stupid

21:39 <phoebos> i wonder if vlang is any good

21:40 <phoebos> meant to be like go without gc

21:42 <phoebos> compiles to c

21:42 <phoebos> no cla

21:50 <illiliti> vlang is yet another vala with bad reputation

21:52 <illiliti> iirc, it is implemented gc recently

21:57 <phoebos> ugh

22:00 <noocsharp> my language has if/else now :v

22:00 <illiliti> xd

22:00 <illiliti> link?

22:01 <noocsharp> https://github.com/noocsharp/nooc

22:02 <noocsharp> i don't think it's even turing complete yet

22:07 <illiliti> looks simple and clean

22:11 <noocsharp> hopefully i can keep it that way as it grows

22:18 <illiliti> wow

22:18 <illiliti> zfs survived power outage with no data corruption

22:18 <illiliti> that's good

22:19 <illiliti> yes, i did zfs-on-root

22:20 <illiliti> zfs is the only way to get rid of lvm2

22:22 <akspecs> illiliti: do it again, jim!

22:26 <illiliti> i will!

22:26 <illiliti> btw, zfs+encryption is much faster than luks

22:26 <illiliti> zfs boots in 2-3s, while luks boots in 9s

22:27 <illiliti> i don't know why luks is so bad

22:30 <noocsharp> i should encrypt my laptop's disk again

22:30 <noocsharp> before i moved to kiss i had an arch install that was encrypted

22:37 <akspecs> has zfs native encryption ever gone up against an audit?

22:38 <akspecs> i imagine LUKS is tried, tested, reliable

22:39 <akspecs> one can make the argument, that since there some 3 letter agency influence in the development of zfs, they would implement some form of a backdoor -- label it a bugdoor the moment it's found out, and so on, and so forth

22:40 <illiliti> valid point

22:40 <noocsharp> you could make that argument about the linux kernel

22:41 <illiliti> luks is battle-tested and reliable, while zfs is still new

22:41 <illiliti> BUT

22:41 <illiliti> zfs is better maintained than lvm2

22:42 <illiliti> lvm2 contains shitton of legacy(and probably vulnerable) code

22:42 <illiliti> i rather trust zfs than lvm2

22:43 <illiliti> fyi: cryptsetup depends on lvm2

22:45 <akspecs> how about luks + zfs + something other + ???? = profit

22:45 <akspecs> or however the meme goes

22:45 <illiliti> too slow

22:45 <akspecs> apparently veracrypt underwent an audit, or whatever it was called prior

22:46 <akspecs> and the audit spoke favorably of it, despite the code being considered "outdated"

22:47 <akspecs> i imagine a good cypher may withstand time longer that most will appreciate depsite quantum computing and other advancements in tech

22:47 <akspecs> to this day, millions of dollars worth of super computers will take a looooooonnnngg time to break a good encryption