Steemit Update.png

Steemit developers have made some UI changes in hopes of improving the platform by making it more user friendly, so there has been few slight changes that I want to sum up in this post as part of my mission to keep track of the latest Developments. By doing so, we get to witness how a platform like Steemit changes through time to meet the growing demand of users who want to be part of a Social Network that is easy to join and participate in

It is important for any web designer to design functional sites that can easily generate interest and online traffic among the internet users, hence the community should discuss or accept changes done to UI/UX, if it allows for for more mainstream adoption

There are 2 notable changes such as:

Adding Post Payout under ‘’Settings’’
Allow for Direct Image Upload

Adding Post Payout under ‘’Setting’’

Now, you can adjust the post payout under ‘’Settings’’ with the additional options of manually adjusting the Payout for Posts & Comments

Previously, there was a custom drop-down menu available at the bottom of the page during Post Editing that allowed you to adjust the payout of the post however this option is no longer available. Now, users have to go ‘’Settings’’ if they want to adjust the Post Payout under ''Preferences''

Allow for Direct Image Upload

For user convenience, Steemit now accepts direct Image uploads under ‘’Settings’’ for the display Picture and Cover Photo

Before this, Users needed to use third-party image hosting solution to upload their Profile/Cover photo, a process that involved copying & pasting HTTPS Links under ‘’Settings’’ as explained in this Post: How to quickly setup your Steemit Profile Image using the right HTTPS Link

Additional Announcement

Apparently, there is a discussion going regarding the decline payout reward option, with the suggestion of burning rewards by sending payouts to null. With this functions, any decline post payout will result in reducing the over supply thus increasing the price in the long-run. Keep up with this proposal or feel free to join the community discussion on Github Issue 2512