moecki

This was a hivemind problem and has already been fixed (https://github.com/steemit/hivemind/issues/329). Maintainer should close this issue. @ety001

I rebased the feature branch and removed some commits that are not required for the final version. This should make the review a little easier.

There are some more accounts in my production hivemind node: ``` db=# select name,followers,following from hive_accounts where following

@steemchiller Yes, it's strange. I have 3 hivemind nodes and two different counts. poduction: `bullionstackers | 7446 | -541` (current official db version 20; db build on a snapshot from...

I tested some cases with @moecki.tests: - [x] three new follows/unfollows in one transaction, - [x] follow already followed accounts, - [x] unfollow not followed accounts, - [x] and some...

After `force_recount` there are better results: ``` db=# select name,followers,following from hive_accounts where following

I would suggest to add a optional start parameter to forcing recount in Sync.run() before [updating the chain state](https://github.com/steemit/hivemind/blob/90f5311aee49bb901ea04037ba0e44143b1440db/hive/indexer/sync.py#L73).

I checked it on my testing2 hivenode: before recount: ```sql name | followers | following -----------------+-----------+----------- bullionstackers | 7453 | 2107 ``` after recount: ```sql name | followers | following...

Another eample: https://steemit.com/dynamicdevs-s20w4/@mohammadfaisal/sec-s20w4-or-or-introduction-to-php-part-2 It was written, deleted and written again with the same permlink. Maybe it is different because the first post is a community post.

@the-gorilla-steem I would check this, but where can I see your changes?