Taylor, Firefox 4.01 on Windows Server 2003 and IE8 on Windows Server 2003 (I believe they are both fully utf-8 compatible) (using jQuery 1.3.2 js library, I would upgrade but I am stuck at it w/ other dependencies )
Can you not reproduce the error on the jsFiddle<http://jsfiddle.net/NBCGf/34/>? (I will test on my ubuntu laptop when I get home) As for the tweetid/url it is happening on multiple but I have http://search.twitter.com/search.json?q=from:LansdowneResort&rpp=1&callback=? <http://search.twitter.com/search.json?q=from:LansdowneResort&rpp=1&callback=?%20> hard-coded in the jsfiddle example and its showing error after a couple iterations. In any event, if you cannot, I am fine w/ the window.onerror error handling I have implemented and have it working in both browsers now and have implemented dom caching so as not to make too many requests. Update: I just tested in chrome and it threw search.json:1<http://search.twitter.com/search.json?q=from:TrumpSoHo&rpp=1&callback=jsonp1308002393614&_=1308002425423>Uncaught SyntaxError: Unexpected token ILLEGAL http://search.twitter.com/search.json?q=from:TrumpSoHo&rpp=1&callback=jsonp1308002393614&_=1308002425423 So I imagine maybe it is an OS/charset thing. Thanks //mh On Mon, Jun 13, 2011 at 5:20 PM, Taylor Singletary < [email protected]> wrote: > It would be very helpful if you could provide a specific Tweet ID that > is exhibiting this behavior -- the test case you're presenting is a bit > artificial. Do you know if the environment you're doing this consumption is > fully capable of understanding the UTF-8 character set? Tweets can contain > just about any UTF-8 character and your parsing should be prepared for > that. > > On a side note, executing a specific query against the Search API every six > seconds isn't the most efficient use of the API. Have you considered > increasing the time you wait to poll and using additional Search API feature > like since_id? > > @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor > Singletary > > > On Mon, Jun 13, 2011 at 12:49 PM, michael hazzard <[email protected] > > wrote: > >> Oh answers to #2 and #3 >> >> 2) I am polling the jsonp api every second in this test but it will be >> changed for production to like 6 seconds and cached after all 30 feeds are >> loaded >> >> 3) No, I haven't tried outside the browser since this is strictly a jsonp >> feed and I chose jsonp over server-side xml but now regretting a bit. >> >> //mh >> >> >> >> On Mon, Jun 13, 2011 at 3:43 PM, michael hazzard <[email protected] >> > wrote: >> >>> Taylor(); >>> >>> I took a pic of firebug here: >>> >>> https://docs.google.com/leaf?id=0B1lcI5OlKM2xNDczZDdmYTMtMjFjZi00Y2E2LWE4MTMtM2YyM2I5ZTM4Njhl&sort=name&layout=list&num=50 >>> >>> >>> It is similar to this case (I believe the same chars) >>> >>> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7567404004266db5?pli=1 >>> >>> It is reproducible on the jsfiddle url if you look at the error console >>> usually 10-20 iterations. >>> >>> http://jsfiddle.net/NBCGf/34/ >>> >>> (Note: I recently added window.onerror to get around it for now and >>> continue loading feeds.) >>> >>> Thanks, >>> //mh >>> >>> >>> On Mon, Jun 13, 2011 at 3:13 PM, Taylor Singletary < >>> [email protected]> wrote: >>> >>>> Do you have more details about the specific illegal character(s) you're >>>> receiving? How frequently are you polling the API? Have you tried >>>> reproducing your scenario outside of a browser-based environment? >>>> >>>> @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor >>>> Singletary >>>> >>>> >>>> >>>> On Mon, Jun 13, 2011 at 11:55 AM, miramardesign < >>>> [email protected]> wrote: >>>> >>>>> All browsers throw error "illegal character" in twitter jsonp feed >>>>> >>>>> http://jsfiddle.net/NBCGf/34/ >>>>> >>>>> Please advise, >>>>> //mh >>>>> >>>>> -- >>>>> Twitter developer documentation and resources: >>>>> https://dev.twitter.com/doc >>>>> API updates via Twitter: https://twitter.com/twitterapi >>>>> Issues/Enhancements Tracker: >>>>> https://code.google.com/p/twitter-api/issues/list >>>>> Change your membership to this group: >>>>> https://groups.google.com/forum/#!forum/twitter-development-talk >>>>> >>>> >>>> -- >>>> Twitter developer documentation and resources: >>>> https://dev.twitter.com/doc >>>> API updates via Twitter: https://twitter.com/twitterapi >>>> Issues/Enhancements Tracker: >>>> https://code.google.com/p/twitter-api/issues/list >>>> Change your membership to this group: >>>> https://groups.google.com/forum/#!forum/twitter-development-talk >>>> >>> >>> >>> >>> -- >>> Thank You, >>> >>> Michael Hazzard >>> (954) 247-4461 <https://www.google.com/voice#phones> >>> >>> >>> >> >> >> -- >> Thank You, >> >> Michael Hazzard >> (954) 247-4461 <https://www.google.com/voice#phones> >> >> >> -- >> Twitter developer documentation and resources: >> https://dev.twitter.com/doc >> API updates via Twitter: https://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> https://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> https://groups.google.com/forum/#!forum/twitter-development-talk >> > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Thank You, Michael Hazzard (954) 247-4461 <https://www.google.com/voice#phones> -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
