Called @nathansenn and he thinks it's a good idea to have @kencode lead D.Buzz.
I'll be completely out of the equation as I surrendered my stake for the betterment of the project.
Let's see if this can get resolved, thank you everyone.
You are viewing a single comment's thread from:
Alright then, but obviously funding is going to be needed. For the first few months we will need to get acquainted with the code and start squashing bugs and improving its efficiency and ux.
We'll also want to spin up the dbuzz api node again (not HAF yet, have not had a chance to audit that).
Also, if Agorise is assuming this project in perpetuity, the d.buzz domain name will need to be transferred over.
Also, if not too many people object, I would like to focus on the short-form, not the long form blogging. One thing that dbuzz is really good at is short form and I would like to stay focused on that instead of trying to compete with peakd and ecency, as they have mastered long form blogging. Dbuzz shines in the micro-blogging space.
A couple of the whales hate me though and my political and scientific views of the world, so someone else is going to have to be the marketer of my skills to them (of which they have been fully aware of since 2014). If they say yes, then let's type up the Proposal and get on it. Let me know, I can be reached any time on matrix (http://agorise.chat) or by email at: [email protected]
If you eliminate blog.d.buzz would be nice to allow the rendering of longer comments on d.buzz, maybe with a "show more" button for comments from 3rd party dApps.
It can be mentioned that I'm no longer officially affiliated with d.buzz in any way after the failures I ended with.
Posted via D.Buzz
I like the "show more" ux as well, I'll implement that.
Wonderful news! Keeping DBuzz alive for the benefit of the Hive community is important. Thank you Chris for helping to navigate the transition. Even though you are no longer officially ties to the DBuzz team, you have put the good of Hive above all else. Thank you, sir!