Dustin Long

Seems like you're correct. `perUserBus` is no longer needed. The desired functionality matches very closely to how `automation` is adding the profile.ID to the context, so I refactored that part...

Incoming http / rpc requests should have an `auth` token (created by `qri access token --for me`) sent as an "Authorization" header. The scope builder in lib/dispatch.go can parse this...

This should nearly basically work right now, but is hard to setup for testing and development purposes. It's not easy to run a qri node such that multiple users can...

I think you're right that this is the same problem as what's happening in https://github.com/qri-io/qri/issues/1483. A user with two different logbooks, attached to the same handle, pushed those to cloud,...

Just to add some context, we've gone back and forth on the question of "HTTP as RPC layer" vs "HTTP as RESTful API" and which should take priority, as there...

WIP change to just the field names (not their usages): https://github.com/qri-io/qri/pull/1735

The first part of this was implemented by https://github.com/qri-io/qri/pull/1754, but ListParams are still TODOs.

TODO: These examples should be added to official docs / tutorials some point soon. Some examples of using curl to get responses from the qri API. You need to be...

The help text for each command declared in `cmd/` is used to generate the docs on the website. However, each command contains the repeated "Options inherited from parent commands" for...

Ok, I thought some more about this, and I have a recommendation. First, agreed that FSI is not in the domain of a cache, totally correct. However, I think the...