Newest at the top
2025-04-30 20:05:46 +0200 | sayurc | (~sayurc@169.150.203.34) sayurc |
2025-04-30 20:00:38 +0200 | califax | (~califax@user/califx) califx |
2025-04-30 20:00:21 +0200 | califax | (~califax@user/califx) (Remote host closed the connection) |
2025-04-30 19:59:32 +0200 | zzz | (~z@user/zero) zero |
2025-04-30 19:58:50 +0200 | sayurc | (~sayurc@169.150.203.34) (Quit: Konversation terminated!) |
2025-04-30 19:55:24 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 260 seconds) |
2025-04-30 19:50:43 +0200 | euleritian | (~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) |
2025-04-30 19:50:28 +0200 | acidjnk_new | (~acidjnk@p200300d6e71c4f99080af51b38705a6b.dip0.t-ipconnect.de) |
2025-04-30 19:48:29 +0200 | ttybitnik | (~ttybitnik@user/wolper) ttybitnik |
2025-04-30 19:44:59 +0200 | euleritian | (~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) (Ping timeout: 245 seconds) |
2025-04-30 19:44:28 +0200 | zzz | (~z@user/zero) (Client Quit) |
2025-04-30 19:43:08 +0200 | zzz | (~z@user/zero) zero |
2025-04-30 19:39:16 +0200 | <jco> | Yes... I've used pipes-attoparsec a bit as well. Really nice, and it handles a lot of the ugly boilerplate that I had to write myself without it... Maybe I'll try and go down the pipe rabbit hole a bit for this then... |
2025-04-30 19:32:45 +0200 | zzz | (~z@user/zero) (Quit: quit) |
2025-04-30 19:32:09 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
2025-04-30 19:30:56 +0200 | lxsameer | (~lxsameer@Serene/lxsameer) (Ping timeout: 252 seconds) |
2025-04-30 19:29:58 +0200 | fraznel | (~fuag1@c-76-28-152-212.hsd1.wa.comcast.net) |
2025-04-30 19:23:39 +0200 | jespada | (~jespada@r167-61-126-65.dialup.adsl.anteldata.net.uy) jespada |
2025-04-30 19:22:53 +0200 | jespada | (~jespada@r167-61-126-65.dialup.adsl.anteldata.net.uy) (Quit: My Mac has gone to sleep. ZZZzzz…) |
2025-04-30 19:13:58 +0200 | wootehfoot | (~wootehfoo@user/wootehfoot) wootehfoot |
2025-04-30 19:11:12 +0200 | <haskellbridge> | <Jack> Also that’s a cool project |
2025-04-30 19:08:31 +0200 | ft | (~ft@p4fc2a6e6.dip0.t-ipconnect.de) ft |
2025-04-30 19:08:15 +0200 | <EvanR> | the attoparsec parser can partially complete, waiting for you to provide more input |
2025-04-30 19:08:02 +0200 | <haskellbridge> | <Jack> Yeah EvanR’s definitely right |
2025-04-30 19:07:45 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds) |
2025-04-30 19:07:40 +0200 | <haskellbridge> | <Jack> Pipes and conduit kinda exist to fill in the hole that lazy IO makes |
2025-04-30 19:07:31 +0200 | <EvanR> | if you just want to incrementally parse some stream attoparsec exists |
2025-04-30 19:07:26 +0200 | zzz | (~z@user/zero) zero |
2025-04-30 19:06:43 +0200 | <haskellbridge> | <Jack> You’ll be able to tell it to separate the other stuff into discrete events and then pass those events on to other stuff for the messages. |
2025-04-30 19:06:25 +0200 | ft | (~ft@p4fc2a6e6.dip0.t-ipconnect.de) (Quit: leaving) |
2025-04-30 19:06:00 +0200 | Square2 | (~Square4@user/square) (Ping timeout: 252 seconds) |
2025-04-30 19:05:54 +0200 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh |
2025-04-30 19:05:32 +0200 | __monty__ | (~toonn@user/toonn) toonn |
2025-04-30 19:05:21 +0200 | <EvanR> | but I'm not sure if that's relevant |
2025-04-30 19:05:19 +0200 | <haskellbridge> | <Jack> You should think of pipes as a streaming/streaming IO library. I’d say it’s a good fit for that’s use case, at least for the “we’re sending you a bunch of data over time” part. |
2025-04-30 19:05:05 +0200 | <EvanR> | pipes are parameterized by a monad for effects |
2025-04-30 19:03:59 +0200 | <jco> | Another thing is that the BitTorrent protocol has a lot of state-machine style messages, where certain requests are matched with certain responses. This makes me think that pipes maybe is not a great fit, since pipes maybe is more geared towards uniform processing where everything is treated the same...? |
2025-04-30 19:02:37 +0200 | Square3 | (~Square@user/square) Square |
2025-04-30 19:01:55 +0200 | tabaqui | (~tabaqui@167.71.80.236) (Ping timeout: 260 seconds) |
2025-04-30 18:57:55 +0200 | ljdarj | (~Thunderbi@user/ljdarj) ljdarj |
2025-04-30 18:57:36 +0200 | <jco> | Is pipes (or similar) a good fit for protocol implementations in general? And specifically, for BitTorrent... I'm making a small BT (subset) client (hobby project), and I'm contemplating whether to start translating things to use pipes or not. There'll be a lot of back-and-forth messages being sent over TCP... Sorry for unspecific thinking-out-loud question... |
2025-04-30 18:54:45 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
2025-04-30 18:50:39 +0200 | dhil | (~dhil@5.151.29.137) (Ping timeout: 260 seconds) |
2025-04-30 18:49:31 +0200 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds) |
2025-04-30 18:49:24 +0200 | euleritian | (~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) |
2025-04-30 18:48:55 +0200 | econo_ | (uid147250@id-147250.tinside.irccloud.com) |
2025-04-30 18:46:35 +0200 | tabaqui | (~tabaqui@167.71.80.236) tabaqui |
2025-04-30 18:40:20 +0200 | tabaqui | (~tabaqui@167.71.80.236) (Ping timeout: 252 seconds) |
2025-04-30 18:33:09 +0200 | j1n37 | (~j1n37@user/j1n37) (Ping timeout: 260 seconds) |
2025-04-30 18:31:54 +0200 | j1n37- | (~j1n37@user/j1n37) j1n37 |