ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | song of the day: http://yewtu.be/fG0xfGZSmR4
vulpine has quit [Ping timeout: 256 seconds]
<noocsharp> a wayland command line copy/paste implementation with seat and mimetype selection in 315 lines of c
<noocsharp> (a lot of it duplicated)
clemens3 has quit [Ping timeout: 256 seconds]
clemens3 has joined #kisslinux
vulpine has joined #kisslinux
vulpine has quit [Max SendQ exceeded]
vulpine has joined #kisslinux
vulpine has quit [Ping timeout: 240 seconds]
ehawkvu[m] has quit [Ping timeout: 256 seconds]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
<testuser[m]> Hi
ehawkvu[m] has quit [Ping timeout: 240 seconds]
ehawkvu[m] has joined #kisslinux
Guest77 has joined #kisslinux
<Guest77> Does encryption (LUKS) work with the busybox init? Nothing on the wiki about it
<tleydxdy[m]> those two things doesn't really have much to do with each other
Guest77 has quit [Quit: Client closed]
vulpine has joined #kisslinux
Guest77 has joined #kisslinux
<Guest77> tleydxdy[m] Yes that's what I thought. Are there any special kernel parameters I need to enable if I want to use cryptsetup
Guest77 has quit [Quit: Client closed]
<noocsharp> testuser[m]: i updated wayclip again, can you check if there's anything that's obviously wrong?
zlg has joined #kisslinux
an3223 has quit [Ping timeout: 240 seconds]
an3223 has joined #kisslinux
illiliti has joined #kisslinux
<illiliti> ssize_t
an3223 has quit [Remote host closed the connection]
<testuser[m]> o
<testuser[m]> rcount can be SIZE_MAX
<testuser[m]> maybe u forgor a return after warn()
<testuser[m]> oh illiliti already pointed out the wrong type
an3223 has joined #kisslinux
<testuser[m]> The author clearly confuses one problem for another. Yes, if you allocate elements in a linked list with malloc, you're going to have a bad fucking time as it will spread out yourallocations everywhere. This is a problem with malloc/free and not with linked lists. I don't use libc and don't even have a "malloc" function because the concept of treating allocations as side effects is horrible and stupid
<illiliti> source?
<illiliti> Could not resolve host: www.futurechips.org
<testuser[m]> Lol I was just using the comment as copy pasta , didnt read the original article
<testuser[m]> its dead for me too
<illiliti> lol
an3223 has quit [Ping timeout: 240 seconds]
an3223 has joined #kisslinux
an3223 has quit [Remote host closed the connection]
an3223 has joined #kisslinux
u0_a331 has joined #kisslinux
u0_a331 has quit [Client Quit]
dimaK has joined #kisslinux
mcpcpc_on_kirc has quit [Quit: mcpcpc_on_kirc]
dimaK has quit [Client Quit]
ehawkvu[m] has quit [Ping timeout: 240 seconds]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
phinxy has quit [Changing host]
phinxy has joined #kisslinux
ehawkvu[m] has quit [Ping timeout: 256 seconds]
ehawkvu[m] has joined #kisslinux
<midfavila> reminds me of a video that computerphile did on the performance of linked lists versus arrays
<midfavila> the result was that on average linked lists either beat arrays or performed about the same as them
* midfavila shrugs
<illiliti> qemu with sdl2 doesn't work
<illiliti> it hangs at startup
<testuser[m]> works here
dKstv has joined #kisslinux
<testuser[m]> did u strace it
<illiliti> yep
<illiliti> it does poll with 0 timeout
<illiliti> it causes cpu spikes as well
<testuser[m]> inb4 udev related
<illiliti> don't think so
<illiliti> -nographic works btw
<illiliti> SDL_VIDEODRIVER=wayland ssu -p qemu-system-x86_64 -enable-kvm -m 4G -cdrom netbsd.iso -device virtio-scsi -drive file=netbsd.qcow2,if=virtio
<testuser[m]> why as root?
<illiliti> kvm
illiliti has quit [Quit: brb]
illiliti has joined #kisslinux
<illiliti> tried as non-root and it still hangs
riteo has joined #kisslinux
<riteo> hiiiii!
<midfavila> Oh, long time no see, riteo.
<riteo> It's been quite a while, hasn't it?
<riteo> hiiii mid!
<riteo> I missed you
<midfavila> >.<
<testuser[m]> riteo: hi
<midfavila> Oh, one sec, clocksync from WWV
<riteo> hi testuser!
<riteo> how are things going, other than dylan disappearing from the public once again?
<midfavila> No idea wrt: KISS
<midfavila> I haven't used upstream in months
<midfavila> personally I guess I'm alright. Just slowly making progress on maths and CS, as usual. You?
<riteo> I've closed quite a lot of projects (minekiss and stuff) to focus on learning more C/C++
<riteo> I've also read a bit that C book I *ahem* found on the internet
<riteo> (only a little bit though, got distracted with other, more pratical stuff)
<riteo> the biggest thing I've been doing is porting Godot to Wayland
<midfavila> C is something I need to dedicate more time to. Ordered a bunch of books about Unix programming, so hopefully that'll give me ideas for good projects. What have you been reading?
<midfavila> Oh, that's neat. Has it been difficult?
<riteo> surprisingly, not that much
<riteo> I mean, it's still not done, but, ignoring weird limitation imposed by Wayland, I've been really liking the whole API-from-protocol thing
<riteo> s/limitation/limitations/
<riteo> people hate fragmentation, but I really like the idea of making everything a different protocol. People have different needs.
<midfavila> Hmm. I'm definitely in the opposite camp.
<midfavila> Ideally everything would use formatted text communicated via identical IPC mechanisms, at least in my opinion
<riteo> I don't see how that would go against the idea of different protocols for different things
<midfavila> Well, depends on how you define protocol, I guess - but fair enough.
<riteo> I haven't looked your website in a while, have you been collecting more weird hardware?
<midfavila> I considered it, but no, not as of late
<midfavila> was talking to a guy about two of these complete with dock, and then mid-negotiation he sold them to someone else
<riteo> oof
<riteo> lmao that "NOTHING'S THOUGHER" on top of that brick is really funny
* midfavila shrugs
<midfavila> I mean, they've stopped bullets, so it's kinda accurate
<midfavila> this exact model, I mean
<riteo> that's crazy
<midfavila> Yeah, an American soldier in Iraq had one stop a bullet from an enemy sniper back in 2003 or something
riteo has quit [Quit: zzz]
riteo has joined #kisslinux
<riteo> catgirl messed up, for some reason
<midfavila> they do that sometimes
<midfavila> give it a ball of yarn
* riteo gives catgirl a ball of yarn
<riteo> wow, that bullet thing could be quite an ad
<riteo> what repo are you using now?
<riteo> carbs?
<midfavila> Yeah, it's kinda serendipitous.
<midfavila> and no, I maintain my own base
<midfavila> although I need to go through and update some of the packages
<midfavila> might port Xenocara to replace XOrg at some point, too
<riteo> I see
<riteo> why not using rootless xorg?
<midfavila> ngl haven't looked into tech stuff much lately, so I'm just not informed about it
<midfavila> doesn't it require PAM or something?
<riteo> I have no idea actually, kiss linux allowed rootless xorg though
<riteo> I don't recall it depending on PAM
<midfavila> Guess I'll have to look into it. Apparently XDM doesn't like it
<midfavila> gives me a reason to take a crack at making a display manage
<midfavila> manager*
<riteo> talking about isolation from root, I found out that dylan's sway guide is kinda wrong
<midfavila> Oh?
<riteo> oooh, your own display manager? How are you gonna use common GUI apps?
<midfavila> Display manager is just the login screen :p
<riteo> oh
<midfavila> I don't like logging in from a tty
<riteo> it's kinda a mess, yeah, I understand that
<riteo> the guide issue is very minor, but potentially quite unsafe (not root escalation though)
<riteo> basically it says to put the user into the input group, which allows to bypass wayland's so famous window isolation
<riteo> libseat is made exactly to avoid that issue, but since dylan uses sway-tiny he probably didn't notice it
<midfavila> wayland btfo
<riteo> the solution is simply not to put the user there, and run seatd
<riteo> (which has to be already done on a normal sway install)
<midfavila> I see
<midfavila> Reminds me that I need to look into writing a window manager, too...
<riteo> what will you put in it?
<midfavila> literally nothing
<midfavila> i intend for it to implement the entirety of the EWMH and that's it
<riteo> I see
<midfavila> probably won't be a reparenting WM
<riteo> reparenting?
<midfavila> most WMs are reparenting, so they sit between X11 and clients
<midfavila> the WM intercepts requests from the client and from X11, and determines if they go through, are blocked, or are modified
<midfavila> usually it's done for the purposes of a window border
<midfavila> but it makes it rather difficult to handle windows using other programs without implementing some kind of bespoke protocol in the WM
<riteo> that's an interesting approach, the one you want to take
<midfavila> good illustration of this is using wmutils with dwm versus wmutils with anything else
<riteo> wait, dwm is not reparenting?
<midfavila> that's correct
<riteo> oh, that's interesting
<midfavila> Yeah. 9wm, which I also tried for a little while, *is*
<midfavila> But since its primitive operations on windows are so limited, it's... kinda hard to use
<riteo> I had no idea wikipedia had a page for this
<midfavila> now you do
<riteo> wikipedia for some reason has pages for the weirdest or most "obvious" of things
<riteo> like use case
<riteo> why is there the need to have a whole page for "use case"
* midfavila shrugs
<riteo> oh wait, it might look at it in some weird technical sense
<riteo> whatever
<dKstv> Hi everyone
<riteo> hi!
<dKstv> Im new to kiss, enjoying it a lot so far
<illiliti> dilyn: fyi, people at wlroots are reworking libinput backend. not sure if it's related to the bug you have, but there's a possibility
dKstv has quit [Remote host closed the connection]
dKstv has joined #kisslinux
dKstv has quit [Remote host closed the connection]
eudfty has joined #kisslinux
eudfty has quit [Remote host closed the connection]
<testuser[m]> C is the only sane language left. It never changes and it lets us write code that just works. We can focus on getting things done and shipping rather than learning new features and Googling compiler errors. Learn once, ship forever.
<testuser[m]> On my last workplace we argued if we dared to use stdint.h, since it was so new and fancy. I was a proponent, but there is something calm over discussing whether to use 23 year old additions or not.
<testuser[m]> I almost had a heart attack when the twitter post stated that "true" and "false" are keywords in C23. However that seems incorrect.
<illiliti> i wish we have go-style defer in c23
Rohan has joined #kisslinux
<Rohan> hi guys
<Rohan> any news about dylan?
<testuser[m]> Hi
<testuser[m]> No
<testuser[m]> But you know what? Something happened that changed my life. I bumped into a Rustacean. And another Rustacean. And a few more Rustaceans. I found five Rustaceans. And they showed me what they did to become Rustaceans. Again, it’s not just about jobs, it’s about the good programming; ergonomics, safety, zero cost abstractions and efficiency.
<Rohan> lol
<Rohan> rust compared to c++ is better?
<omanom> it's probably that i haven't used it very much / learned much about it... but rust is such a PITA to read and comprehend
<Rohan> ive been thinking in learn rust for some projects
<Rohan> but dont know if that be useful than other languages
<omanom> depends on the project and how you define "useful"
<Rohan> not that big just some CLI programms
<Rohan> for practice
<testuser[m]> Use rust or goolang
<illiliti> rust is no-go absolutely
<testuser[m]> Why
<illiliti> pita to bootstrap
<illiliti> extemely slow and inefficient build system
<Rohan> anyone have a weston build out of the box?
<illiliti> "move fast and break things" TM
<Rohan> need some to test my waydroid package
<midfavila> do they have non-x86 support yet
<midfavila> or is memory safety still limited to the high-reliability world of PCs
<omanom> looks like no musl "tier 1"
<midfavila> lmao
<midfavila> at least they support arm64 now
<riteo> lmao
<riteo> how is that possible?
<midfavila> the power of rust
<midfavila> that's how
<riteo> amazing
<midfavila> C is dead, long live C
<omanom> musl is tier 2 looks like: "Tier 2 targets can be thought of as "guaranteed to build". The Rust project builds official binary releases for each tier 2 target, and automated builds ensure that each tier 2 target builds after each change. Automated tests are not always run so it's not guaranteed to produce a working build, but tier 2 targets often
<omanom> work to quite a good degree and patches are always welcome!"
<omanom> kind of sounds like "if it works, great, but we're not going to put any effort into it"
<midfavila> fucking cat keeps jumping on my desk when I'm trying to work
<midfavila> reeeeeeee
<testuser[m]> Send cat.jpg
<riteo> I don't understand, is there the possibility of them using GNU extensions?
<testuser[m]> Gnu extensions in what
<testuser[m]> Rust is in rust
<riteo> how can you possibly not support a correct libc?
<midfavila> because fuck you
<midfavila> you're not relevant
<midfavila> begone, brogrammer
<riteo> I thought it was about bootstrapping, how else would musl not be garaunteed to supported
<riteo> s/garaunteed to/ garaunteed to be/
<testuser[m]> What's the least worst alternative to c
<midfavila> lisp
<omanom> nim lol
<midfavila> or forth
<midfavila> or $lang
<midfavila> anyway here
<riteo> >KIT
<midfavila> shit picture but this is the cat.jpg that was requested
<riteo> that's more than enough, thanks for your service
<midfavila> she just fuckin
<midfavila> comes in here at random
<testuser[m]> Bruh
<midfavila> and starts meowing at me
<midfavila> "MOOOOOOOOOOOOOOOOOOOOW"
<midfavila> "MIAAAAAAAAAAAAAAAAAAAAAAAAO"
<midfavila> "MOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOW"
<riteo> maybe she wants something, I've never had a cat
<midfavila> she wants attention lmao
<illiliti> zig is not bad, but it's over-engineered
<testuser[m]> Is that a button phone thingy on charging
<midfavila> it's called a "blackberry" and yes
<omanom> i guess we're all just waiting for drewlang
<illiliti> indeed
<testuser[m]> Zig seems good but it's not stable yet and syntax is pretty shit like rust
<illiliti> looks promising
<noocsharp> help me design nooc and we can make it the least bad alternative for c
<riteo> omanom is that a codename?
<testuser[m]> Drewlang seems similar to zig
<testuser[m]> midfavila: does it run android
<midfavila> no
<midfavila> it runs QNX
<riteo> > no
<omanom> @riteo i don't think he's given it a name yet
<riteo> based
<riteo> yes he did
<riteo> but he asked to keep it secret
<midfavila> i'm going to be ordering a pinephone here in a bit
<midfavila> once they're available again
<omanom> oh then i don't know what the name is
<riteo> there's also a website for it, with draft docs and whatever
<noocsharp> drewlang is much simpler than zig, but it has some weird things built-in to the language
<testuser[m]> riteo: https://termbin.com/iy53
<midfavila> if I could get away with it i'd buy one of those clusterboards and use it as my main PC, too
<testuser[m]> midfavila: what stuff can u do on qnx
<riteo> testuser great copypasta, I'll still keep using it lmao
<midfavila> testuser[m]: anything you can on a regular Unix
<midfavila> albeit sans root, because muh soycurity
<midfavila> i used to have a complete GNU userland on my phone
<riteo> I'm not sure honestly whether drewlang will become more famous as a general purpose language than other C alternatives
<testuser[m]> What browser does it run
<midfavila> webkit c. 2014
<testuser[m]> But vro sekurity
<testuser[m]> 2014
<midfavila> it's enough for me to use ebay and check my banking info /shrug
<omanom> his (original) goal was for it to be a systems programming language, rather than a general purpose one
<riteo> I doubt that many people waiting for it are system programmers
<noocsharp> i would want a high degree of control in a systems programming language, which **** doesn't seem to provide
<omanom> well its sort of like calling rust a systems programming language yet people are using it to write CLI system info fetch tools
ithuriel has quit [Remote host closed the connection]
<noocsharp> i want to be able to create typesafe constructs using a possibly non-typesafe superset of the language
<noocsharp> but dynamic arrays and unions are built-in to the syntax of the language, rather than implemented in **** as a library or something
<riteo> I wonder why, that also makes the whole "static standard" idea harder to do properly
<testuser[m]> I want C with RAII and templates
<riteo> doesn't RAII add unexpected code execution?
<noocsharp> not if you're aware of it
<testuser[m]> Zero cost abstraction vroo
<riteo> IMO, the best standard structure is one which has an extremely basic but basically frozen core, slowly going up in complexity with different extension outside of it
<riteo> kinda like (very roughly) RISC or Wayland
<riteo> although RISC has "official" extensions
<riteo> IIRC
<noocsharp> that's essentially want i want to do with my language
<riteo> ooh, nooc is a real thing?
<riteo> from the context I thought it was a joke, sorry
<riteo> could you tell me more about it?
<testuser[m]> noocsharp: i thought it was a c coompiler
<testuser[m]> As of C++20, the right way to write a trivial getter in C++ looks like [[nodiscard]] constexpr auto GetFoo() const noexcept -> Foo { return foo_; }
<noocsharp> it's basically a (crappy) toy compiler atm
<riteo> have you thought about using QBE as the backend?
<riteo> at least for testing
<noocsharp> i've thought about it
<noocsharp> what i'm probably gonna do with it is make it into an interpreter, and then write a compiler as a library in nooc
<riteo> as a bootstrapping method or as a core language feature?
<noocsharp> well there
<noocsharp> 's this language called jai which does a similar thing
<noocsharp> except the compiler is implemented in the interpreter
<riteo> mhhh, I see
<riteo> so that'd make it both an interpreted and compiled language
<noocsharp> the idea is you have a build "script" written in nooc which calls the compiler library
<riteo> that's a very interesting approach, but won't it make the compiler very slow?
<noocsharp> i'll worry about that if it actually becomes a problem
<noocsharp> and if i get that far
<riteo> but it's bound to be slow, isn't it?
<illiliti> i'm shocked that in 2022 we still don't have a portable way to set symbol visibility
<illiliti> i wish c23(or posix) do something about this
<noocsharp> it's gonna be a pretty lightweight bytecode interpreter and a pretty small core compiler
<riteo> wait wait wait
<riteo> bytecode?
<noocsharp> that's how interpreters generally work
<riteo> oh, as a preloading step I supposed
<riteo> s/supposed/suppose/
<riteo> I thought it was going to be bytecode compiled manually before running
<riteo> if it does that after parsing the script then it makes sense
<noocsharp> no, the compiler will compile to native code
<riteo> I see
<noocsharp> but most of this is hypothetical at this point, right now i just have a compiler written in c which compiles to amd64 machine code
<riteo> well, gotta start somewhere
<testuser[m]> "Just put namespaces in C" YOU just put namespaces in C, goddamnit. It's hard enough getting existing practice used by 5+ compilers past the Committee, do you know what it fucking takes to put a WHOLE FEATURE in, that people DO NOT understand???
<riteo> what happened
<riteo> why is C23 getting talked about so much lately, is it a fresh thing?
<riteo> even while looking at cproc it talks about c23 features
mahmutov has joined #kisslinux
<riteo> omg are we sure that the `true`,`false` keyword thing was wrong?
<riteo> wikipedia cites it https://en.wikipedia.org/wiki/C2x
<riteo> s/cites/mentions/
<riteo> italian moment
<riteo> oh wait, it exists in english
<omanom> there's supposedly another features update planned soon?
<riteo> actually this new revision doesn't sound that bad (ignoring true/false, if that's true)
<riteo> quite the opposite
<noocsharp> what's the problem with true and false being keywords?
<riteo> if they map to integers, hide their real value
<riteo> if they don't, they add a new type into the core, if there isn't already a bool
dKstv has joined #kisslinux
dKstv has quit [Remote host closed the connection]
<noocsharp> stdbool.h already hides their real value
dKstv has joined #kisslinux
<riteo> yes, but it's a library
<riteo> it's optional, and at discretion of the user
<noocsharp> yeah, wouldn't want to pollute my prestine programming language with bloated built-in booleans
<riteo> bruh, those aren't full-fledged booleans
dKstv has quit [Quit: dKstv]
<riteo> are constants that can be added in an extremely trivial way
<riteo> s/^are/they are/
dKstv has joined #kisslinux
<illiliti> testuser[m]: which version of sway are you using?
dKstv has quit [Client Quit]
dKstv has joined #kisslinux
dKstv has quit [Client Quit]
dKstv has joined #kisslinux
dKstv has quit [Client Quit]
dKstv has joined #kisslinux
ehawkvu[m] has quit [Ping timeout: 256 seconds]
<dilyn> illiliti: have you tried using -display sdl in your qemu invocation? qemu with just sdl2 works perfectly fine for me; I just specify -display sdl -vga virtio to get dynamic resizing
<dilyn> also ofc they would be rewriting libinput backend for wlroots smdh. I suppose I just have to play the waiting game; I feel like there's no sufficiently good reason to backport these patches to pre-0.15
<testuser[m]> illiliti: ee7668c1f2b5ba31420d972161d6d43fc1c84bb4
<illiliti> dilyn: yep, tried that. nothing is working
ehawkvu[m] has joined #kisslinux
<dilyn> that's very interesting. especially since I don't even have to invoke root to launch my qemu machines...
<illiliti> try -enable-kvm and you will need root or rw for /dev/kvm
<dilyn> ah yes I am in the kvm group
<dilyn> forgot about that
<dilyn> are you just building qemu with the standard recipe?
<illiliti> yes
<dilyn> curiouser and curiouser
<illiliti> i even tried downgrading it to 6.1.0 and 6.0.0. neither is working
<illiliti> gonna rebuild everything with -O0 -ggdb and debug
<dilyn> XD  all in
<dilyn> might as well; I'm not certain what could be wrong. by all measures my system should be completely broken and yet...
<midfavila> that's a mood
<dilyn> *cries in ffast-math*
<testuser[m]> funroll all loops
dKstv has quit [Quit: dKstv]
<midfavila> wish I could recompile myself with -ffast-math
<midfavila> smh
<dilyn> sometimes I think I was built with ffast-math
<dilyn> I didn't understand most of my senior thesis:'(
<jslick> rohan learn all the languages that you are interested in. Don't let these people dissuade you. Unless you are doing it for something specific. The overlap of peoples' opinions of what makes a good programming language here is probably very narrow.
dKstv has joined #kisslinux
ehawkvu[m] has quit [Read error: Connection reset by peer]
<Rohan> jslick thanks for advice
dKstv has quit [Client Quit]
ehawkvu[m] has joined #kisslinux
<omanom> except java
dKstv has joined #kisslinux
dKstv has quit [Remote host closed the connection]
dKstv has joined #kisslinux
dKstv has quit [Client Quit]
ehawkvu[m] has quit [Read error: Connection reset by peer]
ehawkvu[m] has joined #kisslinux
ehawkvu[m] has quit [Ping timeout: 272 seconds]
midfavila has left #kisslinux [#kisslinux]
ehawkvu[m] has joined #kisslinux
mahmutov has quit [Ping timeout: 256 seconds]
<Rohan> java i agree
<Rohan> i just need it for flutter
<Rohan> and SDK tools
illiliti has quit [Quit: leaving]
progenyx has quit [Quit: progenyx]
<riteo> well, it's been fun, I'll go for now, bye!
riteo has quit [Quit: epic comeback moment]
mahmutov has joined #kisslinux
progenyx has joined #kisslinux
midfavila has joined #kisslinux
<midfavila> bluuuuuuuuh
<midfavila> lang keeps kicking my ass
<midfavila> how do I become not shit at math dilyn
<dilyn> choose a different sub-topic /shrug
<dilyn> maths is difficult to be good at. I'm not very good at it
<dilyn> I'm a far better logician than an Analyst, I'm a far better teacher than a student
<midfavila> fuck
<phoebos> wow git-add(1) has an interactive mode
Rohan has quit [Ping timeout: 250 seconds]
<phoebos> wild
<phoebos> o/ all
<phoebos> busy in here today for once
Guest93 has joined #kisslinux
<Guest93> Hi
<Guest93> Is it possible to install the nouveau driver on Kiss Linux?
<dilyn> testuser[m]: ^
ella-0_ has joined #kisslinux
ella-0 has quit [Ping timeout: 250 seconds]
Guest93 has quit [Quit: Client closed]
midfavila has left #kisslinux [#kisslinux]
dimKv has joined #kisslinux
dimKv has quit [Quit: leaving]
mahmutov has quit [Ping timeout: 250 seconds]
dimKv_ has joined #kisslinux
dimKv_ has quit [Client Quit]
icy has quit [Quit: ZNC 1.9.x-nightly-20210409-e0ffdddd - https://znc.in]