jadewang has quit [Remote host closed the connection]
asmyers has quit [Ping timeout: 252 seconds]
KooBaa has joined #sandstorm
NwS has quit [Ping timeout: 240 seconds]
jacksingleton has quit [Ping timeout: 248 seconds]
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
KooBaa has quit [Ping timeout: 255 seconds]
rustyrazorblade has quit [Quit: rustyrazorblade]
|jemc| has quit [Ping timeout: 240 seconds]
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Quit: rustyrazorblade]
mnutt__ has joined #sandstorm
|jemc| has joined #sandstorm
<mnutt__>
I don't _think_ it would hurt anything to have sandstorm unauthenticated OPTIONS send Dav: 1 header always, but I'd be willing to test it.
wolcen has joined #sandstorm
wolcen has quit [Ping timeout: 244 seconds]
KooBaa has joined #sandstorm
sydney_untangle has joined #sandstorm
KooBaa has quit [Ping timeout: 248 seconds]
paroneayea has joined #sandstorm
frigginglorious has joined #sandstorm
wolcen has joined #sandstorm
joshbuddy has quit [Quit: joshbuddy]
rustyrazorblade has joined #sandstorm
<e`>
Â/window 19
joshbuddy has joined #sandstorm
|jemc| has quit [Ping timeout: 240 seconds]
rustyrazorblade has quit [Quit: rustyrazorblade]
rustyrazorblade has joined #sandstorm
KooBaa has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
dwrensha_ has joined #sandstorm
KooBaa has quit [Ping timeout: 252 seconds]
dwrensha_ is now known as dwrensha
<asheesh>
Great seeing people at the meetup today!
ecloud_wfh is now known as ecloud
<ocdtrekkie>
So, if I have an old Sandstorm local install I used for all my dev'ing of things, and I tried updating an app on it, and it no longer runs. (The app runs correctly still outside Sandstorm, and the grain does load most of the way in Sandstorm, it just can't load the saved sqlite data, I'm guessing.)
<ocdtrekkie>
I'm kinda confused where to start troubleshooting it.
mnutt__ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<ocdtrekkie>
I took my previous version app code, and it does the same thing now.
KooBaa has joined #sandstorm
synchrone has joined #sandstorm
KooBaa has quit [Ping timeout: 240 seconds]
xobs has quit [Quit: No Ping reply in 180 seconds.]
xobs has joined #sandstorm
<synchrone>
mnutt__: except iOS would be complaining about Ca(rd|l)DAV address being invalid
<synchrone>
it would of course work, but the user would have to insist on saving that configuration
<synchrone>
..which is a bad UX. Even worse than having to somehow copy the url and token to device (potentially giving them up to Apple\Google via email or some IM in the process of sending to one's self), since there's no way a human being can type all those chars
<canuky>
MongoDB question ... I have a few handles in my admin/users table that I don't recognize and I would like to look them up ... correct query is- db.users.find({"profile.handle": <handle>}) ?
xet7 has joined #sandstorm
<dwrensha>
canuky: that should work, unless the handles aren't filled in yet
juicef has joined #sandstorm
<dwrensha>
(the field get filled in when the user confirms their profile on first login)
<canuky>
Ah ha ... I have a few people listed as 'Guest' that used passwordless email login .. hoping to find their email so I can reach out to them
<canuky>
handle is listed in the table, just not sure how to find their associate email domain
wolcen has joined #sandstorm
<canuky>
listed in the user/admin dashboard table, that is
<juicef>
I wonder about the Ghost app. It seems like it's been abandoned since it's lags several major app updates behind. Is there an idea of how much update lag there's gonna be with Ghost specifically, or apps in general?
<dwrensha>
juicef: Agreed that the Ghost app could use some love.
preilly has joined #sandstorm
<dwrensha>
juicef: the big blocker is that upstream redid their authentication logic a while back
eternaleye has quit [Ping timeout: 240 seconds]
Guest88610 has quit [Excess Flood]
xobs has quit [Ping timeout: 240 seconds]
preilly is now known as Guest2937
<dwrensha>
... so there are some major changes to be made in the Sandstorm port, and jparyani hasn't had time to figure them out.
xobs has joined #sandstorm
<dwrensha>
juicef: the ideal is that upstream authors will be responsible for maintaining their Sandstorm packages
<dwrensha>
this is already the case for rocket.chat, wekan, and ethercalc
<juicef>
dwrensha: I agree, I reckoned that was the thought up ideal solution. How's the Ghost team on this issue? Resource scarcity or competing business logic interfering perhaps?
<dwrensha>
I don't know whether we have ever contacted the Ghost upstream people.
<juicef>
dwrensha: I feel that for certain apps with their own infrastructure up and running (WP and WP.com) (Ghost and Ghost.org) an extra effort is going to be needed to have those apps freshly available on SS.
<juicef>
Seems now that the smallest, less known apps are the perfect fit for SS. But alot of people need the big ones as well.
<jacksingleton>
dwrensha: ah yeah I see it's compiled in
<jacksingleton>
I am thinking more of the case where we share signing keys with several members of a team, and then rotate keys after people roll off
<jacksingleton>
right now I'm the only person holding the deployment key for SandForms, which is bad as it's a team effort that shouldn't be dependant on me
<asheesh>
+1
<jacksingleton>
but we also have quite high turn over, and I don't want the number of people with deployment rights to grow and grow
<phildini>
hmm... by "deployment key" do you mean the app id key, or your pgp signing key?
<jacksingleton>
the app id key
<phildini>
interesting.
<jacksingleton>
i might file an issue or two for team app managment
<asheesh>
+1
<jacksingleton>
the other thing that would be nice is having a team in the authors field, possibly linking to multiple peoples keybase and social media accounts
<asheesh>
FWIW, https://theupdateframework.github.io/ is based on the theory that most app authors trust the app market's to do key management more than they trust themselves (but then the app authors can take direct control of the app key if they want)
<asheesh>
(as I recall)
<asheesh>
Those who do not learn from history are doomed to repeat it, I understand.
<jacksingleton>
makes sense to me for many cases. secret management is a difficult problem
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
<asheesh>
BTW, if anyone feels like writing for LWN.net: I think that the story of Giftr on Sandstorm ("Everyone can make a [gift] list, and other folks will be able to coordinate and comment on your requests, but you won't be able see it, so it won't spoil the surprise") would make a really good article. See also https://sandstorm.io/news/2016-02-25-giftr
<asheesh>
(I said this in a few other places too; pardon the repetition)
<asheesh>
I have part of an outline already written, in case that helps someone say yes. :)
<synchrone>
asheesh: I'll repeat my question as well: could you guys add <meta> support to appstore?
<synchrone>
I forgot what's that web standard called
<asheesh>
There's og:description etc.
<synchrone>
yep, that would be it
<synchrone>
thanks for the ticket :)
amyers has quit [Ping timeout: 240 seconds]
eglimi has quit [Ping timeout: 255 seconds]
<asheesh>
Happy to file bugs, synchrone !
wolcen has quit [Ping timeout: 250 seconds]
wolcen has joined #sandstorm
TwoJames has joined #sandstorm
neynah has joined #sandstorm
synchrone has quit [Ping timeout: 244 seconds]
amyers has joined #sandstorm
asmyers has joined #sandstorm
amyers has quit [Ping timeout: 276 seconds]
jadewang has quit [Remote host closed the connection]
wolcen has quit [Ping timeout: 255 seconds]
<eternaleye>
Hey, I revoked all access to a grain and then deleted it, but another user (who I had shared access to it with) still has it show up in his grains list, though it says he does not have permission. We're not seeing a way to remove it from the list.
<eternaleye>
This remains across refreshing.
<dwrensha>
eternaleye: can you click the trash bin icon while the grain is "open"?
<dwrensha>
that should forget the grain
<eternaleye>
Will check.
<eternaleye>
That works, thanks! Though forgetting deleted grains automatically would be nice.
<jacksingleton>
I have noticed this too, the person who you share the grain with has to delete it themselves even after you delete it yourself
<dwrensha>
yeah, I'm starting to think it would be better if the grain just disappeared from everyone's grain list
<dwrensha>
our original thought was that such a disappearance might be confusing
<dwrensha>
users might wonder "where'd it go?"
<dwrensha>
if we keep around the references, we can at least display an explanatory error when someone attempts to open it
<dwrensha>
... but admittedly we are not doing a good job right now of displaying a helpful error
<dwrensha>
it should be "this grain has been deleted" not "you don't have permission"
<asheesh>
FWIW one more good thing we could do if we had a 'trash' section.
asmyers has quit [Read error: Connection reset by peer]
amyers has joined #sandstorm
amyers has quit [Remote host closed the connection]
<neynah>
dwrensha +1 on ""this grain has been deleted" not "you don't have permission""
frigginglorious has quit [Ping timeout: 255 seconds]
<neynah>
However, if we did find reason to want to display the grain in the grain list anyway we could grey it out and mark it as deleted by the owner.
amyers has joined #sandstorm
amyers has quit [Remote host closed the connection]
amyers has joined #sandstorm
amyers has quit [Ping timeout: 240 seconds]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 240 seconds]
jacksingleton has quit [Ping timeout: 244 seconds]
wolcen has joined #sandstorm
mnutt__ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
jacksingleton has joined #sandstorm
<digitalcircuit>
Alongside 'Trash' section, maybe 'Archive', so you can keep grains around for others without cluttering your own list? Though that could easily be a part of grain folders.