Repository
https://github.com/busyorg/busy
Update: Originally I also mentioned steemit.com (condenser), but utopian reviewer let me know that the post should have only one project, so I removed the steemit part, but I believe you can easily imagine the same thing for it.
Components
Busy.org is one of the most widely used UIs for Steem. Powerdown is a very critical transaction. It may be initiated by mistake or even initiated by an attacker. But it doesn't show sufficient information about powerdown.
For instance, here is a well-known user who has been powering down for more than 11 weeks :) Who said 13 weeks is too long?
However, steemit.com only shows the next withdrawal date, and busy.org shows nothing.
Steemit only shows the next powerdown date (on the bottom).
Busy shows nothing!
In the case of Busy, there is another problem. As steemd.com shows, the amount of SP that is under powerdown shouldn't be included for vote weight. But Busy includes this and therefore shows the wrong value. This bug had been reported and fixed, and the pull request had also been submitted by me.
In addition, while steempeak.com is not an open source,
Steempeak also shows nothing!
Proposal Description
Each UI should show the following powerdown information:
- Powerdown amount
- Next withdrawal date
- (optional) Powerdown route (if different from the owner's account)
I've checked the source code of condenser and busy and 1 and 2 are doable without many modifications of the code. For 3, some more work might be needed. I may submit the pull request for busy soon.
Mockups / Examples
mockup for busy.
As shown in the above, "Steem Power" now shows both powerdown and delegation (in parenthesis). And the powerdown has a tooltip, showing the scheduled date.
One may include powerdown route if it's different from the owner's account, since it might be due to a hacking. But these two (amount and next withdrawal date) are the most critical information and maybe sufficient.
Of course, when a different powerdown route is set, a one-time alarm would be very helpful, but this requires more work.
Benefits
Given that most users are not familiar with steemd.com or at least not using it daily basis, widely used UIs should show sufficient powerdown information. There are several benefits.
Hacking prevention
There are many cases where hackers start the powerdown and victims even don't recognize it! If the information is properly shown, this hacking can be prevented.Correct vote value
It can also prevent a bug of incorrect vote value. Even if the vote value is shown correctly, e.g., steempeak, users may wonder why their vote value is quite low. Note that around the end of 13 weeks of powerdown, the difference can be huge. In Ned's case, it's almost twice, and much more than twice next week.Stopping powerdown
In addition, users powering down may change their mind to stop the powerdown if the information is clearly shown everyday. Especially when it's almost done (again, for instance, Ned), the powerdown amount is quite big compared to the remaining so the chance of changing their mind might be pretty high :)
GitHub Account
https://githumb.com/economicstudio
ps. The mockup for busy (suggestions 1&2 only not 3) is now implemented and PR has been submitted by me: https://github.com/busyorg/busy/pull/2147