4 ms·
Embedly is interesting, but this seems like yet another service that really ought to be a client-side Javascript library. I see no advantage to this being a se
by jluxenberg 16y ago
Embedly is interesting, but this seems like yet another service that really ought to be a client-side Javascript library. I see no advantage to this being a service, besides the fact that the client-side code can be a little thinner.
Besides, if the source was available, it would be trivial to set up your own "Embedly" endpoint, and reap all the benefits of thin client-side code while having control over your infrastructure.
- antrix 16y agoI've been running oohEmbed.com, a similar service, for more than two years now. The problem with doing this in client-side JS is that (a) the oEmbed spec doesn't specify json callbacks so oembed providers don't support callbacks making async stuff in the browser difficult; (b) dealing with SOAP APIs, html parsing, etc. are difficult to say the least within browsers. But if you really want to do this without relying on an external service, you can take the oohEmbed.com source (BSD licensed) and run it as your own 'private' Google App Engine app. oohEmbed.com itself is App Engine hosted.