Open lmeyerov opened 4 years ago
Twitter's API supports returning enriched URLs, such as following redirects and getting some page metadata: https://developer.twitter.com/en/docs/tweets/enrichments/overview/expanded-and-enhanced-urls
-- Our use of Twarc should try to include these and push as part of URLs to neo4j (tweet -> URL + ResolvedUrl -> Metadata)
-- If possible, in Twint too
-- Our own URL enrichments should only run if twitter doesn't already give us (and to augment what's left, e.g., post-redirect)
@bechbd just confirming, this is done already?
cc @bmorphism for twint
twint
Twitter's API supports returning enriched URLs, such as following redirects and getting some page metadata: https://developer.twitter.com/en/docs/tweets/enrichments/overview/expanded-and-enhanced-urls
-- Our use of Twarc should try to include these and push as part of URLs to neo4j (tweet -> URL + ResolvedUrl -> Metadata)
-- If possible, in Twint too
-- Our own URL enrichments should only run if twitter doesn't already give us (and to augment what's left, e.g., post-redirect)