@earnjam @bph @redcrew Yeah, perhaps a core patch, however I have to believe that @helenhousandi & @markjaquith were intentional about not blanket respecting the provider’s `cache_age`. It begs the question, who should be in control of the caching, the provider or the consumer?

@earnjam @redcrew @bph Right, but what about the oEmbed cache expiration standard, that Twitter indicates they send? If the cache expires, and the Tweet(s) have been deleted at that point, my assumption is that you will end up with a refresh that is now just the link.

@earnjam @redcrew @bph It seems pretty clear from the Twitter Developer documentation that the oEmbeds are more than just “text” and there is a cache expiration they send so that can cause the oEmbed to go missing later also. developer.twitter.com/en/docs/twitte…

@earnjam @redcrew @bph A good example of oEmbed falling apart that is more clear is when you oEmbee a YouTube video. The WordPress site doesn’t have a local copy of that video. This is the problem I’m talking about solving. A way to “embed” essentially a copy of the Tweet.

@bph @earnjam @redcrew Ha, yeah I was just reading that one too. I think the piece to be clear about is that the embed code is cached, but that doesn’t mean the actual content is in post_meta. When the Page/Post is loaded the embed content is pulled from the provider.