Re: [twitter-dev] Re: Support from a...@twitter.com sucks!!!
The GWT community was pretty responsive to inquiries and that made it a lot more appealing IMO. Email lists in general are a gamble and a haven for self promotion and the old diagnose a problem and offer a solution marketeers. I offered some pretty detailed research to some chiq that claimed to want feedback on social crm clients on here and she ignored me, her loss. I knew who she was though, kinda. Weak style. Support from MS sounds hellish, what do they do, how many numbers do they assign to you and how many times do they make you repeat yourself? On Mon, Jan 11, 2010 at 11:44 PM, M. Edward (Ed) Borasky zzn...@gmail.comwrote: I'm not labelling everyone as freelance / developers. I'm simply saying that as someone who doesn't have (yet) an established business relationship with Twitter, I'm getting treated very well. Better, in fact, than Microsoft treated me when I paid for support, and as well as ActiveState treats me where I pay support now. Of course, I haven't seen the hotel room prices for the developers' conference yet ;-) On Jan 11, 10:34 pm, Dewald Pretorius dpr...@gmail.com wrote: It is a big misnomer to label everyone as developers let alone as freelance. A good number of us actually run very serious businesses with substantial revenues. On Jan 12, 2:21 am, M. Edward (Ed) Borasky zzn...@gmail.com wrote: I've found Twitter's support of freelance developers to be *way* above average. Compared to Apple, Microsoft, or even Google, Twitter is a joy to work with. There's a sense of community here that I rarely see outside of pure open source projects like PostgreSQL, Perl, Ruby and Linux.
Re: [twitter-dev] Support from a...@twitter.com sucks!!!
Twitter's been trying to hire new support staff for quite a while now. You'll probably remember Doug's email. From what I can determine, they've had no luck finding people, because it's still the engineers answering questions in here. They're stretched. Saying something sucks and following it with !!! probably doesn't help the moral of the guys who are helping - often out of hours from what I can see. I feel the frustration too, but there's definitely more constructive things you can do about it. Why not send out a tweet, or message to your other networks saying Twitter's looking for support staff? Tim. On Tue, Jan 12, 2010 at 5:50 PM, Dewald Pretorius dpr...@gmail.com wrote: I sent very specific questions to a...@twitter.com, not knowing that it is now being automatically fed into the Zendesk Twitter helpdesk system. The answer I received back consisted of: - I suggest that you check out the API wiki for this information: http://apiwiki.twitter.com/ . We also have a very active and helpful community at http://groups.google.com/group/twitter-development-talk , where our API team interacts with developers on a regular basis. You may want to join the group to participate in conversations about topics like these. Hope that helps, Support -- Well, F-ING D-UH!! Thanks for nothing.
[twitter-dev] Re: Support from a...@twitter.com sucks!!!
On Jan 12, 12:27 am, Tim Haines tmhai...@gmail.com wrote: Twitter's been trying to hire new support staff for quite a while now. You'll probably remember Doug's email. From what I can determine, they've had no luck finding people, because it's still the engineers answering questions in here. They're stretched. Saying something sucks and following it with !!! probably doesn't help the moral of the guys who are helping - often out of hours from what I can see. I feel the frustration too, but there's definitely more constructive things you can do about it. Why not send out a tweet, or message to your other networks saying Twitter's looking for support staff? Tim. Well ... I've seen the Twitter job postings. They've got, what, 20 - 30 positions open? I'm guessing they've pulled in, since the jobs were posted on Twitter and many of the major Twitter-related blogs, probably close to 20,000 resumes, maybe 2,000 of which are from people actually qualified to do the work - people with track records. It's going to take a while to go through all of those electrons. ;-) And I think, in addition to not having all the people they need, there's another more interesting phenomenon here. Twitter is co- evolving with its user base and it's non-employee developer base. Twitter has evolved in many different ways, especially in the past year or so. It's a social media conversation platform, it's a real- time news feed, it's a huge text-based cocktail party, it's an evolving meta-language for Web 2.0, and it's even a search engine. ;-) I've been around a long time, and I can't remember anything that evolved as rapidly in more or less life on the edge of chaos fashion. Twitter is one of a kind.
[twitter-dev] Re: Any iPhone Twitter apps with OAuth login ?
Hi Raffi, If you guys really wanted to go all out for the iPhone, you could implement your OAuth login page using PastryKit. It would provide ideal webview integration. For those not familiar: http://davidbcalhoun.com/2009/pastrykit-digging-into-an-apple-pie Thanks, Andrew twitter.com/siggy_sf On Jan 11, 10:32 pm, Raffi Krikorian ra...@twitter.com wrote: 2. Replace the manual PIN entry requirement with something else. The OAuth 1.0a designers greatly under-estimated the poor usability of manual PIN entry, especially on mobile devices. One suggestion off the top of my head: allow OAuth 1.0 (in addition to OAuth 1.0*a*) if--and only if--all parts of the OAuth authorization flow take place in the same TLS session (e.g. using TLS session resumption and/or a persistent HTTPS connection when/if Twitter supports persistent connections) and the application is registered as a desktop app (not a web app). i definitely hear the pain in the PIN workflow -- just as a quick point of note, we're not set up to handle persistent HTTP/HTTPS connections at this time. keep the ideas going - loving this thread. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
Hi, What about this? http://code.google.com/p/twitter-api/issues/detail?id=1233 I'm not interested in passwords at all, but it's not possible using oAuth for the streaming API. You have suggested mixing the streaming API and REST API for providing the best experience for users, but this way I have no choice but using username/password authentication to be able to use the streaming API. Bye, Andras On Tue, Jan 12, 2010 at 8:01 AM, Raffi Krikorian ra...@twitter.com wrote: As it stands, developers who have relatively new desktop apps are penalized by having updates from their app say 'from web'. Older Basic Auth desktop clients continue to enjoy a link back to the client web site with a 'from app' link. ... I understand Twitter is trying to force people to use OAuth, but that won't happen in a meaningful way until OAuth is reliable, has a truly usable workflow (PIN method isn't it), and can work well with other services (Twitpic, yfrog, etc). We aren't there yet. i'm trying to gather use cases around OAuth to help it make sense for more people to use it -- as it stands, we are not going to allow the source parameter to be set in new applications unless they come from OAuth. so, please help me out! is the reliability of OAuth an actual concern? do you have a suggestion as to what you would like to see other than the PIN workflow? additionally, we're actively working on a delegation method for integration with other services. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Storing historic tweets.
Hi All, Just wanted to ask a quick question regarding historic tweets. Is there anything in the twitter TCs to say that search results can't be stored? I ask because the API only returns results from the last week (?) or so... what if I want to use data from previous searches I've conducted. Also, is there any other TC doc other than this page: http://apiwiki.twitter.com/Terms-of-Service Cheers, ~redders.
[twitter-dev] Account linking with Thrid party Site and Twitter
Hi, I am working on an application which would integrate ‘Login with twitter’ as secondary login and registration mechanism. This application is also have some user base already. My question is : Is there any way with twitter API, so that I can Link existing users account with their twitter accounts. As if they login with their twitter account, he will get linked with his existing account on my application. This way his previous information would not be lost or he would not to have a new profile on same application with twitter account. This is something like Facebook’s account linking http://wiki.developers.facebook.com/index.php/Linking_Accounts_and_Finding_Friends Please let me know if it possible in any case, so that I propose the solution to my team. Ram Sharma
Re: [twitter-dev] Storing historic tweets.
The following also apply: http://twitter.com/tos http://twitter.com/apirules http://help.twitter.com/forums/26257/entries/18311 On Tue, Jan 12, 2010 at 5:56 AM, redders redders6...@googlemail.com wrote: Hi All, Just wanted to ask a quick question regarding historic tweets. Is there anything in the twitter TCs to say that search results can't be stored? I ask because the API only returns results from the last week (?) or so... what if I want to use data from previous searches I've conducted. Also, is there any other TC doc other than this page: http://apiwiki.twitter.com/Terms-of-Service Cheers, ~redders.
[twitter-dev] Re: Any iPhone Twitter apps with OAuth login ?
Just FWIW, this isn't really an iPhone-specific issue – there are a lot of rich mobile devices out there. One reason (excuse?) for not using OAuth in Spaz on webOS is the poor functionality on mobile. I'm really reluctant to move to OAuth until the flow for mobile is improved. The data from heypic.me is just what I was afraid of. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Dec 6 2009, 3:08 am, Ram group...@cascadesoft.net wrote: As a followup to the mobile OAuth discussions from October (seehttp://groups.google.com/group/twitter-development-talk/browse_thread...) Does anyone know of any (publicly released) iPhone or other mobile Twitter apps that use OAuth ? I'm partly curious to know/confirm whether our app is the only iPhone (or mobile) app that uses Twitter OAuth login for posting tweets, but I also want to know what you think of the UI, if you've used Twitter OAuth login in any publicly released mobile app. Thanks Ram
[twitter-dev] Re: Support from a...@twitter.com sucks!!!
Twitter support in the past has been great. That is why it was such a shock and disappointment to get that absolutely worthless canned reply to my request. And it wasn't an automated reply from the Zendesk system. The reply was manually sent many hours later. It was clearly from someone who knows absolutely nothing about the Platform. Why is such a person even looking at and responding to tickets sent to api[at]twitter.com? On this forum, Twitter staff always tell us to send support requests, debug info, etc., to api[at]twitter.com. With all the millions in cash that Twitter has in the bank, one really does not want to hear about staff shortages. On Jan 12, 4:27 am, Tim Haines tmhai...@gmail.com wrote: Twitter's been trying to hire new support staff for quite a while now. You'll probably remember Doug's email. From what I can determine, they've had no luck finding people, because it's still the engineers answering questions in here. They're stretched. Saying something sucks and following it with !!! probably doesn't help the moral of the guys who are helping - often out of hours from what I can see. I feel the frustration too, but there's definitely more constructive things you can do about it. Why not send out a tweet, or message to your other networks saying Twitter's looking for support staff? Tim. On Tue, Jan 12, 2010 at 5:50 PM, Dewald Pretorius dpr...@gmail.com wrote: I sent very specific questions to a...@twitter.com, not knowing that it is now being automatically fed into the Zendesk Twitter helpdesk system. The answer I received back consisted of: - I suggest that you check out the API wiki for this information: http://apiwiki.twitter.com/. We also have a very active and helpful community athttp://groups.google.com/group/twitter-development-talk, where our API team interacts with developers on a regular basis. You may want to join the group to participate in conversations about topics like these. Hope that helps, Support -- Well, F-ING D-UH!! Thanks for nothing.
Re: [twitter-dev] Storing historic tweets.
Thanks John, that's been helpful. It looks like storing tweets is fine... On related note, the documentation suggests that tweets using the search API (REST), are time limited to ~1.5 weeks. I have read that developers are now encouraged to use the streaming API. I see that it's possible to get historic tweets from the streaming API, but reading the documentation quoted below, I get the impression that this is limited to 150,000 tweets *before* they have been filtered. So if I searched for a term that has not been tweeted in the last 150,000 tweets, I'll get no historic results? Or have I interpreted that completely wrong? :) ~~~ count Indicates the number of previous statuses to consider for delivery before transitioning to live stream delivery. On unfiltered streams, all considered statuses are delivered, so the number requested is the number returned. On filtered streams, the number requested is the number of statuses that are applied to the filter predicate, and not the number of statuses returned. *Values:* -150,000 to 150,000. This range is subject to change on short notice. Positive values transition seamlessly to the live stream. Negative values terminate when the historical stream has finished, useful for debugging. ~~~ Thanks in advance, ~redders. 2010/1/12 John Kalucki j...@twitter.com The following also apply: http://twitter.com/tos http://twitter.com/apirules http://help.twitter.com/forums/26257/entries/18311 On Tue, Jan 12, 2010 at 5:56 AM, redders redders6...@googlemail.comwrote: Hi All, Just wanted to ask a quick question regarding historic tweets. Is there anything in the twitter TCs to say that search results can't be stored? I ask because the API only returns results from the last week (?) or so... what if I want to use data from previous searches I've conducted. Also, is there any other TC doc other than this page: http://apiwiki.twitter.com/Terms-of-Service Cheers, ~redders.
Re: [twitter-dev] Account linking with Thrid party Site and Twitter
Ram, Just allow them to authorize their twitter account from the existing control panel and on callback save their twitter id with existing id in the db table. You will have to create separate database column to save twitter id for associating it with existing id. Next time, when they logon using twitter, you will look for their twitter id and pull up the already existing data from the table created by previous association. Let me know if you need more explanation Thanks. Lalit Goklani Manage Multiple Twitter Accounts From Facebook - http://bit.ly/6xcEnu On Tue, Jan 12, 2010 at 2:47 AM, Ram Sharma ramsharma...@gmail.com wrote: Hi, I am working on an application which would integrate ‘Login with twitter’ as secondary login and registration mechanism. This application is also have some user base already. My question is : Is there any way with twitter API, so that I can Link existing users account with their twitter accounts. As if they login with their twitter account, he will get linked with his existing account on my application. This way his previous information would not be lost or he would not to have a new profile on same application with twitter account. This is something like Facebook’s account linking http://wiki.developers.facebook.com/index.php/Linking_Accounts_and_Finding_Friends Please let me know if it possible in any case, so that I propose the solution to my team. Ram Sharma
[twitter-dev] Re: bug with search using max_id
RE: Couldn't find Status with ID=7406995447
I'm wondering if the geocode search API is completely dead? It started
to go out intermittently yesterday, now it's completely out. Any help
would be much appreciated since we want to demo this app.
It's throwing a 404 {error:Couldn't find Status with
ID=7406995447}. We've tried this from various IP addresses and it
doesn't matter. I'll include the request and exact error dump below.
The example I use below was taken directly from the Twitter API
documentation on this page.
To reproduce: I took the following URL from that page and tried to
load it using a browser:
http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
GET /search.atom?geocode=40.757929%2C-73.985506%2C25km HTTP/1.1
HTTP/1.0 404 Not Found
Date: Tue, 12 Jan 2010 16:34:36 GMT
Server: hi
Status: 404 Not Found
X-Served-From: sjc1c004
Content-Type: application/xml; charset=utf-8
X-Served-By: sjc1i009.twitter.com
Content-Length: 111
Vary: Accept-Encoding
Cache-Control: max-age=5
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Varnish: 327593908
Age: 0
Via: 1.1 varnish
X-Cache-Svr: sjc1i009.twitter.com
X-Cache: MISS
Connection: close
?xml version=1.0 encoding=UTF-8?
hash
errorCouldn't find Status with ID=7406995447/error
/hash
On Jan 2, 9:03 pm, John munz...@gmail.com wrote:
I recently switched from using page to max_id to prevent duplicates
from appearing due to new tweets. But there seems to be an issue when
hitting the end when doing a search. It results in an error of
Couldn'tfindStatuswith ID=[id of tweet]. The id that gets
returned in the error also doesn't match the ID that I passed in. I
can reproduce it everytime.
To reproduce: Do a search for #tests then take the ID of the last
tweet and do another search using that as the max_id.
Also search and favorites API methods does not list max_id as a
parameter but they do work correctly with max_id besides the issue
above. Shouldn't they be included in the docs?
[twitter-dev] Re: Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
Hi Raffi, What is the reason for no longer allowing the source parameter for Basic Auth desktop apps? The issue is this: The policy is blatantly unfair. The current policy benefits some desktop apps that use Basic Auth while penalizing others. The policy should either remove the source parameter from all Basic Auth desktop apps or allow it for all. It's unfair and hurts a subset of devs while benefiting another subset. I can't believe there is still debate about whether the PIN workflow for *desktop* apps is better from a usability standpoint than simply using username/password. I'm looking forward to the adoption of the new browserless api that exchanges username/password for an access token. In addition, as you stated, you are currently working on a delegation method for integration with other apps. Since it isn't available yet, how can you penalize devs for not adopting it? In many ways, the Twitter api and documentation are quite nice. But this is one area where the company has gone far astray. This arbitrary and unfair policy feels punitive and ham-handed compared with the many well thought out aspects of the Twitter api. For my app, I've had many feature requests including people wanting their tweets to say 'from Itsy' rather than 'from web'. They don't understand why some apps do this and some don't. I've had exactly zero people asking for OAuth or anything like it. No one wants a more convoluted login procedure. They do want new apps to work like Tweetie, Twitterrific and the many other apps they are used to. Please reinstate the source parameter for Basic Auth desktop apps until OAuth for desktop is fully ready and a reasonable transition period has elapsed. The policy should be uniformly applied so that it's fair. Not allowing the source parameter isn't going to coerce devs who have thought through the legitimate issues with Twitter's current incomplete OAuth implementation. It just creates a situation where users and devs are hurt due to an arbitrary and unfair policy. Thank you. Sanjay itsyapp (at) gmail http://mowglii.com/itsy On Jan 11, 11:01 pm, Raffi Krikorian ra...@twitter.com wrote: As it stands, developers who have relatively new desktop apps are penalized by having updates from their app say 'from web'. Older Basic Auth desktop clients continue to enjoy a link back to the client web site with a 'from app' link. ... I understand Twitter is trying to force people to use OAuth, but that won't happen in a meaningful way until OAuth is reliable, has a truly usable workflow (PIN method isn't it), and can work well with other services (Twitpic, yfrog, etc). We aren't there yet. i'm trying to gather use cases around OAuth to help it make sense for more people to use it -- as it stands, we are not going to allow the source parameter to be set in new applications unless they come from OAuth. so, please help me out! is the reliability of OAuth an actual concern? do you have a suggestion as to what you would like to see other than the PIN workflow? additionally, we're actively working on a delegation method for integration with other services. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
What is the reason for no longer allowing the source parameter for Basic Auth desktop apps? the ability to forge the source parameter is too easy when simply using basic auth. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Support from a...@twitter.com sucks!!!
Dewald, I appreciate that the response email was probably not helpful to you, but there are reasons that the new zendesk-based system are greatly beneficial to the community. Surely we can tailor some of the responses so they are more specific to your inquiry (and we will do that), but it's important for us moving forward to have one ticketed channel that allows us to make sure we follow up to every response at scale. Previously those emails were coming into our personal inboxes where they could slip for weeks before we noticed them which left a developer hanging in the lurch the whole time. I would also ask of you that you assume the best of people's actions instead of following up with something as unconstructive as your first response. We are here working with you to continue to improve the system and a simple email calling out that the form response hadn't been helpful to you with a suggested email of what would have been more helpful is something we can work with you on. We are committed to building the best support we can and that can only be done through feedback from everyone on what is working and what isn't. We actually aren't getting a lot of resumes for the Developer Advocate role, so anyone on this list is interested in helping the community or knows of someone who is, please pass them along. The upside is if they do get hired they'll be in your debt :) So again, I do appreciate and hope you continue to give us feedback on how we are doing, but I hope in the future that it is in a more constructive format than your email here. Thanks, Ryan On Tue, Jan 12, 2010 at 7:59 AM, Dewald Pretorius dpr...@gmail.com wrote: Twitter support in the past has been great. That is why it was such a shock and disappointment to get that absolutely worthless canned reply to my request. And it wasn't an automated reply from the Zendesk system. The reply was manually sent many hours later. It was clearly from someone who knows absolutely nothing about the Platform. Why is such a person even looking at and responding to tickets sent to api[at]twitter.com? On this forum, Twitter staff always tell us to send support requests, debug info, etc., to api[at]twitter.com. With all the millions in cash that Twitter has in the bank, one really does not want to hear about staff shortages. On Jan 12, 4:27 am, Tim Haines tmhai...@gmail.com wrote: Twitter's been trying to hire new support staff for quite a while now. You'll probably remember Doug's email. From what I can determine, they've had no luck finding people, because it's still the engineers answering questions in here. They're stretched. Saying something sucks and following it with !!! probably doesn't help the moral of the guys who are helping - often out of hours from what I can see. I feel the frustration too, but there's definitely more constructive things you can do about it. Why not send out a tweet, or message to your other networks saying Twitter's looking for support staff? Tim. On Tue, Jan 12, 2010 at 5:50 PM, Dewald Pretorius dpr...@gmail.com wrote: I sent very specific questions to a...@twitter.com, not knowing that it is now being automatically fed into the Zendesk Twitter helpdesk system. The answer I received back consisted of: - I suggest that you check out the API wiki for this information: http://apiwiki.twitter.com/. We also have a very active and helpful community athttp://groups.google.com/group/twitter-development-talk, where our API team interacts with developers on a regular basis. You may want to join the group to participate in conversations about topics like these. Hope that helps, Support -- Well, F-ING D-UH!! Thanks for nothing.
Re: [twitter-dev] Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
The OAuth discussion and call for uses cases has been asked for before by the API team. Specifically 11 months ago by Alex. Here's the link to that discussion: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/629b03475a3d78a1/655a8425e1e5e045?show_docid=655a8425e1e5e045 It's a good thread that deserves reading as it has contributions from Loren, Blaine, Chris Messina, and Alex. It's pretty much the who's who of desktop/auth/twitter-api. Many of the things that people have put in this thread are some of the same things that were discussed then. Also note that Alex specifically asked for the the community to set up a Wiki about this topic to collect feedback: http://groups.google.com/group/twitter-development-talk/msg/afda4fdf52f78fe3?dmode=source Loren did that and here it is: http://twitter.pbworks.com/oauth-desktop-discussion Just thought I'd post it to this discussion in case someone forgot. isaiah http://twitter.com/isaiah On Jan 11, 2010, at 11:01 PM, Raffi Krikorian wrote: As it stands, developers who have relatively new desktop apps are penalized by having updates from their app say 'from web'. Older Basic Auth desktop clients continue to enjoy a link back to the client web site with a 'from app' link. ... I understand Twitter is trying to force people to use OAuth, but that won't happen in a meaningful way until OAuth is reliable, has a truly usable workflow (PIN method isn't it), and can work well with other services (Twitpic, yfrog, etc). We aren't there yet. i'm trying to gather use cases around OAuth to help it make sense for more people to use it -- as it stands, we are not going to allow the source parameter to be set in new applications unless they come from OAuth. so, please help me out! is the reliability of OAuth an actual concern? do you have a suggestion as to what you would like to see other than the PIN workflow? additionally, we're actively working on a delegation method for integration with other services. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Storing historic tweets.
Historical queries are always going to be the strong point of the Search API. You should perform initial queries against Search to collect the history, then transition to Streaming for the duration of the query demand. The Streaming API offers a few minutes of backlog to allow connections to cycle, request the last few minutes of statuses, and avoid missing data. The status count is a proxy for seconds that you were disconnected. If you know the approximate rate of statuses created per second, and how many seconds you were off, you can adjust the backlog more finely. This is easiest to see at the Firehose level, otherwise you have to overrequest and deduplicate. If you are using a filtered resource at an elevated access level, you specify how many statuses to examine, not the number of results. The idea is the same- to paper over the time between connections, not specify a result set size. We only offer the count parameter on the firehose and higher access levels of follow. It's probably too expensive to run for track and counter to the philosophy of the sample feeds. (It probably should work on the Retweet and Links stream, but it doesn't.) If there's popular demand, we can look into filling these gaps. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Tue, Jan 12, 2010 at 8:11 AM, Edward Hinchliffe redders6...@googlemail.com wrote: Thanks John, that's been helpful. It looks like storing tweets is fine... On related note, the documentation suggests that tweets using the search API (REST), are time limited to ~1.5 weeks. I have read that developers are now encouraged to use the streaming API. I see that it's possible to get historic tweets from the streaming API, but reading the documentation quoted below, I get the impression that this is limited to 150,000 tweets *before* they have been filtered. So if I searched for a term that has not been tweeted in the last 150,000 tweets, I'll get no historic results? Or have I interpreted that completely wrong? :) ~~~ count Indicates the number of previous statuses to consider for delivery before transitioning to live stream delivery. On unfiltered streams, all considered statuses are delivered, so the number requested is the number returned. On filtered streams, the number requested is the number of statuses that are applied to the filter predicate, and not the number of statuses returned. *Values:* -150,000 to 150,000. This range is subject to change on short notice. Positive values transition seamlessly to the live stream. Negative values terminate when the historical stream has finished, useful for debugging. ~~~ Thanks in advance, ~redders. 2010/1/12 John Kalucki j...@twitter.com The following also apply: http://twitter.com/tos http://twitter.com/apirules http://help.twitter.com/forums/26257/entries/18311 On Tue, Jan 12, 2010 at 5:56 AM, redders redders6...@googlemail.comwrote: Hi All, Just wanted to ask a quick question regarding historic tweets. Is there anything in the twitter TCs to say that search results can't be stored? I ask because the API only returns results from the last week (?) or so... what if I want to use data from previous searches I've conducted. Also, is there any other TC doc other than this page: http://apiwiki.twitter.com/Terms-of-Service Cheers, ~redders.
[twitter-dev] JSON Response Error and Search API Error for location.
Hi, I am a developer of TweetTime which is iPhone Twitter Client. I have been through similar problem about a month ago. But one day it was fixed. And I got another huge JSON response error, again. It makes TweetTime app work weird. http://twitpic.com/xt0vw/full - Check out this screenshot to see errors. From left to right, First is a tweet without Geotagging, Second one is with Geotagging, and third one is one it should be. It makes my app look like this. http://twitpic.com/xt208 http://twitpic.com/xt22f Also, searching Api for location no longer work. Not only my App, TweetTime, but also Tweetie, Twitbird... all the iPhone apps supporting near by tweets cannot search the results. All these are happened since I guess couple of hours ago. Hope it will be fixed quickly. Thanks.
[twitter-dev] Widget Profile - Tweet Background floating above lightbox
I have added a Twitter Profile Widget to a website I am developing. It works well and looks good but I have a slight problem in that same web page invokes a lightbox using mootools and the 'tweet background', not the whole widget, floats above my lightbox when displayed. It could be a 'z-index' modification but all the same it is strange that the whole widget isn't consistently floating above the lightbox. How can I change this please so that it doesn't do this? Thank you DS
[twitter-dev] Re: Support from a...@twitter.com sucks!!!
Ryan, Next time something like that happens, I will count to 10 before clicking the Send button. You may have noticed in the past that diplomacy is not an attribute that I will prominently feature on my resume, especially not when I am mad. However, that still leaves us with the original issue. You said, Surely we can tailor some of the responses so they are more specific to your inquiry (and we will do that). Ryan, what I want and need from you and your team, is a relevant, knowledgeable, and helpful reply to a support request. You know that I do not inundate you with emails to api[at]twitter.com, or even to your personal email addresses, even though I have many of those. Your 1st-line support staff should know what to escalate and when to escalate a request to an engineer. As you have seen from others in this thread, it is a slap in the face and an insult to one's intelligence to receive such an irrelevant reply to a bona fide support request. I have no problem with a canned response being sent to someone who is too lazy to RTFM. Thanks, Dewald On Jan 12, 12:45 pm, Ryan Sarver rsar...@twitter.com wrote: Dewald, I appreciate that the response email was probably not helpful to you, but there are reasons that the new zendesk-based system are greatly beneficial to the community. Surely we can tailor some of the responses so they are more specific to your inquiry (and we will do that), but it's important for us moving forward to have one ticketed channel that allows us to make sure we follow up to every response at scale. Previously those emails were coming into our personal inboxes where they could slip for weeks before we noticed them which left a developer hanging in the lurch the whole time. I would also ask of you that you assume the best of people's actions instead of following up with something as unconstructive as your first response. We are here working with you to continue to improve the system and a simple email calling out that the form response hadn't been helpful to you with a suggested email of what would have been more helpful is something we can work with you on. We are committed to building the best support we can and that can only be done through feedback from everyone on what is working and what isn't. We actually aren't getting a lot of resumes for the Developer Advocate role, so anyone on this list is interested in helping the community or knows of someone who is, please pass them along. The upside is if they do get hired they'll be in your debt :) So again, I do appreciate and hope you continue to give us feedback on how we are doing, but I hope in the future that it is in a more constructive format than your email here. Thanks, Ryan On Tue, Jan 12, 2010 at 7:59 AM, Dewald Pretorius dpr...@gmail.com wrote: Twitter support in the past has been great. That is why it was such a shock and disappointment to get that absolutely worthless canned reply to my request. And it wasn't an automated reply from the Zendesk system. The reply was manually sent many hours later. It was clearly from someone who knows absolutely nothing about the Platform. Why is such a person even looking at and responding to tickets sent to api[at]twitter.com? On this forum, Twitter staff always tell us to send support requests, debug info, etc., to api[at]twitter.com. With all the millions in cash that Twitter has in the bank, one really does not want to hear about staff shortages. On Jan 12, 4:27 am, Tim Haines tmhai...@gmail.com wrote: Twitter's been trying to hire new support staff for quite a while now. You'll probably remember Doug's email. From what I can determine, they've had no luck finding people, because it's still the engineers answering questions in here. They're stretched. Saying something sucks and following it with !!! probably doesn't help the moral of the guys who are helping - often out of hours from what I can see. I feel the frustration too, but there's definitely more constructive things you can do about it. Why not send out a tweet, or message to your other networks saying Twitter's looking for support staff? Tim. On Tue, Jan 12, 2010 at 5:50 PM, Dewald Pretorius dpr...@gmail.com wrote: I sent very specific questions to a...@twitter.com, not knowing that it is now being automatically fed into the Zendesk Twitter helpdesk system. The answer I received back consisted of: - I suggest that you check out the API wiki for this information: http://apiwiki.twitter.com/. We also have a very active and helpful community athttp://groups.google.com/group/twitter-development-talk, where our API team interacts with developers on a regular basis. You may want to join the group to participate in conversations about topics like these. Hope that helps, Support -- Well, F-ING D-UH!! Thanks
[twitter-dev] Invalid / suspended application error
I am using twitter4j library and get a strange error that I do not
understand how to fix. Maybe anybody has come across the same issue
before and would be able to to explain what is wrong.
Exception I get:
twitter4j.TwitterException: 401:Authentication credentials were
missing or incorrect.
?xml version=1.0 encoding=UTF-8?
hash
request/oauth/request_token/request
errorInvalid / suspended application/error
/hash
twitter4j.http.HttpClient.httpRequest(HttpClient.java:477)
twitter4j.http.HttpClient.getOauthRequestToken(HttpClient.java:167)
twitter4j.Twitter.getOAuthRequestToken(Twitter.java:138)
Code where it happends:
Twitter twitter = new Twitter();
twitter.setOAuthConsumer(consumerKey, consumerSecret);
RequestToken requestToken;
try {
requestToken = twitter.getOAuthRequestToken(); // exception happends
here
Any help is appreciated.
[twitter-dev] Re: Is this application breaking Twitter API standards?
Hey Colin, To echo Mark's comment, we'd appreciate a report so that we can look into the app and take any necessary action. If you like, you can directly reply to me with a name or URL and I'd be happy to investigate. Brian On Jan 11, 4:38 pm, Colin colinjos...@googlemail.com wrote: I've discovered an online application - I won't mention the name - but it seems to break Twitter API. I'm wondering how they get away with it. Here's what the application does. It allows the user to enter a number of keyword phrases to monitor with. Every time a phrase is mentioned e.g. twitter api, it replies to the person who sent that tweet with an automated response e.g. 'to find out more about twitter api visithttp://xxx' Seems there's a couple of issues here. 1. How are they getting passed rate limiting to scan every tweet and then send out a reply? The application could have thousands of users! 2. According to Twitter The @reply function is intended to make communication between users easier, and automating this process to put unsolicited messages into lots of users’ reply tabs is considered an abuse of feature. If you are automatically sending @reply messages to a bunch of users, the recipients must request or approve this action in advance. For example, sending automated @replies based on keyword searches is not permitted. Users should also have an easy way to opt-out of your service (in addition to the requirement that all users must opt-in before receiving the messages). We review blocks and reports of spam, so you’ll need to provide a clear way for users to stop your messages. *Spam: You may not use the Twitter service for the purpose of spamming anyone. What constitutes “spamming” will evolve as we respond to new tricks and tactics by spammers. Some of the factors that we take into account when determining what conduct is considered to be spamming are: If you send large numbers of duplicate @replies; If you send large numbers of unsolicited @replies in an attempt to spam a service or link; Can anyone explain to me how this online application is getting around these issues? Thanks Colin
[twitter-dev] Re: OAuth image upload: how does Twitter want to see multi-part post OAuth parts?
Hey Raffi, I know about the basics of oAuth I already working code for posting tweets with OAuth. I have few doubts with respect to building signature for multi part requests. 1. What all parameters should be part of the signature base string? 2. Where should the parameters and the signature be placed in the request stream? 3. How should the file data be sent? Please help me out.
Re: [twitter-dev] Re: OAuth image upload: how does Twitter want to see multi-part post OAuth parts?
i haven't actually written code to upload profile images recently, but what i would try is the following (and i apologise if i'm slightly incorrect as i'm doing this from memory): 1. What all parameters should be part of the signature base string? oauth_consumer_key oauth_signature_method oauth_timestamp oauth_nonce oauth_version oauth_token of course, the request type and URL comprise the block that needs to be signed 2. Where should the parameters and the signature be placed in the request stream? the authorization header would be the best place to stick it. 3. How should the file data be sent? multipart/form-data, i believe. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Support from a...@twitter.com sucks!!!
On 1/12/2010 9:45 AM, Ryan Sarver wrote: Dewald, I appreciate that the response email was probably not helpful to you, but there are reasons that the new zendesk-based system are greatly beneficial to the community. Surely we can tailor some of the responses so they are more specific to your inquiry (and we will do that), but it's important for us moving forward to have one ticketed channel that allows us to make sure we follow up to every response at scale. Previously those emails were coming into our personal inboxes where they could slip for weeks before we noticed them which left a developer hanging in the lurch the whole time. I would also ask of you that you assume the best of people's actions instead of following up with something as unconstructive as your first response. We are here working with you to continue to improve the system and a simple email calling out that the form response hadn't been helpful to you with a suggested email of what would have been more helpful is something we can work with you on. We are committed to building the best support we can and that can only be done through feedback from everyone on what is working and what isn't. We actually aren't getting a lot of resumes for the Developer Advocate role, so anyone on this list is interested in helping the community or knows of someone who is, please pass them along. The upside is if they do get hired they'll be in your debt :) So again, I do appreciate and hope you continue to give us feedback on how we are doing, but I hope in the future that it is in a more constructive format than your email here. Thanks, Ryan Ryan, We all appreciate the work you do and the support you give when we can talk to you.And I'm sure a lot of us have sent off e-mails when we should have counted to ten first. But even you can see that when you get an e-mail that is a form letter minus the filled out part, you get a little ticked off. We understand the pressures you're under; we just would ask that you understand the frustration we're under in return.
[twitter-dev] Re: bug with search using max_id
Oh ... I thought I was doing something wrong. But I was getting
Internal Server Error, not 404. Here's what I was doing (Perl, but
the HTTP should be obvious):
q = $search_string,
geocode = $geocode,
rpp = 100,
max_id = $max_id,
page = $page
On Jan 12, 9:15 am, Mark McBride mmcbr...@twitter.com wrote:
The search team is aware of the problem, I'll let you know when we
have more info.
---Mark
http://twitter.com/mccv
On Tue, Jan 12, 2010 at 8:38 AM, andy_edn andygup@gmail.com wrote:
RE: Couldn't find Status with ID=7406995447
I'm wondering if the geocode search API is completely dead? It started
to go out intermittently yesterday, now it's completely out. Any help
would be much appreciated since we want to demo this app.
It's throwing a 404 {error:Couldn't find Status with
ID=7406995447}. We've tried this from various IP addresses and it
doesn't matter. I'll include the request and exact error dump below.
The example I use below was taken directly from the Twitter API
documentation on this page.
To reproduce: I took the following URL from that page and tried to
load it using a
browser:http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
GET /search.atom?geocode=40.757929%2C-73.985506%2C25km HTTP/1.1
HTTP/1.0 404 Not Found
Date: Tue, 12 Jan 2010 16:34:36 GMT
Server: hi
Status: 404 Not Found
X-Served-From: sjc1c004
Content-Type: application/xml; charset=utf-8
X-Served-By: sjc1i009.twitter.com
Content-Length: 111
Vary: Accept-Encoding
Cache-Control: max-age=5
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Varnish: 327593908
Age: 0
Via: 1.1 varnish
X-Cache-Svr: sjc1i009.twitter.com
X-Cache: MISS
Connection: close
?xml version=1.0 encoding=UTF-8?
hash
errorCouldn't find Status with ID=7406995447/error
/hash
On Jan 2, 9:03 pm, John munz...@gmail.com wrote:
I recently switched from using page to max_id to prevent duplicates
from appearing due to new tweets. But there seems to be an issue when
hitting the end when doing a search. It results in an error of
Couldn'tfindStatuswith ID=[id of tweet]. The id that gets
returned in the error also doesn't match the ID that I passed in. I
can reproduce it everytime.
To reproduce: Do a search for #tests then take the ID of the last
tweet and do another search using that as the max_id.
Also search and favorites API methods does not list max_id as a
parameter but they do work correctly with max_id besides the issue
above. Shouldn't they be included in the docs?
[twitter-dev] Re: bug with search using max_id
Somebody's corollary to Murphy's Law: When a programmer writes logic
into his Perl Twitter app to dump the handle and error objects in YAML
on an error, so he can send the data to Twitter, he stops getting
'Internal Server Error' from Twitter. ;-)
On Jan 12, 10:56 am, M. Edward (Ed) Borasky zzn...@gmail.com
wrote:
Oh ... I thought I was doing something wrong. But I was getting
Internal Server Error, not 404. Here's what I was doing (Perl, but
the HTTP should be obvious):
q = $search_string,
geocode = $geocode,
rpp = 100,
max_id = $max_id,
page = $page
On Jan 12, 9:15 am, Mark McBride mmcbr...@twitter.com wrote:
The search team is aware of the problem, I'll let you know when we
have more info.
---Mark
http://twitter.com/mccv
On Tue, Jan 12, 2010 at 8:38 AM, andy_edn andygup@gmail.com wrote:
RE: Couldn't find Status with ID=7406995447
I'm wondering if the geocode search API is completely dead? It started
to go out intermittently yesterday, now it's completely out. Any help
would be much appreciated since we want to demo this app.
It's throwing a 404 {error:Couldn't find Status with
ID=7406995447}. We've tried this from various IP addresses and it
doesn't matter. I'll include the request and exact error dump below.
The example I use below was taken directly from the Twitter API
documentation on this page.
To reproduce: I took the following URL from that page and tried to
load it using a
browser:http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
GET /search.atom?geocode=40.757929%2C-73.985506%2C25km HTTP/1.1
HTTP/1.0 404 Not Found
Date: Tue, 12 Jan 2010 16:34:36 GMT
Server: hi
Status: 404 Not Found
X-Served-From: sjc1c004
Content-Type: application/xml; charset=utf-8
X-Served-By: sjc1i009.twitter.com
Content-Length: 111
Vary: Accept-Encoding
Cache-Control: max-age=5
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Varnish: 327593908
Age: 0
Via: 1.1 varnish
X-Cache-Svr: sjc1i009.twitter.com
X-Cache: MISS
Connection: close
?xml version=1.0 encoding=UTF-8?
hash
errorCouldn't find Status with ID=7406995447/error
/hash
On Jan 2, 9:03 pm, John munz...@gmail.com wrote:
I recently switched from using page to max_id to prevent duplicates
from appearing due to new tweets. But there seems to be an issue when
hitting the end when doing a search. It results in an error of
Couldn'tfindStatuswith ID=[id of tweet]. The id that gets
returned in the error also doesn't match the ID that I passed in. I
can reproduce it everytime.
To reproduce: Do a search for #tests then take the ID of the last
tweet and do another search using that as the max_id.
Also search and favorites API methods does not list max_id as a
parameter but they do work correctly with max_id besides the issue
above. Shouldn't they be included in the docs?
[twitter-dev] Re: OAuth image upload: how does Twitter want to see multi-part post OAuth parts?
Raffi, If you have ever worked with DotNet then please help me. What I do currently is as follows: - Set the request type to POST. - ContentType to multipart/form-data; boundary= + boundary (generated); - Then I add this to the request stream L--+boundary+L\r\n+LContent-Disposition: form-data; name=\image\; filename=\test.JPG\ + L\r\n+LContent-Type: image/jpg+L\r\n\r\n; - followed by the bytestream of the image. - Then I continue to add the OAuth params/signature to the stream All the above are URL encoded. Twitter responds with a 401 to this request. What do I have to correct.
Re: [twitter-dev] Re: OAuth image upload: how does Twitter want to see multi-part post OAuth parts?
i've never used dot.net, however, it looks suspicious to me that the bytestream of the image is coming before the oauth params/signature in your example. i would expect the oauth params/signature to be in the Authorization header, and the image to be in the body of the POST. On Tue, Jan 12, 2010 at 10:50 AM, Vikram vikram.prav...@gmail.com wrote: Raffi, If you have ever worked with DotNet then please help me. What I do currently is as follows: - Set the request type to POST. - ContentType to multipart/form-data; boundary= + boundary (generated); - Then I add this to the request stream L--+boundary+L\r\n+LContent-Disposition: form-data; name=\image\; filename=\test.JPG\ + L\r\n+LContent-Type: image/jpg+L\r\n\r\n; - followed by the bytestream of the image. - Then I continue to add the OAuth params/signature to the stream All the above are URL encoded. Twitter responds with a 401 to this request. What do I have to correct. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] question about PIN code
hi,,, i am trying to make mobile app for Android. For athenticaion, i followed this procedure. i got concumer key and secret key,, problem is , i don't know how to generate PIN code.. is there any web site? please answer my question. The application uses oauth/request_token to obtain a request token from twitter.com. The application directs the user to oauth/authorize on twitter.com. After obtaining approval from the user, a prompt on twitter.com will display a 7 digit PIN. The user is instructed to copy this PIN and return to the appliction. The application will prompt the user to enter the PIN from step 4. The application uses the PIN as the value for the oauth_verifier parameter in a call to oauth/access_token which will verify the PIN and exchange a request_token for an access_token. Twitter will return an access_token for the application to generate subsequent OAuth signatures.
[twitter-dev] oneforty e-commerce alpha launch
The oneforty team is excited to be launching an alpha version of our ecommerce platform for Twitter applications this Thursday, Jan 14th. We wanted to let other Twitter developers know, and offer the opportunity to have their app highlighted as we roll out this marketplace. If you're interested in building a premium version of your app, we'd like to work with you to make it simple to get discovered and process sales. We have a getting started guide (http://oneforty.com/pages/seller_guide) that covers the process, and documentation on our API (http://oneforty.com/pages/fulfillment) for app developers. I'm happy to answer any questions, or find us in on IRC in #oneforty on freenode. Thanks, -mike -- Mike Champion http://oneforty.com
Re: [twitter-dev] question about PIN code
When you direct the user to oauth/authorize, the user will be presented with an Allow/Deny page from Twitter. If they Allow, they then will be given an PIN on the screen. The user will need to give this PIN to you. Ryan On Tue, Jan 12, 2010 at 7:59 PM, dduby nezzi...@gmail.com wrote: hi,,, i am trying to make mobile app for Android. For athenticaion, i followed this procedure. i got concumer key and secret key,, problem is , i don't know how to generate PIN code.. is there any web site? please answer my question. The application uses oauth/request_token to obtain a request token from twitter.com. The application directs the user to oauth/authorize on twitter.com. After obtaining approval from the user, a prompt on twitter.com will display a 7 digit PIN. The user is instructed to copy this PIN and return to the appliction. The application will prompt the user to enter the PIN from step 4. The application uses the PIN as the value for the oauth_verifier parameter in a call to oauth/access_token which will verify the PIN and exchange a request_token for an access_token. Twitter will return an access_token for the application to generate subsequent OAuth signatures.
[twitter-dev] Re: bug with search using max_id
Andy - I'm experiencing the the same problem. All geosearches result
in:
{error:Couldn't find Status with ID=7406995447}
On Jan 12, 11:38 am, andy_edn andygup@gmail.com wrote:
RE:Couldn't find Status with ID=7406995447
I'm wondering if the geocode search API is completely dead? It started
to go out intermittently yesterday, now it's completely out. Any help
would be much appreciated since we want to demo this app.
It's throwing a 404 {error:Couldn't find Status withID=7406995447}. We've
tried this from various IP addresses and it
doesn't matter. I'll include the request and exact error dump below.
The example I use below was taken directly from the Twitter API
documentation on this page.
To reproduce: I took the following URL from that page and tried to
load it using a
browser:http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
GET /search.atom?geocode=40.757929%2C-73.985506%2C25km HTTP/1.1
HTTP/1.0 404 Not Found
Date: Tue, 12 Jan 2010 16:34:36 GMT
Server: hi
Status: 404 Not Found
X-Served-From: sjc1c004
Content-Type: application/xml; charset=utf-8
X-Served-By: sjc1i009.twitter.com
Content-Length: 111
Vary: Accept-Encoding
Cache-Control: max-age=5
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Varnish: 327593908
Age: 0
Via: 1.1 varnish
X-Cache-Svr: sjc1i009.twitter.com
X-Cache: MISS
Connection: close
?xml version=1.0 encoding=UTF-8?
hash
errorCouldn't find Status with ID=7406995447/error
/hash
On Jan 2, 9:03 pm, John munz...@gmail.com wrote:
I recently switched from using page to max_id to prevent duplicates
from appearing due to new tweets. But there seems to be an issue when
hitting the end when doing a search. It results in an error of
Couldn'tfindStatuswith ID=[id of tweet]. The id that gets
returned in the error also doesn't match the ID that I passed in. I
can reproduce it everytime.
To reproduce: Do a search for #tests then take the ID of the last
tweet and do another search using that as the max_id.
Also search and favorites API methods does not list max_id as a
parameter but they do work correctly with max_id besides the issue
above. Shouldn't they be included in the docs?
[twitter-dev] Re: Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
What is the reason for no longer allowing the source parameter for Basic Auth desktop apps? the ability to forge the source parameter is too easy when simply using basic auth. Hi Raffi, Why not disallow it for all apps then? Would the users of Tweetie, Twitterrific, etc like that? Would the devs? This reason doesn't seem to make any sense. The issue is about applying a rule fairly and uniformly to all devs. This issue hasn't been addressed. The currently policy hurts devs and users who reasonably choose not to adopt a system that that doesn't work well yet. None of the issues I brought up have been addressed. As Twitter matures, how you treat the devs and users who make your ecosystem successful will be increasingly important. Please reinstate the source parameter so that all devs and users are treated equally. It doesn't cost Twitter much (anything?) to do the right thing here. Thanks, Sanjay
[twitter-dev] Re: Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
What is the reason for no longer allowing the source parameter for Basic Auth desktop apps? the ability to forge the source parameter is too easy when simply using basic auth. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi Hi Raffi, If that is the reason for disallowing the source param, why is this policy not being applied uniformly? How would users of Tweetie, Twitterrific, etc. feel if all their updates now said 'from web'? How would the developers of those apps feel? You've stated yourself that issues with OAuth are being worked on. So why are you hurting a subset of developers and users who aren't using a system that isn't ready to be used? At the same time, you are benefiting another subset that made the same reasonable decision? Twitter is now a mature, massively funded corporation. The way you treat your developer and user ecosystem and handle situations in which corporate policy is uneven and unfair will matter more. This is one of those situations. Please do the right (and easy) thing and reinstate the source param so that all developers and users are treated equally. It is simply a matter of fairness. Thanks, Sanjay
[twitter-dev] search.twitter.com over last couple of days intermittently says that the page has been moved
It does not matter what I search for. The json and atom responses are not coming back either. I believe that this is some kind of routing problem because when I log onto a server in US and do the same it works (I do my queries normally from Canada). To test, it is quite easy, just do any query on search.twitter.com directly such as: http://search.twitter.com/search?q=twitter from an IP that is in Canada. I think it happens elsewhere in the world based on some tweets that I have seen while searching for search.twitter.com. The search on main twitter site is unaffected (i.e. http://twitter.com/#search?q=twitter works) as it uses some different mechanism (what is that mechanism, that would be nice to know, because I certainly would like to have the same level of reliability as the main site at least, I don't think that streaming api is the solution as it requires authentication).
[twitter-dev] mobile.twitter.com from iphone app
I'm planning to link to mobile.twitter.com from my iphone application, so was wondering if the mobile.twitter.com site is just a preview or will it work forever. Just want to make sure that mobile.twitter.com will still work after the design is transitioned to m.twitter.com at some point.
[twitter-dev] Re: Account linking with Thrid party Site and Twitter
Hi Lalit, Thanks for your reply but that is a solution I already knew. I just wanted to know if the user does not authorize their twitter account in their existing account, still can we have any chance to link the accounts? Thanks Ram Sharma On Jan 12, 8:42 pm, lalit goklani lgokl...@gmail.com wrote: Ram, Just allow them to authorize their twitter account from the existing control panel and on callback save their twitter id with existing id in the db table. You will have to create separate database column to save twitter id for associating it with existing id. Next time, when they logon using twitter, you will look for their twitter id and pull up the already existing data from the table created by previous association. Let me know if you need more explanation Thanks. Lalit Goklani Manage Multiple Twitter Accounts From Facebook -http://bit.ly/6xcEnu On Tue, Jan 12, 2010 at 2:47 AM, Ram Sharma ramsharma...@gmail.com wrote: Hi, I am working on an application which would integrate ‘Login with twitter’ as secondary login and registration mechanism. This application is also have some user base already. My question is : Is there any way with twitter API, so that I can Link existing users account with their twitter accounts. As if they login with their twitter account, he will get linked with his existing account on my application. This way his previous information would not be lost or he would not to have a new profile on same application with twitter account. This is something like Facebook’s account linking http://wiki.developers.facebook.com/index.php/Linking_Accounts_and_Fi... Please let me know if it possible in any case, so that I propose the solution to my team. Ram Sharma- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Re: Reinstate 'from app' for Basic Auth desktop apps until OAuth is fixed
If that is the reason for disallowing the source param, why is this policy not being applied uniformly? How would users of Tweetie, Twitterrific, etc. feel if all their updates now said 'from web'? How would the developers of those apps feel? those applications have been grandfathered in -- requiring oauth to set the source parameter applies to newer applications. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: bug with search using max_id
I'm testing this and it looks like I can reproduce an Internal Server
Error when I use the call
_uri: !!perl/scalar:URI::http
http://api.twitter.com/1/search.json?rpp=100page=1q=geocode=40.645%2C-124.763%2C100mimax_id=7678398633
_uri_canonical: !!perl/scalar:URI::http
http://api.twitter.com/1/search.json?rpp=100page=1q=geocode=40.645%2C-124.763%2C100mimax_id=7678398633
Note that this is strictly a geocode search - the query string is
empty and that's intended. Interesting thing is that if I use
until_id rather than max_id, it appears to be searching and
returning tweets. If you want, I've got HTTP request / response dumps
I can send you for this.
On Jan 12, 9:04 am, ImNotQuiteJack jon.coll...@gmail.com wrote:
Andy - I'm experiencing the the same problem. All geosearches result
in:
{error:Couldn't find Status with ID=7406995447}
On Jan 12, 11:38 am, andy_edn andygup@gmail.com wrote:
RE:Couldn't find Status with ID=7406995447
I'm wondering if the geocode search API is completely dead? It started
to go out intermittently yesterday, now it's completely out. Any help
would be much appreciated since we want to demo this app.
It's throwing a 404 {error:Couldn't find Status withID=7406995447}.
We've tried this from various IP addresses and it
doesn't matter. I'll include the request and exact error dump below.
The example I use below was taken directly from the Twitter API
documentation on this page.
To reproduce: I took the following URL from that page and tried to
load it using a
browser:http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
GET /search.atom?geocode=40.757929%2C-73.985506%2C25km HTTP/1.1
HTTP/1.0 404 Not Found
Date: Tue, 12 Jan 2010 16:34:36 GMT
Server: hi
Status: 404 Not Found
X-Served-From: sjc1c004
Content-Type: application/xml; charset=utf-8
X-Served-By: sjc1i009.twitter.com
Content-Length: 111
Vary: Accept-Encoding
Cache-Control: max-age=5
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Varnish: 327593908
Age: 0
Via: 1.1 varnish
X-Cache-Svr: sjc1i009.twitter.com
X-Cache: MISS
Connection: close
?xml version=1.0 encoding=UTF-8?
hash
errorCouldn't find Status with ID=7406995447/error
/hash
On Jan 2, 9:03 pm, John munz...@gmail.com wrote:
I recently switched from using page to max_id to prevent duplicates
from appearing due to new tweets. But there seems to be an issue when
hitting the end when doing a search. It results in an error of
Couldn'tfindStatuswith ID=[id of tweet]. The id that gets
returned in the error also doesn't match the ID that I passed in. I
can reproduce it everytime.
To reproduce: Do a search for #tests then take the ID of the last
tweet and do another search using that as the max_id.
Also search and favorites API methods does not list max_id as a
parameter but they do work correctly with max_id besides the issue
above. Shouldn't they be included in the docs?
