Open documentation issues

[chm-diederichs]

This issue is for tracking missing documentation. Please add suggestions below.

[sbosshardt]

Indexed Length
The linearizing algorithm is able to define a point at which the ordering of the graph below will never change.

I'm trying to understand how this handles hypercores of peers that are lagging behind the group. Maybe because of poor network connectivity, maybe because of maliciously operated hypercores. Apologies if I get some of the terminology wrong.

Let's say I have an autobase for a p2p application that has five peers running (5 different users, one hypercore per user). Peers A, B, and C are healthy. Peers D and E are compromised - maybe at first they function normally, but at some point they don't.

If Peer A creates a legitimate block, Peers B and C observe the block, but Peers D and E remain unresponsive, will the autobase linearizer/view eventually consider Peer A's block to be final/indexed (its order not to change)? Or can a minority of peers perpetually obstruct progress?

[sbosshardt]

Is there a mistake in this statement in the documentation or am I confused?:

The simplest kind of linearized view (const view = base.linearize()), is just a Hypercore containing the results of a causal stream in reversed order (block N in the index will not be causally dependent on block N+1).

I'd think that block N in the index would be causally dependent on block N+1 (since the order is reversed).

[iamyellow]

I'm more a 1st see the thing in action and then check the docs. this workshop is a hidden gem, helped me a lot in the past. how far is current autobase from there?