b) Completely agree c) I thought the reason for even implementing this despite the fact that most 3rd party clients already handle retweets by creation of a new tweet, was to allow text that's being sent by 100's 1000's and so on to be stored in a single location to save on database space as well as to allow for quicker retrieval of the tweet by allowing for more specific caching.
Again, that was a thought, since i dont actually know :)
