# Topic embedding needs some love **URL:** \ **Category:** Feature\ **Created:** [April 24, 2023, 10:32pm UTC](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763 "2023-04-24T22:32:35Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\ **Post date:** [April 24, 2023, 10:32pm UTC](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763/1 "2023-04-24T22:32:36Z")
I was reminded of this today after clicking the “Show Full Post” button for [Introducing Discourse AI](https://meta.discourse.org/t/introducing-discourse-ai/262744). The full post that is displayed on Discourse is missing all images and many headings. Adding to the confusion, image captions are displayed, but without their associated images. It might be possible to fix the issue on Meta for its (Ghost?) blog by adjusting Meta’s `allowed embed selectors` site setting: [Configuring allowed embed selectors](https://meta.discourse.org/t/configure-the-allowed-embed-selectors-setting/134481). From past experience, I know that getting this setting can be a tricky process. If you try adjusting it, pay close attention to the results. Discourse has a lot of potential to function as a comment system for external posts, but to do a good job of this, clicking the “Show Full Post” button needs to reliably pull in all elements of the external post. I think the issue is that the Ruby Readability gem that’s used for parsing external posts isn’t intended for the job that Discourse is using it for. It’s also not being actively maintained: [GitHub - cantino/ruby-readability: Port of arc90's readability project to Ruby · GitHub](https://github.com/cantino/ruby-readability). --- _[View the full topic](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763)._