[twitter-dev] Re: Deleting a Retweeted Tweet
Now does this deletion occur recursively including retweets of retweets? Let's say Bob retweets John and Mike retweets Bob's retweets. Will Both John and Mike retweets be deleted if John original tweet is deleted or just Bob retweet? I'm not sure I like the idea of the delete of retweets if the original tweet is deleted. Unless there is a good reason for doing so (the tweet is spreading a bad link that causes harm, etc) the retweets should be treated as a regular tweet and left alone. Josh On Mon, Sep 21, 2009 at 7:45 PM, Marcel Molina mar...@twitter.com wrote: If the original retweet is deleted its retweets will also disappear. On Sun, Sep 20, 2009 at 3:56 PM, Dewald Pretorius dpr...@gmail.com wrote: With the new retweeting, what happens with retweets if the original tweet is deleted, or the author's account is closed or suspended? Do all the retweets of that tweet also just disappear with it? Dewald -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] PHP Sample for streaming sample call
Greetings, I'm trying to get the streaming sample (GET /1/statuses/sample.json) call working in PHP. I was able to get the POST to /track.json working fine -- but having trouble getting access to the sample stream. Anyone have working example PHP code I could use for this? I think I'm close, but perhaps getting tripped up on the format of the GET vs. the POST. Thanks.
[twitter-dev] Re: Twitter API: I keep hitting 502 status codes on /statuses/user_timeline
Here's a sample entry from my logs if that would help you: 23.09.2009 02:51:16 Request: aroundmarketing 23.09.2009 02:51:16 Error code: 502 23.09.2009 02:51:16 API Limit: 19103 23.09.2009 02:51:16 Response: Array ( [url] = http://twitter.com/statuses/user_timeline/aroundmarketing.json?id=aroundmarketingcount=200 [content_type] = text/html; charset=UTF-8 [http_code] = 502 [header_size] = 253 [request_size] = 232 [filetime] = -1 [ssl_verify_result] = 0 [redirect_count] = 0 [total_time] = 1.954398 [namelookup_time] = 0.020713 [connect_time] = 0.087937 [pretransfer_time] = 0.087948 [size_upload] = 0 [size_download] = 4729 [speed_download] = 2419 [speed_upload] = 0 [download_content_length] = 4729 [upload_content_length] = 0 [starttransfer_time] = 1.874366 [redirect_time] = 0 ) P.S. Both my account and IP address are whitelisted and have 20,000 API calls on each.
[twitter-dev] Re: I'm back baby
Do You understand the difference between a Twitter website tool that can make 150 API calls an hour on behalf of your single Twitter account and a dedicated Twitter .Net application running on your computer that can make 20,000 API calls an hour across multiple accounts? Isn't exactly accurate. Except in the sense that politicians use the word. On Sep 22, 9:26 am, Dean Collins d...@cognation.net wrote: I'm back baby, bigger and badder than before -www.MyTwitterButler.com http://www.mytwitterbutler.com/ is no.MyPostButler.com http://www.mypostbutler.com/ feel free to tweet it on. Lawyers suck! Cheers, Dean P.S. No they didn't get the domain, my response was not without a court case baby.
[twitter-dev] Re: whitelisting of IP for application - does it applies for all users
Hi Chad, You were right!Thanks for the hint.The point is: 1)I am moving to another hosting account and my new IP address is 69.175.24.45 , but just for accepting the client connections.I have an outband IP - probably NAT server or some GATEWAY with IP address of 69.175.29.34. 2) I already asked for whitelisting of 69.175.24.45 and it was approved.Then I understood that i need whitelisting for 69.175.29.34 and also asked for that but it was rejected with no stated reason. 3)Probably your whitelisting team decided that this is not a production system but note that it is exactly regarding production migration, so i will really need 69.175.29.34 whitelisted so i can point my current production domain to the new hosting account. I know that this is a bit confusing but could you kindly help me to resolve this issue. I already sent another whitelisting request...i hope you will approve it. Note that, i will let you now when migration finish so you can delete the IP addresses that i do not longer need. Thanks! On Sep 18, 11:21 pm, Chad Etzel c...@twitter.com wrote: Hello, Are you absolutely sure that outgoing requests from your server are coming from the same IP you whitelisted? You will see an increased rate-limit on your personal account because that is the account you used to apply for whitelisting, so it will always have an increased limit no matter what IP it is using. Many hosting providers perform outgoing requests through a different IP (usually in some sort of NAT configuration). If you run curlhttp://jazzychad.net/iponly.php from your server do you get back the same IP? -Chad On Fri, Sep 18, 2009 at 8:03 AM, twittme_mobi nlupa...@googlemail.com wrote: Hi, I have my ip whitelisted so it should get 2 request per hour. The point is that when i login in with my username to my twitter application hosted on the specified IP - i get all the 2 requests per hourbut if i login with a different user name - i get only 150. My question is - shouldn't it apply for all the users using this IP ? Isn't it that the purpose of the whitelisting? My application will work fine only for my username? You can find a test version of the app at -http://69.175.24.45 Thanks.
[twitter-dev] Re: I'm back baby
No they didn't force me to, I chose to. (also I kept the domain- just doing a redirect to the new brand name). However I haven't complied at all about changing the way the app works as they are yet to show how it is detrimental to twitter ecosphere. Like I said weird part is how their lawyers have just stopped returning calls and given no explanation at all about their intentions. Cheers, Dean From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Adam Cloud Sent: Wednesday, September 23, 2009 12:56 AM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: I'm back baby Wait, so they actually got away with forcing you to change your domain? Or you did so on your own on advice of a lawyer while you wait out the court case? If you were forced...this is big news...let us know! On Tue, Sep 22, 2009 at 10:26 AM, Dean Collins d...@cognation.net wrote: I'm back baby, bigger and badder than before - www.MyTwitterButler.com http://www.mytwitterbutler.com/ is now www.MyPostButler.com http://www.mypostbutler.com/ feel free to tweet it on. Lawyers suck! Cheers, Dean P.S. No they didn't get the domain, my response was not without a court case baby.
[twitter-dev] Re: Are account suspensions permanent?
For the record, it's not because I have an account that's suspended, it's because I want to know whether my analytics platform I can permanently stop tracking suspended accounts, or whether I have to periodically check back in to see if they're still suspended. I wonder what the rate of reinstatement is, because if it's small, it'll save my app a lot of cycles to just permanently ignore these users. On Sep 23, 12:52 am, Adam Cloud cloudy...@gmail.com wrote: I had an experience that took over 4 months of back and forth, forth being me, back being them marking my ticket as taken care of without doing anything. I finally just created a new account, changed the name of the old one and used that name for the new one. Had another experience where the account was fixed after two unanswered tickets without a word said to the person. So you may have a few days, a week, a few months, maybe forever of being suspended without getting an actual account banning. Twitter may have excellent interaction with their 3rd-party developers, but their customer service blows.
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
I'm seeing retweet_details information appearing in the payload of the statuses/show call. Is this normal behavior? Try this curl http://twitter.com/statuses/show/4297637412.xml Thanks - Martin On Sep 18, 4:57 pm, Marcel Molina mar...@twitter.com wrote: The Retweet API launch is close at hand. You might have already seen some retweets appearing in the new statuses/home_timeline from people who've been testing them out. We've gotten lots of great questions and feedback about the retweet API. Thanks to everyone who has rolled up their sleeves and gotten involved. It's been a big help. One of the main confusions and criticisms about the retweet API was around what happens when a given tweet is retweeted multiple times. The explanation was that developers need to do their own retweet collapsing. If N people retweet a given tweet, you'd get N instances of that same tweet in the appropriate retweet timeline and the home timeline. You would then have to do your own internal book keeping about whether that tweet had already come in. If it hadn't you'd display it for the first time. If it had you'd update the already displayed tweet. Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the first retweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Here is the documentation for the new resource, statuses/retweets:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retweets Sincere apologies if you've already written collapsing logic for retweets. Beta releases are beta releases and I think the retweet API is a lot better without the onerous collapsing requirement. To give you some ideas of how you can use the API to display retweets, here is a recent mock up of one of the potential UIs for the retweets timeline on twitter.com:http://a1.twimg.com/example-retweet-ui-18-sep-09.png If you've got questions, find bugs, or have any kind of feedback, get in touch via the dev mailing list, send an @reply to @twitterapi or jump into the #twitterapi IRC channel on irc.freenode.net. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] How do I get a hold of the preview version of the GeoLocation API?
I'm told that developers will be given access to a preview version of this API, so that we can start building code around it. How do I go about getting access to this preview API? Please advise.
[twitter-dev] Search calls ever moving into REST API?
I've seen talk of moving Search API calls into the REST API for a while now. Twitter, are there any plans or dates that you can discuss yet? Is this still planned at all? This will be very useful to my application because of REST's account- based rate limiting. I'm constantly being Search rate limited because I'm on Rackspace Cloud, sharing the same IP as other Twitter apps.
[twitter-dev] Re: How do I get a hold of the preview version of the GeoLocation API?
hello. we've released the specifications of the API, and those are available at apiwiki.twitter.com. the actual API should be launched on the order of weeks. thanks! I'm told that developers will be given access to a preview version of this API, so that we can start building code around it. How do I go about getting access to this preview API? Please advise. -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Maybe this isn't the right place, but... From a developer perspective I love the retweet API and it's potential uses. As a regular twitter user, I'm less thrilled. Once this is in place, is it going to fundamentally what/how I see my public timeline? If the mockups are anything to go by, it looks less useful. If someone I'm following retweets something from SarahKSilverman, I don't want to see SarahKSilverman appear in my timeline. I want to see the person I know, that way I can easily attribute it with the appropriate amount of importance and credibility. This issue becomes even more pronounced when lesser known individuals are the source of the original tweet, and when the topic being retweeted becomes more niche. Or have I completely misunderstood the final implementation/ implications? Thanks, Glenn
[twitter-dev] Direct message ID question
Hi, Does Twitter use the same range for Direct messages id and Statuses Id? Can DM id be equal Status Id? Thanks.
[twitter-dev] Allowing inner window modification
Since we have the full range of colors for our text, wouldn't it be nice to have the full range of colors for the inner display page that sits over the background? I've been through all the wiki and help discussion pages and I'm sure it's in there somewhere, but I can feel my hair growing as I try to read through all the jargon and lamentations.
[twitter-dev] Re: Search calls ever moving into REST API?
The Search API is served from a totally different infrastructure than api.twitter.com. As such, it has limits that are tuned to protecting a very different back-end. Even if Search was served through the api.twitter.com stack, the policies would still be driven by the back- end. If you are hitting search API limits, there's a good chance there is a better way to service your application. If you share your use case, perhaps we can point out a better way to get the same results? -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 8:41 am, Aaron Rankin aran...@gmail.com wrote: I've seen talk of moving Search API calls into the REST API for a while now. Twitter, are there any plans or dates that you can discuss yet? Is this still planned at all? This will be very useful to my application because of REST's account- based rate limiting. I'm constantly being Search rate limited because I'm on Rackspace Cloud, sharing the same IP as other Twitter apps.
[twitter-dev] Odd behavior with the search API when using since_id
Hello, This has just appeared in the last few days. When I perform a search with the search API I keep track of the newest status id so I can pass that back when doing the next query (as since_id) so that only tweets with a status id greater than since_id are returned. Oddly, beginning yesterday the search API started returning the status specified in since_id but only when I specify a from: parameter to limit the search to a specific user. It's like it is returning statuses = since_id instead of since_id when I add the from: parameter. Anyone else seen odd behavior when using from:?
[twitter-dev] Re: About my MASHUP!
I'm already registered my app, am implementing OAuth and am still in development. I don't know of any approval process. Maybe I'm missing something. On Sep 22, 6:36 pm, sandropype sandro.p...@gmail.com wrote: Hi! I developed a mashup with the twitter api. very simple but works :) what next step to get into the whitelist or know what the staff thinks about twitter mashup Only after it is approved it is possible to implement the OAuth? Thanks!
[twitter-dev] Twitter+Oauth on iPhone: How does one logout?
I'm implementing Twitter+Oauth on the iPhone using http://github.com/bengottlieb/Twitter-OAuth-iPhone. I'm creating a login/logout button/feature like facebook connect uses. I've got the login working and am wondering how does one logout using Oauth?
[twitter-dev] Re: Are account suspensions permanent?
Well, as it stands i've seen 5 people i know go through suspensions 4 of them got it back, the other did not and did what i stated. So unfortunately you can't just rule the suspended out entirely, but maybe you could take them out of your main processing and have a job that runs every night to check to see if their still suspended and update their account accordingly to allow them to be included in your normal processing.
[twitter-dev] Re: Twitter+Oauth on iPhone: How does one logout?
There's no logout for OAuth, per se, as I understand it. It's just a matter of not sending the tokens any longer. On Wed, Sep 23, 2009 at 12:25, joeygreen...@gmail.com joeygreen...@gmail.com wrote: I'm implementing Twitter+Oauth on the iPhone using http://github.com/bengottlieb/Twitter-OAuth-iPhone. I'm creating a login/logout button/feature like facebook connect uses. I've got the login working and am wondering how does one logout using Oauth? -- Internets. Serious business.
[twitter-dev] Re: Odd behavior with the search API when using since_id
Same thing here, it started to happen since yesterday. When doing searches with parameter from:username and since_id, sometimes I got the tweet with since_id back as well. It only happens some times, not every time, so I suspect it's a bug other than API change. Any idea? On Sep 23, 9:40 am, James Teters jtet...@gmail.com wrote: Hello, This has just appeared in the last few days. When I perform a search with the search API I keep track of the newest status id so I can pass that back when doing the next query (as since_id) so that only tweets with a status id greater than since_id are returned. Oddly, beginning yesterday the search API started returning the status specified in since_id but only when I specify a from: parameter to limit the search to a specific user. It's like it is returning statuses = since_id instead of since_id when I add the from: parameter. Anyone else seen odd behavior when using from:?
[twitter-dev] Re: Deleting a Retweeted Tweet
I definitely do not like the fact the a deletion of a tweet also deletes the retweets. It means someone else's actions can subtract content from my time line and completely negate an action that I performed on my account, namely a retweet. To be very honest, I think Twitter is oiling a wheel that did not squeak and is fixing something that was not broken. Three things I do not like about the retweet system: a) The deletions, of course. b) The fact that the original poster's mugshot is shown against the retweet, with the retweeter being attributed in the source area, instead of the other way around. c) The inability to modify or add to the tweet text that you are retweeting. The old/current retweeting method is/was not broken. Dewald On Sep 21, 9:45 pm, Marcel Molina mar...@twitter.com wrote: If the original retweet is deleted its retweets will also disappear. On Sun, Sep 20, 2009 at 3:56 PM, Dewald Pretorius dpr...@gmail.com wrote: With the new retweeting, what happens with retweets if the original tweet is deleted, or the author's account is closed or suspended? Do all the retweets of that tweet also just disappear with it? Dewald -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Odd behavior with the search API when using since_id
Thanks for reporting this. If there is a way for you to capture request/response logs when this happens it will help our search team to track this down. Since it is happening inconsistently it may mean that one of the servers is acting funny, and the HTTP headers could help track that down. -Chad On Wed, Sep 23, 2009 at 4:42 PM, Beier beier...@gmail.com wrote: Same thing here, it started to happen since yesterday. When doing searches with parameter from:username and since_id, sometimes I got the tweet with since_id back as well. It only happens some times, not every time, so I suspect it's a bug other than API change. Any idea? On Sep 23, 9:40 am, James Teters jtet...@gmail.com wrote: Hello, This has just appeared in the last few days. When I perform a search with the search API I keep track of the newest status id so I can pass that back when doing the next query (as since_id) so that only tweets with a status id greater than since_id are returned. Oddly, beginning yesterday the search API started returning the status specified in since_id but only when I specify a from: parameter to limit the search to a specific user. It's like it is returning statuses = since_id instead of since_id when I add the from: parameter. Anyone else seen odd behavior when using from:?
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
As a regular twitter user, I'm less thrilled. Once this is in place, is it going to fundamentally what/how I see my public timeline? If the mockups are anything to go by, it looks less useful. If someone I'm following retweets something from SarahKSilverman, I don't want to see SarahKSilverman appear in my timeline. I want to see the person I know, that way I can easily attribute it with the appropriate amount of importance and credibility. This issue becomes even more pronounced when lesser known individuals are the source of the original tweet, and when the topic being retweeted becomes more niche. The nice thing about being an API client is that you can, of course, change how the tweet is presented. In fact, that is exactly my plan for TTYtter to change retweets so that they come from the person who RTed it, not the person being RTed (who appears appended). Still, I'm sort of with Dewald and others that I'm really having a hard time seeing what the RT API buys, and I can see quite a few things that the old manual way does better. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Smile! God loves you! --
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
I think the new RT API is an attempt to turn related tweets into a computer-parseable conversation. Humans can fairly easily determine what it part of an existing conversation by reading the different tweets and using contextual clues, but computers cannot. The small benefit to us humans is that clients may be more able to present tweets as a threaded conversation if they understand that discreet tweets are, in fact, part of a conversation. The large benefit to Twitter and corporations is that they can more easily track social behavioral patterns (== more finely targeted marketing and advertising and ROI calculations). Fortunately, it's all opt-in. Unfortunately, it's all opt-in. I'm with the others, though, that IMHO retweets should not be deleted if an original retweet (or one up in the chain? dunno) is deleted. Possibly it's only in there because this (having gaps in tweets brought about by deleted tweets) breaks the programmatic ability to follow a thread. Not sure. Joseph Cheek jos...@cheek.com, www.cheek.com twitter: http://twitter.com/cheekdotcom Cameron Kaiser wrote: Still, I'm sort of with Dewald and others that I'm really having a hard time seeing what the RT API buys, and I can see quite a few things that the old manual way does better.
[twitter-dev] Re: How do I get a hold of the preview version of the GeoLocation API?
I saw the api spec already. I guess I was under the assumption that an updated version of the API that included the location functionality would be available for integration testing. Looks like I'll have to just code the components on my end and just wait until the new API goes live to test. Thanks for your prompt response Raffi. ~ Hardip On Sep 23, 11:47 am, Raffi Krikorian ra...@twitter.com wrote: hello. we've released the specifications of the API, and those are available at apiwiki.twitter.com. the actual API should be launched on the order of weeks. thanks! I'm told that developers will be given access to a preview version of this API, so that we can start building code around it. How do I go about getting access to this preview API? Please advise. -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
from http://us2.php.net/json_decode: |In PHP = 5.1.6 trying to decode an integer value that's PHP_INT_MAX will result in an intger of PHP_INT_MAX. In PHP 5.2+ decoding an integer PHP_INT_MAX will cause a conversion to a float. Neither behaviour is perfect, capping at PHP_INT_MAX is marginally worse, but the float conversion loses precision. If you expect to deal with large numbers at all, let alone in JSON, ensure you're using a 64-bit system. -- my thoughts: if moving to a 64-bit system is not feasible and you aren't interesting in hacking the (php itself) source (num_as_string json_decode() patch at http://bugs.php.net/bug.php?id=46363), you could try xml or writing a quick-n-dirty twitter-specific decoder. other alternatives are looking at a hosting provider or paying someone (ahem) to patch your PHP instance plug(I do Linux only, not BSD or 'doze, but I've been doing Linux for a long time and I'm pretty good at it)/plug. thanks! Joseph Cheek jos...@cheek.com, www.cheek.com www.twitter.com/cheekdotcom | Dewald Pretorius wrote: I've run into a serious issue and I don't know if I am overlooking something. When retrieving ids with cursoring, and then doing a PHP json_decode on the data, the cursor value is converted to an exponentional number expression. For example: http://twitter.com/followers/ids/barackobama.json?cursor=-1 yields next_cursor:1314614526448841129 in the raw JSON data. After json_decode the value is converted to 1.31461452645E+18. I've tried both json_decode to an object and to an associative array and both give the same result. As you will notice, even if one were to typecast that number to float, there is still 8 digits missing, which would yield an invalid cursor. So, am I missing something glaringly obvious, or does someone have a solution to this issue? Dewald
[twitter-dev] Re: Deleting a Retweeted Tweet
b) Completely agree c) I thought the reason for even implementing this despite the fact that most 3rd party clients already handle retweets by creation of a new tweet, was to allow text that's being sent by 100's 1000's and so on to be stored in a single location to save on database space as well as to allow for quicker retrieval of the tweet by allowing for more specific caching. Again, that was a thought, since i dont actually know :)
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
All that Twitter needs to do to solve this problem is to build the JSON out with next_cursor and previous_cursor as string values. I.e., the JSON data should contain: next_cursor:12398712981212987,previous_cursor:-12398712981212987 I don't know what it will do to Java apps, but for PHP apps it will solve the problem. Dewald
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Is there a way to connect to the streaming api and only get my friends retweets? Or would I get *everyones* retweets and have to filter millions of unwanted messages out? On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Retweets will be searched by the follow parameter on the filter resource. The intention is that you get all statuses (including retweets) where any user_id field matches your predicate list. So, tweets, replies and both ends of retweets. If GAE cuts you off after 30 seconds, then you shouldn't open connections to the Streaming API. Gather ye data elsewhere and smuggle it into GAE by other means. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 7:50 pm, hansamann sven.hai...@googlemail.com wrote: One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] WEIRD DISPLAY
ok fine.. so i finally found a way to make it work with oauth and
twitter API. now the problem is it is returnig me values I don't want.
To be specific, after posting something using this code
$content = $to-OAuthRequest('http://twitter.com/statuses/update.xml',
array('status' = $linkpath.' - '.$messageThem), 'POST');
this returns an extra XML which is automatically displayed on my page.
Unfortunately, this appears at the end of my file. How can I get rid
of this?
[twitter-dev] Re: SERIOUS Problem With Cursors In JSON Followers/Friends Ids
Hello, As Joseph points out, PHP on a 64-bit system can handle these numbers. If you really want this data as a string, you could write a regex in PHP to alter the json string to wrap the digits in quotes before sending it through json_decode(), but that would be a pretty gnarly kludge. -Chad On Wed, Sep 23, 2009 at 10:28 PM, Dewald Pretorius dpr...@gmail.com wrote: All that Twitter needs to do to solve this problem is to build the JSON out with next_cursor and previous_cursor as string values. I.e., the JSON data should contain: next_cursor:12398712981212987,previous_cursor:-12398712981212987 I don't know what it will do to Java apps, but for PHP apps it will solve the problem. Dewald
[twitter-dev] Re: tweeting with oauth
I've been using Abraham's library and combined it with your library to
do some logging in and posting using PHP. I'm trying to create
actually a module for joomla that would do some logging and posting at
the same time after clicking a link.
It seems working except for the part that it returns an extra result
XML that is displayed at the end of my display. I actually don't know
how to get rid of that since I don't know how and where it came from.
I tried to comment out a certain line in my code and i think this one
is causing it (though its just my hyphothesis)
$content = $to-OAuthRequest('http://twitter.com/statuses/update.xml',
array('status' = $linkpath.' - '.$messageThem), 'POST');
Tell me how I can get rid of these? THANKS!!!
On Sep 3, 12:31 pm, jmathai jmat...@gmail.com wrote:
Could use Abraham or my library.
https://github.com/abraham/twitteroauth/treehttps://github.com/jmathai/twitter-async/tree
I have some blog posts that might help as well.
http://www.jaisenmathai.com/blog/2009/03/31/how-to-quickly-integrate-...http://www.jaisenmathai.com/blog/2009/04/30/letting-your-users-sign-i...
On Sep 2, 1:58 pm, root root892...@yahoo.com wrote:
Hi,
Are there any examples of how to post tweet using an oauth token rather
than username:password? I'm trying to do this in php.
Thanks
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Thanx, I'll give that a try. On Sep 23, 8:11 pm, John Kalucki jkalu...@gmail.com wrote: Retweets will be searched by the follow parameter on the filter resource. The intention is that you get all statuses (including retweets) where any user_id field matches your predicate list. So, tweets, replies and both ends of retweets. If GAE cuts you off after 30 seconds, then you shouldn't open connections to the Streaming API. Gather ye data elsewhere and smuggle it into GAE by other means. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 7:50 pm, hansamann sven.hai...@googlemail.com wrote: One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: WEIRD DISPLAY
Don't echo $content.
On Sep 23, 2009, at 8:35 PM, ajibanda ajiba...@gmail.com wrote:
ok fine.. so i finally found a way to make it work with oauth and
twitter API. now the problem is it is returnig me values I don't want.
To be specific, after posting something using this code
$content = $to-OAuthRequest('http://twitter.com/statuses/update.xml',
array('status' = $linkpath.' - '.$messageThem), 'POST');
this returns an extra XML which is automatically displayed on my page.
Unfortunately, this appears at the end of my file. How can I get rid
of this?
