2023/07/18

2023-07-18 01:08:56 +0000 <jabuxas> to explain a bit better the issue, when I click edit, it does go into edit mode, but as soon as my cursor touches the bar, it kicks me out of edit mode
2023-07-18 01:32:56 +0000ft(~ft@p508dbe50.dip0.t-ipconnect.de) (Ping timeout: 246 seconds)
2023-07-18 01:34:58 +0000ft(~ft@p3e9bc856.dip0.t-ipconnect.de)
2023-07-18 02:28:38 +0000td_(~td@i53870921.versanet.de) (Ping timeout: 272 seconds)
2023-07-18 02:30:02 +0000td_(~td@i53870919.versanet.de)
2023-07-18 03:02:53 +0000vetu_(~vetu@91-156-31-97.elisa-laajakaista.fi) (Read error: Connection reset by peer)
2023-07-18 03:02:58 +0000vetu(~vetu@91-156-31-97.elisa-laajakaista.fi)
2023-07-18 05:47:10 +0000mncheck(~mncheck@193.224.205.254)
2023-07-18 07:36:16 +0000 <xmonadtrack> xmonad-contrib Tony Zorman * v0.17.1-161-g5b5a5178: ci/stack: Add lts-21 resolver (2 days ago, 1 file, 3+ 1-) https://github.com/xmonad/xmonad-contrib/commit/5b5a51787ce8
2023-07-18 07:36:17 +0000 <xmonadtrack> xmonad-contrib Tony Zorman * v0.17.1-162-g34b544b7: ci/cabal: Bump GHC versions (2 days ago, 2 files, 13+ 13-) https://github.com/xmonad/xmonad-contrib/commit/34b544b7a17b
2023-07-18 07:36:25 +0000 <xmonadtrack> xmonad-contrib Tony Zorman {GitHub} * v0.17.1-165-g7062b75e: Merge pull request #819 from slotThe/ci/bump (29 seconds ago, 0 files, 0+ 0-) https://github.com/xmonad/xmonad-contrib/commit/7062b75ea993
2023-07-18 07:41:21 +0000 <xmonadtrack> xmonad Tony Zorman * v0.17.2-61-g9138046: ci/stack: Add lts-21 resolver (2 days ago, 1 file, 1+ 0-) https://github.com/xmonad/xmonad/commit/9138046ec515
2023-07-18 07:41:22 +0000 <xmonadtrack> xmonad Tony Zorman * v0.17.2-62-g0932779: ci/cabal: Bump GHC versions (2 days ago, 2 files, 13+ 13-) https://github.com/xmonad/xmonad/commit/0932779f15c7
2023-07-18 07:41:30 +0000 <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 +0000defjam(~defjam@90.211.252.220)
2023-07-18 08:32:48 +0000rundown(~defjam@2a02:c7e:2807:b900:40dc:8f12:e31c:79a6) (Ping timeout: 272 seconds)
2023-07-18 08:36:36 +0000hightower2(~hightower@141-136-175-55.dsl.iskon.hr) (Ping timeout: 272 seconds)
2023-07-18 08:59:12 +0000ft(~ft@p3e9bc856.dip0.t-ipconnect.de) (Quit: leaving)
2023-07-18 09:13:14 +0000liskin[m](~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-18 09:18:18 +0000unclechu(~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-18 09:26:20 +0000hightower2(~hightower@85.94.71.188)
2023-07-18 09:32:59 +0000vetu(~vetu@91-156-31-97.elisa-laajakaista.fi) (Read error: Connection reset by peer)
2023-07-18 09:33:06 +0000vetu_(~vetu@91-156-31-97.elisa-laajakaista.fi)
2023-07-18 12:03:41 +0000obimod(~weechat@user/obimod)
2023-07-18 12:07:41 +0000tv(~tv@user/tv) (Ping timeout: 246 seconds)
2023-07-18 12:09:34 +0000tv(~tv@user/tv)
2023-07-18 12:14:07 +0000tv(~tv@user/tv) (Ping timeout: 245 seconds)
2023-07-18 12:15:59 +0000tv(~tv@user/tv)
2023-07-18 14:13:32 +0000mncheck(~mncheck@193.224.205.254) (Ping timeout: 272 seconds)
2023-07-18 15:14:52 +0000thunderrd(~thunderrd@183.182.111.104)
2023-07-18 15:32:52 +0000beastwick[m](~beastwick@2001:470:69fc:105::3:8087)
2023-07-18 15:50:11 +0000berberman_(~berberman@user/berberman) (Quit: ZNC 1.8.2 - https://znc.in)
2023-07-18 15:50:33 +0000berberman(~berberman@user/berberman)
2023-07-18 16:03:06 +0000sagax(~sagax_nb@user/sagax)
2023-07-18 16:52:31 +0000hightower2(~hightower@85.94.71.188) (Ping timeout: 245 seconds)
2023-07-18 16:55:08 +0000hightower2(~hightower@85.94.71.188)
2023-07-18 17:02:27 +0000berberman(~berberman@user/berberman) (Quit: ZNC 1.8.2 - https://znc.in)
2023-07-18 17:02:48 +0000berberman(~berberman@user/berberman)
2023-07-18 17:28:21 +0000hightower2(~hightower@85.94.71.188) (Ping timeout: 245 seconds)
2023-07-18 20:45:39 +0000hightower2(~hightower@141-136-175-55.dsl.iskon.hr)
2023-07-18 21:07:24 +0000mon_aaraj(~montchncs@2001:470:69fc:105::8e6b)
2023-07-18 22:06:43 +0000 <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 +0000 <u8353v[m]> but X11 just works!
2023-07-18 22:06:43 +0000 <u8353v[m]> i want to know how can i harden it's security?
2023-07-18 22:06:43 +0000 <u8353v[m]> or this comes down to hardening the OS?
2023-07-18 22:08:18 +0000 <geekosaur> it needs a major server redesign, its security model is from the 1980s
2023-07-18 22:08:32 +0000liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-07-18 22:10:56 +0000 <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 +0000 <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 +0000sagax(~sagax_nb@user/sagax) (Ping timeout: 246 seconds)
2023-07-18 22:16:35 +0000 <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 +0000 <geekosaur> it's wayland-the-implementation that I don't trust…
2023-07-18 22:19:12 +0000 <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 +0000ft(~ft@p3e9bc856.dip0.t-ipconnect.de)
2023-07-18 22:22:38 +0000 <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 +0000 <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.