cookie-cut-copy posts may be meaningless
But it did happen!
Btw, have you logged int https://d.buzz to view the feed there?
I have nothing against D.Buzz. My message was for risingstargame. For what I understand, Risingstargame uses this D.Buzz to promote the service. Promotion is cool, but one needs to use the right promotion channels and the right promotion setup while staying away from those channels and practices that increases the problems around our own HIVE chain.
At HIVE we need more users. Those users are not onboarded yet. These users can be found anywhere else. Therefore, when these DBuzz messages are for promotion of the game, then dont integrate DBuzz, but integrate Twitter, Facebook, Reddit and whatnot. Learn form the team behind Splinterlands. They promote external HIVE and they land new HIVE users. They provide onboarding tools and services. Great! That is what we need!
In case DBuzz integration with the game serves other wanted purposes, I can think of: 1) notifications, 2) enticing reaction.
In case 1, then thats a no go, build notifications into the game itself, or use notification services, not a post.
In case 2, great, but who will respond to a one liner with some statement about having played the game, or gaming results (even when customised)? Will the game users scroll HIVE to check on the DBuzz posts from others playing the same game? I dont think so. Who else? I can't think of users being interested to respond to a Risingstargame DBuzz to be honest.
In the post you mentioned in your comment, I read a statement about cross-promotion, and a request you made to somebody else. Again, promotion within HIVE? Really? How many active users we have? A handful. They all will know soon enough the existence of some new dApp, social network, game, or whatever. Really no need at all to promote in post form manner. The dApp team shall promote in whatever form, and there will be enough HIVE users writting posts about a dApp they like, or use. I've seen soooo many for the RisingStarGame already. DBuzz's are totally unnessary for the purpose of promotion within the HIVE community.
This post by @ahmadmanga will provide more context, so long as you read the replies
Yah, read post and comments. As mentioned already, I have no issues with D.Buzz (would've loved to see all rewards for social networks in second layer, and different types of services using their own tokens and rewards pools, but that aside). The issue is with the RisingStargame: 1. the use case for D.Buzz (promotion within the HIVE community is not needed in this form at all) and 2. the effects: spam. And 3. another drama in developent. We had and have enough of them already.
Okay, just read your comment @edje and I am happy that you are voicing your ideas.
The Buzz widget is intended to replace, or maybe even compliment Twitter's Tweet button:
https://hive.blog/hive-139531/@dbuzz/embed-and-buzz-directly-from-any-web-page-meet-the-embed-buzz-button
And I am in the middle of helping a bussiness associate & friend setup a Startup Incubator & Marketing Facility w/40 computers setup:
https://hive.blog/dbuzz/@dbuzz/tuesday-development-updates-or-pulling-back-the-veil-of-what-s-in-store
It might take longer than expected, but we plan on on using the facility for an in-house marketing team.. I will live on-site, and we will market @dbuzz across Web 2.0 platforms..
And that's what I meant by Cross-Promoting 👍
I fail to see how my statements around the NO need for promting HIVE dApps within the HIVE community by means of DBuzz or any other ppst directly from the dApp itself is addressed by DBuzz.
And that is in fact what I have against this (see my statement above). Search hivesearcher for risingstargame and you'll see how many posts are alrewady made as normal posts. These all are promotions by itself. Also search for other HIVE based dApps in the same search engine and you'll start understanding what I mean.
Thats super! I suggest (if not done already) to check with the splinterland team, they seem to have a lot of experience already in onboarding new users. You both may work together?
And I agree that promoting externally is important, but You do realize that #Splinterlands owes much of it's success to marketing inwardly within the #HIVE community (IMO) BEFORE and during their external marketing activies.. right?
External marketing is important ✔️ @edje
BUT I disagree with your belief that internal marketing, within the #HIVE community is worthless (get the low hanging fruit first).
We are a Top #20 Dapp worldwide (at least right now) across all blockchains (not just #HIVE) thanks to marketing within the #HIVE community 1st.
Many in #HIVE still don't know much about @dbuzz and You might fit in that category (knowingly or unknowingly).
IN case Aggroed advised you to let dApps spam the HIVE chain under the statements: Its marketing the way it shall be done? Then he is wrong.
Now you making statements based on assumptions.
Check the stats for daily users of @dbuzz before & after @risingstargame integrated the Buzz widget.
The term is: Network Effect https://www.investopedia.com/terms/n/network-effect.asp
Posted via D.Buzz
You fail to see how many no value posts are now entering the HIVE chain. This morning I've seen a few Risingstargame Dbuzz posts with again the default message by the game owners, this message to provide quality content. Users seem to just press the send button without adding any value. You fail to see what happens now with Risingstargame, will increase a lot when more dApp owners integrate DBuzz in similar ways.
As metioned before, I have nothing against DBuzz. When users add value to the community, the content consumers, its a perfect solution for HIVE.
I believe the solution is for @chrisrice and the team to have a default message as part of the widget and for it to not allow posting if it is not changed.
Are players incentivised in one or the other way to post a D.Buzz?
When they Buzz to @dbuzz, users like me will (and have) replied to them invite them to Buzz more often on @dbuzz 🙂👍
Posted via D.Buzz
Ahh yeah, if it's not changed and it should probably be a certain length @risingstargame.
That is better than having the text delete itself 😀✌️✔️
Posted via D.Buzz
So you see yourselves... I deliberately not show the users, since I can't really blame the users at this stage. What you give them, they will use. The easier it is to make (some) money, they'll go for it. DBuzz upvotes several of these comments. Either through autovote (why only a few, and not all?), or manual ones (if so, why?)
We don't autovote anything, everything is manually curated but you brought up a good point @edje . . thank you 🙂✌️
-> Please don't upvote shares from @risingstargame if the caption hasn't been changed @iamraincrystal, and try to use comedy to let them know they didn't Read the Caption before Buzzing 👍
Again, this is Live and a Buzz embed button has never been done on #HIVE, so we are learning as we go.
If you see any other things you dislike, please let me know 😎👍
Interesting that curators needs to be told what curation means. I really hope you'll get things in order. In a decentralised world we need to have respect for what we use. A dApp owner, creator shall not only be careful launching new services and features in an existing community and around existing technology, but shall also monitor the effects of changes and act upon immediatelty when unwanted behaviour is driven. It should not be the community pointing these out to the dApp team.
Umm, I disagree with your belief that the community shouldn't be the one's to give feedback to DApp owners.
Feedback is one of the most important things, a DApp, Business or Project can receive and listen to, and YES it helps, and YES the community can and probably should give feedback.
Having said that, after looking at the screenshot you shared, it looks like @dbuzz didn't curate those Buzz's @edje.
I also want to challenge you to visit:
We are doing good work and we focus on discussions.
@risingstargame is a discussion starter, especially if it has a good caption 👍
Posted via D.Buzz