Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→ 184,927 events total
2023-07-18 07:41:30 <xmonadtrack> xmonad Tony Zorman {GitHub} * v0.17.2-75-gf289b3b: Merge pull request #462 from slotThe/ci/bump (6 minutes ago, 0 files, 0+ 0-) https://github.com/xmonad/xmonad/commit/f289b3b1340b
2023-07-18 08:30:19 defjam joins (~defjam@90.211.252.220)
2023-07-18 08:32:48 × rundown quits (~defjam@2a02:c7e:2807:b900:40dc:8f12:e31c:79a6) (Ping timeout: 272 seconds)
2023-07-18 08:36:36 × hightower2 quits (~hightower@141-136-175-55.dsl.iskon.hr) (Ping timeout: 272 seconds)
2023-07-18 08:59:12 × ft quits (~ft@p3e9bc856.dip0.t-ipconnect.de) (Quit: leaving)
2023-07-18 09:13:14 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-18 09:18:18 × unclechu quits (~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-18 09:26:20 hightower2 joins (~hightower@85.94.71.188)
2023-07-18 09:32:59 × vetu quits (~vetu@91-156-31-97.elisa-laajakaista.fi) (Read error: Connection reset by peer)
2023-07-18 09:33:06 vetu_ joins (~vetu@91-156-31-97.elisa-laajakaista.fi)
2023-07-18 12:03:41 obimod joins (~weechat@user/obimod)
2023-07-18 12:07:41 × tv quits (~tv@user/tv) (Ping timeout: 246 seconds)
2023-07-18 12:09:34 tv joins (~tv@user/tv)
2023-07-18 12:14:07 × tv quits (~tv@user/tv) (Ping timeout: 245 seconds)
2023-07-18 12:15:59 tv joins (~tv@user/tv)
2023-07-18 14:13:32 × mncheck quits (~mncheck@193.224.205.254) (Ping timeout: 272 seconds)
2023-07-18 15:14:52 thunderrd joins (~thunderrd@183.182.111.104)
2023-07-18 15:32:52 beastwick[m] joins (~beastwick@2001:470:69fc:105::3:8087)
2023-07-18 15:50:11 × berberman_ quits (~berberman@user/berberman) (Quit: ZNC 1.8.2 - https://znc.in)
2023-07-18 15:50:33 berberman joins (~berberman@user/berberman)
2023-07-18 16:03:06 sagax joins (~sagax_nb@user/sagax)
2023-07-18 16:52:31 × hightower2 quits (~hightower@85.94.71.188) (Ping timeout: 245 seconds)
2023-07-18 16:55:08 hightower2 joins (~hightower@85.94.71.188)
2023-07-18 17:02:27 × berberman quits (~berberman@user/berberman) (Quit: ZNC 1.8.2 - https://znc.in)
2023-07-18 17:02:48 berberman joins (~berberman@user/berberman)
2023-07-18 17:28:21 × hightower2 quits (~hightower@85.94.71.188) (Ping timeout: 245 seconds)
2023-07-18 20:45:39 hightower2 joins (~hightower@141-136-175-55.dsl.iskon.hr)
2023-07-18 21:07:24 mon_aaraj joins (~montchncs@2001:470:69fc:105::8e6b)
2023-07-18 22:06:43 <u8353v[m]> <geekosaur> "well, some of them. if it..." <- no - i was told wayland is more secure than X11
2023-07-18 22:06:43 <u8353v[m]> but X11 just works!
2023-07-18 22:06:43 <u8353v[m]> i want to know how can i harden it's security?
2023-07-18 22:06:43 <u8353v[m]> or this comes down to hardening the OS?
2023-07-18 22:08:18 <geekosaur> it needs a major server redesign, its security model is from the 1980s
2023-07-18 22:08:32 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
2023-07-18 22:10:56 <geekosaur> I mean, even the IPC it uses is insecure, AF_UNIX sockets the only security is uid-based filesystem access and INET sockets even less. a modern protocol would take advantage of dbus, polkit, etc.
2023-07-18 22:12:52 <geekosaur> any client with any kind of access to the server can observe any event not sent under a server grab, which means passwords can be sniffed by any process
2023-07-18 22:15:59 × sagax quits (~sagax_nb@user/sagax) (Ping timeout: 246 seconds)
2023-07-18 22:16:35 <geekosaur> if you sit down and redesign X11 to fix its security flaws, multiscreen shortcomings, etc., you'll come out with something looking a lot like wayland-the-protocol
2023-07-18 22:16:53 <geekosaur> it's wayland-the-implementation that I don't trust…
2023-07-18 22:19:12 <geekosaur> well, I shouldn't say "don't trust", aside from stability. I question what they've done with what they have; it seems like wayland has failed to actually improve on X11 in many areas where it should easily be able to
2023-07-18 22:19:23 ft joins (~ft@p3e9bc856.dip0.t-ipconnect.de)
2023-07-18 22:22:38 <geekosaur> I also have doubts about how far additional security will get you when people don't make use of it
2023-07-18 22:43:55 <geekosaur> Don't get me wrong — I'd love to see someone pick up and modernize X11. I just think the result will be Wayland.
2023-07-19 00:23:20 × ml| quits (~ml|@user/ml/x-5298235) (Ping timeout: 250 seconds)
2023-07-19 00:36:29 ml| joins (~ml|@user/ml/x-5298235)
2023-07-19 01:02:25 hightower3 joins (~hightower@213-202-64-66.dsl.iskon.hr)
2023-07-19 01:04:57 × hightower2 quits (~hightower@141-136-175-55.dsl.iskon.hr) (Ping timeout: 245 seconds)
2023-07-19 01:47:38 × obimod quits (~weechat@user/obimod) (Ping timeout: 240 seconds)
2023-07-19 02:27:34 × td_ quits (~td@i53870919.versanet.de) (Ping timeout: 272 seconds)
2023-07-19 02:28:46 td_ joins (~td@i5387092E.versanet.de)
2023-07-19 02:42:14 × terrorjack quits (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat)
2023-07-19 02:45:18 terrorjack joins (~terrorjac@2a01:4f8:c17:87f8::)
2023-07-19 02:48:46 × thunderrd quits (~thunderrd@183.182.111.104) (Ping timeout: 245 seconds)
2023-07-19 02:52:33 <absta[m]> Oh do you think Wayland protocol of monolithic compositor is inevitable?
2023-07-19 04:15:26 × geekosaur[c] quits (sid609282@xmonad/geekosaur) (Ping timeout: 246 seconds)
2023-07-19 04:19:22 geekosaur[c] joins (sid609282@xmonad/geekosaur)
2023-07-19 06:09:23 <geekosaur> yes
2023-07-19 06:09:26 <geekosaur> and necessary
2023-07-19 06:10:19 <geekosaur> X11's compositor setup is an ugly hack that will always perform horribly and be weirdly unstable
2023-07-19 06:11:06 <geekosaur> "the compositor is the display server" is the same thing as "the display server is the compositor" which is how it should have been to begin with
2023-07-19 06:12:00 <geekosaur> but with X11's 1980s architecture it isn't possible
2023-07-19 06:15:46 mncheck joins (~mncheck@193.224.205.254)
2023-07-19 06:16:02 <geekosaur> the only real problem with wayland is it'll take 5-10 years to mature
2023-07-19 06:17:16 <geekosaur> (well, the real real problem with it is monolithic gnome being rammed down everyone's throats, but that's rh/gnome, not something required by wayland)
2023-07-19 06:47:50 <geekosaur> I suspect what will happen is gnome and maybe kde will use their own monoliths and everyone else will standardize on wlroots or similar; in fact it's already happening
2023-07-19 06:50:10 <geekosaur> (and indeed I just checked and KDE seems to be moving to wlroots)
2023-07-19 06:51:28 <geekosaur> so in the end wlroots is likely to become a more traditional display server, with the compositor baked in because it needs to be tight up with the low level display drivers to work well
2023-07-19 06:52:19 <geekosaur> and KDE, Sway, Enlightenment, and presumably some form of xmonad among others will use it
2023-07-19 07:00:47 <geekosaur> what I hope is that standardization will see something usable in manageHooks to come back; currently gnome doesn't use it so nobody implements it
2023-07-19 08:56:38 × ft quits (~ft@p3e9bc856.dip0.t-ipconnect.de) (Quit: leaving)
2023-07-19 10:46:05 <absta[m]> I thought gnome went that way because of Wayland, not the other way around ;P
2023-07-19 10:47:08 <absta[m]> It makes sense how compositor and display server is tied together, but I am yet to see why window management and various functionalities like taskbar would be tied up to the compositor. Wish wlroots would become a proper compositor!
2023-07-19 11:10:07 × tv quits (~tv@user/tv) (Quit: derp)
2023-07-19 11:13:36 tv joins (~tv@user/tv)
2023-07-19 11:30:22 obimod joins (~weechat@user/obimod)
2023-07-19 12:11:30 tv1 joins (~tv@user/tv)
2023-07-19 12:11:32 × tv quits (~tv@user/tv) (Ping timeout: 240 seconds)
2023-07-19 14:04:47 <geekosaur> I thought it was
2023-07-19 14:05:11 <geekosaur> wlroots is the compositor component of sway but has been adopted by a number of other wayland window managers
2023-07-19 14:05:26 unclechu joins (~unclechu@2001:470:69fc:105::354)
2023-07-19 14:06:22 <geekosaur> window management doesn't need to be directly tied to the compositor; it wants better integration than X11 offers but that's because it's not part of the window system core / the display driver
2023-07-19 15:16:10 gar[m] joins (~randyorto@2001:470:69fc:105::3:85fa)
2023-07-19 15:19:58 <gar[m]> Can I open certain sites on opening browser on a particular workspace and login to them using selenium with xmonad
2023-07-19 15:21:34 <geekosaur> I would expect yes, although you would need to do some work
2023-07-19 15:22:16 <geekosaur> https://hackage.haskell.org/package/webdriver may be of interest
2023-07-19 16:10:12 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-19 16:37:32 × unclechu quits (~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-19 17:30:33 × jeeeun quits (~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat)
2023-07-19 17:35:58 jeeeun joins (~jeeeun@78.40.148.178)
2023-07-19 18:02:43 scrungus joins (~scrungus@70.24.87.181)
2023-07-19 18:03:44 <scrungus> Does anyone here use window swallowing? I have this issue where when I launch an application through dmenu it swallows whatever terminal window happened to be focused
2023-07-19 18:04:00 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
2023-07-19 18:04:14 unclechu joins (~unclechu@2001:470:69fc:105::354)
2023-07-19 18:07:46 × scrungus quits (~scrungus@70.24.87.181) (Quit: WeeChat 4.0.2)
2023-07-19 18:12:54 scrungus joins (~scrungus@70.24.87.181)
2023-07-19 18:17:46 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2023-07-19 18:17:46 allbery_b joins (~geekosaur@xmonad/geekosaur)
2023-07-19 18:17:49 allbery_b is now known as geekosaur
2023-07-19 18:19:17 × xmonadtrack quits (~xmonadtra@user/geekosaur/bot/xmonadtrack) (Ping timeout: 246 seconds)
2023-07-19 18:36:39 × scrungus quits (~scrungus@70.24.87.181) (Quit: WeeChat 4.0.2)

All times are in UTC.