Closed expede closed 3 years ago
FYI @walkah
What I learned today: If you don't have access to private files (e.g. when you're running this from within some other app with fewer permissions), then it'll just generate a new key. In other words, in that case it's confusingly useless :smile:
What I learned today: If you don't have access to private files (e.g. when you're running this from within some other app with fewer permissions), then it'll just generate a new key. In other words, in that case it's confusingly useless 😄
Oooooooh that's indeed confusing. We may want to wrap that in a tag, something like:
{existing: "mywnfskey"}
{generated: "newwnfskey"}
Thoughts?
Or maybe better, it would be good to have separate methods for getOrGenerate
versus getExisting
Alternative:
{ key: ...
, generated: true
}
(Whoops excuse the Elm syntax)
Or maybe better, it would be good to have separate methods for getOrGenerate versus getExisting
Yup. Agree
And possibly support both. Eh. I mean. Just yes. :D
Oh, I think I have this in my notes:
This should work when run in the auth lobby/drive.