Hi, we are consumers of both streaming APIs (which return extended tweets in the backwards-compatible “compatibility + extended tweet mode”, i.e. it has an extra “extended_tweet” key) and REST APIs (which return extended tweets in the breaking “extended” format, if the right query param is sent).
We are planning on normalizing all extended tweets - from all APIs - to compatibility + extended tweet internally for storage, to store them in a consistent, non-breaking format for consumers of our own APIs. Therefore, we need to convert tweets from REST APIs (extended format) to compatibility + extended format (extra “extended_tweet” key). It’s not feasible to make two requests, due to rate limiting issues.
Is there a set “conversion”/“truncation” process documented anywhere or, alternatively - has anyone written this/does anyone have a set process?