Hive Network Adoption And Front Ends Need Feeding
The Problem
People's stories and opinions during the COVID scamdemic were censored on Facebook according to an RT article here and they are kind of late to the party. Various users have been centored or voted too low for their posts to be seen, but the banning is done publicly. The source code is open and the list of those being banned is in the source code. Legitimately, this is done because of the illegal numbers that people sometimes post to the blockchain.
The Solution
So Hive is the solution. Make the two billion users come over to Hive. The only people who are incentivized to run a public web page front end are those who already get DHF funding. What is more, the vast majority of posts are done on only two public facing webpages: Just two of them.
Ecency and PeakD Are Not The Problem
Perhaps the reason these two platforms are so wildly popular a part from having history on the Hive blockchain is that they are so feature rich. There really are not many incentives to encourage the authors to start new websitse.
Although some of them have funding:
There are many that get no funding at all. Even Leofinance gets no funding from the DHF.
Apart from regular reasons to run an open source project, the fact that it is cryptocurrency wallet, making it open source helps people to trust it. Now it is possible that someone takes the Ecency source code modifies it for rebranding and sets up a new page somewhere. Maybe call it https://proofofbrain.blog. Then this person or leprechaun could add features not already in Ecency. Well all of this happened but people didn't all migrate at once. There is inertia in getting people to change over. Some of the changes when they find it interesting has been integrated into their project and then with all of the man power they have Ecency grows and grows.
One of the problems I face as a website developer on Hive is the utter lack of good documentation for Hive-Engine and actually a good API. The Hive-Engine API ought to be an API like the bridgeAPI. One that takes the same inputs but also includes the not only the rshares of the votes in active votes but how many POB they are going to get and so on.
There are some differences of opinion between myself and other devs of the Ecency code (@ecency). And that is why there are some notable differences. In reality there are many dozens of front ends with focus on particular Hive Engine tokens or they want to provide a distinct experience. I don't know if I should create yet another token for people to speculate on.
So why should a person create a new website when these two have done such a good job? There are all kinds of changes I would like to see in Ecency and instead of begging people to accept my changes it is in my nature to simply make the changes and run it. If the Ecency guys want them they can take them. If they don't, I can make my case that they should but it is up to them.
There are situations when people wont agree that a change is a good one. That's okay.
You guys reading this now could checkout the source code and run it on your own computer. After following the install instructions browse to 'http://localhost' and you would have your own site that could resist an attack against the proofofbrain.blog front end.
My Latest POB Change
I will post using the @proofofbrainblog alt account my new changes make to the proofofbrain.blog website. I will put for development changes I am making. Follow that account for news on that front.
🍀🍀🍀🍀 leprechaun
Posted with proof of brain.... Prove your brain now.🧠🧠🧠
Thank you for all your contribution! I agree, we don't have lack of features, perhaps community should be more involved into addition of new changes and before developing new features if community could vote or give feedback or support the changes then we as developers don't have option but to accept. I think, Busy tried this approach in early days but didn't work out because target audience of our users usually not with technical background or don't normally know what they would like to see as new feature, because chain and websites already have dozen things to learn about. We should re-iterate or perhaps go to whiteboard and figure out ways to evolve opensource development without blocking innovation.