Thanks a lot for your comment. Now I included github issue in my posts. This is my first utopian-io post so I'm not even sure I followed the direction well :)

BTW, floating point isn't my main point at all :) I just mentioned that there is a very tiny chance that the bug may **not** occur due to floating point precision problem. I know, internal calculation is mostly done by integers, but A/B is basically floating point operation even if both A and B are integers, which may lead to some unavoidable error. Again that's not my main point at all.

I agree that 1% isn't a big issue in practice. But in theory it's a big issue I believe. If one thing doesn't work as intended, who can believe the others work well? And that's why I suggested fixing it very carefully with enough time, not by a temporary measure. I still believe that the current inconsistent and not self-contained feed history is a pretty bad idea. I know Steemit is having a hard time, so maybe they don't have enough resources to handle this. I'm very sorry about it.

I'm not sure if you work for Steemit too or not, but I presume you're close to them. One suggestion is that Steemit should admit that it isn't sustainable without ads. I worked at facebook before (now I'm in the academia) and that's why I have much interests in Steemit. A decentralized SNS/Blog without ads is too unrealistic to me. While Steemit pretends to be decentralized, they are actually very centralized imho. Then why not having ads before it's too late? Let's face the reality.