00:09 <ocdtrekkie> isd: This should give you some idea: https://github.com/sandstorm-io/blackrock/blob/master/src/sandstorm

00:39 <isd> Ah.

12:51 <metaphysician> I would like to see Scuttlebutt P2P chat in Sandstorm. https://staltz.com/an-off-grid-social-network.html Is it available?

14:01 <TimMc> metaphysician: It's not available as a packaged application, no.

14:02 <TimMc> By the way, do you happen to know where I can find a spec for it?

14:09 <metaphysician> TimMc: spec?

14:10 <TimMc> metaphysician: Specification.

14:11 <TimMc> All I could find was basically a mareting and overview site.

14:17 <metaphysician> TimMc: Did you see this handbook https://www.scuttlebutt.nz/ ? And list of applications https://www.scuttlebutt.nz/applications.html

14:34 <TimMc> Those aren't a spec. :-)

14:36 <metaphysician> TimMc: I don't know what specification mean. I am a bit new to Sandstorm.

14:36 <metaphysician> *what spec you mean

14:40 <TimMc> metaphysician: It's nothing specific to Sandstorm, it's a term from software development in general. A specification is a technical description of how a piece of software works, and importantly how it interoperates with other software.

14:40 <TimMc> It would be potentially pretty important for anyone who was packaging SSB for Sandstorm.

14:51 <metaphysician> #scuttlebutt on this network is quite active

14:59 <metaphysician> patchwork (the client) uses scuttlebot (sort of the reference implementation of SSB) https://github.com/ssbc/patchwork/blob/master/package.json

15:01 <metaphysician> git-ssb too uses sbot https://github.com/ssbc/scuttlebot

17:05 <funwhilelost> TimMc: looks like this page is an intro to the API docs. https://ssbc.github.io/secure-scuttlebutt/

17:08 <funwhilelost> It's an encrypted database, of sorts, that you can synchronize in various ways. The most common way is posting to public replication nodes via HTTP.

17:09 <funwhilelost> Assuming you could get those requests out through the capnp pipes it seems package-able.

17:10 <funwhilelost> metaphysician is talking about a client that leverages the database to show chat messages.

17:11 <funwhilelost> Each node is supposed to act like a node in a mesh network (both send and receive) so it might be tricky to get the incoming data.

17:12 <funwhilelost> But it seems like you could make a node viable with some basic polling.

17:14 <funwhilelost> (Considering that they support updates via sneakernet!)

17:39 <BlueNinja> mernin

20:13 <ill_logic> Question: Given that FreeNAS exists, what was the motivation for Sandstorm? I'm still learning about NAS, but they also sounds like an open ended platforms.

20:16 <mokomull> (disclaimer: not a Sandstorm person, I just idle here a lot) I don't think the two are nearly comparable. Sandstorm provides separation between even instances of the same application, the ability to share those instances with other people, among a bunch of other things I'm absolutely over-simplifying.

20:37 <ill_logic> Some things I perhaps took for granted.

20:42 <ill_logic> I have inertia leading me to want to support Sandstorm. I just wanted to make sure I understood.

20:43 <ill_logic> Inertia was having me support Indiebox/UBOS for a while, until I went to a Sandstorm meetup and I realized you guys actually care about security :-P

22:07 <isd> ill_logic: FreeNAS is also focused on storage, whereas sandstorm is a more general platform for applications. NAS = Network attached storage.

22:09 <ill_logic> Right, but I've heard all about apps available for it.

22:09 <ill_logic> At least the other NASes. Maybe not FreeNAS in pariculary

22:09 <ill_logic> particular*