Hey there, let's break down why your tweets are getting truncated when switching from from: to about: queries, even with tweet_mode: "extended" configured. Here are the most actionable fixes to try:

1. Confirm tweet_mode Is a Top-Level Parameter #

First, make sure tweet_mode: "extended" is passed as a top-level request parameter, not nested inside the q value. It’s easy to accidentally misplace this when updating your query format.

Correct Parameter Structure:

// Example request configuration (JS/Node.js)
const requestParams = {
  q: `about:${body.name}`,
  tweet_mode: "extended" // This needs to be at the top level, not part of the query string
};

If you had it incorrectly embedded in the q string before (unlikely, but possible), that would explain why it worked for from: but broke with about:.

2. Handle Retweets in Your Response Logic #

Queries using about: tend to return far more retweets (RTs) compared to from: (which only pulls tweets directly from the target user). For retweets, the full untruncated text isn’t stored in the main full_text field—it lives in retweeted_status.full_text.

Add this logic to extract the correct full text based on tweet type:

// Helper function to get full text for any tweet type
function getFullTweetText(tweet) {
  if (tweet.retweeted_status) {
    // For retweets, grab the full text from the original tweet
    return tweet.retweeted_status.full_text;
  }
  // For original tweets, use the full_text field (fallback to text if needed)
  return tweet.full_text || tweet.text;
}

// Usage when processing API results
apiResponse.statuses.forEach(tweet => {
  const fullText = getFullTweetText(tweet);
  console.log(fullText);
});

This is likely the core issue—your original from: query had few retweets, so you didn’t need this check, but about: changes the composition of your result set.

3. Validate API Endpoint Compatibility #

Ensure you’re using an endpoint that supports tweet_mode: "extended":

• For Twitter API v1.1, the search/tweets endpoint works as expected with this parameter.
• If you’ve switched to API v2, the setup is different: use tweet.fields=text to get untruncated text, and note that the about: operator isn’t directly supported (you’ll need to use context.annotations or other filter logic instead).

4. Debug the Raw Response #

Quickly debug by logging a sample tweet object from your about: query. Check if the full_text field exists at all. If it doesn’t, double-check for typos (like tweetmode instead of tweet_mode) or confirm the parameter is being passed correctly to the API.

内容的提问来源于stack exchange，提问作者ChronicLogic