<isd>
gpg -ae $my_email_addres < input > output.asc for the actual encrypt operation. I forget how to import keyrings off hand.
<isd>
Looks like it's just gpg --import /path/to/key
<ocdtrekkie>
Keybase chat has worked well in the past, still wondering how long that'll be an option though
<isd>
Well, as long as it's not already broken it will work for this.
xet7 has quit [Remote host closed the connection]
xet7 has joined #sandstorm
<ocdtrekkie>
So I have been using Sandstorm as somewhat of a PWA on iOS, and I wonder if I found an issue Sandstorm should be addressing.
<ocdtrekkie>
I want to say that on desktop if the grain dies, something usually tells me as much if I try to interact with it again.
<ocdtrekkie>
However, with Sandstorm added to my home screen, if I'm interacting with an app, and come back to it later, the front end usually still "works" with whatever grain was open, but no data is actually saved.
<ocdtrekkie>
In such scenarios, Sandstorm doesn't even update the last modified of the grain... the grain was never so much as reopened when I tried entering data into it again.
<isd>
Is something actually broken? the grain should get booted again if you do anything that actually triggers network traffic.
<ocdtrekkie>
So I can type in TextEditor (or enter a diaper change on BabyBuddy) and the grain never starts back up, and hence no data is saved.
<isd>
Interesting. If you tail -f the grain log while you do it, does anything actually show up? (Obv. just opening it in a browser would interfere with the test)
<ocdtrekkie>
I am usually not by a desk when trying to Sandstorm from my phone, unfortunately, but if the grain even tried to load the time on the grain list would update.