02:39 <synimas> Do i need to include the official repo as well?

02:39 <synimas> Or just the community maintained one

02:40 <sad_plan> no. the official repo is out of date by a long shot by now. just use those from kiss-community

02:40 <synimas> So i should apply the perl patch too?

02:40 <synimas> Well obvi lol

02:41 <sad_plan> if youd like to build the kernel without needing perl, then yes.

02:41 <synimas> Well perl isnt in communtiy

02:41 <synimas> Or im just blind and setup my path wrong

02:42 <sad_plan> perl is in kiss-community/community

02:42 <synimas> Ah

02:43 <synimas> Thank you very much

07:20 <sewn> hi

14:36 <sad_plan> ji

14:36 <sad_plan> hi

15:19 <sewn> hi sad_plan

15:41 <sad_plan> hi sewn

15:55 <sewn> how are things

16:23 <sad_plan> good. a bit frustrated with me not figuring out the scaling on my website, but ill figure it out eventually. also watching latest season of dark

16:23 <sad_plan> timetravel is a complete clusterfuck if you think about it

16:23 <sad_plan> how about you?

16:27 <sewn> whats dark?

16:27 <sewn> sad_plan: personally, i think timetravel isnt possible because of the time travel paradox

16:33 <sad_plan> a german tv series

16:34 <sad_plan> well, thats the issue I was refering to. i.e. if you go back in time to fix something you wish didnt happen. you now wont travel back in time, because it didnt happen, so you now have no reason to. and even if it did, which "future" do you go to? the one youve now created, or the one where you didnt go back in time?

16:34 <sad_plan> theres all kinds of paradoxes with timetravel, both forward and backwards are both the same

16:47 <sewn> it only depends on if multiverses theory is true

16:47 <sewn> if it is, then you go to the universe of the one where you changed something

16:47 <sewn> if not, then the event of you travelling in time just cannot happen

17:04 <sad_plan> yeah, it gets complicated real fast if one doesnt take multuverse into consideration

17:51 <sewn> should i give up on chromium and firefox and return to alpine or keep fighting by moving to wayland (cuz apparently wayland works better on both browsers)

17:57 <sad_plan> im obvously impartial to neither of these options. nevertheless, how is both browsers worse on xorg? did they partially remove support for X?

18:13 <sewn> sad_plan: chromium segfaults on X without ATK, chromium fails to compile GLSL (basically cannot render anything) for some reason after an update, and firefox just cant play videos without it's video threads segfaulting

18:13 <sewn> ive always had that firefox problem but chromium not really

18:25 <sewn> bruh i fixed chromium by just one rm -rf gpu cache command

18:25 <sewn> kiss r firefox'ing now

18:40 <sad_plan> right. so its fixed now I suppse. why dont you just use atk so chromium doesnt segfault?

18:44 <sewn> i am using atk

18:44 <sad_plan> and yet it segfaults?

18:44 <sewn> the fault is in gtk's remove atk patch, as compiling a specifically designed gtk program will segfault

18:45 <sad_plan> I see

18:46 <sewn> although, one of chromium's patches is to have atk be conditional too

18:46 <sewn> but atk is always disabled within the build, regardless if gtk is atk or not

18:46 <sewn> its (mostly) being investigated at https://github.com/ehawkvu/kiss-xorg/issues/145

18:50 <sad_plan> hm. glad Im not affected by this. seeing as I use luakit :D

18:53 <raph_ael> luakit is still developped ?

18:54 <raph_ael> dwb was nice, but no more developped since years

18:55 <sad_plan> yeah luakit is still in active developement. and yes, dwb is unfortunatly unmaintained now. never tried it myself, but seemed cool

18:56 <raph_ael> it was

18:56 <raph_ael> luakit is nice too, i'll retry it

18:58 <sewn> is luakit different from WebKit

18:58 <sewn> please tell me it is sad_plan

19:08 <sad_plan> luakit is just the browser. it is webkit based, like surf