ssb-replication-scheduler's use of hopStream means that it gets any graph updates during indexing which may reflect an older version of the social graph (where I was still friends with bob, before I started disagreeing with him).
Solution
Use ssb-db2's indexingActive to monitor the state of indexes, and if indexing is about to start, stop draining hopStream. Once done, resume draining hopStream.
Context
https://github.com/ssbc/ssb-friends-purge/issues/1
Problem
ssb-replication-scheduler's use of
hopStreammeans that it gets any graph updates during indexing which may reflect an older version of the social graph (where I was still friends with bob, before I started disagreeing with him).Solution
Use
ssb-db2'sindexingActiveto monitor the state of indexes, and if indexing is about to start, stop draining hopStream. Once done, resume draining hopStream.1st :x: 2nd :heavy_check_mark: