fc42bebb47
Without `legacy.id_str`, reply URLs would be constructed with conversion IDs, resulting in: - wrong URLs: pointing to the first tweet in the conversion (thread) - multiple items with the same guid: each tweet in a conversion (thread) had the same URL and thus guid The bug was caused by the widely used temporary fix (legacy.id_str || legacy.conversation_id_str) after Twitter had upgraded their API. Thus, it is quite easy to fix it: Refill legacy.id_str using the rest_id that resides in the container of legacy. With it fixed, take a step further to include threads when excludeReplies=1 (simulating the behavior of Twitter Web/App). Signed-off-by: Rongrong <i@rong.moe> |
||
|---|---|---|
| .. | ||
| developer-api | ||
| web-api | ||
| api-fallback-common.js | ||
| collection.js | ||
| followings.js | ||
| keyword.js | ||
| likes.js | ||
| list.js | ||
| maintainer.js | ||
| media.js | ||
| radar.js | ||
| router.js | ||
| trends.js | ||
| tweet.js | ||
| user.js | ||
| utils.js | ||