Dustin Long

Alternatively, keep the private keys in those locations, and copy them into the config when we load it at startup. Don't serialize the private keys anymore.

Related: https://github.com/qri-io/qri/issues/959, we should not be returning 500 error codes. We currently are sending 500's in lots of cases, but by definition that means "there's a bug in our code"....

Reversing the fix for this issue: https://github.com/qri-io/qri/issues/1116. Related: https://github.com/qri-io/qri/issues/1153 and https://github.com/qri-io/qri/issues/1132

Related issue that can be fixed at the same time. It's not possible to infer a name using a file that contains unicode: ``` > qri save --body=здравствуйте.csv invalid name:...

Tried to reproduce but the save worked for me. The steps you gave, do they reliably work when run using a brand new user with an empty repo? (I used...

Sure, send me along the backed up repo. Though it'll probably be lower priority if it's hard to reproduce. How were you using a fresh user but an existing ipfs...

Still unable to reproduce this. But looks at the logging output you added I'm noticing the following: ``` buildComponentChanges HD:9, BD:3 ... buildBodyChanges parentPath: '' buildBodyChanges delta: ' ' buildBodyChanges...

Would deeply enjoy fixing this bug, but likely it will require a rewrite, or at least a large overhaul of deepdiff. Part of the problem is that deepdiff contains non-determinism:...

Should this be changed to being a log.Info instead? It's mainly intended for developers, who can run `--log-all` or whatever, and there's no actionable response that other users can do...

Even better idea, inspired by your mention of context. The scoped `perUserBus` could assign the profileID to the context, and the main bus could get it from there to add...