as they all contain a link to a tweet and not even the tweet itself.
It included the actual Tweet but we were not done rolling out our services some some of the Tweet was cut-off.
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.
We are in the planning stages of modifying D.Buzz and will get started after we rest some and re-group.
That sounds great. I think immutable data storage could be a major use case for Hive in the future.