You are viewing a single comment's thread from:

RE: Unoriginal Twitter Spam - @dbuzz Sending Users AWAY From Hive TO Twitter!

in #hive4 years ago

How is automatically posting tweets to Hive that direct people to twitter good for Hive?

From an SEO standpoint it actually helps Twitter. From a content standpoint, it helps twitter.

Please explain to me how this helps Hive.

Sort:  

Right. It will help same way as Steempress plugins helps, the only difference is that dbuzz has declined payouts for posts published from Twitter.
It will help when you post from dbuzz and publish your post automatically to Twitter. I don't have to tell you how important Twitter was in last weeks for Hive community

But they don’t offer that feature, they only offer the ability to post to twitter and it be copied to hive (where it directs you to twitter). So we can talk ideas, many have, but this is about the current features and how they do nothing beneficial for Hive in the slightest.

That feature was actually in the works @justineh after @mmmmkkkk311 mentioned that it wouldn't require the use of Twitter's API.

We have actually been very open to feedback and criticism, but after realizing that Community posts show up in people's feed, even if they are not subscribed, we took the site offline today.

So we can talk ideas

That's what I see when reading their comments, so maybe X should stop for a while downvoting and give them a chance to implement some new features

I would start from:

  • autopsting to TT
  • title setting in this format: [This is post title] This is post body
  • set post beneficiary @steem.dao (50% for posts published from TT, 25% for posts from d.buzz

They were given an opportunity, they said they would stop, then told me they aren't.

Now, they are where they are.

Is it still possible that you would accept existence of this app on Hive chain? If yes, which features would you like to see implemented first?

Yeah, if you remember I told you I would consult with my team 1st . . but after receiving a DM from @guiltyparties, I jumped the gun and said we would comply with your recommendations without consulting with my team.

When the rest of my team woke up, we discussed, and felt like a rework could possibly set us back weeks if not over a month to get it done.

So we decided to move forward, but after @nathansenn realized that Community posts ARE posted in people's feed, even if they are not subscribed (thank you @notconvinced), we took the site offline today.

I thought we were talking about the app, not downvotes. You stated the app is very beneficial, I asked how. So we have determined in its current state it’s not beneficial in the slightest, but you feel it’s shouldn’t be downvoted.

Well, downvotes literally were never discussed here but will agree that I don’t see the need to bury them but also think making accounts to spam the chain is not beneficial and those actions have led to downvotes in the past, so not really surprised they are now.