cjqf
Would it be possible to provide a "count" only query interface? Some folks (like convo space) want to be able to get this information, and while a client-side wrapper can...
This is a common error that we see coming from various Threads Clients. It is essentially the default error coming back from a Client that doesn't receive a valid response...
This is different to the current method semantics, where we go back from current head to limit or offset. This would be useful for doing things like "paging" record sync...
It could be super helpful for certain enterprise situations, to allow threads/buckets, etc to connect only with a private IPFS network. This shouldn't be too hard to expose in threads,...
Right now, this throws an error, but should it? For remote clients that don't know ahead of time if an instance has already been deleted, it would be useful if...
Ideally, ThreadDelete should be tied to the identity of the peer that created it on a given peer in the first place, be that via CreateThread or AddThread. For now,...
This will be useful on the JS side of the equation for listening the DB updates from _outside_ a ThreadDB client. Part of the "great refactor" (https://github.com/textileio/js-threads/issues/414) over in `js-threads`.
Some folks would like to explore using https://github.com/ipfs/go-ds-leveldb rather than then default badger datastore for various memory issues. Right now, buckets and other external libs that use go-threads rely on...
This came up during a discussion with @andrewxhill. What if every `threadsd` also side-car'd (or however we decided to implement it) a textile gateway that was capable of rendering bucket-style...
It would be useful, when working with external devs, to be able to print version information to the console. Even just as part of the default startup output would be...