01:38 <MatheusRV> @JonTheNiceGuy but kiwirc is booring .. move to mattermost or rocket.chat it incentivate the project.. my english is trash.. i use gramatic and here it does not work

01:39 <pdurbin> MatheusRV: which one do you prefer, mattermost or rocket.chat?

03:32 <kentonv> MatheusRV, you don't have to use kiwi... you can use any IRC client. Arguably we should switch to Rocket.Chat on Sandstorm, but a lot of people who are happy to keep a channel open in IRC won't be as happy to keep a browser tab open for us. :/

03:58 <compuguy> kentonv: you can also self host thelounge

05:16 <ocdtrekkie> kentonv: Did you by chance see the Content-Range question on the list in the Kiwix thread?

14:03 <matheusrv> I agree with @compuguy The Lounge is perfect solution..

14:05 <matheusrv> i create alot of suggestions on github issue of snadstorm app market, if someone could give me a feedback I will be happy :) https://github.com/sandstorm-io/sandstorm-app-market/issues

14:09 <TimMc> Yeah, definitely wouldn't keep a browser tab open for this. It's not worth the tens of MiBs of memory that would require. :-P

14:10 <matheusrv> TheLounge is a self-hosted IRC server.. if you prefer use the IRC client no problem

14:10 <TimMc> Ah, OK.

14:11 <matheusrv> i think in change for the lounge cause the chat isnt clear everytime you enter

14:11 <pdurbin> I use Shout, the previous version of The Lounge, to make it easy for my users to join my projects IRC channel, and people use it a lot. Without it, I think I'd have way less participation in IRC.

14:11 <matheusrv> and the chat could flow with this

14:11 <TimMc> IRC bridges are fine by me, as long as they work...

14:14 <matheusrv> @TimMc do you know Franz? www.meetfranz.com is a nice away to run from tabs

14:23 <TimMc> ehhhh, don't need more apps

14:24 <TimMc> One of the important things about IRC is that I can run it on my home server, and I can be logged into that from either home or work.

21:29 <mrdomino> kentonv: what's the rationale behind having a Runnable on the cron interface, rather than just waking up the grain?

21:31 <kentonv> mrdomino, well, two reasons. First, if Sandstorm only woke up the grain, the grain would have to have its own possibly-complicated logic to figure out what tasks are scheduled. Having Sandstorm call it is a lot more convenient for app developers.

21:31 <kentonv> mrdomino, second, Sandstorm needs some way to know when it's safe to shut the grain down again

21:31 <mrdomino> ok, great

21:32 <kentonv> mrdomino, also keep in mind that we want to display some information in the notifications UI about scheduled tasks. Hmm, it occurs to me that my API proposal doesn't include any display info...

21:32 <mrdomino> yeah, i was wondering if that'd be included later on

21:33 <mrdomino> i'm noticing some confusion about how you'd get a runnable to persist across grain runs, but maybe i just haven't looked closely enough at it

21:33 <kentonv> mrdomino, it would need to implement the AppPersistent interface, and the app's MainView needs to implement restore()

21:43 <mrdomino> okay, so capnproto generic types make a little more sense now... i have a question that's something like "how do you specify what AppObjectId is?" or "how do you implement AppPersistent over a Runnable?" although both of those might be resolvable by staring at the code longer

21:45 <kentonv> mrdomino, AppObjectId is entirely up to the app. It can specify whatever type it wants to use to identify objects. Sandstorm obtains these values by calling save() on AppPersistent objects and then sends the value back to the app when calling MainView.restore().

21:46 <kentonv> mrdomino, to have one object implement both interfaces, you'll want to create a capnp file with a definition like "interface MyRunnable extends(AppPersistent(MyObjectId), Runnable) {}"

21:46 <kentonv> then implement that interface in your app code

21:46 <kentonv> (or instead of "MyRunnable" I might name it "PersistentRunnable" -- you can see versions of this pattern in the various -impl.capnp files in the Sandstorm source tree)

21:50 <mrdomino> ok, great

21:54 <mrdomino> i can't yet see how i'd thread that all the way into a bridge definition to expose the API to general-purpose webapps, but i think i have enough to start a first pass

21:55 <mrdomino> (i mean, i probably will have more questions, but this is helpful)

21:58 <kentonv> mrdomino, for sandstorm-http-bridge, you'll want to build on the object ID format it defines for HTTP API purposes. Probably you'll introduce a new type of object ID which acts like a webhook of sorts. http-bridge would implement a Runnable which, when called, makes an HTTP request against the app.

21:59 <kentonv> in order for the app to set up the recurring event in the first place, I suppose we'd need to expose a new HTTP API on the internal-facing HTTP proxy, for the app to call to. See the docs on powerbox HTTP APIs...

22:58 <Darude> Hi there. Can anyone advise me on the simplest way to set up a limited number of user accounts and disallow all other logins. I understand this has to be via an authentication provider of some kind.

23:00 <Darude> Would self-hosting some kind of simple LDAP be the easiest method?

23:01 <TimMc> Darude: You also want to disallow creation of sharing links?

23:01 <TimMc> Because if not, you could just rely on how Visitor accounts can't create grains.

23:05 <kentonv> Darude, send invites via the admin panel to the people you want to have accounts. Anyone else will only be "visitors", meaning they can't see anything unless a real user shared with them.

23:06 <kentonv> Darude, if you want to prohibit your users from sharing with visitors, then you'll need to set up an organization and choose the "disallow collaboration with people outside the organization" option. For this purpose, LDAP may be the way to go, unless all your users happen to be under a single e-mail domain already.

23:31 <Darude> Thanks for the advice. I'm having trouble completing the final set-up stage now. Whenever I try to create an account with Google at the 'Admin account' stage of set-up I'm constantly being redirected to the same page, only to repeat those steps again with the same result. I've tried Chrome and Firefox, both without any extensions.

23:45 <Darude> Never mind, I figured out the issue. I had ticked the "disallow collaboration with people outside the organization" option without configuring an organization, meaning the OAuth request looped back to the set-up page instead of making me an admin.