A few days ago, I received a post telling me that replies to tweets was not working https://tweetinvi.codeplex.com/discussions/645063.
At first I thought the user was not using the library correctl as few days ago the library was working as expected.
Today, I received the same error as he still encounters.
The problem is that as written in the documentation for in_reply_to_status_id
This parameter will be ignored unless the author of the tweet this parameter references is mentioned within the status text. Therefore, you must include @username, where username is the author of the referenced tweet, within the update.
Now this rule has never been enforced in the past, Tweetinvi has successfully passed the integration tests of Tweet replies for years. And we all know that no one can rely on the documentation to know what to expect from the twitter rest api (test and failure is the only way).
And to be honest this rule does not make any sense at all. When a tweet is published with a valid in_reply_to_status_id, you should ensure that the @username is set up on your side. Because otherwise it forces user to make 2 request to do a single action.
https://api.twitter.com/1.1/statuses/show.json to get the creator ScreenName
- https://api.twitter.com/1.1/statuses/update.json to post the tweet
In the past we were able to only call https://api.twitter.com/1.1/statuses/update.json once and this worked as expected. I hope this is temporary because this does not make sense, it costs Rate Limits which are already too restricted and in addition it forces your platform (api.twitter.com) to reply to even more requests.
The error is not unique to the twitter library Tweetinvi but can also be reproduced on apigee and other libraries.
So please could you confirm what is to be expected. Should we follow the documentation in for this parameter or should we expect the REST API to behave as it always did for the last 3 years.