Could we have an input parameter available in the request for “POST statuses/update” API which could be used to indicate that the ‘status’ attribute passed is to be consumed as a simple text tweet and not as a special twitter message?
There are some particular sequence of characters which are treated as “special commands” by Twitter (e.g. tweets starting with 'M ’ and 'D ').
Reference for commands: https://support.twitter.com/articles/14020-twitter-for-sms-basic-features
When posting status through API, it is rarely used for issuing special commands and is mostly always used for issuing text based tweets. Now since some of these texts coincidentally match the pattern of some special command, the posting of the status may fail. This is specially confusing in case of 'd ’ and 'm ', as these can be easily used for ‘the’ or ‘I am’ while posting a simple status.
Also the global list of “commands” may keep changing, making it practically impossible for the ‘end-user’ or for the ‘developer using the API’ to avoid posting such tweets.
Thus, there should be an input parameter available in the request for “POST statuses/update” API (https://dev.twitter.com/docs/api/1.1/post/statuses/update) which could be used to indicate that the ‘status’ attribute passed is to be consumed as a simple text tweet and not as a special twitter message.
Please share your thoughts on the same.