<Pilori>
Hello, can anybody kindly assist me with a issue im having for viewing a sandstorm spreadsheet?
<isd>
Pilori: Hi! Maybe; could you elaborate? What's the issue? What are app are you using?
<Pilori>
Hello, I am not using any form of app. Im basically trying to access the sandstorm spreadsheet that lists the admin log in info required for my job. I send a token to the email I am logged into in order to view the sheet. The tab is shown on the bottom, however, the content of the sheet is a blank white page. I have tried clearing my browsers cache
<Pilori>
with no luck. any advice?
<isd>
This is something someone else has shared with you? (there's *some* app that's implementing it; sandstorm doesn't have spreadsheets "built in", though if someone's sent you a link I can see that you might not know)
<Pilori>
Yes, someone has shared the link with me for work purposes.
<isd>
Could you send a screenshot? Hard to guess at the problem without knowing the app or even being able to look at it
<Pilori>
sure, no problem.
<isd>
Also, I've got to head out fairly soon. If we can't figure it out by then and no-one else responds tonight, you might have better luck during the week; the core team isn't as active on the weekends, but they're super responsive during the week.
<isd>
Hmm, I actually just opened one of my own ethercalc spreadsheets and got the same thing
<isd>
What browser are you using? I'm getting that in firefox, about to try chromium
<Pilori>
im using chrome at the moment
<isd>
I bet I will be unsuccessful then :(
<Pilori>
(T T)
<Pilori>
Well, I dont want to keep you from doing what you gotta do. I can simply explain to my client that I was not able to access the sheet if anything. Im just glad to hear that Im not the only one experiencing this at the moment.
<isd>
Yeah, same thing in chromium
<isd>
asheesh: I will likely be gone when you get back to your computer. Might want to investigate this when you do.
<isd>
And yeah, I think it's time for me to leave.
<Pilori>
No problem. Will it be okay to send this chat log to my client for proof that I have contacted support?
<isd>
Pilori: fine with me. Note that the channel is publicly logged, so you can just link to the public version if you want (in the topic).
<Pilori>
Okay, thank you.
<isd>
You're welcome
Jan\ has quit [Read error: Connection reset by peer]
<asheesh>
Most servers auto-update within 24 hours, so tomorrow the problem may be gone.
<asheesh>
If you do run into this issue with Sandstorm v0.182 or v0.183 then it's a different problem which we don't already know about and which is very important.
<Pilori>
Hello, thank you kindly for the feedback, I will let my client know.
isd has quit [Remote host closed the connection]
<Pilori>
Just a update, we are able to view the spreadsheet now. Thank you very much.
<liam>
oh yeah i didn't even look at the nginx example conf, i just winged it lol
<liam>
i didn't do too bad xD
<zarvox>
:D
<zarvox>
Let me know if that sorts things out or if you'd appreciate a second pair of eyes on anything
<liam>
that fixed it, thanks
<liam>
( i still see "xhr-polling" but i'm not going to complain because it works :P)
<zarvox>
might need the same treatment in the non-wildcarded domain? *shrug*
<liam>
they are in the same server block
<liam>
zarvox, re phabricator-ss #8, signing the package: i'm a bit hesitant to do this because I think it's misleading. I'm "claiming responsibility," which isn't particularly special, and, more importantly, doesn't prevent tampering with the .spk. That's why I'm using detached signatures now. It verifies the entire .spk is tamperless
<zarvox>
.spk files are always signed by the app key; only you are capable of producing an SPK that validates as signed with that key
<liam>
the app key?
<zarvox>
.spk files that have been tampered with already won't pass the app-id signature check
<zarvox>
the appId in sandstorm-pkgdef.capnp is a public key
<liam>
ecc, fancy. i thought it was just random uuid to prevent apps overwriting each other
<zarvox>
you have the private key in $HOME/.sandstorm/sandstorm-keyring
<liam>
now i'm obligated to tamper with one and find out :P
<zarvox>
Anyway, by having all spks be signed by app keys, it keeps anyone from being able to publish a malicious update to an app you already have installed, and provides a basis for cryptographically connecting a human-intelligible identity to that artifact :)