# oEmbed + Embed.ly

**URL:** <https://meta.discourse.org/t/oembed-embed-ly/47275>\
**Category:** Development\
**Created:** [14.Июль.2016 05:44:44 UTC](https://meta.discourse.org/t/oembed-embed-ly/47275 "2016-07-14T05:44:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![shri](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/shri/32/197750_2.png) [@shri](https://meta.discourse.org/u/shri)\
**Post date:** [14.Июль.2016 05:55:45 UTC](https://meta.discourse.org/t/oembed-embed-ly/47275/3 "2016-07-14T05:55:45Z")

</div>

> [@codinghorror](#):
>
> Not particularly good timing if you look at 1.7 in #releases.
> 
> We view this as a core competency so, as with any core competency, we would never outsource it.

Just saw that. Thanks.

No clue how you’re going to do this and what the end result would look like and for sure don’t want to tread on core features. I hope you do consider an approach which may allow a developer to override the built in onebox. 🙂

I actually do want to go further and bring in some tagging / entity and term extraction using some services like alchemyapi / semantria / diffbot into the links posted on this forum that I’m looking at developing, so figured this sort of plugin would be a good start for me to learn ruby / discourse at the same time.

---

_[View the full topic](https://meta.discourse.org/t/oembed-embed-ly/47275)._