Newest at the top
| 2025-02-22 01:36:52 +0100 | atwm | (~andrew@19-193-28-81.ftth.cust.kwaoo.net) atwm |
| 2025-02-22 01:36:10 +0100 | sprotte24 | (~sprotte24@p200300d16f1c5a00fd9f2f224d47518c.dip0.t-ipconnect.de) (Quit: Leaving) |
| 2025-02-22 01:32:57 +0100 | <haskellbridge> | <Liamzee> i mean it feels like caching intermediate results in memory with non-destructive updates, i guess it's not the same thing |
| 2025-02-22 01:29:52 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-02-22 01:27:18 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-02-22 01:24:52 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-22 01:22:53 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-02-22 01:13:44 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |
| 2025-02-22 01:13:22 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Remote host closed the connection) |
| 2025-02-22 01:13:00 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-02-22 01:12:07 +0100 | <EvanR> | reversible computing |
| 2025-02-22 01:12:03 +0100 | <EvanR> | when wearable computing combines with reversible garments |
| 2025-02-22 01:11:01 +0100 | <monochrom> | Pretty nice actually. I heard of reversibile computing 20-25 years ago. I forgot why I heard of it, but it's nice to see it realized. |
| 2025-02-22 01:09:25 +0100 | atwm | (~andrew@19-193-28-81.ftth.cust.kwaoo.net) (Ping timeout: 248 seconds) |
| 2025-02-22 01:06:01 +0100 | ljdarj1 | ljdarj |
| 2025-02-22 01:06:00 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds) |
| 2025-02-22 01:05:05 +0100 | hattckory | (~hattckory@149.102.242.103) (Ping timeout: 248 seconds) |
| 2025-02-22 01:04:06 +0100 | atwm | (~andrew@19-193-28-81.ftth.cust.kwaoo.net) atwm |
| 2025-02-22 01:03:06 +0100 | ljdarj1 | (~Thunderbi@user/ljdarj) ljdarj |
| 2025-02-22 00:59:07 +0100 | ljdarj1 | ljdarj |
| 2025-02-22 00:59:07 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 268 seconds) |
| 2025-02-22 00:56:34 +0100 | ljdarj1 | (~Thunderbi@user/ljdarj) ljdarj |
| 2025-02-22 00:49:32 +0100 | hattckory | (~hattckory@149.102.242.103) |
| 2025-02-22 00:45:38 +0100 | __monty__ | (~toonn@user/toonn) (Quit: leaving) |
| 2025-02-22 00:42:15 +0100 | target_i | (~target_i@user/target-i/x-6023099) (Quit: leaving) |
| 2025-02-22 00:41:38 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 272 seconds) |
| 2025-02-22 00:37:32 +0100 | alp | (~alp@2001:861:8ca0:4940:be63:3b87:5f1:7fac) (Ping timeout: 268 seconds) |
| 2025-02-22 00:36:49 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-02-22 00:35:54 +0100 | <haskellbridge> | <Liamzee> sounds eerily familiar |
| 2025-02-22 00:35:49 +0100 | <haskellbridge> | <Liamzee> https://spectrum.ieee.org/reversible-computing |
| 2025-02-22 00:35:47 +0100 | <haskellbridge> | <Liamzee> lol |
| 2025-02-22 00:33:22 +0100 | caconym | (~caconym@user/caconym) caconym |
| 2025-02-22 00:32:04 +0100 | caconym | (~caconym@user/caconym) (Quit: bye) |
| 2025-02-22 00:25:42 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds) |
| 2025-02-22 00:24:29 +0100 | <haskellbridge> | <sm> see you |
| 2025-02-22 00:23:21 +0100 | <haskellbridge> | <magic_rb> Anyway, sleep time |
| 2025-02-22 00:21:40 +0100 | <haskellbridge> | <magic_rb> Im planning to try to shoehorn vodozemac into ement.el (emacs matrix client) to get e2ee |
| 2025-02-22 00:21:30 +0100 | noxp | (~ensyde@2600:381:df29:528d:5c12:4661:6233:7eba) (Ping timeout: 268 seconds) |
| 2025-02-22 00:21:08 +0100 | <haskellbridge> | <magic_rb> And for e2ee youll have to bind against vodozemac which is in rust |
| 2025-02-22 00:20:44 +0100 | <haskellbridge> | <sm> oh interesting, that's good news |
| 2025-02-22 00:20:31 +0100 | <haskellbridge> | <magic_rb> Crypto is largely a client side thing only, https is ofc server side, but e2ee is completely client side |
| 2025-02-22 00:20:26 +0100 | <haskellbridge> | <sm> To be honest, with bridges out of the picture I rarely see state resolution / split brain issues on matrix. (I see it more often on irc, or used to) |
| 2025-02-22 00:19:07 +0100 | <haskellbridge> | <sm> And another part must be the amount of data to be managed, though you could restrict that |
| 2025-02-22 00:18:44 +0100 | ensyde | (~ensyde@70-33-158-82.unassigned.ntelos.net) (Ping timeout: 252 seconds) |
| 2025-02-22 00:18:35 +0100 | <haskellbridge> | <sm> I imagine another hard part of building a matrix server is the cryptography, eg availability of the right good libraries. |
| 2025-02-22 00:18:18 +0100 | <haskellbridge> | <sm> Yes.. I look forward to v3. There's a nifty state visualiser now which must be a help |
| 2025-02-22 00:17:46 +0100 | <haskellbridge> | <magic_rb> And other fun things, dunno much about the actual impl, just what i heard while hanging out in matrix dev adjacent rooms |
| 2025-02-22 00:17:13 +0100 | ensyde_ | (~ensyde@70-33-158-82.unassigned.ntelos.net) |
| 2025-02-22 00:16:43 +0100 | <haskellbridge> | <magic_rb> Effect is that people might not see each others messages. You might get rejoined into a room you left, because the leave event disappears |
| 2025-02-22 00:16:15 +0100 | <haskellbridge> | <magic_rb> If you hear "split brain" its a stateres bug, where room state permanently diverges and different servers see and advertise different state. |