# 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:** 8

<div class="post-metadata">

**Author:** ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)\
**Post date:** [November 2, 2023, 12:51am UTC](https://meta.discourse.org/t/topic-embedding-needs-some-love/262763/8 "2023-11-02T00:51:24Z")

</div>

Just bumping this, as I agree with @simon that this should be re-thought at some point.

> [@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

A fair chunk of support requests for the [WP Discourse](https://github.com/discourse/wp-discourse) plugin are actually readability crawling issues of some form or another.

> [@Falco](#):
>
> It may be pointless fighting with all the possible embed problems in every website after all.

I think that sums up my gut on this.

That said, I don’t have a great solution at the moment besides this.

> [@Falco](#):
>
> 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

But I’m keen to contribute to a better solution than the status quo, as it would reduce the [WP Discourse](https://github.com/discourse/wp-discourse) support workload.

---

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