00:10 <kentonv> oh, I think Darude just figured out a bug that's been reported a few times that we never figured out. Sweet.

00:26 <TimMc> ha!

04:30 <matheusrv> is @kentonv only? are you here kentonv??

04:30 <matheusrv> online* o.O

04:31 <kentonv> hi

04:35 <matheusrv> how do u do? finaly i could talk to you.. i want to suport sandstorm

04:35 <matheusrv> can us go to private?

04:36 <kentonv> ok...

12:50 <Darude> Hello community. Thank you very much for your advice last night. I'm self-hosting a Sandstorm instance and would like to also self-host LDAP to provide authentication. Does anyone know of a simple guide to setting up an LDAP server to this end? Just a handful of basic user accounts.

18:16 <simpson> Good morning. In Capn Proto, groups basically behave like new ways of interpreting structs when it comes to the struct layout in the packet, right? Would that be a reasonable implementation approach, or am I oversimplifying?

18:41 <dwrensha> simpson: I'm not sure exactly what you mean, but it sounds like you have the right idea.

18:41 <dwrensha> a group has the same data section and pointer section as its parent struct

18:41 <simpson> dwrensha: My Monte implementation of Capn treats messages as an opaque buffer of words, and then interprets the message by overlaying a schema on top.

18:42 <simpson> I know it's different from the codegen that most of the other language backends do, but it seemed better from a cap-based POV.

18:42 <simpson> So I was thinking that a group's schema is basically just an alternative schema for the same struct.

18:42 <dwrensha> the schema can be provided at run time, I guess?

18:43 <simpson> Yeah.

18:43 <simpson> e.g. https://github.com/monte-language/typhon/blob/capn/mast/lib/capnp.mt#L388-L408

18:43 <dwrensha> sounds like how the dynamic reflection API works in capnproto-c++

18:54 <simpson> Okay, I think I've got my plan. I'll extend my schemata from two to three kinds of field access; in addition to data and pointer accesses, I'll add *group* access, which merely reinterprets the struct.

22:31 <mrdomino> blargh, spk dev is busted on ubuntu 16.04.1 and ubuntu 14.04 has the gets bug in the ekam build

22:32 <mrdomino> what OS are you guys using to develop on? it'd probably be easiest if i just used that

22:46 <dwrensha> debian is probably easiest

22:47 <dwrensha> I use fedora

22:50 <mrdomino> jessie or other?

22:51 <dwrensha> I'd go with sid/testing

22:51 <dwrensha> well, depends on the use case

22:51 <mrdomino> strictly sandstorm core + app development

22:52 <dwrensha> if you're setting up an automated build thing that you want to have keep working... then maybe jessie is better

22:56 <kentonv> FWIW vagrant-spk uses jessie and I personally use sid, so those are pretty well-exercised distros for Sandstorm development.

23:23 <HeyItsMeUrIRC> what do y'all think of this

23:23 <HeyItsMeUrIRC> https://github.com/racklab/Monorail/wiki/Extension-Spec

23:23 <HeyItsMeUrIRC> it's the API for Monorail Extensions