# Topic embedding needs some love

**URL:** <https://meta.discourse.org/t/topic-embedding-needs-some-love/262763>\
**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:** 2

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [April 24, 2023, 10:39pm UTC](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763/2 "2023-04-24T22:39:14Z")

</div>

> [@simon](#):
>
> 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](https://github.com/cantino/ruby-readability).

Yes, at this point we either move to something else that makes it slightly better or just change the embedding strategy into making the Show Full Post into a Read Full Post that is a simple link to the original post. It may be pointless fighting with all the possible embed problems in every website afterall.

---

_[View the full topic](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763)._