Got it. The clarification helps!

It’s an official restriction. There’s nothing I can do about it.

But making an additional TweetDetail call would imply extra cost and latency just to view the remaining text. And the text itself isn’t long anyway.

Is the truncation done by design within your control, or returned as-is by the offical twiitter API? Would be nice to have the option of getting the full-text, perhaps via a parameter that can be defaulted to truncation?

Tweets in the list will be truncated if they are too long, if you need the full content, please use the TweetDetail api.