<maurer>
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create
<maurer>
reloading does not fix it, but I get The connection to wss://sandstorm.wub.site/sockjs/003/ggjvu8l_/websocket was interrupted while the page was loading. during the reload
jadewang has quit [Remote host closed the connection]
erikoeurch has quit [Ping timeout: 246 seconds]
erikoeurch has joined #sandstorm
erikoeurch has quit [Quit: Leaving]
jadewang has joined #sandstorm
<dwrensha>
paulproteus: "these docs are pretty decent for such a young project" says jcreed re docs.sandstorm.io
NOTevil has quit [Quit: Leaving]
<paulproteus>
Aw yay.
<dwrensha>
paulproteus: also, jcreed hit an installation problem where /opt/sandstorm/var/pid was owned by root:root
* paulproteus
blinks
<paulproteus>
That's who it's owned by on my laptop, at least!
<maurer>
Is there any long term provision for sandstorm grains which use network access, or are long lived?
<paulproteus>
Who's it supposed to be owned by? The Sandstorm group? If so, then hmmm.
<maurer>
One service that is close to fitting the sandstorm model, but not quite, is a personal IRC bouncer, e.g. a grain version of IRCCloud
<paulproteus>
Yeah, for long-lived grains we'll have a way for apps to request the system not shut them down.
<paulproteus>
I really want a grain version of IRCCloud.
<paulproteus>
I think jparyani was working on that, and it's "nearly ready"?
<paulproteus>
("that" == "apps having a way to ask the system to not shut them down")
<paulproteus>
re: network access: Via the powerbox, similarly in progress.
<maurer>
OK. I think we'd want both that and intergrain comms to build something like this
<maurer>
since probably what we'd want to do would be make a grain using powerbox that is an irc bouncer
<maurer>
then make a web frontend as a separate grain
<maurer>
and have them talk
<paulproteus>
Yeah, I am thinking one app that just speaks the IRC protocol, and maybe queues it (therefore == a bouncer) and then the web one that connects to it.
<paulproteus>
Amusingly you could build this so the web one doesn't have to stay awake all the time, and gets messages replayed to it as part of waking up when the user visits it, depending on the details.
<maurer>
That way everything other than the teeeeny piece of code that knows how to remain connected to IRC remains lowpriv and can be shut down
<dwrensha>
paulproteus: "upon trying to do spk dev: sandstorm/run-bundle.c++:1132: failed: You do not have permission to read the pidfile directory."
<paulproteus>
Oh my.
<paulproteus>
maurer++
jadewang has quit [Remote host closed the connection]
<paulproteus>
dwrensha: Hmmmmm. "How does this work for vagrant-spk"?
<dwrensha>
paulproteus: does `spk dev` work for you, on your laptop where /opt/sandstorm/var/pid is owned by root:root?
<paulproteus>
➜ .sandstorm git:(master) ✗ spk dev
<paulproteus>
App is now available from Sandstorm server. Ctrl+C to disconnect.
<paulproteus>
WriteResult({ "nInserted" : 1 })
<paulproteus>
Seems to.
<paulproteus>
➜ ~ ls -l /opt/sandstorm/var/pid/sandstorm.pid
<paulproteus>
-rw-rw---- 1 root paulproteus 5 Aug 1 17:31 /opt/sandstorm/var/pid/sandstorm.pid
<paulproteus>
What's the permissions like on that file in particular?
<paulproteus>
SERVER_USER=paulproteus # fwiw from my sandstorm.conf
NwS has quit [Read error: Connection reset by peer]
<paulproteus>
I gave that a read-through and liked it more than I expected to by the end, and would be willing to try using it.
<paulproteus>
The "main" problem with that is that inspect element in the browser I guess gets messier?
<zarvox>
Some day we'll get to the enlightened world where each visual component has its own styles and templates and helpers all together in one file
<paulproteus>
But also we could use a more helpful hash function.
<paulproteus>
Like cx('button/container/public') => 'sandstorm-css-button-container-public'
<paulproteus>
or something.
<zarvox>
Yeah, one downside is "inspect element" doesn't tell you where each style came from. Instead, you've explicitly combined them. And it turns out most styles are not inheirited all over, but belong to the widget itself.
<paulproteus>
I see, okay, sure.
<zarvox>
IMO global styles like default typeface/CSS reset/etc. *should* stay in some global CSS file.
<paulproteus>
I'm pretty up for whatever, CSS-wise, fwiw.
<paulproteus>
GlobalSign takes 31 to sign a cert, probably including at least 1 unnecessary API call, so things are looking up for me.
<paulproteus>
31 *sec*
<zarvox>
31 seconds is surprisingly long.
<zarvox>
Maybe that test system is running on TI-86 or something.
<paulproteus>
The real one runs on a TI-89!
<zarvox>
Maybe there's a person who manually clicks an "approve" box as soon as they notice the request come in.
<paulproteus>
I *think* that's honestly how StartCom's stuff works.
<paulproteus>
Except therefore it takes some minutes.
<paulproteus>
I think geofft told me it works this way.
<zarvox>
Maybe adding the cert to the OCSP dataset and CT log and other things takes some time.
<paulproteus>
juri_: That's neat that you made your own competing thing, btw.