It has been more than two years since I have been on Hive. During this time I have witnessed several changes on the platform's back-end and front-ends. Some new front-ends supporting specific aspect have been created and the older front-ends have evolved and added new features to them. With introduction of every novel feature there opens a new way for thrill and excitement.
When I came to Hive Resource Credits (RC) and Hive Power(HP) couldn’t be delegated separately. For delegating RC one had to delegate HP. The separation of the two entities made it easier for newbies to be more active in engagement as higher RC delegation is easier to receive as compared to HP.
With time, Hive became as supportive to short-form content as long-form content via introduction of waves (on Ecency) and threads (on LeoFinance). Several variations in various aspects of the front-ends made the navigation sophisticated.
In other words, Hive has continuously been on journey of improvement. No matter how much we are improved there is always a room for betterment. While the creativity of developers is crucial for the upgrade of the platform, the feedback of its users is also important for evolution of the features they think would create sophistication in their user experience.
On the basis of my experiences, there are a few upgrades I want to see on the platform.
People who use a desktop or laptop may not understand the worth of undo option in the editor because ctrl+z keys work for them. However, people consuming Hive via their mobiles have no option to deal with chaos caused by an unwanted editing.
I have passed through such an incident more than once when my whole post was lost because of some wrong press. I desperately wanted to have an undo option during those occasions.
I have used 5 front-ends so far and none of them provides an undo option in the editor. I wonder why no one pondered over its need. Anyways, I think it’s an upgrade that would save time and efforts in case of accidental editing.
There are some methods that can be used to increase the visibility of the post. While some front-ends offer the option to promote a post within their interface, certain methods are commonly employed across the blockchain. They include reblogging, using tags and cross posting.
A problem with cross posting is that the monetization of a cross post is aromatically cancelled. It so happened to me once that I received bigger upvotes on the cross-post as compared to the original post. Nevertheless, they were of no value neither for me nor for the curators.
I would like to propose an enhancement in this context. The upvotes for a cross-post should be aggregated with those of the original post. This design should ensure that when a user casts a vote on either of the posts, it's counted for both. This approach would effectively prevent any abuse related to vote farming.
Auto voting is a way to support one’s favourite authors even if one is unable to take time to upvote them manually. Nevertheless, this approach has certain drawbacks.
I have seen (I am sorry to say) some not-so-good authors receiving high valued votes because someone had set them on auto vote long time ago.
On the other hand, there are some curators with high valued votes who hardly look for new content creators but their auto votes keep on bringing them curation reward. In this way, curation is not given to deserving members.
I think an upgrade should be implemented where autovotes should be reset after a certain period of time (say 3 months ) and the member has to reconsider one’s choices again. This way, new members are likely to achieve the support.
That’s all from my side today. Hoping to see the platform growing with advancement and prosperity.
●●●●●●●●●●
The post is my participation for Hive Learner’s featured contest.
Image by geralt on Pixabay.com
