sydney_untangle has quit [Read error: No route to host]
sydney_untangle has joined #sandstorm
Rym has joined #sandstorm
Guest57779 has quit [Ping timeout: 260 seconds]
zeroish has quit [Ping timeout: 260 seconds]
prettyvanilla has quit [Remote host closed the connection]
_whitelogger has joined #sandstorm
simonv3_ is now known as simonv3
KCinJP_ is now known as KCinJP
DanC__ has joined #sandstorm
<mrdomino>
any thoughts on how to do something like folder organization for grains? I'm considering doing a folder-layout link organizer as a meteor starter app, but it occurs to me that this is probably something that'd work better in sandstorm proper.
<dwrensha>
a lot of people seem to prefer the notion of "tags" over the notion of "folders"
<mrdomino>
Tags are pretty useful in general, but there are times when the hierarchical structure of folders comes in handy. Specifically I've seen a use case recently of an org using folders of documents in Google Drive to implement a wiki.
<mrdomino>
The ability to do something like that in Sandstorm would probably reduce friction for them moving to it.
<mrdomino>
(yeah we have a couple wiki apps, but afaik none of them provide real-time editing as smooth as etherpad's for instance)
<dwrensha>
we're working on an idea of a "collections" app
<dwrensha>
a grain would store references to other grains
<dwrensha>
one that that's not quite clear to me yet is the question of when does it make sense for a grain to appear on the main list
<dwrensha>
one major use case of the collections app is to allow sharing of a bunch of grains to a group of people
<mrdomino>
i wonder if the grain list ought not to be the user's main entry point
<mrdomino>
"show me a list of all the grains i own" maybe ought to be buried somewhere that's easy to find if you look for it but not the first thing you encounter
<mrdomino>
the first thing you encounter maybe should ought to be a collection grain or a configurable root grain
raoulzecat has joined #sandstorm
mrshu has quit [Ping timeout: 252 seconds]
mrshu has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
<rolig>
I'm getting 'Upload failed: Unauthorized [403]' when trying to restore one particular (largish) grain. Any ideas?
<dwrensha>
rolig: on Oasis or some other server?
<rolig>
some other
<dwrensha>
Do you have a reverse proxy like nginx set up in front of the Sandstorm server?
<rolig>
nope
<dwrensha>
does it work to restore smaller grains?
<rolig>
yes
<rolig>
also the grain is from a different sandstorm server originally
xet7b has quit [Remote host closed the connection]
<dwrensha>
jparyani: I'm getting a 401 when I try to set up tinytinyrss on my phone
<dwrensha>
is there something in particular I should be putting in for "the username of your Tiny Riny RSS account"
<jparyani>
nope, anything should work
<dwrensha>
or "The password of you TinyTiny Rss account"?
<jparyani>
password should be the webkey I believe
<dwrensha>
this is separate from the http-authentication settings
<dwrensha>
which is where I put the webkey
<jparyani>
ah ok, put nothing there
<dwrensha>
actually, I put the webkey in both password fields
<jparyani>
ya dont do that
<dwrensha>
OMG it worked
<jparyani>
haha nice
<jparyani>
but ya, it needs clearer instructions it seems
<jparyani>
ill rewrite and add an offer template to boot
<dwrensha>
it was really annoying to have to select just the token part of the URL
<jparyani>
ya
<dwrensha>
i ended up pasting into a mail compose field
<jparyani>
haha
<dwrensha>
so that I would have a good selection cursor
<jparyani>
offer template should solve this problem
<rolig>
dwrensha, for the record no error restoring the same grain to oasis =/
frigginglorious has quit [Ping timeout: 246 seconds]
frigginglorious has joined #sandstorm
<dwrensha>
rolig: how large is the zip file?
<rolig>
60mb
<rolig>
that's large for me - it takes like 2 hours to upload
<dwrensha>
ouch
<dwrensha>
does it also take 2 hours on Oasis?
<rolig>
yeah i just have a slow connection
frigginglorious has quit [Quit: frigginglorious]
<dwrensha>
rolig: how many times have you tried, and has it been the same error each time?
<rolig>
three or four, and yeah same 403 error. right now I've logged out all other sessions, unlinked my google account, freshly logged in, trying again
<rolig>
maybe worth noting that the first time i didn't have the app i was restoring installed, and still got the 403
<rolig>
i tried that on oasis and got 550 - install the app first or something
<rolig>
err 500*
amyers has quit [Ping timeout: 246 seconds]
<dwrensha>
rolig: I was able to reproduce your error!
<asheesh>
Also rolig you said you were experiencing the big red wildcard host warning?
<asheesh>
zarvox: My current intuition (your opinion requested) is that "Perform a self-test" should be an opt-in action, and that it should eventually grow a home in "New admin". +1/-1/discuss-later ?
<asheesh>
That doesn't have to be part of the work toward "Ship new admin" since it's a new feature, but I thought I'd see what you think.
<zarvox>
asheesh: I think the primary value comes in catching the misconfiguration before you get too far down the rabbit hole, so I'd rather see it *earlier*, like in the setup wizard.
<zarvox>
Also I suspect that it should happen automatically.
<zarvox>
The idea of the setup wizard is that you can't think you have a functional setup when you in fact don't, and the wildcardhost checks sound like they totally fit in there.
<zarvox>
It is a bit sad that if we block you earlier, you can't fix your wildcard DNS later, especially if you have to wait for DNS propagation delays or something.
<zarvox>
So maybe it should remain advisory rather than mandatory. But basically, if you don't have a wildcardhost, you don't have any working apps, so...there's a limit to how much you can actually use the server.
frigginglorious has joined #sandstorm
<zarvox>
I would be +1 on automatic checks in setup, and +1 on invokable checks somewhere in new-admin.
<asheesh>
I like that a lot.
NwS has quit [Ping timeout: 244 seconds]
Triplefox has quit [Quit: No Ping reply in 180 seconds.]
aldeka has quit [Ping timeout: 246 seconds]
Triplefox has joined #sandstorm
aldeka has joined #sandstorm
NwS has joined #sandstorm
<rolig>
asheesh, yep getting the wildcard error but not actually having problems
<Mitar>
zarvox: can you release a new version of the test app?
frigginglorious has quit [Ping timeout: 240 seconds]
jadewang_ has joined #sandstorm
<zarvox>
Mitar: I can, but I would like to first rename the method you added to something like `showConnections` or something hinting at a connection graph more broadly, since as we move forward with powerbox things, the audit view will also include which grains we import capabilities from, which grains we export capabilities to, etc.
<Mitar>
as you want
jadewang has quit [Ping timeout: 276 seconds]
<Mitar>
you can merge into the test app and change it there
<Mitar>
and I can give you permissions on my fork to just edit in the branch
<Mitar>
or you can merge in and then edit
<Mitar>
in general, I think I cannot contribute much here because those details you know the best
<zarvox>
okay
<zarvox>
I am also looking into your JSCS issues, FWIW