推特API部分参数过滤规则

约定不等于承诺〃 2021-09-22 16:38 531阅读 0赞

## 1.实时推文 ##

[https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/basic-stream-parameters][https_developer.twitter.com_en_docs_tweets_filter-realtime_guides_basic-stream-parameters]

### track ###

A comma-separated list of phrases which will be used to determine what Tweets will be delivered on the stream. A phrase may be one or more terms separated by spaces, and a phrase will match if all of the terms in the phrase are present in the Tweet, regardless of order and ignoring case. **By this model, you can think of commas as logical ORs, while spaces are equivalent to logical ANDs** (e.g. ‘the twitter’ is the AND twitter, and ‘the,twitter’ is the OR twitter).（逗号可以视为‘或’，空格可以视为‘与’）

The text of the Tweet and some entity fields are considered for matches. Specifically, the text attribute of the Tweet, expanded\_url and display\_url for links and media, text for hashtags, and screen\_name for user mentions are checked for matches.

Each phrase must be between 1 and 60 bytes, inclusive.

Exact matching of phrases (equivalent to quoted phrases in most search engines) is not supported.

Punctuation and special characters will be considered part of the term they are adjacent to. In this sense, “hello.” is a different track term than “hello”. However, matches will ignore punctuation present in the Tweet. So “hello” will match both “hello world” and “my brother says hello.” Note that punctuation is not considered to be part of a \#hashtag or @mention, so a track term containing punctuation will not match either \#hashtags or @mentions.

UTF-8 characters will match exactly, even in cases where an “equivalent” ASCII character exists. For example, “touché” will not match a Tweet containing “touche”.

Non-space separated languages, such as CJK are currently unsupported.

URLs are considered words for the purposes of matches which means that the entire domain and path must be included in the track query for a Tweet containing an URL to match. Note that display\_url does not contain a protocol, so this is not required to perform a match.

Twitter currently canonicalizes the domain “www.example.com” to “example.com” before the match is performed, so omit the “www” from URL track terms.

Finally, to address a common use case where you may want to track all mentions of a particular domain name (i.e., regardless of subdomain or path), you should use “example com” as the track parameter for “example.com” (notice the lack of period between “example” and “com” in the track parameter). This will be over-inclusive, so make sure to do additional pattern-matching in your code. See the table below for more examples related to this issue.

Track examples:

<table> 
 <tbody> 
  <tr> 
   <td>Parameter value</td> 
   <td>Will match...</td> 
   <td>Will not match...</td> 
  </tr> 
  <tr> 
   <td>Twitter</td> 
   <td> <p>TWITTERtwitter “Twitter” twitter. #twitter @twitter&nbsp;<a href="http://twitter.com/" rel="nofollow">http://twitter.com</a></p> </td> 
   <td> <p>TwitterTracker#newtwitter</p> </td> 
  </tr> 
  <tr> 
   <td>Twitter’s</td> 
   <td>I like Twitter’s new design</td> 
   <td>Someday I’d like to visit @Twitter’s office</td> 
  </tr> 
  <tr> 
   <td>twitter api,twitter streaming</td> 
   <td> <p>The Twitter API is awesomeThe twitter streaming service is fast Twitter has a streaming API</p> </td> 
   <td>I’m new to Twitter</td> 
  </tr> 
  <tr> 
   <td>example.com</td> 
   <td>Someday I will visit example.com</td> 
   <td>There is no example.com/foobarbaz</td> 
  </tr> 
  <tr> 
   <td>example.com/foobarbaz</td> 
   <td> <p>example.com/foobarbazwww.example.com/foobarbaz</p> </td> 
   <td>example.com</td> 
  </tr> 
  <tr> 
   <td>www.example.com/foobarbaz</td> 
   <td>&nbsp;</td> 
   <td>www.example.com/foobarbaz</td> 
  </tr> 
  <tr> 
   <td>example com</td> 
   <td> <p>example.comwww.example.com foo.example.com foo.example.com/bar I hope my startup isn’t merely another example of a dot com boom!</p> </td> 
   <td>&nbsp;</td> 
  </tr> 
 </tbody> 
</table>

## 2.人的历史推文 ##

[https://developer.twitter.com/en/docs/tweets/timelines/api-reference/get-statuses-user\_timeline.html][https_developer.twitter.com_en_docs_tweets_timelines_api-reference_get-statuses-user_timeline.html]

## Parameters ##

<table> 
 <tbody> 
  <tr> 
   <td>Name</td> 
   <td>Required</td> 
   <td>Description</td> 
   <td>Default Value</td> 
   <td>Example</td> 
  </tr> 
  <tr> 
   <td>user_id</td> 
   <td>optional</td> 
   <td>The ID of the user for whom to return results.</td> 
   <td>&nbsp;</td> 
   <td><em>12345</em></td> 
  </tr> 
  <tr> 
   <td>screen_name</td> 
   <td>optional</td> 
   <td>The screen name of the user for whom to return results.</td> 
   <td>&nbsp;</td> 
   <td><em>noradio</em></td> 
  </tr> 
  <tr> 
   <td>since_id</td> 
   <td>optional</td> 
   <td>Returns results with an ID greater than (that is, more recent than) the specified ID. There are limits to the number of Tweets that can be accessed through the API. If the limit of Tweets has occured since the since_id, the since_id will be forced to the oldest ID available.</td> 
   <td>&nbsp;</td> 
   <td><em>12345</em></td> 
  </tr> 
  <tr> 
   <td>count</td> 
   <td>optional</td> 
   <td>Specifies the number of Tweets to try and retrieve, up to a maximum of 200 per distinct request. The value of&nbsp;<em>count</em>&nbsp;is best thought of as a limit to the number of Tweets to return because suspended or deleted content is removed after the count has been applied. We include retweets in the count, even if&nbsp;<em>include_rts</em>&nbsp;is not supplied. It is recommended you always send&nbsp;<em>include_rts=1</em>&nbsp;when using this API method.</td> 
   <td>&nbsp;</td> 
   <td>&nbsp;</td> 
  </tr> 
  <tr> 
   <td>max_id</td> 
   <td>optional</td> 
   <td>Returns results with an ID less than (that is, older than) or equal to the specified ID.</td> 
   <td>&nbsp;</td> 
   <td><em>54321</em></td> 
  </tr> 
  <tr> 
   <td>trim_user</td> 
   <td>optional</td> 
   <td>When set to either&nbsp;<em>true</em>&nbsp;,&nbsp;<em>t</em>&nbsp;or&nbsp;<em>1</em>&nbsp;, each Tweet returned in a timeline will include a user object including only the status authors numerical ID. Omit this parameter to receive the complete user object.</td> 
   <td>&nbsp;</td> 
   <td><em>true</em></td> 
  </tr> 
  <tr> 
   <td>exclude_replies</td> 
   <td>optional</td> 
   <td>This parameter will prevent replies from appearing in the returned timeline. Using&nbsp;<em>exclude_replies</em>&nbsp;with the&nbsp;<em>count</em>parameter will mean you will receive up-to count tweets — this is because the&nbsp;<em>count</em>&nbsp;parameter retrieves that many Tweets before filtering out retweets and replies.</td> 
   <td>&nbsp;</td> 
   <td><em>true</em></td> 
  </tr> 
  <tr> 
   <td>include_rts</td> 
   <td>optional</td> 
   <td>When set to&nbsp;<em>false</em>&nbsp;, the timeline will strip any native retweets (though they will still count toward both the maximal length of the timeline and the slice selected by the count parameter). Note: If you're using the trim_user parameter in conjunction with include_rts, the retweets will still contain a full user object.</td> 
   <td>&nbsp;</td> 
   <td><em>false</em></td> 
  </tr> 
 </tbody> 
</table>

## 3.关键词历史推文（搜索推文） ##

[https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators][https_developer.twitter.com_en_docs_tweets_search_guides_standard-operators]

此方法不支持使用逗号 “,” 标识关键词的或关系。

Limit your searches to 10 keywords and operators（搜索词数量限制在10个以内）

Standard search operators

The query can have operators that modify its behavior.  Below are examples that illustrate the available operators in standard search:

<table> 
 <tbody> 
  <tr> 
   <th>Operator</th> 
   <th>Finds Tweets...</th> 
  </tr> 
 </tbody> 
 <tbody> 
  <tr> 
   <td>watching now</td> 
   <td>containing both “watching” and “now”. This is the default operator.</td> 
  </tr> 
  <tr> 
   <td>“happy hour”</td> 
   <td>containing the exact phrase “happy hour”.</td> 
  </tr> 
  <tr> 
   <td><strong>love OR hate</strong></td> 
   <td>containing either “love” or “hate” (or both).</td> 
  </tr> 
  <tr> 
   <td>beer -root</td> 
   <td>containing “beer” but not “root”.</td> 
  </tr> 
  <tr> 
   <td>#haiku</td> 
   <td>containing the hashtag “haiku”.</td> 
  </tr> 
  <tr> 
   <td>from:interior</td> 
   <td>sent from Twitter account “interior”.</td> 
  </tr> 
  <tr> 
   <td>list:NASA/astronauts-in-space-now</td> 
   <td>sent from a Twitter account in the NASA list astronauts-in-space-now</td> 
  </tr> 
  <tr> 
   <td>to:NASA</td> 
   <td>a Tweet authored in reply to Twitter account “NASA”.</td> 
  </tr> 
  <tr> 
   <td>@NASA</td> 
   <td>mentioning Twitter account “NASA”.</td> 
  </tr> 
  <tr> 
   <td>politics filter:safe</td> 
   <td>containing “politics” with Tweets marked as potentially sensitive removed.</td> 
  </tr> 
  <tr> 
   <td>puppy filter:media</td> 
   <td>containing “puppy” and an image or video.</td> 
  </tr> 
  <tr> 
   <td>puppy -filter:retweets</td> 
   <td>containing “puppy”, filtering out retweets</td> 
  </tr> 
  <tr> 
   <td>puppy filter:native_video</td> 
   <td>containing “puppy” and an uploaded video, Amplify video, Periscope, or Vine.</td> 
  </tr> 
  <tr> 
   <td>puppy filter:periscope</td> 
   <td>containing “puppy” and a Periscope video URL.</td> 
  </tr> 
  <tr> 
   <td>puppy filter:vine</td> 
   <td>containing “puppy” and a Vine.</td> 
  </tr> 
  <tr> 
   <td>puppy filter:images</td> 
   <td>containing “puppy” and links identified as photos, including third parties such as Instagram.</td> 
  </tr> 
  <tr> 
   <td>puppy filter:twimg</td> 
   <td>containing “puppy” and a pic.twitter.com link representing one or more photos.</td> 
  </tr> 
  <tr> 
   <td>hilarious filter:links</td> 
   <td>containing “hilarious” and linking to URL.</td> 
  </tr> 
  <tr> 
   <td>puppy url:amazon</td> 
   <td>containing “puppy” and a URL with the word “amazon” anywhere within it.</td> 
  </tr> 
  <tr> 
   <td>superhero since:2015-12-21</td> 
   <td>containing “superhero” and sent since date “2015-12-21” (year-month-day).</td> 
  </tr> 
  <tr> 
   <td>puppy until:2015-12-21</td> 
   <td>containing “puppy” and sent before the date “2015-12-21”.</td> 
  </tr> 
  <tr> 
   <td>movie -scary :)</td> 
   <td>containing “movie”, but not “scary”, and with a positive attitude.</td> 
  </tr> 
  <tr> 
   <td>flight :(</td> 
   <td>containing “flight” and with a negative attitude.</td> 
  </tr> 
  <tr> 
   <td>traffic ?</td> 
   <td>containing “traffic” and asking a question.</td> 
  </tr> 
 </tbody> 
</table>

[https_developer.twitter.com_en_docs_tweets_filter-realtime_guides_basic-stream-parameters]: https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/basic-stream-parameters
[https_developer.twitter.com_en_docs_tweets_timelines_api-reference_get-statuses-user_timeline.html]: https://developer.twitter.com/en/docs/tweets/timelines/api-reference/get-statuses-user_timeline.html
[https_developer.twitter.com_en_docs_tweets_search_guides_standard-operators]: https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators