this is merged
I realized it's okay if hist without values doesn't work, because createUserStream can be used for that.
However, I'm not sure I understand the behavior of block in this context. It looks like this says, if I see you block me, I will stop replicating your feed. Shouldn't it instead be that I stop replicating your feed only if I block you? and so the information about whether to replicate your feed comes from my feed, not yours? (and maybe should come from the feeds I follow, as well, but that could be a different discussion)
Pressed enter too soon - I've gotten used to the publish preview button in patchbay...
Fetch shouldn't need too much changes that I can see. Mainly it should just follow
objectsBranch, if it exists, instead of
The main benefits of this design will be that it will be correct, so we shouldn't get the
'did not send all necessary objects'error anymore. The other benefit is that it should only send to the client what is really needs for what the client requests. This means that packfiles containing only objects which are not needed (e.g. are in branches not being fetched, or have been removed from history) will not be
wanted and sent to the client, while such updates will still be used for calculating the refs state.
Reproduced. Tracked to the call to
Highlight.highlightAuto(https://highlightjs.org/). Fixing by removing highlighting except when the language is specified. e.g.:
```js return true ```
``` return true ```
Built with git-ssb-web