A week ago, I wrote an article describing how the upcoming RC delegations could present a no-compromise option of supporting newbies freshly out of RC, without granting them immense voting power at their infant stages. Such a simple concept as this could open up the door to many more sorts of RC-intensive Layer 2 applications to be built atop HIVE.
The model of RC delegations utilized, and the origin of the problem that will sooner or later buoy itself, is that it's peer-to-peer in nature.
This model is self-defeating to the concept of RC delegations as a whole. Because the process of looking for newbies in the wild is an exhaustive one, only a handful would be on active look out for those promising newbies.
Not to mention that newbies are volatile. Of a hundred of them, the ones actually sticking around are going to be much lower. Imagine how many moot RC delegations are going to be there shouldered upon those ones actively looking for newbies, hogging up valuable RCs for the actually promising ones out there.
Automation is in order
RC delegations are a fantastic idea, just not in its current model or form. In order to successfully, and meaningfully, delegate RCs to newbies, the one delegating would have to look for a newbie, keep up with a newbie, check on that newbie, whether that newbie ended up leaving HIVE for good for an extended period of time... and so on.
This is an exhaustive process made herculean because no one is going to delegate to just one newbie.
A much more viable model of RC delegation, one that encourages actual use, would be an automated pool of RCs assigned to the origin accounts of tribes and community frontends. A massive number of people, that way, could directly delegate to that pool, functioning as a reserve intended to support newbies.
This is great, because RCs by themselves are a filter in essence: The newbies quickly exhausting their RCs are the ones prolifically posting and commenting. The origin account of the frontend being posted to, could then automatically delegate RCs to that newbie.
Spam is not an issue. The automated RC pool could decide which newbie is posting meaningfully, and which is spamming incessantly. The automated structure could synergize with Spaminator, checking for downvotes on a newbies post, utilizing that as a marker for whether or not to delegate.
Such a model was indeed in the works, and was geared for implementation as well, at the birth of RC delegations. Alas, it didn't pan out favorably at all. Reasons it didn't are confined to UX-simplicity, and the complexity of RC pools involved, code- and transaction load-wise.
Conclusion
RC delegations are cool. They encourage worthy newbies to stay and engage more within the HIVE ecosystem. That, though, is arguably bottlenecked by the overtly complex onboarding process, complicated, ironically, by the simplistic nature of peer-to-peer delegations. What use are RC delegations if we don't open wide the floodgates? I myself almost gave up entirely on that part, and I'm glad I didn't.
Thank you for reading!
Posted Using LeoFinance Beta
The Resource Credit delegation will likely be driven by the applications and games. They are the ones who will attract new users to Hive. This is not going to be an individual basis (for the most part).
To optimize content on Leofinance and Hive, check out the Main Menu from @leoglossary.
Posted Using LeoFinance Beta
Of course. Resource Credit delegation is not going to be on an individual basis, but in its current revision, which will likely make it to the hard fork, is it going to allow chain-delegation? The RC pool set up is capable of this, but I'm not sure if peer-to-peer is.
By the way, good job on the @leoglossary. It doesn't make much for a seamless experience, though. The referencing work is menial to the author, and the viewing process is inconvenient on account of opening a new tab to the user, when they simply want to read the first few words of the definition. Wikipedia's implementation of floating information boxes upon hovering over hyperlinks is something to aim for. Do you plan to propose something similar to Khal to integrate onto the Leo frontend?
Posted Using LeoFinance Beta
He already picked up on the idea and commented about it. I think he is going to add it to the to do list for the developers.
In the meantime it is a bit more onerous but still not difficult for the author to have the tab open, click on the appropriate term and link the URL.
It all helps.
Posted Using LeoFinance Beta
Sweet. I really do think a frontend integration is going to supercharge adoption and usage. For the meantime though, I'll try LeoGlossary out in my next post.
Without a doubt that feature will make things a lot easier.
However there is more than one way to skin a cat as they say. For now, we just do it the hard way. In the end, it will help Leofinance.
Posted Using LeoFinance Beta
Congratulations @leonordomonol! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s):
Your next target is to reach 7000 upvotes.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPSupport the HiveBuzz project. Vote for our proposal!