# Understanding how embedding works on remote site **URL:** \ **Category:** Support\ **Created:** [4월 20, 2015, 10:22오후 UTC](https://meta.discourse.org/t/understanding-how-embedding-works-on-remote-site/27781 "2015-04-20T22:22:48Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![rhulse](https://avatars.discourse-cdn.com/v4/letter/r/91b2a8/32.png) [@rhulse](https://meta.discourse.org/u/rhulse)\ **Post date:** [4월 26, 2015, 2:17오전 UTC](https://meta.discourse.org/t/understanding-how-embedding-works-on-remote-site/27781/6 "2015-04-26T02:17:53Z")
Ah right, the penny has dropped now. Also, I did not have a _embed by username_ set, so I presume the system could not create the post. I can easily control the URL used - I have a field in the database called initial\_url which is the url that existed when the item was created (this is for Google Analytics). One thing I’d be interested in your thoughts around is embedding the same topic in more than one story. A good example of this use-case is [this radio programme series](http://www.radionz.co.nz/national/programmes/thiswayup/collections/sourdough). It is on sourdough and ran over many weeks. We might embed the forum in the first story, and then embed it in the second (and so on) so people can enter the discussion on any of the pages at any time. It would be quite cool if there was a mode ‘non-create or update mode’ where you can embed any topic on any page. This is something we’d use a fair amount as it allows you to seed a new story on the same topic with the existing discussion and avoids having many separate topics about essentially the same conversation. I am also going to add an RSS feed of stories we want topics for to our CMS so I can be explicit about the content that appears in the first post. RSS + arbitrary embed appear to do the golden path for us, but I’d be interested on hearing if there are other ways to do this. --- _[View the full topic](https://meta.discourse.org/t/understanding-how-embedding-works-on-remote-site/27781)._