| 2023-10-30 02:13:11 +0000 | hightower2 | (~hightower@141-136-253-109.dsl.iskon.hr) (Read error: Connection reset by peer) |
| 2023-10-30 02:14:56 +0000 | hightower2 | (~hightower@141-136-253-109.dsl.iskon.hr) |
| 2023-10-30 03:07:21 +0000 | td_ | (~td@i53870907.versanet.de) (Ping timeout: 260 seconds) |
| 2023-10-30 03:09:00 +0000 | td_ | (~td@i5387092F.versanet.de) |
| 2023-10-30 06:29:32 +0000 | chomwitt | (~chomwitt@2a02:587:7a01:8f00:1ac0:4dff:fedb:a3f1) |
| 2023-10-30 07:44:29 +0000 | hightower3 | (~hightower@141-136-161-29.dsl.iskon.hr) |
| 2023-10-30 07:46:47 +0000 | <haskellbridge> | <Solid> Let's keep this channel at least vaguely on-topic, shall we? Something like this warsants a ban for spam next time, I think. |
| 2023-10-30 07:47:20 +0000 | hightower2 | (~hightower@141-136-253-109.dsl.iskon.hr) (Ping timeout: 272 seconds) |
| 2023-10-30 07:48:01 +0000 | <haskellbridge> | <Solid> liskin: Well, same idea, different execution. Something that seems to be quite common when comparing our setups, if I remember the last ZuriHac well enough :) |
| 2023-10-30 08:34:49 +0000 | derpyxdhs | (~Thunderbi@user/derpyxdhs) |
| 2023-10-30 08:47:41 +0000 | derpyxdhs | (~Thunderbi@user/derpyxdhs) (Quit: derpyxdhs) |
| 2023-10-30 09:35:47 +0000 | <liskin> | Yeah, although I probably remember even less than you (there was one additional ZuriHac for me to rewrite my memories) |
| 2023-10-30 10:02:38 +0000 | <haskellbridge> | <Solid> Let's keep this channel at least vaguely on-topic, shall we? Something like this warrants a ban for spam next time, I think. |
| 2023-10-30 10:03:02 +0000 | <haskellbridge> | <Solid> Still bummed I couldn't attend that :/ Hopefully next year! |
| 2023-10-30 11:03:38 +0000 | srk_ | (~sorki@user/srk) |
| 2023-10-30 11:06:59 +0000 | srk | (~sorki@user/srk) (Ping timeout: 255 seconds) |
| 2023-10-30 11:06:59 +0000 | srk_ | srk |
| 2023-10-30 11:19:30 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:dad:ed4f:4ccc:4064) (Ping timeout: 272 seconds) |
| 2023-10-30 11:20:22 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 11:26:39 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2023-10-30 11:31:56 +0000 | srk_ | (~sorki@user/srk) |
| 2023-10-30 11:34:21 +0000 | srk | (~sorki@user/srk) (Ping timeout: 255 seconds) |
| 2023-10-30 11:34:46 +0000 | srk_ | srk |
| 2023-10-30 12:40:12 +0000 | chomwitt | (~chomwitt@2a02:587:7a01:8f00:1ac0:4dff:fedb:a3f1) (Ping timeout: 240 seconds) |
| 2023-10-30 13:02:26 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 246 seconds) |
| 2023-10-30 13:05:17 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 13:08:10 +0000 | chomwitt | (~chomwitt@ppp-94-67-189-112.home.otenet.gr) |
| 2023-10-30 14:05:34 +0000 | <liskin> | Yeah, I'm starting to think I might be able to go again next year |
| 2023-10-30 14:06:13 +0000 | <liskin> | Need to book accomodation earlier though, sleeping in a damp cellar wasn't the best |
| 2023-10-30 14:10:53 +0000 | <Solid> | uff |
| 2023-10-30 14:48:12 +0000 | cfricke | (~cfricke@user/cfricke) (Ping timeout: 248 seconds) |
| 2023-10-30 15:22:41 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 258 seconds) |
| 2023-10-30 15:36:00 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 15:40:29 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 245 seconds) |
| 2023-10-30 15:54:10 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 15:55:30 +0000 | <haskellbridge> | <liskin> lol, I can't even mark rooms as read in Matrix |
| 2023-10-30 15:57:07 +0000 | <haskellbridge> | <liskin> This is beyond ridiculous. How can they keep failing at doing the most basic things IRC had for decades :-( |
| 2023-10-30 15:58:10 +0000 | <geekosaur> | which client? |
| 2023-10-30 15:58:45 +0000 | <geekosaur> | afaict the way you do it in element android is to press the X on "jump to unread" |
| 2023-10-30 15:59:13 +0000 | <geekosaur> | which… not exactly intuitive |
| 2023-10-30 15:59:32 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 246 seconds) |
| 2023-10-30 15:59:45 +0000 | <liskin> | both nheko and element |
| 2023-10-30 16:00:00 +0000 | <liskin> | element has a context menu entry for it |
| 2023-10-30 16:00:18 +0000 | <geekosaur> | interesting, those normally do it "live" |
| 2023-10-30 16:00:20 +0000 | <liskin> | and it does absolutely nothing, because there's probably some state somewhere that is messed up or something |
| 2023-10-30 16:10:01 +0000 | <haskellbridge> | <Tranquil Ity> Usually opening and closing a room and spamming escape works |
| 2023-10-30 16:10:30 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 16:11:31 +0000 | <liskin> | Yeah, that has been my experience too. Until today. |
| 2023-10-30 16:19:47 +0000 | <haskellbridge> | <Tranquil Ity> In any case it.s almost always a bug in the client rather than an issue with the protocol. In addition, if you are on a slow homeserver (such as matrix.org), there might be a delay depending on how well the client deals with unresponsive servers as clearing notifications seems to involve a server round trip. |
| 2023-10-30 16:20:37 +0000 | <geekosaur> | yes, they're sent to the server and then forwarded to other clients using the account |
| 2023-10-30 16:20:54 +0000 | <haskellbridge> | <Tranquil Ity> In any case it.s almost always a bug in the client rather than an issue with the protocol. In addition, if you are on a slow and/or buggy homeserver (such as matrix.org), there might be a delay depending on how well the client deals with unresponsive servers as clearing notifications seems to involve a server round trip. |
| 2023-10-30 16:21:29 +0000 | <haskellbridge> | <Tranquil Ity> Yep, that seems to be what the spec suggests. Send a read event, then sync. |
| 2023-10-30 16:21:36 +0000 | <geekosaur> | I've seen, for example, someone highlighting me, the phone pops up a notification, then the desktop client marks it read, then the notification disappears once the phone receives it |
| 2023-10-30 16:23:05 +0000 | <haskellbridge> | <Tranquil Ity> Yep I.ve seen that as well |
| 2023-10-30 16:23:06 +0000 | <haskellbridge> | <Tranquil Ity> I believe there.s some account data or maybe to-device shared on what.s the active client between clients that support it, as it doesn.t happen that often |
| 2023-10-30 16:24:31 +0000 | <haskellbridge> | <Tranquil Ity> Negotiating which client will be used to deliver a notif, and whether multiple will deliver it, certainly sounds like a pretty difficult problem |
| 2023-10-30 16:25:21 +0000 | <geekosaur> | afaict all of them receive it and the first one to mark it read clears it for the others |
| 2023-10-30 16:27:02 +0000 | <haskellbridge> | <Tranquil Ity> That is possible |
| 2023-10-30 16:27:03 +0000 | <haskellbridge> | <Tranquil Ity> Maybe might be worth it to suggest an MSC for negotiating which clients will silence their notifications |
| 2023-10-30 16:27:04 +0000 | <haskellbridge> | <Tranquil Ity> I haven.t looked too deep into it, maybe I should |
| 2023-10-30 16:30:39 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 240 seconds) |
| 2023-10-30 16:33:40 +0000 | <haskellbridge> | <Tranquil Ity> Right now my priority is figuring out why `rotation_period_msgs` is not working as it.s supposed to in element, and whether that is a security issue heh. |
| 2023-10-30 16:36:44 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 17:55:11 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 260 seconds) |
| 2023-10-30 18:06:57 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 18:13:23 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 260 seconds) |
| 2023-10-30 18:25:32 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 18:31:35 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 255 seconds) |
| 2023-10-30 18:32:25 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 18:46:00 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 272 seconds) |
| 2023-10-30 18:58:18 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 19:03:33 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 260 seconds) |
| 2023-10-30 19:05:05 +0000 | justache | justHaunted |
| 2023-10-30 19:14:52 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 19:20:44 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 258 seconds) |
| 2023-10-30 19:33:03 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 19:39:08 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 258 seconds) |
| 2023-10-30 19:47:39 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 19:53:43 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) (Ping timeout: 260 seconds) |
| 2023-10-30 19:56:41 +0000 | defjam | (~defjam@2a02:c7e:2807:b900:ac13:d447:79b2:3f03) |
| 2023-10-30 22:30:00 +0000 | chomwitt | (~chomwitt@ppp-94-67-189-112.home.otenet.gr) (Ping timeout: 255 seconds) |
| 2023-10-30 23:13:10 +0000 | terrorjack4 | (~terrorjac@2a01:4f8:c17:87f8::) |
| 2023-10-30 23:14:11 +0000 | Mion | (~Urist@archlinux/op/MrElendig) |
| 2023-10-30 23:15:23 +0000 | MrElendig | (~Urist@archlinux/op/MrElendig) (Ping timeout: 264 seconds) |
| 2023-10-30 23:15:23 +0000 | geekosaur | (sid609282@xmonad/geekosaur) (Ping timeout: 264 seconds) |
| 2023-10-30 23:15:24 +0000 | ectospasm | (~ectospasm@user/ectospasm) (Ping timeout: 264 seconds) |
| 2023-10-30 23:15:25 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) (Ping timeout: 264 seconds) |
| 2023-10-30 23:15:26 +0000 | terrorjack4 | terrorjack |
| 2023-10-30 23:16:11 +0000 | geekosaur | (sid609282@xmonad/geekosaur) |
| 2023-10-30 23:28:21 +0000 | ectospasm | (~ectospasm@user/ectospasm) |
| 2023-10-30 23:55:20 +0000 | sometypeofuser | (~user@92.40.184.196.threembb.co.uk) |