[twitter-dev] Re: Streaming API time drifting problem and possible solutions
Thank everyone for the quick reply, I have implemented a downloading program which uses curl, and it is fast enough to avoid the time drift. -Larry On Jul 8, 5:00 pm, Pascal Jürgens lists.pascal.juerg...@googlemail.com wrote: Larry, moreover, I assume you checked I/O and CPU load. But even if that's not the issue, you should absolutely check if you have simplejson with c extension installed. The python included version is 1.9 which is decidedly slower than the new 2.x branch. You might see json decoding load drop by 50% or more. Pascal On Jul 8, 2010, at 17:31 , Larry Zhang wrote: Hi everyone, I have a program calling the statuses/sample method of a garden hose of the Streaming API, and I am experiencing the following problem: the timestamps of the tweets that I downloaded constantly drift behind real-time, the time drift keeps increasing until it reaches around 25 minutes, and then I get a timeout from the request, sleep for 5 seconds and reset the connection. The time drift is also reset to 0 when the connection is reset. One solution for this I have now is to proactively reset the connection more frequently, e.g., if I reconnect every 1 minute, the time drift I get will be at most 1 minute. But I am not sure whether this is allow by the API. So could anyone tell me if you have the same problem as mine or I am using the API in the wrong way. And is it OK to reset connection every minute? I am using Tweepy (http://github.com/joshthecoder/tweepy) as the library for accessing the Streaming API. Thanks a lot! -Larry
[twitter-dev] Streaming API time drifting problem and possible solutions
Hi everyone, I have a program calling the statuses/sample method of a garden hose of the Streaming API, and I am experiencing the following problem: the timestamps of the tweets that I downloaded constantly drift behind real-time, the time drift keeps increasing until it reaches around 25 minutes, and then I get a timeout from the request, sleep for 5 seconds and reset the connection. The time drift is also reset to 0 when the connection is reset. One solution for this I have now is to proactively reset the connection more frequently, e.g., if I reconnect every 1 minute, the time drift I get will be at most 1 minute. But I am not sure whether this is allow by the API. So could anyone tell me if you have the same problem as mine or I am using the API in the wrong way. And is it OK to reset connection every minute? I am using Tweepy (http://github.com/joshthecoder/tweepy) as the library for accessing the Streaming API. Thanks a lot! -Larry
[twitter-dev] Re: Twitter Platform blog post
That's how I read it as well, but there's certainly some gray area there. Some twitter clients just display an ad at the top of bottom of the app, those would seem to be ok. Some I've seen recently put things in the timeline that look exactly like tweets (except for a line at the bottom that says sponsored tweet or similar. Those would seem to be obviously NOT ok. But then there are apps that insert a graphical ad in the timeline (clearly not a tweet)... are those ok? I think Tweetie for OS X used to do this. On May 24, 11:27 am, Shannon Clark shannon.cl...@gmail.com wrote: I'm not at Twitter but I read the blog post as saying that ads around the Twitter timeline (as part of the UI of an application or website) are fine but ads IN the Twitter timeline (as paid tweets) are not. Shannon Sent from my iPhone On May 24, 2010, at 12:19 PM, Liz nwjersey...@gmail.com wrote: Ryan, It's confusing to me that Dick says there will be no third party ads (8th paragraph) but under Fostering Innovation, #2, he talks apps about selling ads. Does this decision do away with services like Sponsored Tweets? I appreciate such a thoughtful blog post (and hope there are more in the future) but what is absent is any language of partnership or collaboration. Twitter's goals are stated and basically, everyone else has to deal with the consequence. Also, the language of optimizing user experience. Can you tell me what is the basis of user experience testing that occurs at Twitter? Because there is no mechanism for users to offer feedback to Twitter about their experience. How do you know whether a development enhances user experience or not? It seems like Twitter does what they think is best, regardless of what the bulk of users might want. Thanks for any answers you can provide. Liz Pullen nwjer...@yahoo.com
[twitter-dev] Re: alert() in anywhere.js
I think throw() seems more appropriate. Firebug and WebKit-based browsers will work with console.log(). A javascript error for an undefined function would still be better than an alert(). Larry On May 19, 12:03 pm, nischalshetty nischalshett...@gmail.com wrote: One of us is crazy here. If I'm not wrong console.log belongs to firebug. Which means you will get a javascript error on ALL browsers which do not have firebug installed and running. -Nischal On May 19, 11:41 pm, Dan Webb d...@twitter.com wrote: On Wed, May 19, 2010 at 11:27 AM, Steve C st...@twitpic.com wrote: We just rolled out @anywhere yesterday and some of our users are experiencing similar issues. http://twitpic.com/1p00d6 We rolled out a fix at the weekend that we fixed all the browsers that we test under but there are obviously still some browsers getting the issue. I think we'll use console.info to display these message instead of an alert. We wanted to let developers know that they needed a clientID in the most noticable way but to avoid unintended annoyance of users we'll move to console.log. Thanks, -- Dan Webb Front-end Engineer, Platform d...@twitter.com / @danwrong +1 415 425 5631
[twitter-dev] Re: alert() in anywhere.js
Our site has been running @anywhere for over a week now without error. Yesterday my coworker was getting the alert(). He is running an older version of Firefox (3.0.8) on Ubuntu, so there might be another cause other than missing clientID or version? I still believe alert() is intrusive, especially for this case where it works fine except for this edge case. Instead of users complaining about broken hovercards, they are complaining about alert dialogs. Larry On May 14, 8:38 pm, Abraham Williams 4bra...@gmail.com wrote: Both of which are issues that will pretty much stop @Anywhere from working and need to be noticed as soon as possible at installation. Hiding them in console.log will make it more likely that @Anywhere will be installe improperly and the admins will only find out when users complain. Abraham On Fri, May 14, 2010 at 15:57, Larry la...@topsy.com wrote: I just came across a coworker's browser that triggered an alert() call from anywhere.js. While okay for development, the use of alert() is not friendly for production websites. Could these be converted console.log() or some other benign mechanism? Grepping through anywhere.js I found two instances of alert(): alert(To set up @anywhere, please provide a client ID); alert(No version matching +Z); Cheers Larry -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: alert() in anywhere.js
I can reliably reproduce this with Firefox 3.0.8 at the following url: http://cornsyrup.org/~larry/anywhere/index.html Error console is reporting S.get is not a function Larry On May 15, 11:31 am, Larry la...@topsy.com wrote: Our site has been running @anywhere for over a week now without error. Yesterday my coworker was getting the alert(). He is running an older version of Firefox (3.0.8) on Ubuntu, so there might be another cause other than missing clientID or version? I still believe alert() is intrusive, especially for this case where it works fine except for this edge case. Instead of users complaining about broken hovercards, they are complaining about alert dialogs. Larry On May 14, 8:38 pm, Abraham Williams 4bra...@gmail.com wrote: Both of which are issues that will pretty much stop @Anywhere from working and need to be noticed as soon as possible at installation. Hiding them in console.log will make it more likely that @Anywhere will be installe improperly and the admins will only find out when users complain. Abraham On Fri, May 14, 2010 at 15:57, Larry la...@topsy.com wrote: I just came across a coworker's browser that triggered an alert() call from anywhere.js. While okay for development, the use of alert() is not friendly for production websites. Could these be converted console.log() or some other benign mechanism? Grepping through anywhere.js I found two instances of alert(): alert(To set up @anywhere, please provide a client ID); alert(No version matching +Z); Cheers Larry -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: alert() in anywhere.js
Firefox 3.X is a supported browser for @anywhere and my example is properly configured, yet it triggered when it wasn't supposed to. This highlights my point of why alert() not a good choice for notification of incorrect installations. Instead maybe it should use throw(). That would be more useful to a developer and not intrusive to a user. Larry On May 15, 3:26 pm, Abraham Williams 4bra...@gmail.com wrote: I agree that @Anywhere should degrade gracefully when configured properly on unsupported platforms and not prompt incorrect alert()s. But I do think alert()s are probably the best way to notify developers of incorrect installations. Abraham On Sat, May 15, 2010 at 11:55, Larry la...@topsy.com wrote: I can reliably reproduce this with Firefox 3.0.8 at the following url: http://cornsyrup.org/~larry/anywhere/index.html Error console is reporting S.get is not a function Larry On May 15, 11:31 am, Larry la...@topsy.com wrote: Our site has been running @anywhere for over a week now without error. Yesterday my coworker was getting the alert(). He is running an older version of Firefox (3.0.8) on Ubuntu, so there might be another cause other than missing clientID or version? I still believe alert() is intrusive, especially for this case where it works fine except for this edge case. Instead of users complaining about broken hovercards, they are complaining about alert dialogs. Larry On May 14, 8:38 pm, Abraham Williams 4bra...@gmail.com wrote: Both of which are issues that will pretty much stop @Anywhere from working and need to be noticed as soon as possible at installation. Hiding them in console.log will make it more likely that @Anywhere will be installe improperly and the admins will only find out when users complain. Abraham On Fri, May 14, 2010 at 15:57, Larry la...@topsy.com wrote: I just came across a coworker's browser that triggered an alert() call from anywhere.js. While okay for development, the use of alert() is not friendly for production websites. Could these be converted console.log() or some other benign mechanism? Grepping through anywhere.js I found two instances of alert(): alert(To set up @anywhere, please provide a client ID); alert(No version matching +Z); Cheers Larry -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] alert() in anywhere.js
I just came across a coworker's browser that triggered an alert() call from anywhere.js. While okay for development, the use of alert() is not friendly for production websites. Could these be converted console.log() or some other benign mechanism? Grepping through anywhere.js I found two instances of alert(): alert(To set up @anywhere, please provide a client ID); alert(No version matching +Z); Cheers Larry
[twitter-dev] Re: 200 errors
I am seeing this as well on the search api, also sporadically. Where do I send the details you are requesting? On Aug 25, 7:18 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: I am seeing this error right now when doing a search. (FWIW: I'm using since_id) This is seriously messing things up! @jeffGreenberg @tweettronics Details: url:http://search.twitter.com/search.json?q=%23fail%20since%3A2009-08-19;... httpresponse = 200 returned text: !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN http://www.w3.org/ TR/1999/REC-html401-19991224/strict.dtd !-- !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN http://www.w3.org/TR/html4/strict.dtd; -- HTML HEAD META HTTP-EQUIV=Refresh CONTENT=0.1 META HTTP-EQUIV=Pragma CONTENT=no-cache META HTTP-EQUIV=Expires CONTENT=-1 TITLE/TITLE /HEAD BODYP/BODY /HTML
[twitter-dev] Re: Search API Limits lowered?
In addition to setting a unique user-agent, I believe it was requested that we set a referrer header that pointed back to a domain. On Tue, Aug 11, 2009 at 9:30 AM, David Fisher tib...@gmail.com wrote: While i haven't done scientific testing of this, I was able to run up to 3-4 instances of my search script prior at a time before it told me to enhance my calm. Now I'm barely able to run one without hitting the limit. I can put delays in my code to slow it down, but I'm wondering if this is just a symptom of the aftermath of the DDoS attack or something else? My server has a dedicated IP and no one else runs code from it, so it isn't other people on my IP hitting the Search API. Maybe I need to talk about Search API whitelisting... dave http://webecologyproject.org -- Larry Wright
[twitter-dev] Re: FW: Twitter is Suing me!!!
As others have pointed out, this isn't a lawsuit. That aside, Twitter announced some time ago that they were not comfortable with people using their name as part of the name of their product ( http://blog.twitter.com/2009/07/may-tweets-be-with-you.html) , so it seems odd that you would be surprised by this. Regardless, you'll get little sympathy from me. Your application encourages many of the behaviors most twitter users find annoying. The Twitter ecosystem is frankly better off without it. Larry Wright http://larrywright.me On Aug 11, 2009, at 9:48 PM, Dean Collins wrote: Any other developer being sued by Twitter today? If so give me a call – feel free to tweet out www.MyTwitterButler.com/I ’m_Being_Sued to anyone you want – looking forward to the press having a field day with this. Regards, Dean Collins d...@mytwitterbutler.com +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial).
[twitter-dev] Re: FW: Twitter is Suing me!!!
There's two different issues here: the name, and what it does. If it was just the name, that letter would likely just ask you to do that prior to continuing sales. The larger issue, it seems, is that the app does things that violate the TOS (and annoy Twitter users). Unless you change the application to not do those things, you can't sell it. Standard disclaimer: I'm not a lawyer, I've never even played one on tv, yada yada yada. On Tue, Aug 11, 2009 at 11:08 PM, Dean Collins d...@cognation.net wrote: It’s not that simple – if you read the letter they are telling me I have to stop selling the software entirely. www.MyTwitterButler.com/I’m_Being_Suedhttp://www.mytwitterbutler.com/I'm_Being_Sued Regards, Dean Collins d...@mytwitterbutler.comd...@mytwitterbutler.com?subject=i'm%20being%20Sued +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -- *From:* twitter-development-talk@googlegroups.com [mailto: twitter-development-t...@googlegroups.com] *On Behalf Of *EdPimentl *Sent:* Wednesday, August 12, 2009 12:06 AM *To:* twitter-development-talk@googlegroups.com *Subject:* [twitter-dev] Re: FW: Twitter is Suing me!!! Have you consider renaming your app to Tweetrobot , twtrbutler, tweeturk? They own the brand Twitter why not rename your service? -E Gpro.ws On Tue, Aug 11, 2009 at 11:56 PM, Dean Collins d...@cognation.net wrote: I'm glad you feel you can move on.I'm the one facing legal action!! (and yes I read the comment I'm not being suedI'm facing legal action) Does Twitter inc know that their lawyers are shutting down the third party developer community? (sorry I'm new to this and freaking out - never had a lawyer sue me like this) Regards, Dean Collins d...@mytwitterbutler.com +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -Original Message- From: twitter-development-talk@googlegroups.com [mailto: twitter-development-t...@googlegroups.com] On Behalf Of jim.renkel Sent: Tuesday, August 11, 2009 11:51 PM To: Twitter Development Talk Subject: [twitter-dev] Re: FW: Twitter is Suing me!!! An interesting implication is buried in all of this. FACT: http://apiwiki.twitter.com/Terms-of-Service states: Please give us a nod in your app, perhaps by including one of these stylish Powered by Twitter badges, which I read as If ya use the API you must acknowledge twitter. FACT: The letter from twitter's lawyers states: stop all use of ... the TWITTER mark, which I read as Ya can't use the word twitter in your application or on your website. IMPLICATION: No one can use the API !!! I guess we should all pack up and move on. Jim On Aug 11, 10:13 pm, Larry Wright larrywri...@gmail.com wrote: As others have pointed out, this isn't a lawsuit. That aside, Twitter announced some time ago that they were not comfortable with people using their name as part of the name of their product ( http://blog.twitter.com/2009/07/may-tweets-be-with-you.html) , so it seems odd that you would be surprised by this. Regardless, you'll get little sympathy from me. Your application encourages many of the behaviors most twitter users find annoying. The Twitter ecosystem is frankly better off without it. Larry Wrighthttp://larrywright.me On Aug 11, 2009, at 9:48 PM, Dean Collins wrote: Any other developer being sued by Twitter today? If so give me a call - feel free to tweet outwww.MyTwitterButler.com/I 'm_Being_Sued to anyone you want - looking forward to the press having a field day with this. Regards, Dean Collins d...@mytwitterbutler.com +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -- Larry Wright
[twitter-dev] Re: You have been rate limited. Enhance your calm.
You can use Wireshark or any other packet sniffer to determine whether your client is following redirects. I'm not sure what ruby twitter client you're using, but if it's John Nunemaker's, I believe it does follow redirects. Larry Wright/@larrywright On Fri, Aug 7, 2009 at 2:03 PM, David Fisher tib...@gmail.com wrote: I can't be sure if my client is following redirects. Probably not. I'm just using the Ruby Twitter Gem which haven't been updated for a month or so I think dave On Aug 7, 1:15 pm, lucasnicolato eternitya...@gmail.com wrote: im having the same problem. im just lucky my app is still in test. RT @twitter Due to defense measures some Twitter clients are unable to communicate with our API, and many users are unable to tweet via SMS. I think we can only wait for twitter to normalize de api. On 7 ago, 12:20, diddy david.barrowcl...@gmail.com wrote: Hi, I use the Twitter search api, e.g: - http://search.twitter.com/search.rss?q=iphone and I now get: - You have been rate limited. Enhance your calm. I rely on this for my application. Anything I can do to stop it? Thanks! -- Larry Wright
