You should know that you will NOT see the posts on Peakd or Esteem from others unless you subscribe to our D.Buzz Hive community. You can even use D.Buzz and not be subscribed to our HIVE community. This option means you won't have your news feed filled up with people reposting from Twitter.

This isn’t entirely true as you’ll see these posts from the people you currently follow. I don’t see this as a huge issue, as it’s up to the individual user to unfollow people whose content becomes unenjoyable in their feed. That’s why many people started alternate accounts during past applications like D.Buzz, such as Share2Steem or ZAPPL. Also, I believe most front ends auto recognize using a #hashtag within a post. Any cross posted content containing hashtags will find its way into the corresponding news feeds outside of the D.Buzz community.

I honestly believe you should be broaching this conversation the most with the teams behind the interfaces of hive.blog and PeakD. Ideally, I believe that your content should perhaps not be displayed on these front ends at all. Obviously this limits your early exposure, but may be much more favorable to long term plans.

Running your own front end interface built on Hive with a focus on micro blogging is wonderful in my opinion. I also do not mind the Twitter cross posts. I do not see your goal of pushing the Hive hashtag on Twitter as relevant or useful though. The real goal is to onboard new users with a system that is effortless as it piggybacks off their already existing social media activity. Hive has the same difficulty acquiring users as any social media upstart. No serious content creator or influencer wants to put much effort into posting on a platform with such a small userbase. Allowing them to “dip their toe in the water” via cross posting automation is perfectly valid.

The main friction you face now comes from the creep of these micro blogging cross posts mixing into Hive platforms not designed for it. There is an appeal to a “one stop shop” where I can see all the content of everyone I follow in one place... but no one is presenting that well, and it may honestly be an unsolvable UI nightmare to achieve. Many new dApps will run into this issue you’re facing, and it needs to be solved sooner than later. I’d rather see Actifit posts only when I go to the Actifit app, D.Buzz posts only when I go to the D.Buzz app, Dapplr posts only on the Dapplr app, etc. than have the morass of conflicting content that occurs on the two main front ends currently.

Unfortunately that’s not your fault, but it is your current problem. It may take some creative solutions to properly compartmentalize your data to avoid conflicts. I would not expect the D.Buzz front end to show all the Hive blockchain data. The long form content doesn’t fit. You need to expect that it’s a two way street and find ways to voluntarily further limit the appearance of D.Buzz content on the current prominent front ends. The community function alone isn’t sufficient.