# Twitter Native Embed **URL:** https://meta.discourse.org/t/twitter-native-embed/261792 **Category:** Theme component **Created:** [April 15, 2023, 12:35pm UTC](https://meta.discourse.org/t/twitter-native-embed/261792 "2023-04-15T12:35:49Z") **Posts on this page:** 1 **Showing post:** 11
### Author: ![agemo](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@agemo](https://meta.discourse.org/u/agemo) #### Post date: [May 20, 2023, 11:27am UTC](https://meta.discourse.org/t/twitter-native-embed/261792/11 "2023-05-20T11:27:06Z")
On another point of the fragility of embeds as content after looking at the twitter imploding topic. made me think again of an old idea I had. **If embeds were able to generate a backup bitmap of the embed preview as part of the embed function, that would guard against photobucket outcomes and similar.** I have no idea how that could be coded up but I imagine it would work in principle much like the function that grabs the image of posted image link and is stored int eh native database, while I assume that is easier since it’s an already existing file out there on a server somewhere, it would act as I suppose the same as a custom screen grab function on the fly, that occurs when an embed is committed to a discourse post. Sites archiving a level of their content is helpful as the net ages, stuff does disappear form time to time. I’m going to suggest another feature along these lines too [here](https://meta.discourse.org/t/auto-archive-content/265632) --- _[View the full topic](https://meta.discourse.org/t/twitter-native-embed/261792)._