Use version 1.1 for Twitter.com oEmbed
|Reported by:||kovshenin||Owned by:|
|Cc:||kovshenin, dromsey@…, ipstenu@…, bananastalktome@…|
This sounds like a no-brainer, however one of the biggest changes between the two versions is the authentication model. Version 1.1 does not support unauthenticated requests. This means that we can no longer anonymously query the oembed endpoint.
I'm not sure we want to build an OAuth client into Core specifically for this and have users go through an authentication process before being able to embed tweets. Another option is to construct the embedded tweets manually without querying Twitter's API.
This should also fix most of the "tweets won't embed" problems people are having on shared hosts, since unauthenticated requests in v1 are rate limited by IP.