Newest at the top
| 2024-09-29 22:14:49 +0200 | <__monty__> | Sure, but I'm on old hardware and in big rooms so I'm not likely to have the best of times. |
| 2024-09-29 22:13:42 +0200 | <haskellbridge> | <sm> I would say don't believe all the matrix client bashing you hear. The experience probably depends on platform , memory, and rooms/activities |
| 2024-09-29 22:13:21 +0200 | druchan | (uid567859@id-567859.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2024-09-29 22:12:37 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) merijn |
| 2024-09-29 22:11:43 +0200 | <__monty__> | Especially when Element does an Olm rugpull with a big ol' CVE. |
| 2024-09-29 22:08:28 +0200 | <Rembane> | Speaking of chats... I must post this: https://xkcd.com/1782/ |
| 2024-09-29 22:08:10 +0200 | <geekosaur> | -fprint-explicit-foralls, unsurprisingly |
| 2024-09-29 22:07:46 +0200 | <pdxleif> | What's the option to get GHCi to show the foralls in type signatures explicitly? |
| 2024-09-29 22:07:16 +0200 | pdxleif | (~ubuntu@ec2-35-163-144-64.us-west-2.compute.amazonaws.com) pdxleif |
| 2024-09-29 22:07:08 +0200 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Remote host closed the connection) |
| 2024-09-29 22:05:43 +0200 | <geekosaur> | and the matrix spec is a moving target that I'm not sure client devs can keep up with |
| 2024-09-29 22:05:22 +0200 | <geekosaur> | yeh, they all have big problems |
| 2024-09-29 22:05:06 +0200 | <__monty__> | Yeah, it's pretty horrendous. But so are all the Matrix clients if I'm to believe the people I talk to. |
| 2024-09-29 22:05:04 +0200 | <haskellbridge> | <sm> geekosaur: yeah :-/ uh.. a bot then ? |
| 2024-09-29 22:05:02 +0200 | <geekosaur> | you mean weechat-matrix? |
| 2024-09-29 22:04:42 +0200 | <glguy> | I guess. For me the only thing worse than using Matrix would be using Matrix via an IRC client |
| 2024-09-29 22:04:20 +0200 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2024-09-29 22:04:02 +0200 | <__monty__> | glguy: Well, not with that attitude. But my cursed Bitlbee-libPurple-PurpleMatrix+<a sprinkling of Bash> makes *any* IRC client a Matrix client ; ) |
| 2024-09-29 22:03:42 +0200 | <geekosaur> | I'm not sure either one is easier. servers have to deal with e.g. the nightmare that is room sync between federated servers; clients have to do all the heavy lifting for pretty much every feature |
| 2024-09-29 22:02:02 +0200 | <glguy> | __monty__: glirc isn't a matrix client |
| 2024-09-29 22:01:54 +0200 | <haskellbridge> | <sm> geekosaur: yes! |
| 2024-09-29 22:01:49 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds) |
| 2024-09-29 22:01:35 +0200 | <__monty__> | Not a fan of GlIRC? |
| 2024-09-29 22:01:33 +0200 | <geekosaur> | hell, I keep thinking about writing a bridge in Haskell, especially after learning that the heisenbridge author/maintainer is apparently stepping back |
| 2024-09-29 22:01:00 +0200 | <haskellbridge> | <sm> (which is easier ? I'm guessing client) |
| 2024-09-29 22:00:43 +0200 | <haskellbridge> | <sm> or an actually good server for that matter |
| 2024-09-29 22:00:23 +0200 | <haskellbridge> | <sm> so, who's going to build the actually good matrix client in haskell ? |
| 2024-09-29 22:00:09 +0200 | <TMA> | more patience is needed for IRCv3 :) |
| 2024-09-29 21:59:57 +0200 | <haskellbridge> | <sm> I don't think typing notifications come over the irc bridge, you're fine monochrom :) |
| 2024-09-29 21:59:47 +0200 | <TMA> | hey IPv6 is around since 1995 and it is slowly gaining traction: 1998 IETF draft standard, 2017 internet standard, 2024 my internet provider offers IPv6 connectivity and assigns addresses upon request... |
| 2024-09-29 21:59:31 +0200 | <monochrom> | OK OK I will write and proofread properly in emacs before pasting into matrix. :) |
| 2024-09-29 21:58:49 +0200 | <monochrom> | Um you don't believe in taking time to write and proofread properly before pressing enter? :) |
| 2024-09-29 21:58:26 +0200 | <haskellbridge> | <sm> lol yeah sometimes in a chat the typing indicator comes and goes.. for minutes.. yet you can't look away |
| 2024-09-29 21:58:23 +0200 | <yushyin> | seems like weechat has +typing support since sept. 2021 o.O |
| 2024-09-29 21:57:48 +0200 | <geekosaur> | (matrix has typing notifications. if someone takes more than about 30 seconds I'm always like "shit or get off the pot already") |
| 2024-09-29 21:56:51 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) merijn |
| 2024-09-29 21:56:43 +0200 | <monochrom> | Yeah that too. :) |
| 2024-09-29 21:56:12 +0200 | <geekosaur> | neh, they'll start showing up after everyone has already abandoned IRC |
| 2024-09-29 21:56:05 +0200 | haskellbridge | sm doesn't send them but still receives them, when that's allowed... which is cheating |
| 2024-09-29 21:55:45 +0200 | <monochrom> | In the case of IRCv3, the theory has been around for decades. You can bet it will stay as theory forever. |
| 2024-09-29 21:55:37 +0200 | <haskellbridge> | <sm> agreed, turn them off |
| 2024-09-29 21:55:02 +0200 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) |
| 2024-09-29 21:54:57 +0200 | <Rembane> | I don't want typing notifications, they stress me out. |
| 2024-09-29 21:54:52 +0200 | <monochrom> | Also, "future version" is euphemism for vapourware. :) |
| 2024-09-29 21:54:10 +0200 | dontdieych2 | (~a@user/dontdieych2) (Quit: WeeChat 4.4.2) |
| 2024-09-29 21:53:37 +0200 | <geekosaur> | I mean, it already has a spec for typing notifications but good luck finding clients that use it |
| 2024-09-29 21:53:28 +0200 | <Rembane> | I think Weechat supports some of them. I need to read up on this! |
| 2024-09-29 21:51:54 +0200 | <geekosaur> | (the server we're on supports IRCv3) |
| 2024-09-29 21:51:42 +0200 | <TMA> | yes, that might be the name. |
| 2024-09-29 21:51:35 +0200 | <geekosaur> | in either server or clients |