He's right about DBuzz filling the chain with low-value posts that serve to drive traffic away from Hive front ends to Twitter as they all contain a link to a tweet and not even the tweet itself. Also, DBuzz does not force a user to include a link to a fully fleshed Hive post in a Tweet. It does not serve Hive's interest for such an app to be used here. But what if DBuzz were modified to not create posts at all? What if it was redesigned as a tool to create immutable backups of Tweets as JSON-transactions and not posts? That way the posts would not appear in anybody's feed or create an issue with monetizable spam using up downvoting power or depending on attention by anti-abuse activists.