TN: Add More "Why" Details to Estimate Upvote

[inertia186]

As an applocation developer, I would like to know more about each component involved in calculating an upvote so that I can understand what I'm calculating.

Specifically, the final calculation:

https://github.com/steemit/devportal/blame/88368fe89f62759edd37ea5efd0dce4e20345066/_tutorials-recipes/estimate_upvote.md#L200-L204

For example, instead of just saying "calculating value of each vote depends on multiple factors", more details should be added, like:

We use delegated_vesting_shares but why? If you do not account for this, the caclulation will be thrown off because delegated_vesting_shares is STEEM Power that has been delegated to someone else and cannot be included as part of total_vests. If it's not accounted for in the calculation (and it's non-zero), the estimated upvote would be higher than it should be.

(extends: #157)

AC

• To get final_vest ...
  • Why do I need vesting_shares?
  • Why do I need received_vesting_shares?
  • Why do I need delegated_vesting_shares?
  • Why do I need to multiply total_vests by 1e6
• To get power ...
  • Why do I need voting_power?
  • Why do I need weight?
  • What's the deal with dividing by 10000?
  • What's the deal with dividing by 50?
• To get rshares ...
• What is rshares and why do we multiply power with final_vests then divide it all by 10000?
• To get estimate ...
  • Explain: rshares / recent_claims * reward_balance * sbd_median_price