2 ms·
Demos are now at the bottom of the post. Thanks
by screeley 16y ago
Demos are now at the bottom of the post. Thanks
- orblivion 16y agoThey should make a "what is this?" link on the front page, instead of people having to guess "API". I don't do much front end web development, so I'm not 100% sure I get the point, let me know if I get this correctly: Problem 1: You want to embed things from different sites. You have to learn each of their APIs. Come oembed, there's just one that all participants agree on. whateversite.com/oembed/url=$url&otherparams=stuff (where $url is within whateversite.com) which saves a lot of code and debugging efforts. Problem 2: You still have to send requests for embedding for a.com to a.com, and so forth. Come embedly, you can send all your requests to the same place, embed.ly/url=$url Thing is, Problem 2 seems trivial compared to Problem 1. oembed seems to do almost everything I'd want. I'm already testing if a given link is in embed.ly's list, right? I have the link I want to embed, I'm sending it to embedly. I might as well parse out the domain, add the oembed path, and send it to the source.
- arthurgibson 16y agoWe are working on better ways to present it, we would definitely welcome some suggestions on how to make it clearer, support@embed.ly. re: problem 2, some sites that use us do a mix of calling the source and embed.ly, we generally are faster on subsequent calls to the same url and also we support sites that don't roll their own.