leeola has quit [Quit: Connection closed for inactivity]
isd has quit [Remote host closed the connection]
sandstorm has joined #sandstorm
sandstorm is now known as isd
jemc has quit [Ping timeout: 258 seconds]
harish has quit [Ping timeout: 258 seconds]
<isd>
As it turns out you can set the timezone via the *controlpanel module. Part of what I'm hitting is I've never actually *used* znc before; still exploring the functionality.
samba__ has joined #sandstorm
bodisiw has joined #sandstorm
bodisiw has quit [Quit: This computer has gone to sleep]
bodisiw has joined #sandstorm
samba__ has quit [Quit: WeeChat 1.7]
bodisiw has quit [Quit: Leaving]
<simpson>
Hi! How does Capn Proto RPC compare to CapTP? We're currently trying to figure out whether we should use Capn's RPC layer instead of implementing CapTP.
xet7 has joined #sandstorm
harish has joined #sandstorm
Zarutian has quit [Quit: Zarutian]
jemc has joined #sandstorm
<maurer>
simpson: What do you intend to do with it? At the moment, level 2 + a little bit of stuff has been done (as referenced at https://capnproto.org/rpc.html)
<maurer>
Most likely CapnProto RPC will be more practical unless you are explicitly interested in larger vats and equality
<simpson>
maurer: I intend to perform arbitrary computations across many vats.
<simpson>
We are adding Capn support to Monte and if we can skip implementing CapTP ourselves then we are fine with that.
<maurer>
simpson: You may want to wait til kentonv is on then, capnproto dealt with multivat primarily through a "brand" mechanism that I'm not familiar with
<simpson>
Yeah, there's only a few people that know this stuff. They do have friam tomorrow though...
<maurer>
I mean, I can answer some things, e.g. we don't have 3-way introduction
<maurer>
err, multivat wasn't branding it was multidomain that was brand
<maurer>
Another thing to consider is that if you find something missing, it might be easier to add it than to build a full CapTP from scratch
<simpson>
As long as actual messages are polymorphic, I think we're fine. (Monte uses a slightly different calling convention from E.)
<dwrensha_>
what do you mean by "polymorphic"?
<simpson>
Well, in E, messages are `[verb :Str, args :List]`, but in Monte, messages are `[verb :Str, args :List, namedArgs :Map]`.
<simpson>
I've admittedly only scratched the surface of the RPC layer.
<kentonv>
simpson, Cap'n Proto is based on CapTP. Mark Miller helped us with the design, and I think he now recommends Cap'n Proto unless you are specifically programming in E.
<simpson>
kentonv: SGTM
<kentonv>
note that Cap'n Proto is statically typed (via .capnp files), which is a major difference
<simpson>
Hm. To what extent? Monte is dynamically typed but its messages always have a schema.
<simpson>
Maybe that doesn't especially matter. Maybe I should read the code again.
<kentonv>
well, in theory Cap'n Proto wants you to define all your types in .capnp IDL. However, you could always define a type that is just a set of string / value pairs.
<simpson>
In practice we're going to basically be sending Data-E around.
<simpson>
So we'll encode our graph exits as caps in the cap table and hopefully it all Just Works.
jemc has quit [Ping timeout: 260 seconds]
jemc has joined #sandstorm
jemc has quit [Ping timeout: 240 seconds]
HalfEatenPie has quit [Ping timeout: 260 seconds]
HalfEatenPie has joined #sandstorm
jemc has joined #sandstorm
jemc has quit [Ping timeout: 240 seconds]
harish has quit [Ping timeout: 258 seconds]
Zarutian has joined #sandstorm
afuentes has joined #sandstorm
xet7 has quit [Quit: Leaving]
ShalokShalom has quit [Remote host closed the connection]
<TimMc>
It sounds like maaaybe wildcard support could be coming to Let's Encrypt soon. :-)
<KCinJP>
isd: See you there.
yeehi has joined #sandstorm
yeehi1 has quit [Ping timeout: 268 seconds]
<isd>
See you there.
<isd>
TimMc: the last time I looked, the issues weren't about ACME protocol support, but rather logistical/political issues with the other CAs
<isd>
So I'm not hopeful.
<isd>
Perhaps I will try to pick Seth's brain about it if he's here this weekend though.
<isd>
It would be *really* nice to be able to get wildcard certs from letsencrypt though
<TimMc>
isd: Hmm, what is the relationship between LE and boulder, then?
<isd>
TimMc: Let's encrypt is a particular CA. ACME is the protocol used for automatically issuing certificates, and it's an IETF standard; in theory someone else could do the same thing. Boulder is an ACME server.
dwrensha has joined #sandstorm
<TimMc>
So LE might implement wildcard support in the server code they use, but not actually turn it on for their own service?
<isd>
TimMc: yeah, that's a possibility
<isd>
Again, the last time I spoke to someone about it, it sounded like the issues were more around the politics of them issuing wildcard certs than the engineering of it.
<TimMc>
*nod*
<TimMc>
I was hoping that the engineering work was a sign of a political change, but I guess that's not a given.
<isd>
Yeah, I don't know
<isd>
I think I will try to find an appropriate brain to pick this weekend.
<TimMc>
isd: There's the guy running LE Office Hours. :-)
michaelw has quit [Remote host closed the connection]
<isd>
That's true! I will have to go to that.
<isd>
Ah, Noah's doing it. cool.
<mrdomino>
sandstorm core folks, i'm trying to figure out how to persist data that a grain can access across restarts -- specifically cron tasks
<mrdomino>
my current best guess is that i need to implement a key/value save/restore call on SandstormCore
<dwrensha>
mrdomino: it's quite possible that you'll need to add methods on SandstormCore
<dwrensha>
which process is saving what exactly?
<dwrensha>
hm... I gather you are implementing scheduleAt() in supervisor.c++
michaelw has joined #sandstorm
FredFredFred has joined #sandstorm
FredFredFred_ has quit [Ping timeout: 260 seconds]
FredFredFred_ has joined #sandstorm
FredFredFred has quit [Ping timeout: 246 seconds]
CaptainCalliope_ has quit [Ping timeout: 255 seconds]
CaptainCalliope_ has joined #sandstorm
xming_ has quit [Ping timeout: 255 seconds]
xming has joined #sandstorm
xming has joined #sandstorm
cstrahan has quit [Ping timeout: 255 seconds]
cstrahan has joined #sandstorm
FredFredFred has joined #sandstorm
FredFredFred_ has quit [Ping timeout: 240 seconds]
<mrdomino>
dwrensha: yes correct
<mrdomino>
someone needs to know the existing scheduled tasks... i'm just realizing now that it shouldn't be the supervisor
<mrdomino>
since the supervisor is typically not around when it's time to run a scheduled task
<mrdomino>
(this should be obvious, but i've been zoomed-in trying to understand the parts of the system)
<mrdomino>
(i was imagining that the supervisor would load the set of scheduled tasks on startup)
leeola has joined #sandstorm
jemc has quit [Ping timeout: 256 seconds]
jemc has joined #sandstorm
Telesight has quit [Quit: Leaving.]
<mrdomino>
ergh, is the best place for this really the frontend?
yeehi1 has joined #sandstorm
yeehi has quit [Ping timeout: 260 seconds]
<TimMc>
isd: More details on that boulder github issue. "Our position is that wildcard issuance is still not a high priority for Boulder, though it has now been unblocked by the specification update and is a possibility at sometime in the future."
cevi has quit [Quit: ZNC 1.6.4+deb1+b1 - http://znc.in]