oohembed - Project Hosting on Google Code

Earlier this year Sep 16, 2009 issue 7 (YouTube embed doesn't respect maxwidth and maxheight) commented on by damian.janowski - GET http://oohembed.com/oohembed/?maxwidth=300&maxheight=250&format=json&url=http%3A//www.youtube.com/watch%3Fv%3DI_B8H956-rg&callback= { "title": "Nightingale - Yanni", "html": "<embed src='http://www.youtube.com/v/I_B8H956-rg&fs=1' allowfullscreen='true' type='application/x-shockwave-flash' wmode='transparent' width='300' height='250'></embed>", "author_name": "carrie820", "height": 250, "thumbnail_width": 120, "width": 300, "version": "1.0", "author_url": "http://www.youtube.com/user/carrie820", "provider_name": "Youtube", "thumbnail_url": "http://i.ytimg.com/vi/I_B8H956-rg/1.jpg", "type": "video", "thumbnail_height": 90 } GET http://oohembed.com/oohembed/?maxwidth=300&maxheight=250&format=json&url=http%3A//www.youtube.com/watch%3Fv%3DI_B8H956-rg&callback= { "title": "Nightingale - Yanni", "html": "<embed src='http://www.youtube.com/v/I_B8H956-rg&fs=1' allowfullscreen='true' type='application/x-shockwave-flash' wmode='transparent' width='300' height='250'></embed>", "author_name": "carrie820", "height": 250, "thumbnail_width": 120, "width": 300, "version": "1.0", "author_url": "http://www.youtube.com/user/carrie820", "provider_name": "Youtube", "thumbnail_url": "http://i.ytimg.com/vi/I_B8H956-rg/1.jpg", "type": "video", "thumbnail_height": 90 } Sep 16, 2009 issue 7 (YouTube embed doesn't respect maxwidth and maxheight) commented on by deepak.sarda - Can you post a sample request & expected response here? Can you post a sample request & expected response here? Sep 16, 2009 issue 7 (YouTube embed doesn't respect maxwidth and maxheight) commented on by damian.janowski - Thank you for your reply. I understand the rationale, but in YouTube's case it's possible to assign arbitrary dimensions to the <object> embed. So one could simply assign width=maxWidth and height=maxHeight and everything will work. Apparently this works very well and is very easy to implement. I don't know much Python but I can get a coworker to submit a patch if you agree to apply. Thank you again. Thank you for your reply. I understand the rationale, but in YouTube's case it's possible to assign arbitrary dimensions to the <object> embed. So one could simply assign width=maxWidth and height=maxHeight and everything will work. Apparently this works very well and is very easy to implement. I don't know much Python but I can get a coworker to submit a patch if you agree to apply. Thank you again. Sep 15, 2009 issue 7 (YouTube embed doesn't respect maxwidth and maxheight) Status changed by deepak.sarda - This is a known issue. Max width/height are not supported by oohembed for situations where the site in question isn't an oembed provider. As a middle-man, there's no reliable way for oohembed to determine how to constrain the resulting code in size. However, Youtube itself is testing oembed support and pretty soon, once they go live as oembed providers, I'll switch to using their endpoint. As a side-effect of that, max width/height will be automatically supported. Hope I was clear in this explanation! Status: WontFix This is a known issue. Max width/height are not supported by oohembed for situations where the site in question isn't an oembed provider. As a middle-man, there's no reliable way for oohembed to determine how to constrain the resulting code in size. However, Youtube itself is testing oembed support and pretty soon, once they go live as oembed providers, I'll switch to using their endpoint. As a side-effect of that, max width/height will be automatically supported. Hope I was clear in this explanation! Status: WontFix Sep 15, 2009 issue 7 (YouTube embed doesn't respect maxwidth and maxheight) reported by damian.janowski - Take, for example: http://oohembed.com/oohembed/?maxwidth=300&format=json&url=http%3A//www.youtube.com/watch%3Fv%3DI_B8H956-rg&callback= The resulting embed does not respect the maxwidth parameter. YouTube support arbitrary widths and heights on the <object>. Take, for example: http://oohembed.com/oohembed/?maxwidth=300&format=json&url=http%3A//www.youtube.com/watch%3Fv%3DI_B8H956-rg&callback= The resulting embed does not respect the maxwidth parameter. YouTube support arbitrary widths and heights on the <object>. Sep 05, 2009 2 new revisions pushed by deepak.sarda - Revision 6c525cd85b:Tighten the LiveJournal regex Revision c1ccc61245:New XKCD comic photo provider Revision 6c525cd85b:Tighten the LiveJournal regex Revision c1ccc61245:New XKCD comic photo provider Sep 04, 2009 issue 4 (Wordpress responses are incorrectly escaped) commented on by deepak.sarda - >> the title is text - not HTML, so it should not have HTML entities in it. So out of the context of HTML, who's to say that – is a HTML entity and not just funny looking text? Why are you assuming that oembed responses will be used exclusively in the context of rendering HTML documents? In any case, the HTML spec itself says that TITLE should be text but entities are allowed. Further, how do you propose handling cases like this? Should I just strip the entities out? That may actually leave the title meaningless. Or should I maintain some kind of conversion table and try converting every entity encountered into suitable unicode? I still think you should just take the suggestion in the link I provided in the previous comment. If you want to discuss this further, please bring it up in the oembed list. >> the title is text - not HTML, so it should not have HTML entities in it. So out of the context of HTML, who's to say that – is a HTML entity and not just funny looking text? Why are you assuming that oembed responses will be used exclusively in the context of rendering HTML documents? In any case, the HTML spec itself says that TITLE should be text but entities are allowed. Further, how do you propose handling cases like this? Should I just strip the entities out? That may actually leave the title meaningless. Or should I maintain some kind of conversion table and try converting every entity encountered into suitable unicode? I still think you should just take the suggestion in the link I provided in the previous comment. If you want to discuss this further, please bring it up in the oembed list. Sep 02, 2009 Revision a9374d6abb (Added Yfrog.com support.) pushed by harish.mallipeddi - Added Yfrog.com support. Added Yfrog.com support. Aug 31, 2009 issue 6 ([Feat Req] Support for yfrog, pikchur) changed by deepak.sarda - Status: Started Owner: harish.mallipeddi Status: Started Owner: harish.mallipeddi Aug 31, 2009 Revision 97daa99eec (Updated Changelog for chocochip release) pushed by deepak.sarda - Updated Changelog for chocochip release Updated Changelog for chocochip release Aug 21, 2009 Revision ef78a28863 (New Scribd provider. Fixed bliptv blooper) pushed by deepak.sarda - New Scribd provider. Fixed bliptv blooper New Scribd provider. Fixed bliptv blooper Aug 20, 2009 issue 4 (Wordpress responses are incorrectly escaped) commented on by candr...@integralblue.com - I disagree with your assessment. According to the spec at http://www.oembed.com the title is text - not HTML, so it should not have HTML entities in it. I believe the proper, specification compliant solution is for the provider (oohembed) to send only text, so in this case, you should be converting those html entities to regular characters in oohembed. I disagree with your assessment. According to the spec at http://www.oembed.com the title is text - not HTML, so it should not have HTML entities in it. I believe the proper, specification compliant solution is for the provider (oohembed) to send only text, so in this case, you should be converting those html entities to regular characters in oohembed. Aug 20, 2009 Revision 41f1ff59c6 (New crossdomain.xml policy file) pushed by deepak.sarda - New crossdomain.xml policy file New crossdomain.xml policy file Aug 20, 2009 issue 3 (Upgrade to SlideShare's v2 API) Labels changed by deepak.sarda - Labels: Milestone-Chocochip Labels: Milestone-Chocochip Aug 20, 2009 issue 5 (some metacafe urls return bad responses) changed by deepak.sarda - Fixed in r211a51e81d Status: Fixed Labels: Milestone-Chocochip Fixed in r211a51e81d Status: Fixed Labels: Milestone-Chocochip Aug 20, 2009 2 new revisions pushed by deepak.sarda - Revision 211a51e81d:Fix #5 - metacafe url parsing Revision 1c082d4b15:fixed couple of log lines in wordpress provider Revision 211a51e81d:Fix #5 - metacafe url parsing Revision 1c082d4b15:fixed couple of log lines in wordpress provider Aug 20, 2009 issue 4 (Wordpress responses are incorrectly escaped) Status changed by deepak.sarda - I don't think this is a oohembed bug. The original page uses HTML entities in the title element. The oembed response from oohembed carries those html entities as-is. I thing the problem on the identi.ca page is that you aren't rendering those entities correctly. See this for what I mean: http://blog.rebeccamurphey.com/2007/12/19/html- entities-from-ajax-into-input-fields-using-jquery/ Status: Invalid I don't think this is a oohembed bug. The original page uses HTML entities in the title element. The oembed response from oohembed carries those html entities as-is. I thing the problem on the identi.ca page is that you aren't rendering those entities correctly. See this for what I mean: http://blog.rebeccamurphey.com/2007/12/19/html- entities-from-ajax-into-input-fields-using-jquery/ Status: Invalid Aug 19, 2009 issue 5 (some metacafe urls return bad responses) Status changed by deepak.sarda - Status: Started Status: Started Aug 19, 2009 issue 6 ([Feat Req] Support for yfrog, pikchur) changed by deepak.sarda - Status: Accepted Labels: Type-Enhancement −Type-Defect Status: Accepted Labels: Type-Enhancement −Type-Defect Aug 19, 2009 issue 6 ([Feat Req] Support for yfrog, pikchur) reported by steveivy - Requesting support for other image sites oft-used by twitter clients, including yfrog and pikchur. Requesting support for other image sites oft-used by twitter clients, including yfrog and pikchur. Aug 12, 2009 issue 5 (some metacafe urls return bad responses) reported by jamesbellenger - What steps will reproduce the problem? 1. The front page of metacafe has some videos with more exotic urls than are standard. This one, for example: http://www.metacafe.com/watch/cb- 4wyzfz4L9Av3PzI8BTmhMvt0JSNXTc4G/leadbetters_tips_posture/ 2. I'm using the above url in this request: http://oohembed.com/oohembed/? format=json&url=http%3A%2F%2Fwww.metacafe.com%2Fwatch%2Fcb- 1HLReZ5qjkgIn6WvL0_IAruqth9Ki2Tx%2Fthe_amazing_race_14_phil_rides_across_am erica_highlights_season_14%2F What is the expected output? What do you see instead? I expect a json response, but am getting a 404 instead: HTTP/1.1 404 Not Found Cache-Control: no-cache Content-Type: application/json Expires: Fri, 01 Jan 1990 00:00:00 GMT Date: Wed, 12 Aug 2009 16:43:33 GMT Server: Google Frontend Transfer-Encoding: chunked Could not determine suitable representation for queried URL What steps will reproduce the problem? 1. The front page of metacafe has some videos with more exotic urls than are standard. This one, for example: http://www.metacafe.com/watch/cb- 4wyzfz4L9Av3PzI8BTmhMvt0JSNXTc4G/leadbetters_tips_posture/ 2. I'm using the above url in this request: http://oohembed.com/oohembed/? format=json&url=http%3A%2F%2Fwww.metacafe.com%2Fwatch%2Fcb- 1HLReZ5qjkgIn6WvL0_IAruqth9Ki2Tx%2Fthe_amazing_race_14_phil_rides_across_am erica_highlights_season_14%2F What is the expected output? What do you see instead? I expect a json response, but am getting a 404 instead: HTTP/1.1 404 Not Found Cache-Control: no-cache Content-Type: application/json Expires: Fri, 01 Jan 1990 00:00:00 GMT Date: Wed, 12 Aug 2009 16:43:33 GMT Server: Google Frontend Transfer-Encoding: chunked Could not determine suitable representation for queried URL Aug 05, 2009 2 new revisions pushed by deepak.sarda - Revision 5df1d0f9a0:new blip.tv provider Revision 0a5606945d:New phodroid.com provider Revision 5df1d0f9a0:new blip.tv provider Revision 0a5606945d:New phodroid.com provider Aug 03, 2009 issue 4 (Wordpress responses are incorrectly escaped) commented on by candr...@integralblue.com - BTW - here's the laconica ticket that caused me to discover this problem: http://laconi.ca/trac/ticket/1761 BTW - here's the laconica ticket that caused me to discover this problem: http://laconi.ca/trac/ticket/1761 Aug 03, 2009 issue 4 (Wordpress responses are incorrectly escaped) reported by candr...@integralblue.com - It appears that oohembed's Wordpress.com responses are double escaped (or something). Go to http://identi.ca/notice/7446621 and notice how the title is wrong (it shows as "401 – What’s On Earth Tonight? « Strange Maps"). Look at the JSON response at http://www.oohembed.com/oohembed/?url=http://strangemaps.wordpress.com/2009/07/23/401-whats-on-earth-tonight/ it seems that the title is incorrect. It appears that oohembed's Wordpress.com responses are double escaped (or something). Go to http://identi.ca/notice/7446621 and notice how the title is wrong (it shows as "401 – What’s On Earth Tonight? « Strange Maps"). Look at the JSON response at http://www.oohembed.com/oohembed/?url=http://strangemaps.wordpress.com/2009/07/23/401-whats-on-earth-tonight/ it seems that the title is incorrect. Jul 27, 2009 chocochip Wiki page commented on by candr...@integralblue.com - laconica is an oEmbed provider as of 0.8.1 (which should be released soon) and it publishes descriptors. So you shouldn't need to do anything to support it. laconica is an oEmbed provider as of 0.8.1 (which should be released soon) and it publishes descriptors. So you shouldn't need to do anything to support it. Jul 27, 2009 Revision 56a859e37c (HTTP Cache headers) pushed by deepak.sarda - HTTP Cache headers HTTP Cache headers Jul 26, 2009 issue 3 (Upgrade to SlideShare's v2 API) commented on by deepak.sarda - Hi Ryan. Just created a [wiki page][1] that lists the stuff I plan to do for this release. Hopefully, I'll switch oohembed.com to chocochip within the next week or so. [1]: http://code.google.com/p/oohembed/wiki/chocochip Hi Ryan. Just created a [wiki page][1] that lists the stuff I plan to do for this release. Hopefully, I'll switch oohembed.com to chocochip within the next week or so. [1]: http://code.google.com/p/oohembed/wiki/chocochip Jul 26, 2009 issue 3 (Upgrade to SlideShare's v2 API) commented on by ryan.mcgeary - Deepak, Works great. Thanks! When do you expect the "production" side of things to take advantage of this new feature and your other refactors? Deepak, Works great. Thanks! When do you expect the "production" side of things to take advantage of this new feature and your other refactors? Jul 26, 2009 issue 3 (Upgrade to SlideShare's v2 API) Status changed by deepak.sarda - I've applied this path to the main code line. You can test it out at: http://chocochip.latest.oohembed.appspot.com/ Status: Fixed I've applied this path to the main code line. You can test it out at: http://chocochip.latest.oohembed.appspot.com/ Status: Fixed Jul 26, 2009 3 new revisions pushed by deepak.sarda - Revision 10ae0ea6a4:Cache responses in memcache Revision d4f78cd177:New dailymotion provider Revision 12f427d7ad:Update Slideshare provider to v2 of upstream api Revision 10ae0ea6a4:Cache responses in memcache Revision d4f78cd177:New dailymotion provider Revision 12f427d7ad:Update Slideshare provider to v2 of upstream api Jul 25, 2009 Revision 19ab93e119 (Refactoring for better error propagation to client) pushed by deepak.sarda - Refactoring for better error propagation to client Refactoring for better error propagation to client Jul 21, 2009 issue 3 (Upgrade to SlideShare's v2 API) changed by deepak.sarda - Thanks for the info & the patch. I am currently doing some refactoring of the oohembed code and will hopefully have a new beta version live this weekend (famous last words!) I'll check the patch and decide whether to merge it with the current version or wait till I finish the refactoring and merge it with that. Status: Accepted Owner: deepak.sarda Thanks for the info & the patch. I am currently doing some refactoring of the oohembed code and will hopefully have a new beta version live this weekend (famous last words!) I'll check the patch and decide whether to merge it with the current version or wait till I finish the refactoring and merge it with that. Status: Accepted Owner: deepak.sarda Jul 21, 2009 issue 3 (Upgrade to SlideShare's v2 API) reported by ryan.mcgeary - SlideShare now support documents and spreadsheets that utilize a new format for the embedded code. v1 of the SlideShare API (using get_slideshow_info) does not output the correct embedded html code for these kinds of documents. Here is an example SlideShare document that does not behave well with the current version of oohEmbed: http://www.slideshare.net/CrystalTecheSolutions/how-dry-cleaning-works v2 of the SlideShare API does output the correct embedded code. Please upgrade oohEmbed to use the SlideShare v2 API. Here is documentation on the working get_slideshow API call in v2: http://www.slideshare.net/developers/documentation/v2#get_slideshow Attached is a cursory patch to upgrade the API. The changes are pretty trivial, but my lack of python and app engine experience kept me from fully testing it. Hopefully, it gets you started if not takes you the whole way. SlideShare now support documents and spreadsheets that utilize a new format for the embedded code. v1 of the SlideShare API (using get_slideshow_info) does not output the correct embedded html code for these kinds of documents. Here is an example SlideShare document that does not behave well with the current version of oohEmbed: http://www.slideshare.net/CrystalTecheSolutions/how-dry-cleaning-works v2 of the SlideShare API does output the correct embedded code. Please upgrade oohEmbed to use the SlideShare v2 API. Here is documentation on the working get_slideshow API call in v2: http://www.slideshare.net/developers/documentation/v2#get_slideshow Attached is a cursory patch to upgrade the API. The changes are pretty trivial, but my lack of python and app engine experience kept me from fully testing it. Hopefully, it gets you started if not takes you the whole way. Jul 17, 2009 Revision ae09c1e0df (Initial repo conversion to mercurial) pushed by deepak.sarda - Initial repo conversion to mercurial Initial repo conversion to mercurial Jun 07, 2009 issue 2 (Youtube response no longer includes width and height) commented on by h...@winkwaves.com - Confirmed that the oohembed service works fine again for Youtube. Thanks for fixing! Confirmed that the oohembed service works fine again for Youtube. Thanks for fixing! Jun 06, 2009 issue 2 (Youtube response no longer includes width and height) Status changed by deepak.sarda - Fixed in r14 Status: Fixed Fixed in r14 Status: Fixed Jun 06, 2009 r14 (Fix #2. Added missing width, height elements to Youtube prov...) committed by deepak.sarda - Fix #2. Added missing width, height elements to Youtube provider. Added title, author and thumbnail parameters to Metacafe provider. Fix #2. Added missing width, height elements to Youtube provider. Added title, author and thumbnail parameters to Metacafe provider. May 31, 2009 issue 2 (Youtube response no longer includes width and height) Status changed by deepak.sarda - Indeed - the width & height went missing! Will fix it ASAP. Status: Accepted Indeed - the width & height went missing! Will fix it ASAP. Status: Accepted May 29, 2009 issue 2 (Youtube response no longer includes width and height) reported by h...@winkwaves.com - It looks like a recent change to the service no longer includes the width and height parameters of the embeddeable object in the json response. The width and height are encoded in the html field, but they used to be available in the json response as well. As far as I understand the oembed specification the width and height are required fields for a video embed. It looks like a recent change to the service no longer includes the width and height parameters of the embeddeable object in the json response. The width and height are encoded in the html field, but they used to be available in the json response as well. As far as I understand the oembed specification the width and height are required fields for a video embed. May 10, 2009 r13 (Disable IMDB provider since clearspring widget is gone. Need...) committed by deepak.sarda - Disable IMDB provider since clearspring widget is gone. Need to implement it differently. Disable IMDB provider since clearspring widget is gone. Need to implement it differently. May 10, 2009 r12 (More data returned in Youtube provider using GData feed. Rem...) committed by deepak.sarda - More data returned in Youtube provider using GData feed. Removed Pownce provider. Updated Consumers section. More data returned in Youtube provider using GData feed. Removed Pownce provider. Updated Consumers section. May 10, 2009 r11 (New LiveJournal userpic provider) committed by deepak.sarda - New LiveJournal userpic provider New LiveJournal userpic provider Mar 31, 2009 r10 (Homepage updates to Consumers list. Added Ars Technica & jqu...) committed by deepak.sarda - Homepage updates to Consumers list. Added Ars Technica & jquery-oembed links Homepage updates to Consumers list. Added Ars Technica & jquery-oembed links Mar 02, 2009 r9 (Homepage update) committed by deepak.sarda - Homepage update Homepage update Mar 01, 2009 r8 (New TwitPic.com photo provider) committed by deepak.sarda - New TwitPic.com photo provider New TwitPic.com photo provider Feb 07, 2009 r7 (Server jsonp callback requests with text/javascript mimetype) committed by deepak.sarda - Server jsonp callback requests with text/javascript mimetype Server jsonp callback requests with text/javascript mimetype Feb 02, 2009 r6 (Updated homepage changelog) committed by deepak.sarda - Updated homepage changelog Updated homepage changelog Feb 02, 2009 r5 (New provider for Daily Show with Jon Stewart clips) committed by deepak.sarda - New provider for Daily Show with Jon Stewart clips New provider for Daily Show with Jon Stewart clips Feb 02, 2009 r4 (New providers: 5min.com & nfb.ca) committed by deepak.sarda - New providers: 5min.com & nfb.ca New providers: 5min.com & nfb.ca Jan 15, 2009 issue 1 (Vimeo scheme URL is wrong) Status changed by deepak.sarda - Fixed in r3! Status: Fixed Fixed in r3! Status: Fixed

issue 3 (Upgrade to SlideShare's v2 API) reported by ryan.mcgeary - SlideShare now support documents and spreadsheets that utilize a new format for the embedded code. v1 of the SlideShare API (using get_slideshow_info) does not output the correct embedded html code for these kinds of documents. Here is an example SlideShare document that does not behave well with the current version of oohEmbed: http://www.slideshare.net/CrystalTecheSolutions/how-dry-cleaning-works v2 of the SlideShare API does output the correct embedded code. Please upgrade oohEmbed to use the SlideShare v2 API. Here is documentation on the working get_slideshow API call in v2: http://www.slideshare.net/developers/documentation/v2#get_slideshow Attached is a cursory patch to upgrade the API. The changes are pretty trivial, but my lack of python and app engine experience kept me from fully testing it. Hopefully, it gets you started if not takes you the whole way.

SlideShare now support documents and spreadsheets that utilize a new format for the embedded code. v1 of the SlideShare API (using get_slideshow_info) does not output the correct embedded html code for these kinds of documents. Here is an example SlideShare document that does not behave well with the current version of oohEmbed: http://www.slideshare.net/CrystalTecheSolutions/how-dry-cleaning-works v2 of the SlideShare API does output the correct embedded code. Please upgrade oohEmbed to use the SlideShare v2 API. Here is documentation on the working get_slideshow API call in v2: http://www.slideshare.net/developers/documentation/v2#get_slideshow Attached is a cursory patch to upgrade the API. The changes are pretty trivial, but my lack of python and app engine experience kept me from fully testing it. Hopefully, it gets you started if not takes you the whole way.

Earlier this year