Christopher Joel
Christopher Joel
We used to have container image tags that corresponded to releases. E.g., the orb container would have a `noosphere-v0.14.0` tag that corresponded to the container built against the SHA that...
As of #530 , we now render and synchronize the broader Noosphere graph to the file system when using `orb`. As a basic implementation, this works great. However, some of...
We are reaching that point in Noosphere deployment where it would be _really_ nice to be able to forward-migrate existing spheres as various file system layout, protocol data structure and...
The Noosphere name system is designed after a "petname"-style name system. The term petname is borrowed from [this article](http://www.skyhunter.com/marcs/petnames/IntroPetNames.html), which distinguishes petnames and nicknames: - **Nicknames:** "can be used to...
Currently, if the gateway's device key or sphere ID changes, we accept the change and proceed. This is potentially very dangerous, as an attacker-in-the-middle can potentially receive blocks during a...
It should only be possible to authorize a given DID once via `SphereAuthorityWrite::Authorize`. It's not possible to enforce this as a matter of other implementations, so elsewhere we need to...
As of #530 , the `noosphere-cli` has a robust facility for rendering a sphere to the file system. However, it is not particularly resilient to many failure scenarios. We should...
The `noosphere-cli` infers file extensions from mimes (and vice versa) when reading from or writing to the file system. This is an imperfect exercise, so we should provide ample opportunity...
We should pick an upper limit, especially recognizing that slugs are maximum 200 characters, and some platforms like Windows have very tight limits on file path length.
The construct that reads a sphere's changes inside a file system workspace basically has to read all of the workspace contents into memory at once. This is related to #498...