Problem: reindexEncrypted will call index.processRecord(record, seq, pValue) for every freshly-decrypted box2 msg, but leveldb indexes may build state in such a way that assumes that all records are processed in order.
For instance, take the ssb-about-self index. Every time it stumbles upon an about message, it will destructively update the state of the user profile.
So if the "latest" user profile was published on the about message at sequence 10, if we just decrypted a box2 about message at sequence 6, this one will override the actual latest information from sequence 10.
Problem:
reindexEncryptedwill callindex.processRecord(record, seq, pValue)for every freshly-decrypted box2 msg, but leveldb indexes may build state in such a way that assumes that all records areprocessed in order.For instance, take the ssb-about-self index. Every time it stumbles upon an
aboutmessage, it will destructively update the state of the user profile.So if the "latest" user profile was published on the about message at sequence 10, if we just decrypted a box2
aboutmessage at sequence 6, this one will override the actual latest information from sequence 10.