19:44 <ill_logic> Installing Sandstorm from source still claims that it will upgrade itself in the background. I'm assuming this isn't actually true?

19:45 <isd> ill_logic: the relevant thing is not whether it was built from source, but what sandstorm.conf's UPDATE_CHANNEL syas

19:45 <isd> says

19:45 <isd> if you want it not to update, set it to 'none'

19:45 <ill_logic> 👍️

22:32 <ill_logic> Currently poking around at the dev shell and admin, figuring out how it works.

22:34 <isd> Cool. poke me if you have any specific questions.

22:40 <ill_logic> I guess I should read Meteor 101.

22:46 <isd> +1

23:27 <CaptainCalliope> MIT is sending all its students home/off campus for the forseeable future and it just sent its instructors these resources to help them transition to remote teaching: http://teachremote.mit.edu/

23:27 <CaptainCalliope> It kinda has me thinking about educational use cases for sandstorm.

23:27 <CaptainCalliope> What kinds of apps and app integrations would lend themselves well to different kinds of learning and learning institutions?

23:32 <xet7> Like moodle?

23:34 <kentonv> https://sandstorm.io/go/education

23:35 <CaptainCalliope> Yeah. And maybe things like jit.si server.

23:36 <CaptainCalliope> <kentonv "https://sandstorm.io/go/educatio"> LOL!! Nice! Looks like I'm not so far out in left field.

23:37 <kentonv> oet.sandcats.io is one of the biggest self-hosted sandstorm servers, run by Grant Potter at University of (Northern?) British Columbia

23:38 <isd> Voice/video chat would be nice. Getting webrtc to work right might be challenging though, esp. with the fallback stuff it needs to do if peers can't establish a direct connection...

23:38 <kentonv> TBH I'm kind of uncomfortable with that marketing page still being there, it feels misleading given the current state of the project

23:38 <kentonv> I thought I had removed it...

23:41 <CaptainCalliope> The link's at the bottom of the page along with a link to oasis.

23:41 <isd> Yeah, a lot of the website makes sandstorm sound like more of a supported product than it really should. I don't know if I'm in favor of outright removing stuff; it's nice to have some references about why sandstorm is interesting for $use_case

23:42 <isd> but it would be better if those references didn't feel like they were over-selling the maturity or level of support.

23:43 <CaptainCalliope> Given the state of the project, a lot of the marketing on the website reads to me more like a whitepaper of where the product is headed than a reflection of the platform today.

23:44 <CaptainCalliope> I wonder if maybe we could preserve a bunch of it while simplifying the site by moving it to a slightly different format like a whitepaper. Not proposing this for now btw.

23:47 <kentonv> yeah I feel like all the info is still useful with a slightly different presentation, but I don't have any motivation to actually go through and update everything...

23:50 <CaptainCalliope> We gotchu. I'm starting to timeline out what I want to accomplish and commit to but my guess is that could be a late april to mid-june project.

23:51 <isd> We should just rip out the references to blackrock

23:51 <isd> ...as that's really unmaintained at this point.

23:52 <CaptainCalliope> Is there a quick triage we could do of things to rip out?

23:52 <kentonv> well, if we're saying the site represents what Sandstorm is supposed to be eventually, rather than what it is... I do still like the idea of blackrock.

23:53 <isd> captaincalliope: the website has an issue tracker: https://github.com/sandstorm-io/sandstorm-website/issues

23:59 <isd> kentonv: I guess the distinction is most stuff on the website is at least fairly in-line with where active community members are planning on going. I haven't heard even murmurings of anyone wanting to hack on blackrock, and it seems like most of us are much more interested in focusing on smaller self-hosted installs. So I feel like it's more misleading that the rest of what's on there.