IRC channel logs
2025-11-19.log
back to list of logs
<ArneBab>cwebber: regarding blockers: besides needing full support before I can provide a REPL, the other blocker was parallel loading -- which is what I fixed last sunday. Because I couldn’t use a tool that has to load 4 files one after the other before it can run. <ridley>tsyesika, can I ask why OCapN uses op:gc-answer/op:gc-export with a single position and not op:gc-answers/op:gc-exports with a list of positions? <ridley>It seems like in at least some implementations people would be taking a list and then sending an op:gc-export for every item <cwebber>it could probably be compressed into a list in many circumstances for less operations <cwebber>an optimization worth filing an issue about <cwebber>ridley: how about you file an issue on github and link it? <cwebber>we should be doing more conversations there <ridley>I will make the issue. I can move my ocapn questions there in the future if that is preferred. I just thought it was dead. <ridley>* move the questions to #ocapn I mean. <jfred>I've gotta try out goblinshare soon :) looks cool! <dthompson>ridley: talking more in #ocapn would actually be great because we once heard from a potential funder that the channel seemed dead and they wondered if ocapn was still active <dthompson>which is a fair question when you're not in the know! <ridley>oh okay I will put my ocap stuff there <dthompson>between that and the outdated website, it does appear inactive! <ridley>and leave my fawning over spritely blog posts for here <dthompson>we've updated the outdated stuff on the ocapn home page, at least. redesign forthcoming :) <dthompson>spritely blog readers will be eating good this week and next since we just published juli's goblinshare post yesterday and (spoiler alert) we've got another post lined up for next week. <ridley>I started reading Juli's post but haven't gotten through it yet <dthompson>ACTION is currently drafting fosdem talk proposals