kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
<abliss> uh oh: $ spk publish /home/abliss/gitweb.0.0.10.spk
<abliss> talking to index server...
<abliss> curl: (60) SSL certificate problem: certificate has expired
<abliss> emailed kenton. ocdtrekkie you don't have access to update those certs do ya?
<abliss> kenton replied from china and is investigating...
ocdtr_web has joined #sandstorm
<ocdtr_web> Kenton is the only one with server access
<abliss> looks like he managed to fix it
<ocdtr_web> But yeah, his on-vacation response time is pretty good
ocdtr_web has quit [Remote host closed the connection]
ocdtrekkie has quit [Read error: Connection reset by peer]
kawaiipunk has quit [Quit: Leaving this Club]
kawaiipunk has joined #sandstorm
_whitelogger has joined #sandstorm
_whitelogger has joined #sandstorm
ill_logic has joined #sandstorm
ocdtrekkie has joined #sandstorm
<ocdtrekkie> Almost time for Office Hours!
ocdtrekkie has quit [Client Quit]
ocdtrekkie has joined #sandstorm
<isd> I am dialed in whenever you guys show.
<ocdtrekkie> I was dialed in, but didn't hear anything from you, and now I'm disconnected.
<ocdtrekkie> I may switch to phone myself.
<ill_logic> One thing I didn't get to get in in time regarding making public grains:
<ill_logic> What about performance? I thought that was one of the reasons cited for there not being public grains.
<ill_logic> Static sites are efficient. Other than that, the system is optimized for having many sandboxes requested by a few clients each.
<ill_logic> Rather than a large services requested by many.
<ill_logic> (That said, if we can do public grains, the Kiwix port would make a lot more sense.)
<ocdtrekkie> I mean, if static publishing works for what you're doing, we should encourage that. But there are cases where it's just not going to work.
<ill_logic> Right. Kiwix included.
<ill_logic> But if it's not static, would it hold up to traffic?
<ocdtrekkie> I mean, it should be relatively similar to how it would be if you hosted it not on Sandstorm, presumably?
<ocdtrekkie> I don't think Sandstorm introduces a massive performance overhead.
<ill_logic> I would at least say that if you had a lot of public grains, that's a lot of redundant instances of database software, etc.
<ill_logic> But maybe for just a few, it's not a big deal.
<ill_logic> I dunno, I'd of course be happy to be wrong about this. I just thought Kenton said what I'm saying long ago.
<ocdtrekkie> Yeah, I mean, for apps which are running "big" database apps, it's going to be like having multiple servers of them running in your Sandstorm environment.
<ill_logic> And I guess I'm not so much worried about performance overhead as performance constraints. Like maybe grains are purposely capped?
<ocdtrekkie> App market whitelabeling bug: https://github.com/sandstorm-io/sandstorm/issues/3029 Does have "bite-size" on it already too.
<abliss> <ocdtrekkie "abliss: https://apps.sandstorm.i"> ocdtrekkie: thanks
<ocdtrekkie> You know what we didn't discuss? Who is actually going to write the blog post we all agreed should be written.
<ocdtrekkie> :O
<ill_logic> Office hours notes go both on the wiki and sandstormcommunity.org?
<ill_logic> Also - do we want to start locking down some of these grains? Meeting notes, or especially the new Wekan?
<ill_logic> Especially since we'll be going public soon.
<ocdtrekkie> ill_logic: Time will tell if sandstormcommunity.org sticks around. It is kinda a concept for if we feel the need as a community to make posts/releases independent of what we can do on sandstorm.io.
<ocdtrekkie> I'm mirroring the office hours notes there, and I find it an easy URL to type to get to things like the IRC log link, but if nobody really ends up finding a use for it, I'll end up torching it.
<ocdtrekkie> Just cuz I made it doesn't mean I'm attached to it. :)
<ill_logic> Well I think I just added the notes for the 26th. I selected "draft" but I guess it published anyway.
<ill_logic> Oh wait, no. You added the 26th at the same time. Heh.
<ill_logic> I guess I can delete my draft then.
<ill_logic> I can't figure out how to manage any of this
<ocdtrekkie> Yeah, I did it, sorry. :P
<ocdtrekkie> Impressively, a domain I registered like two weeks ago already had spam comments submitted too!
<ill_logic> No worries, I could have given heads up. Uh... so how do I delete mine?
<ocdtrekkie> I don't see anything
<ill_logic> I guess it's saved as "draft".
<ill_logic> Yeah maybe I'll leave these posts to you...
<ill_logic> I'm not helping.
<isd> I think we should migrate the notes to actual wiki pages after the meetings, so they're versioned and we can at least roll back changes if somebody does something stupid/obnoxious.
<isd> I agree I'd prefer not to just leave them in writable grains on our servers with no versioning.
<ill_logic> Wekan too though right?
ill_logic has quit [Ping timeout: 240 seconds]
<isd> Hm, just moving that to the wiki is not as great; the point of using wekan is that it's supposedly a good tool for organizing priorities and such. Maybe we can just keep that read-only except for a few of us?
<ocdtrekkie> isd: I do have the full text of office hours notes on that website, so for as long as that exists, there's a backup copy as of about right after the meeting.
<isd> Cool
<isd> I posted this on the wekan card, but re: porting mastodon: it occurs to me that clean public urls for sharing the grain probably aren't enough; other instances need to be able to query webfinger, which means they need to be able to do an unauthenticated GET at a specific path. We can't just be returning some javascript that sets up an iframe for that.
<abliss> is there a need for js/iframe?
<abliss> like i can directly fetch the wekan url (by busting it out of the iframe) and it works fine as long as i don't do any fancy stuff like powerbox or offer()
<abliss> couldn't the sandstorm server keep a simple lookup table of subdomain -> fancy-token and serve up the corresponding page in response to a regular web request?
<abliss> perhaps the app could be augmented to detect this and offer a button to pop back into the sandstorm shell whenever a fancy feature is needed.
<isd> I think you could definitely rig things up so the public endpoint served the page directly from the app.
<isd> And yeah, detecting whether you're in an iframe or not is easy: window === window.parent
ill_logic has joined #sandstorm