diff options
| author | Kazuki Yamaguchi <k@rhe.jp> | 2018-08-30 17:49:20 +0900 |
|---|---|---|
| committer | Kazuki Yamaguchi <k@rhe.jp> | 2018-08-31 10:03:35 +0900 |
| commit | fd8a5d04a47cfc30eb4ffac2db1f031a41bf7a01 (patch) | |
| tree | e1f148f8482930ee2cebed4296c1ed32c4d53a2e /README.txt | |
| parent | b0378cb2455072f8981143287ba373be458e2d63 (diff) | |
| download | twitter-event-stream-master.tar.gz | |
The Tweet object retrieved by the retired Streaming API and the Account
Activity follows "Compatibility with additional extended_tweet in
payload". However, the REST API still defaults to the "Compatibility"
mode which does not support >140 characters texts at all. Let's adjust
the response from the REST API to mimic "Compatibility with additional
extended_tweet in payload" mode.
Diffstat (limited to 'README.txt')
| -rw-r--r-- | README.txt | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -133,7 +133,12 @@ twitter-event-stream opens two endpoints for a client: :\r\n\r\n -twitter-event-stream uses "OAuth Echo"[3] to authenticate a client, meaning +In both endpoints, the Tweet object structure BASICALLY follows the +"Compatibility with additional extended_tweet in payload" mode[3]. Each Tweet +object has `extended_tweet` object containing `full_text` key. + + +twitter-event-stream uses "OAuth Echo"[4] to authenticate a client, meaning an application must provide the following HTTP headers: - `x-auth-service-provider` @@ -147,7 +152,8 @@ an application must provide the following HTTP headers: normally send when calling the account/verify_credentials API. [2] https://developer.twitter.com/en/docs/basics/authentication/overview/oauth-echo.html -[3] https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/guides/account-activity-data-objects +[3] https://developer.twitter.com/en/docs/tweets/tweet-updates.html +[4] https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/guides/account-activity-data-objects License ------- |