We are open to advice and constructive criticism, and our team wants to build on #hive.
@nathansenn already invested a decent amount in the project, including our premium domain D.Buzz, and our team plans to invest more.
@xxxxxxxxxx said that there were MANY large stakeholders who disagreed with our project as it was, and told me that they would comment but for the most part, they never did . . that is one of the reasons we walked back our plan to follow @xxxxxxxxxx recommendations.. and I also hadn't consulted with my team at the time yet, so my decision to follow his advice via PM was premature, saying it was our final decision was a mistake on my part.
If there was a consensus of major stakeholders, it wasn't on chain, and we were looking for consensus but I also understand that the majority of you were busy with the 23 million stolen #steem issue.
My request is that you help us gather consensus, @xxxxxxxxxx offered some nice ideas but it wasn't clear that it was the consensus, and we had conflicting information based on the comments we received, the users who used our Dapp, and the advice we received in the #HiveKeepers Discord.
The general consensus was that our Dapp was a hot issue but there were multiple ideas thrown around to help solve it. Some people spoke clearly to us in a way that was respectful and easy to understand, others didn't.
No harm no foul though, we are searching for consensus, please help us find it so we can build on #HIVE.
Is the entire business model of Twitter Inc. for spam?
Bitchute and LBRY both use our model - are they spam?
Stop saying this lol it’s not true in the slightest. Your app is nothing like twitter, lbry, or bitchute.
Perhaps just focus on building what you pretend it is before launching next time, just a thought
Okay @justineh.
We are open to advice and constructive criticism, and our team wants to build on #hive.
@nathansenn already invested a decent amount in the project, including our premium domain D.Buzz, and our team plans to invest more.
@xxxxxxxxxx said that there were MANY large stakeholders who disagreed with our project as it was, and told me that they would comment but for the most part, they never did . . that is one of the reasons we walked back our plan to follow @xxxxxxxxxx recommendations.. and I also hadn't consulted with my team at the time yet, so my decision to follow his advice via PM was premature, saying it was our final decision was a mistake on my part.
If there was a consensus of major stakeholders, it wasn't on chain, and we were looking for consensus but I also understand that the majority of you were busy with the 23 million stolen #steem issue.
My request is that you help us gather consensus, @xxxxxxxxxx offered some nice ideas but it wasn't clear that it was the consensus, and we had conflicting information based on the comments we received, the users who used our Dapp, and the advice we received in the #HiveKeepers Discord.
The general consensus was that our Dapp was a hot issue but there were multiple ideas thrown around to help solve it. Some people spoke clearly to us in a way that was respectful and easy to understand, others didn't.
No harm no foul though, we are searching for consensus, please help us find it so we can build on #HIVE.