[twitter-dev] Re: Logical AND supported in streaming API filter endpoint
Great!! Many thanks to the Streaming API Team. You've done this, just when I needed it. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Logical AND supported in streaming API filter endpoint
When will we get - aka not? On Monday, April 19, 2010, Mark McBride mmcbr...@twitter.com wrote: To date the streaming API has only supported logical OR in track keywords (http://apiwiki.twitter.com/Streaming-API-Documentation#track). Today we're happy to announce that we support logical ANDing in production as well. The track parameter is treated as a series of phrases. Phrases are separated by commas. Words within phrases are delimited by spaces. A tweet matches if any phrase matches. A phrase matches if all of the words are present in the tweet. (e.g. 'the twitter' is 'the' AND 'twitter', and 'the,twitter' is 'the' OR 'twitter'.). Some examples... 1) twitter api,twitter streaming (http://stream.twitter.com/1/statuses/filter.xml?track=twitter+api%2Ctwitter+streaming) will match the tweets The Twitter API is awesome and The twitter streaming deal is fast, but not I'm new to Twitter 2) The same approach to dealing with case, punctuation, @replies and hashtags still applies. So chirp search,chirp streaming (http://stream.twitter.com/1statuses/filter.xml?track=chirp+search%2Cchirp+streaming) will match Listening to the @chirp talk on search, I'm at Chirp talking about search!, and loving this search talk #chirp This should dramatically close the gap on what you can do with the search API but not with streaming, and also reduce the amount of data users have to consumer to match on multiple keywords. Comments/questions welcome as always. ---Mark http://twitter.com/mccv -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: users/lookup issues
Sorry EPI twitter is confusing, I meant the Twitter-Async library. The issue is oAuth and sending the comma list. Has anyone got users/lookup with multi usernames working with oAuth? On Apr 22, 10:22 pm, Ninjamonk dar...@stuartmedia.co.uk wrote: thanks, works in the browser now, however the corrected oAuth call does not work and gives me a 401. Is there trick to getting this method to work with oAuth? I noticed someone else was having problems with it. As I said before every other api method call works except this one. for example this works in the browser but not via oauth -http://api.twitter.com/1/users/lookup.json?screen_name=JAIMEALGUERSUA... I am using EPITwitter so if anyone has come across this issue with that library or php before I would love some help to solve the issue if its not an api one. Kind Regards Darre On Apr 22, 9:36 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ninjamonk, Slight error in the docs that I'll get fixed right now -- try this instead: http://api.twitter.com/1/users/lookup.json?screen_name=dougw,raffi Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, Apr 22, 2010 at 1:33 PM, Ninjamonk dar...@stuartmedia.co.uk wrote: Hi, I am using oauth and EPItwitter and I cannot get a decent response from users/lookup. I keep on getting 401 Unauthorized when with the same instance I can get any other method to work fine. I tried navigating in the browser to http://api.twitter.com/1/users/lookup.json?screen_names=screen_name=d... and that is giving me a 404 I am not sure if I am fighting an api problem or an issue with EPITwitter. Kind Regards Darren -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Logical AND supported in streaming API filter endpoint
When we can squeeze it in and after we understand various cost issues. On Fri, Apr 23, 2010 at 5:52 AM, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: When will we get - aka not? On Monday, April 19, 2010, Mark McBride mmcbr...@twitter.com wrote: To date the streaming API has only supported logical OR in track keywords (http://apiwiki.twitter.com/Streaming-API-Documentation#track). Today we're happy to announce that we support logical ANDing in production as well. The track parameter is treated as a series of phrases. Phrases are separated by commas. Words within phrases are delimited by spaces. A tweet matches if any phrase matches. A phrase matches if all of the words are present in the tweet. (e.g. 'the twitter' is 'the' AND 'twitter', and 'the,twitter' is 'the' OR 'twitter'.). Some examples... 1) twitter api,twitter streaming (http://stream.twitter.com/1/statuses/filter.xml?track=twitter+api%2Ctwitter+streaming) will match the tweets The Twitter API is awesome and The twitter streaming deal is fast, but not I'm new to Twitter 2) The same approach to dealing with case, punctuation, @replies and hashtags still applies. So chirp search,chirp streaming (http://stream.twitter.com/1statuses/filter.xml?track=chirp+search%2Cchirp+streaming) will match Listening to the @chirp talk on search, I'm at Chirp talking about search!, and loving this search talk #chirp This should dramatically close the gap on what you can do with the search API but not with streaming, and also reduce the amount of data users have to consumer to match on multiple keywords. Comments/questions welcome as always. ---Mark http://twitter.com/mccv -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] 401 Unauthorized with oauth gem
Did anything change in the API (couldn't find anything in the API changelog) that would make all new users who are associating their Twitter acounts to my app get a 401 on status update? All accounts up to a few days ago are still working, newer ones get 401 using absolutely the same codebase and the oauth gem (Ruby) version 0.3.6. Kinda hard to debug. Cheers, -Fabio. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] OAuth credentials for test
Hi, I'am developing OAuth support for my Java API, however, I am needing a consumer key and secret in order to test it. Should I register my API to get them or there is a key/secret available for test purpose that I could use? Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Anyone else experiencing errors from /oauth/access_token?
I'm getting Invalid / expired Token when doing a basic OAuth login using EpiTwitter that's worked perfectly every time in the past yet all of a sudden last night stopped working and has yet to work again. Regenerating the tokens or indeed registering a new app doesn't work and there's no notices anywhere that it's been suspended. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] My applications were Suspended
My applications were suspended and none from twitter has given me a reason as to why. Can someone help me out. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] statuses/show.json: profile_background_image_url erroneously populated for users with the background image disabled.
In results from statuses/show.json, the user data returned sometimes contains a 'profile_background_image_url' for users that have chosen to turn off the background image on their profile. I've made an app that attempts to mimic the user's profile design as closely as possible and this is causing acute ugliness in some cases. e.g. http://www.exquisitetweets.com/tweets?ids=10795543407.10795729981.10796641044.10797050988.10797098108.10796710716.10797057786.10797742374 You'll notice that tweets from the user ru show the default theme's cloudy background, while on his profile the background image is hidden: http://twitter.com/ru It would be great if the API could either return an empty profile_background_image_url field in this case or provide an extra profile_background_image_hidden boolean field to indicate whether they've chosen to hide the image in their design settings. Thanks. - James -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] @anywhere - Flash
Hi, really enthused to see Twitter implementing @anywhere. Does anyone know if this will be compatible with Flash/Actionscript APIs? I'm hoping there will be a simple call you can make to convert http:// URLs and @username URLs to clickable links as using RegEx is a royal pain! -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] 401 Unauthorised - Unable to post
Hi all! I am having an issue with one of my apps. I set it up correctly I think, when I do tests through the API console on http://dev.twitter.com/console, it posts just fine, and my app has read/write access level. However on my site, whenever I try to post a new tweet, the tweet process seems to go without any error messages, but nothing gets posted on my twitter account. I have checked it with Firebug, there is in fact an error, I get a 401 Unauthorised status for https://api.twitter.com/1/statuses/update.json. It says Read-only application cannot POST. I consequently changed my app settings, and indeed it was read only at first, but even after changing it to read/write, the problem remains. Any idea where it could come from? What can I do to solve the issue? Thank you! -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Testing Twitter API webapps
Hi, How do you folks test your Twitter apps before uploading them to your hosting servers? Doesn't the Twitter callback URL have to be a valid website? How can we test locally? Thanks, kaps -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Questions about location-based queries
I am interested in gathering tweets from a particular geographic region - currently Nigeria. Initially I ran queries that used the coordinates of Abuja, the capital, and asked for tweets within 400 miles. This covers most of the country save the the far northeastern corner of the country. This gave me 5-6K tweets a day. Since Nigeria has just reached 1M Facebook users, and taking that as an indicator, I expected much more data. Next I tried a query that asked for tweets within 50 miles of Lagos, the largest city in Nigeria - with a population of over 9 million - and I got 12-15K tweets a day. A query asking for tweets within 10 miles of Lagos gave me 5k tweets a day. Both these numbers still seem low, but an improvement nonetheless. Lagos was within the 400 mile radius around Abuja, so it's interesting the query at the higher resolution gave me less data while going from 10 to 50 miles gave me more data. Currently I'm querying a number of the larger cities in Nigeria, in each case using a radius of 40-50 miles, and am getting 30K tweets a day. I'm assuming that I am still missing a lot of data. My questions: How does radius effect the query? 400 miles was clearly too wide a radius. 50 miles gave me more tweets than using 400 miles, but dropping to 10 miles gave me fewer. Any explanations for this behavior? Secondly, what is the best way get get tweets from a region. I'm not convinced I am going about it in the best way. Third, is there ground truth data for the number of Twitter users and tweet-rate by country. It would be great to know just how many tweets per day to expect. My queries page for 15 pages at 100 tweets a page and I stop paging if I get no new tweets. I then wait for a period of time, 10 minutes for Lagos and Abuja, and hour for more sparsely populated locations. I then start paging again with the since_id argument set to the id of the last tweet I got. There may be some tweeking I can do to the wait times, but I would expect that it would only provide marginal benefit. Thanks, Clay -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] posting twitter updates using oauth and java question
Hello, I'm trying to post to the twitter update status api using oauth and I'm getting a 401 without any other error information. I'm posting to http://api.twitter.com/1/statuses/update.xml with a parameter of status=testing twitter! and a access token and access secret generated by twitter/oauth. I've tried generating new tokens both for the twitter application and the twitter user account. I feel everything is valid, any ideas? ?xml version = 1.0 encoding=UTF-8? hash request/1/statuses/update.xml/request errorCould not authenticate you./error /hash http request is: HTTP request = POST /1/statuses/update.xml Content-Type: application/x-www-form-urlencoded User-Agent: Jakarta Commons-HttpClient/3.1 Host: api.twitter.com Content-Length: 277 status=testing%20Twitter %21oauth_token=sWtx2nmAyBaFLzh5WbR6gGRHV9KjF7TFnioJCt87ubsoauth_consumer_key=Xc8W0rJuwkLPdfTngewBgoauth_signature_method=HMAC- SHA1oauth_timestamp=1271968710oauth_nonce=162012765462908oauth_version=1.0oauth_signature=KrLsQjVHUKoZHVPgAaKCqSXLdDI %3D response is: HTTP response = HTTP/1.1 401 Unauthorized Date: Thu, 22 Apr 2010 20:38:33 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API X-Runtime: 0.00163 Content-Type: application/xml; charset=utf-8 Content-Length: 143 Cache-Control: no-cache, max-age=1800 Set-Cookie: guest_id=127196871321167215; path=/; expires=Sat, 22 May 2010 20:38:33 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCPxJPicoAToHaWQiJTg1ZjE0YzNmYjMyZjFm %250AZjM3MTdmNDM3MTAxNGEyODI5IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--4b722ac7a438e73c757947649e1d189f1fc9f29a; domain=.twitter.com; path=/ Expires: Thu, 22 Apr 2010 21:08:33 GMT Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/1/statuses/update.xml/request errorCould not authenticate you./error /hash -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Mutual Friendship
Hi all! I am trying to retrieve a list of users that i follow but that are not me following back i am using http://www.twitter.com/statuses/friends.xml and using ex : http://twitter.com/friendships/exists.xml?user_a=73510797user_b=19001589 that would work but seem like many requests and i would hit the rate limit quickly on big accounts. what would be the proper way to do this cheers! Sam -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Status Update Limit Check
I did a search around to see if I could find a similiar thread asking what I am, but I'm having a hard time putting together the correct search keywords for this. I'm developing a twitter bot and plan to implement some features in the bot itself, and others in a web application. The bot and web application will use the same database to keep in sync. The features I plan to add would potentially increase the status update rate for my bot. If these events occur, I would transition those features to the web app instead. However, I don't see a way to check against the status update limit short of keeping track locally. It seems that the 1000 tweet limit is further broken down into some unknown number. Is there any way to check against the update limit so I know to throttle my bot and modify my code? I'd rather not keep hitting the API limit through HTTP errors and potentially get my bot in trouble. Also, I've seen a limit on duplicate content for not just the last tweet, but x tweets back as well. I normally get around this by adding randomization to my bots tweets, which has worked pretty well, but I'm curious as to why the x tweets back isn't clearly defined somewhere. If these questions are already answered somewhere I appologize ahead of time, Once again I tried a few search keywords and didn't come up with much. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] OAuth credentials for test
Hi Ernandes, Yes, you should register an application at http://dev.twitter.com/apps Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 12:37 PM, Ernandes Jr. ernan...@gmail.com wrote: Hi, I'am developing OAuth support for my Java API, however, I am needing a consumer key and secret in order to test it. Should I register my API to get them or there is a key/secret available for test purpose that I could use? Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Mutual Friendship
Get the 2 relevant lists from the server, then perform the array comparison locally. Friends http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friends%C2%A0ids Followers http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-followers%C2%A0ids On Thu, Apr 22, 2010 at 2:39 PM, so.wakooz wakooz.montr...@gmail.com wrote: Hi all! I am trying to retrieve a list of users that i follow but that are not me following back i am using http://www.twitter.com/statuses/friends.xml and using ex : http://twitter.com/friendships/exists.xml?user_a=73510797user_b=19001589 that would work but seem like many requests and i would hit the rate limit quickly on big accounts. what would be the proper way to do this cheers! Sam -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Oauth thrue Fsockopen
Hello, i am trying to implement the oauth authentication on twitter, but using fsockopen instead of the curl libraries i found on the web. . i could get token and working key for my app, and for 1 account. (i tested them with the curl api), but i always have the message Something is technically wrong. as a respons. i guess the authentication is ok, but i am not sure of it. Could anyone help ? thanks by advance -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: posting twitter updates using oauth and java question
You could try ordering your request parameters. I know that isn't required for the oauth spec, but I remember having to do that with a problem I was facing when making oauth requests where I'd get a 401: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7301cc9b210f585a/9cd5a6d47477ecc4. On Apr 22, 3:45 pm, colin gray cgswts...@gmail.com wrote: Hello, I'm trying to post to the twitter update status api using oauth and I'm getting a 401 without any other error information. I'm posting tohttp://api.twitter.com/1/statuses/update.xmlwith a parameter of status=testing twitter! and a access token and access secret generated by twitter/oauth. I've tried generating new tokens both for the twitter application and the twitter user account. I feel everything is valid, any ideas? ?xml version = 1.0 encoding=UTF-8? hash request/1/statuses/update.xml/request errorCould not authenticate you./error /hash http request is: HTTP request = POST /1/statuses/update.xml Content-Type: application/x-www-form-urlencoded User-Agent: Jakarta Commons-HttpClient/3.1 Host: api.twitter.com Content-Length: 277 status=testing%20Twitter %21oauth_token=sWtx2nmAyBaFLzh5WbR6gGRHV9KjF7TFnioJCt87ubsoauth_consumer_key=Xc8W0rJuwkLPdfTngewBgoauth_signature_method=HMAC- SHA1oauth_timestamp=1271968710oauth_nonce=162012765462908oauth_version=1.0oauth_signature=KrLsQjVHUKoZHVPgAaKCqSXLdDI %3D response is: HTTP response = HTTP/1.1 401 Unauthorized Date: Thu, 22 Apr 2010 20:38:33 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API X-Runtime: 0.00163 Content-Type: application/xml; charset=utf-8 Content-Length: 143 Cache-Control: no-cache, max-age=1800 Set-Cookie: guest_id=127196871321167215; path=/; expires=Sat, 22 May 2010 20:38:33 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCPxJPicoAToHaWQiJTg1ZjE0YzNmYjMyZjFm %250AZjM3MTdmNDM3MTAxNGEyODI5IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--4b722ac7a438e73c757947649e1d189f1fc9f29a; domain=.twitter.com; path=/ Expires: Thu, 22 Apr 2010 21:08:33 GMT Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/1/statuses/update.xml/request errorCould not authenticate you./error /hash -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: 401 Unauthorised - Unable to post
Did you acquire a new token before trying to post again? I'm not positive, but if you didn't, it may be that the old token only had read permissions and didn't get updated to read/write when you changed your settings. On Apr 23, 7:17 am, Jeremy jehe...@gmail.com wrote: Hi all! I am having an issue with one of my apps. I set it up correctly I think, when I do tests through the API console onhttp://dev.twitter.com/console, it posts just fine, and my app has read/write access level. However on my site, whenever I try to post a new tweet, the tweet process seems to go without any error messages, but nothing gets posted on my twitter account. I have checked it with Firebug, there is in fact an error, I get a 401 Unauthorised status forhttps://api.twitter.com/1/statuses/update.json. It says Read-only application cannot POST. I consequently changed my app settings, and indeed it was read only at first, but even after changing it to read/write, the problem remains. Any idea where it could come from? What can I do to solve the issue? Thank you! -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] My applications were Suspended
Take a look at our API Guidelines and see if there's anything your application may have been doing that could have been construed as not being in the spirit of the rules. http://bit.ly/twitter-api-terms Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 12:51 PM, Revabad lookst...@gmail.com wrote: My applications were suspended and none from twitter has given me a reason as to why. Can someone help me out. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
RE: [twitter-dev] My applications were Suspended
Yep Taylor yet again proving you are the antithesis of a developer advocate. From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Taylor Singletary Sent: Friday, April 23, 2010 10:08 AM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] My applications were Suspended Take a look at our API Guidelines and see if there's anything your application may have been doing that could have been construed as not being in the spirit of the rules. http://bit.ly/twitter-api-terms Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 12:51 PM, Revabad lookst...@gmail.com wrote: My applications were suspended and none from twitter has given me a reason as to why. Can someone help me out. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] My applications were Suspended
That's about as useful as those blank e-mails twitter sent out rejecting whitelist applications. Doesn't Twitter record the reason _why_ they suspend the application in the first place? On 4/23/2010 8:07 AM, Taylor Singletary wrote: Take a look at our API Guidelines and see if there's anything your application may have been doing that could have been construed as not being in the spirit of the rules. http://bit.ly/twitter-api-terms Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 12:51 PM, Revabad lookst...@gmail.com mailto:lookst...@gmail.com wrote: My applications were suspended and none from twitter has given me a reason as to why. Can someone help me out. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] My applications were Suspended
You've got to start somewhere. We all have an M.O. My first M.O. is to help people see how they can help themselves. If they're still at a loss we'll take it to the next level. We're all trying to work to scale here folks. I'm happy to look up possible reasons an app got suspended if provided enough information to do so and explicitly asked to do so. I consider your application details private and will not look them up with permission. Useful details to provide: name of the application, name of the Twitter user associated with the application, application ID (if known). But as a general rule -- the reason applications get suspended is because they violated something in our guidelines or terms of service, which aren't impenetrable by any means. Taylor On Fri, Apr 23, 2010 at 7:24 AM, John Meyer john.l.me...@gmail.com wrote: That's about as useful as those blank e-mails twitter sent out rejecting whitelist applications. Doesn't Twitter record the reason _why_ they suspend the application in the first place? On 4/23/2010 8:07 AM, Taylor Singletary wrote: Take a look at our API Guidelines and see if there's anything your application may have been doing that could have been construed as not being in the spirit of the rules. http://bit.ly/twitter-api-terms Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 12:51 PM, Revabad lookst...@gmail.com mailto:lookst...@gmail.com wrote: My applications were suspended and none from twitter has given me a reason as to why. Can someone help me out. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: 401 Unauthorised - Unable to post
Trying to track this bug down. Will update the thread when we've figured it out or otherwise. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Apr 23, 2010 at 7:06 AM, Berto mstbe...@gmail.com wrote: Did you acquire a new token before trying to post again? I'm not positive, but if you didn't, it may be that the old token only had read permissions and didn't get updated to read/write when you changed your settings. On Apr 23, 7:17 am, Jeremy jehe...@gmail.com wrote: Hi all! I am having an issue with one of my apps. I set it up correctly I think, when I do tests through the API console onhttp:// dev.twitter.com/console, it posts just fine, and my app has read/write access level. However on my site, whenever I try to post a new tweet, the tweet process seems to go without any error messages, but nothing gets posted on my twitter account. I have checked it with Firebug, there is in fact an error, I get a 401 Unauthorised status forhttps://api.twitter.com/1/statuses/update.json. It says Read-only application cannot POST. I consequently changed my app settings, and indeed it was read only at first, but even after changing it to read/write, the problem remains. Any idea where it could come from? What can I do to solve the issue? Thank you! -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] My applications were Suspended
On 4/23/2010 8:39 AM, Taylor Singletary wrote: You've got to start somewhere. We all have an M.O. My first M.O. is to help people see how they can help themselves. If they're still at a loss we'll take it to the next level. We're all trying to work to scale here folks. I'm happy to look up possible reasons an app got suspended if provided enough information to do so and explicitly asked to do so. I consider your application details private and will not look them up with permission. Useful details to provide: name of the application, name of the Twitter user associated with the application, application ID (if known). But as a general rule -- the reason applications get suspended is because they violated something in our guidelines or terms of service, which aren't impenetrable by any means. And the reason why people get kicked out of clubs is because they violate the rules--but at least they are provided the name of the rule that they violated in the first place. If somebody is provided with a ticket and a fine for violating traffic rules, the court doesn't just point them to the law library and tell them figure it out yourself. The rules aren't impenetrable by any means. And who are you advocating for, the developer or Twitter? At the very least I would expect you to say on the first e-mail, give me your app information and I'll check it out. In the meantime check out the API and try to see what could have possibly caused the suspension. as opposed to reversing it and only putting out the last part when you are called on it. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] What's Twitter policy regarding porn?
Hello! I have to know this: first off all, there are lots of tweets out there that send links to porn images and stuff like that. Is this allowed? Second, if this is allowed, then can I develop an app that aggregates such tweets (that have links to porn images?) as well as sending out tweets that will include links to porn images? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] What's Twitter policy regarding porn?
On 4/23/2010 9:10 AM, Dmitri Snytkine wrote: I have to know this: first off all, there are lots of tweets out there that send links to porn images and stuff like that. Is this allowed? The only thing I see is here: http://help.twitter.com/entries/18311#spam *Pornography: You may not use obscene or pornographic images in either your profile picture or user background. So as long as it's not in either one of those areas I don't see a direct violation in the rules right now. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
So no one else would find this useful? On Apr 20, 12:34 pm, Orian Marx (@orian) or...@orianmarx.com wrote: I think it would be incredibly helpful to have an endpoint where we could request direct messages sent back and forth between an authorized user and some other user. This would make it significantly easier to allow users to move backward through conversations with a single user. Right now the only alternative is potentially making lots of calls to direct_messages and direct_messages/sent hoping to come across dms specific to that one user. I imagine this endpoint would look like this: url:http://api.twitter.com/1/direct_messages/between.xml(json) parameters: * user_id. Specifies the ID of the user whose private conversations with the authenticated user should be returned. * screen_name. Specifies the screen name of the user whose private conversations with the authenticated user should be returned. * since_id. Optional. Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. * max_id. Optional. Returns only statuses with an ID less than (that is, older than) or equal to the specified ID. * count. Optional. Specifies the number of direct messages to retrieve. May not be greater than 200. * page. Optional. Specifies the page of direct messages to retrieve. It would also be helpful to have an endpoint that retrieved new dms sent or received since some id, instead of having to make calls to two endpoints as we currently do, but I imagine user streams probably covers this need. @orian -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: User Stream's API usage
Being able to retrieve a list of unfollows a user performed since some point in time would be hugely valuable for anyone trying to maintain an up-to-date record of a user's connections without regularly having to refetch all the ids. Is there any way this could be accomplished, perhaps as a REST endpoint? On Apr 21, 5:00 pm, Mark McBride mmcbr...@twitter.com wrote: We likely won't send down the unfollows in the short term, for reasons outlined previously. It's not that we won't *ever* do it, but it's delicate. On the user profile changes, that does seem like a good idea. No promises, but I'll look at what we can do. The highest priorities we have right now are 1) Getting the formatting of messages locked down 2) Getting list activity in (lists created/deleted/modified, users added to lists, etc.) ---Mark http://twitter.com/mccv On Wed, Apr 21, 2010 at 1:30 PM, Cameron Kaiser spec...@floodgap.com wrote: Also, unfollows should be treated the same as follows. I know its sad when an unfollow happens, but this is important information too. I disagree. I think unfollows should be totally without penalty, and making them visible/exposed could depending on the situation assign them a very heavy social penalty. Qwitter comes to mind. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- EH! STEVE! --- -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Apr 23, 2010 at 8:32 AM, Orian Marx (@orian) or...@orianmarx.comwrote: So no one else would find this useful? On Apr 20, 12:34 pm, Orian Marx (@orian) or...@orianmarx.com wrote: I think it would be incredibly helpful to have an endpoint where we could request direct messages sent back and forth between an authorized user and some other user. This would make it significantly easier to allow users to move backward through conversations with a single user. Right now the only alternative is potentially making lots of calls to direct_messages and direct_messages/sent hoping to come across dms specific to that one user. I imagine this endpoint would look like this: url:http://api.twitter.com/1/direct_messages/between.xml(json) parameters: * user_id. Specifies the ID of the user whose private conversations with the authenticated user should be returned. * screen_name. Specifies the screen name of the user whose private conversations with the authenticated user should be returned. * since_id. Optional. Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. * max_id. Optional. Returns only statuses with an ID less than (that is, older than) or equal to the specified ID. * count. Optional. Specifies the number of direct messages to retrieve. May not be greater than 200. * page. Optional. Specifies the page of direct messages to retrieve. It would also be helpful to have an endpoint that retrieved new dms sent or received since some id, instead of having to make calls to two endpoints as we currently do, but I imagine user streams probably covers this need. @orian -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] What's Twitter policy regarding porn?
This is the correct interpretation of the rule surrounding porn, in addition to all other Twitter rules regarding statuses, mentions, direct messages, automation, etc. One such rule that would apply here is that you don't want to surprise users -- porn links should be clearly marked as such. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Apr 23, 2010 at 8:22 AM, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 9:10 AM, Dmitri Snytkine wrote: I have to know this: first off all, there are lots of tweets out there that send links to porn images and stuff like that. Is this allowed? The only thing I see is here: http://help.twitter.com/entries/18311#spam *Pornography: You may not use obscene or pornographic images in either your profile picture or user background. So as long as it's not in either one of those areas I don't see a direct violation in the rules right now. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
On 4/23/2010 9:39 AM, Taylor Singletary wrote: Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod Do we want one endpoint or two endpoints, one for all direct messages sent to a particular account and one for all direct messages sent from a particular user (maybe a filter on the current direct messages endpoint, perhaps)? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: User Stream's API usage
The utility of various use cases has to be balanced with the overall Twitter experience that affects every Twitter user. I'd guess that the product team is generally going to bias away from exposing unfollows to the population at large, while not restricting unfollow discovery from motivated parties. Also, the product team will, just as in any company, always bias towards building features that affect the population at large. So, these features fall into the null intersection of these two disjoint sets. Given competing priorities, little is likely to be done here unless there was a huge efficiency gain to be had somewhere... -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Apr 23, 2010 at 8:39 AM, Orian Marx (@orian) or...@orianmarx.com wrote: Being able to retrieve a list of unfollows a user performed since some point in time would be hugely valuable for anyone trying to maintain an up-to-date record of a user's connections without regularly having to refetch all the ids. Is there any way this could be accomplished, perhaps as a REST endpoint? On Apr 21, 5:00 pm, Mark McBride mmcbr...@twitter.com wrote: We likely won't send down the unfollows in the short term, for reasons outlined previously. It's not that we won't *ever* do it, but it's delicate. On the user profile changes, that does seem like a good idea. No promises, but I'll look at what we can do. The highest priorities we have right now are 1) Getting the formatting of messages locked down 2) Getting list activity in (lists created/deleted/modified, users added to lists, etc.) ---Mark http://twitter.com/mccv On Wed, Apr 21, 2010 at 1:30 PM, Cameron Kaiser spec...@floodgap.com wrote: Also, unfollows should be treated the same as follows. I know its sad when an unfollow happens, but this is important information too. I disagree. I think unfollows should be totally without penalty, and making them visible/exposed could depending on the situation assign them a very heavy social penalty. Qwitter comes to mind. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- EH! STEVE! --- -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Anyone else experiencing errors from /oauth/access_token?
Solved it now. On Apr 22, 7:01 pm, 46Bit m...@46bit.com wrote: I'm getting Invalid / expired Token when doing a basic OAuth login using EpiTwitter that's worked perfectly every time in the past yet all of a sudden last night stopped working and has yet to work again. Regenerating the tokens or indeed registering a new app doesn't work and there's no notices anywhere that it's been suspended. -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Using @anywhere and the Twitter Search Widget
I'm getting this error when I try to use an @anywhere tweetbox and the twitter search widget on the same page. Can anyone shed some light? Unsafe JavaScript attempt to access frame with URL https://api.twitter.com/xd_receiver.html from frame with URL about:blank. Domains, protocols and ports must match. Thanks! -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Good to hear. I've got more coming... :) On Apr 23, 11:39 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Apr 23, 2010 at 8:32 AM, Orian Marx (@orian) or...@orianmarx.comwrote: So no one else would find this useful? On Apr 20, 12:34 pm, Orian Marx (@orian) or...@orianmarx.com wrote: I think it would be incredibly helpful to have an endpoint where we could request direct messages sent back and forth between an authorized user and some other user. This would make it significantly easier to allow users to move backward through conversations with a single user. Right now the only alternative is potentially making lots of calls to direct_messages and direct_messages/sent hoping to come across dms specific to that one user. I imagine this endpoint would look like this: url:http://api.twitter.com/1/direct_messages/between.xml(json) parameters: * user_id. Specifies the ID of the user whose private conversations with the authenticated user should be returned. * screen_name. Specifies the screen name of the user whose private conversations with the authenticated user should be returned. * since_id. Optional. Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. * max_id. Optional. Returns only statuses with an ID less than (that is, older than) or equal to the specified ID. * count. Optional. Specifies the number of direct messages to retrieve. May not be greater than 200. * page. Optional. Specifies the page of direct messages to retrieve. It would also be helpful to have an endpoint that retrieved new dms sent or received since some id, instead of having to make calls to two endpoints as we currently do, but I imagine user streams probably covers this need. @orian -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
I've actually never understood the value of having two endpoints for sent / received DMs in the first place, as you end up needing to make two calls and then sort everything (if you're trying to show a stream of DM conversations). On Apr 23, 11:57 am, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 9:39 AM, Taylor Singletary wrote: Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod Do we want one endpoint or two endpoints, one for all direct messages sent to a particular account and one for all direct messages sent from a particular user (maybe a filter on the current direct messages endpoint, perhaps)? -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
On 4/23/2010 10:58 AM, Orian Marx (@orian) wrote: f having two endpoints for sent / received DMs in the first place, as you end up needing to make two calls and then sort everything (if you're trying to show a stream of DM conversations). But if you're not making them into a conversation it makes more sense (i.e. a history). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] [Feature Request] friends/screen_names and followers/screen_names
It would be useful to have endpoints for retrieving user screen names 5000 at a time just like with friends/ids and followers/ids. The primary use case I see for this is for twitter clients to be able to easily provide screen name auto-complete based on a user's connections (without having to load up the full user objects using statuses/ friends and statuses/followers). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Sure, yeah. But I would argue that DMs make more sense to be viewed by default as a stream of back and forth messages vs a separate history of sent and history of received. I would say it makes more sense to offer it as one endpoint to be split client side rather than two endpoints to be merged client side. Of course, the current situation is they are split and I'm sure there is some historical reason for that and I wouldn't expect it to be changed. But in terms of a new endpoint specifically for retrieving a history of conversation with a particular user I don't really see what the benefit would be of serving it up split (to the consuming application). On Apr 23, 1:04 pm, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 10:58 AM, Orian Marx (@orian) wrote: f having two endpoints for sent / received DMs in the first place, as you end up needing to make two calls and then sort everything (if you're trying to show a stream of DM conversations). But if you're not making them into a conversation it makes more sense (i.e. a history). -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Testing Twitter API webapps
Yes, Twitter requires a callback URL. Make a test page to display (or save to file) your oAuth tokens. Embed those tokens into your local test page (and remove that helpful test page on hosted server). Develop locally, and add if-then blocks, depending if you are local or remote. That way, you can develop locally, and upload same file, as it will work for the remote as well. When remote, instead of saved tokens, use the live tokens from the handshake process. ~PK On Fri, Apr 23, 2010 at 7:13 AM, kaps kap...@yahoo.com wrote: Hi, How do you folks test your Twitter apps before uploading them to your hosting servers? Doesn't the Twitter callback URL have to be a valid website? How can we test locally? Thanks, kaps -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: My applications were Suspended
My name is Brian Truebe and I am on the API Policy team, when apps are suspended they are sent a notice as to how to contest the suspension, however this may have gotten lost in the tubes. Please email a...@twitter.com and let us know the app name and we'll see if we can sort this out. Sorry for the inconvenience. Regards, Brian On Apr 22, 12:51 pm, Revabad lookst...@gmail.com wrote: My applications were suspended and none from twitter has given me a reason as to why. Can someone help me out. -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Testing Twitter API webapps
You can use a callback URL like the following to develop locally. http://dev.local:3000/authenticated Then put your dev, stage, prod callback URLs in a config. Your app should work the same regardless of the server/environment it is running on. I also have different twitter accounts for dev/stage and prod. My prod twitter account is http://twitter.com/imby while dev stage are http://twitter.com/imbyTest That way the @imby lists and feed does not contain test tweets and whatnot. Again, this is contained in a config file so that prod = @imby and everything else = @imbyTest On Fri, Apr 23, 2010 at 12:19 PM, Patrick Kennedy kenned...@gmail.com wrote: Yes, Twitter requires a callback URL. Make a test page to display (or save to file) your oAuth tokens. Embed those tokens into your local test page (and remove that helpful test page on hosted server). Develop locally, and add if-then blocks, depending if you are local or remote. That way, you can develop locally, and upload same file, as it will work for the remote as well. When remote, instead of saved tokens, use the live tokens from the handshake process. ~PK On Fri, Apr 23, 2010 at 7:13 AM, kaps kap...@yahoo.com wrote: Hi, How do you folks test your Twitter apps before uploading them to your hosting servers? Doesn't the Twitter callback URL have to be a valid website? How can we test locally? Thanks, kaps -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- imby - in my back yard An Experiment in Local Professional Networking http://madison.imby.info/p/Philip.Crawford
Re: [twitter-dev] Re: My applications were Suspended
On 4/23/2010 10:58 AM, Brian Truebe wrote: My name is Brian Truebe and I am on the API Policy team, when apps are suspended they are sent a notice as to how to contest the suspension, however this may have gotten lost in the tubes. Please email a...@twitter.com and let us know the app name and we'll see if we can sort this out. Sorry for the inconvenience. Regards, Brian One question: does the e-mail have an explanation about why the application was suspended in the first place (you mention how to contest the suspension but nothing about what the suspension is about). And is there some way to create a sandbox for suspended apps where they can re-test to see if they are in compliance with the rules before going out into the real world Twitterverse? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: My applications were Suspended
Yes, the email that is sent out after an application is suspended does explain possible rule violations. This email is sent to the account that registered the application, so if you've registered an app with an auxiliary account not tied to an email address you check regularly then an app suspension may come as a rather unfortunate surprise. While there is no sandbox, we're very open to discussing any concerns an app developer may have while they develop their app. The best course of action is to read the rules first while developing. If you're still worried a feature you're developing may result in your users being suspended our your entire app being suspended then you can always email us at a...@twitter.com and we'll be happy to work with you to ensure the longevity of your application. I hope this helps. -Brian On Apr 23, 11:37 am, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 10:58 AM, Brian Truebe wrote: My name is Brian Truebe and I am on the API Policy team, when apps are suspended they are sent a notice as to how to contest the suspension, however this may have gotten lost in the tubes. Please email a...@twitter.com and let us know the app name and we'll see if we can sort this out. Sorry for the inconvenience. Regards, Brian One question: does the e-mail have an explanation about why the application was suspended in the first place (you mention how to contest the suspension but nothing about what the suspension is about). And is there some way to create a sandbox for suspended apps where they can re-test to see if they are in compliance with the rules before going out into the real world Twitterverse? -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Counts
I was wondering if there is a better way to get a total number of tweets on a search string than using the search API and then paging through the tweets. I am interested in getting the total number of tweets for a topic since a particular time, generally the time of my last update, but it appears the only way to get a count is to page through the results, which would just lead to a ton of requests, instead of being able to just get an aggregate count in one api call. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Counts
There's not a good way to accomplish this right now. Search API doesn't represent the full body of tweets for a given query -- it goes back only a few days and excludes tweets from accounts identified as spam and otherwise. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Apr 23, 2010 at 11:24 AM, DagoochGuy sponsor.dago...@gmail.comwrote: I was wondering if there is a better way to get a total number of tweets on a search string than using the search API and then paging through the tweets. I am interested in getting the total number of tweets for a topic since a particular time, generally the time of my last update, but it appears the only way to get a count is to page through the results, which would just lead to a ton of requests, instead of being able to just get an aggregate count in one api call. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: My applications were Suspended
On 4/23/2010 1:28 PM, Brian Truebe wrote: Yes, the email that is sent out after an application is suspended does explain possible rule violations. This email is sent to the account that registered the application, so if you've registered an app with an auxiliary account not tied to an email address you check regularly then an app suspension may come as a rather unfortunate surprise. That's still a bit of a head-scratcher. You said possible rule violations. Does this mean that the actual reason why the application was suspended is point out, or does it mean that there's just a link back to the terms of service? As a Developer if my app went over some limits and got cut off I'd like to know what limits they went over (actually what I really would like to know is the specific time and place so I could nail down the problem myself, but I'll just settle for the specific reason). While there is no sandbox, we're very open to discussing any concerns an app developer may have while they develop their app. The best course of action is to read the rules first while developing. If you're still worried a feature you're developing may result in your users being suspended our your entire app being suspended then you can always email us at a...@twitter.com and we'll be happy to work with you to ensure the longevity of your application. I hope this helps. -Brian While that's nice for things that may be forward looking, a lot of us as developers know that bugs are a lot clearer in hind-sight then in foresight, which is a given. After all if we could see our bugs in foresight chances are those bugs wouldn't happen. And cutting off the application completely really doesn't give us a way to reintroduce the app and fix any bugs that we may have introduced accidentally short of a long conversation to prove to you guys that we really aren't spammers or shady characters in black hats. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: My applications were Suspended
Hey Brian - Why don't you guys eat your own dog food and use Direct Messaging to the account that registered the app instead of email ? That way, you have some sort of audit trail for the notifications, no? When I worked through the issue that I had with one of my apps with you, I hadn't received an email about the original suspension either, or at least not that I could find. BJ On 4/23/2010 3:28 PM, Brian Truebe wrote: Yes, the email that is sent out after an application is suspended does explain possible rule violations. This email is sent to the account that registered the application, so if you've registered an app with an auxiliary account not tied to an email address you check regularly then an app suspension may come as a rather unfortunate surprise. While there is no sandbox, we're very open to discussing any concerns an app developer may have while they develop their app. The best course of action is to read the rules first while developing. If you're still worried a feature you're developing may result in your users being suspended our your entire app being suspended then you can always email us at a...@twitter.com and we'll be happy to work with you to ensure the longevity of your application. I hope this helps. -Brian On Apr 23, 11:37 am, John Meyerjohn.l.me...@gmail.com wrote: On 4/23/2010 10:58 AM, Brian Truebe wrote: My name is Brian Truebe and I am on the API Policy team, when apps are suspended they are sent a notice as to how to contest the suspension, however this may have gotten lost in the tubes. Please email a...@twitter.com and let us know the app name and we'll see if we can sort this out. Sorry for the inconvenience. Regards, Brian One question: does the e-mail have an explanation about why the application was suspended in the first place (you mention how to contest the suspension but nothing about what the suspension is about). And is there some way to create a sandbox for suspended apps where they can re-test to see if they are in compliance with the rules before going out into the real world Twitterverse? -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: My applications were Suspended
On 4/23/2010 2:01 PM, BJ Weschke wrote: Hey Brian - Why don't you guys eat your own dog food and use Direct Messaging to the account that registered the app instead of email ? That way, you have some sort of audit trail for the notifications, no? When I worked through the issue that I had with one of my apps with you, I hadn't received an email about the original suspension either, or at least not that I could find. BJ One thing with that: 140-character tweets are good for a lot of things, but technical explanations of suspensions aren't one of them (unless you link together a web-ticket system with it). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Can our twitter app call /oauth/revoke?
One example where it would be useful: I'm trying to troubleshoot a problem with a currently authorized user. The same token and secret are pulled from Twitter each time during the oAuth process, but any calls to the Twitter API respond with unauthorized. I asked the user to revoke access to my app so that she can start with a fresh token. It would have been better if I could have revoked the access for her. I'd then be able to simply ask her to login to the app again. On Wed, Apr 21, 2010 at 1:55 PM, Dean Collins d...@cognation.net wrote: On Wed, Apr 21, 2010 at 13:32, Caliban Darklock cdarkl...@gmail.com wrote: It may seem stupid to revoke the access, but in a tiny minority of cases it may be clever, and for that reason alone you may want to consider including it. And what are those cases? If I was Twitter I would not provide such a case until some of those cases where presented. Abraham -- You already got provided those exaples you chose to steam roller over them. Basically same response when I said why restrict client apps runnign on desktops to oath if basic auth does the job and as a desktop client doesn’t have the issues of web apps. Parroting the pr spin doesn’t solve the problem. Cheers, Dean -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Multiple Account creation
On 4/23/2010 2:58 PM, Taylor Singletary wrote: Hi Dinho, This is a slippery area. You're correct to use the guidance of past discussions on this topic and the policies in place to determine if you're doing the right thing. The best thing I can tell you is: - make sure each account is useful and contributing valuable content to the ecosystem. valuable content is of course interpretable - don't surprise or annoy users with spam, auto-follows, au...@mentions, auto-dms, etc. - don't use any kind of mechanization to create your users. do it iteratively, by hand. it will take you awhile. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod Couldn't another way to localize without having to create multiple accounts be to add geolocation information to the tweet? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Twitter Stream crossdomain.xml
Its very good to hear, I hope he will be able to adress that soon. yours Martin On 12 Apr., 18:29, Raffi Krikorian ra...@twitter.com wrote: yup - totally :P just giving you an update that its been low on our priority list :P twitter now has a dedicated security manager, so i have just elevated this to his attention. On Mon, Apr 12, 2010 at 9:27 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Totally understood. You shouldn't be relaxing any security on anything you're not convinced will remain secure. Just remember you and I started this conversation six months ago ;) http://groups.google.com/group/twitter-development-talk/browse_frm/th... On Apr 12, 11:43 am, Raffi Krikorian ra...@twitter.com wrote: as i said, unfortunately, i'm not comfortable relaxing the crossdomain file on api.twitter.com until we more carefully analyze our own stack that is running there. we completely agree with your statements here, and we will gladly listen to anybody who wants us to relax the file -- but, you're all preaching to the choir :P we want to relax the file! to be responsible, we need to carefully analyze our stack and write a few test cases first. On Mon, Apr 12, 2010 at 8:34 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off ofwww.twitter.commaliciousFlash code could potentially get at user's cookies from any browser sessions from visitingwww.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy.. .. http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.com wrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service
Re: [twitter-dev] Re: My applications were Suspended
That's a great idea. There's already web ticketing built into a...@twitter.com - put all the details in there and then just drop in a DM Your application has been suspended. Please refer to the following ticket (bit.ly link) for more details. On 4/23/2010 4:22 PM, John Meyer wrote: On 4/23/2010 2:01 PM, BJ Weschke wrote: Hey Brian - Why don't you guys eat your own dog food and use Direct Messaging to the account that registered the app instead of email ? That way, you have some sort of audit trail for the notifications, no? When I worked through the issue that I had with one of my apps with you, I hadn't received an email about the original suspension either, or at least not that I could find. BJ One thing with that: 140-character tweets are good for a lot of things, but technical explanations of suspensions aren't one of them (unless you link together a web-ticket system with it). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Multiple Account creation
A great suggestion, yes. In a world where every Twitter client were geo-aware and provided features that would allow for easy segmentation by area (and the API features to match), I would very much recommend that approach. Much of the discoverability features based on locale are present today. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Apr 23, 2010 at 2:00 PM, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 2:58 PM, Taylor Singletary wrote: Hi Dinho, This is a slippery area. You're correct to use the guidance of past discussions on this topic and the policies in place to determine if you're doing the right thing. The best thing I can tell you is: - make sure each account is useful and contributing valuable content to the ecosystem. valuable content is of course interpretable - don't surprise or annoy users with spam, auto-follows, au...@mentions, auto-dms, etc. - don't use any kind of mechanization to create your users. do it iteratively, by hand. it will take you awhile. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod Couldn't another way to localize without having to create multiple accounts be to add geolocation information to the tweet? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: My applications were Suspended
Brian, It is not unreasonable for developers to hope that Twitter does not suspend applications for could violate rules and possible rule violations. I trust this was just a slip of the tongue on your part. We know you must maintain a good-citizen ecosystem. For that to happen, we really do trust that you suspend applications for actual rule violations, which you can point to as to how and when you discovered those actual violations, and *not* for mere suspicion of rule violations. On Apr 23, 4:28 pm, Brian Truebe truebesu...@gmail.com wrote: Yes, the email that is sent out after an application is suspended does explain possible rule violations. This email is sent to the account that registered the application, so if you've registered an app with an auxiliary account not tied to an email address you check regularly then an app suspension may come as a rather unfortunate surprise. While there is no sandbox, we're very open to discussing any concerns an app developer may have while they develop their app. The best course of action is to read the rules first while developing. If you're still worried a feature you're developing may result in your users being suspended our your entire app being suspended then you can always email us at a...@twitter.com and we'll be happy to work with you to ensure the longevity of your application. I hope this helps. -Brian On Apr 23, 11:37 am, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 10:58 AM, Brian Truebe wrote: My name is Brian Truebe and I am on the API Policy team, when apps are suspended they are sent a notice as to how to contest the suspension, however this may have gotten lost in the tubes. Please email a...@twitter.com and let us know the app name and we'll see if we can sort this out. Sorry for the inconvenience. Regards, Brian One question: does the e-mail have an explanation about why the application was suspended in the first place (you mention how to contest the suspension but nothing about what the suspension is about). And is there some way to create a sandbox for suspended apps where they can re-test to see if they are in compliance with the rules before going out into the real world Twitterverse? -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Status Update Limit Check
Hello Taylor, What's your bot all about? The bot is a character bot for a popular Japanese doujin (not commercially backed, a person makes the game in their spare time and usually sells them at conventions) game. Such bots are highly concentrated throughout the Japanese community, as the writing system they have can say a lot more in 140 characters than with English characters (one word can constitute 2 characters for example). Basically such bots are conversational AI bots. Given certain cues they respond in a certain way. Such responses are sometimes randomized to provide a more dynamic interaction to users. With my current twitter bot, I'm currently working on an AI based system to constitute unsupervised learning and responses based on how the user interacts with the bot. However, because of the status updates imposed, and lack of knowledge on the specific rates, I have to consider how a normal person would operate, and include events such as going to sleep and heading out for a bit. If certain interactions require a larger number of status updates, I planned to have it as a kind of web app that users could continue their conversation with the character, making my worries more about the data storage requirements in the database than status update limits. Other bot creators, however, may not have such elaborate setups due to hosting costs. For them, it's important to be able to scale their both with a large number of followers by being able to throttle status updates as per the twitter requirements. These bot creators wish to stay within the guidelines that twitter provides, but armed only with the knowledge of but the daily limit and receiving HTTP error codes, there is nothing to go off of. On the point of how such bots contribute to the twitter community, because the bot acts as the character itself, it draws fans of the characters into a tighter knit community. Users can look at the bot's follower list and find users with more similiar and focused interests with ease. Such bots will usually produce random non-reply based tweets with the character's lines, giving a topic of discussion for the bot's followers. There are even some users that go so far as to follow nothing but their favorite character's bots. Best Regards, Chris White -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Multiple Account creation
On 4/23/2010 3:08 PM, Taylor Singletary wrote: A great suggestion, yes. In a world where every Twitter client were geo-aware and provided features that would allow for easy segmentation by area (and the API features to match), I would very much recommend that approach. Much of the discoverability features based on locale are present today. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod Even putting a state hashtag at the start #CO, #CA, etc would work. Whatever suggestion you use you probably are going to have to apply for whitelisting. Geolocation tags may have an added bonus of being able to guide job applicants to where they should submit their applications. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Image Tags in Tweets?!
The last few tweets from @twitter feature the #endmalaria hash tag. On some pages, like http://twitter.com/twitter and http://twitter.com/#search?q=%23endmalaria, the hash tag is followed by an image of a mosquito (http:// a1.twimg.com/a/1272044617/images/mosquito.gif) which is hyperlinked to a different page than the hash tag itself. Yet on other pages, like http://twitter.com/twitter/status/12719532503, and in the API (http:// api.twitter.com/1/statuses/show/12719532503.xml), the mosquito image doesn't appear at all. What gives? Is this some kind of annotations test or something totally different? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Image Tags in Tweets?!
On 4/23/2010 3:42 PM, Jonathan Strauss wrote: The last few tweets from @twitter feature the #endmalaria hash tag. On some pages, like http://twitter.com/twitter and http://twitter.com/#search?q=%23endmalaria, the hash tag is followed by an image of a mosquito (http:// a1.twimg.com/a/1272044617/images/mosquito.gif) which is hyperlinked to a different page than the hash tag itself. Yet on other pages, like http://twitter.com/twitter/status/12719532503, and in the API (http:// api.twitter.com/1/statuses/show/12719532503.xml), the mosquito image doesn't appear at all. What gives? Is this some kind of annotations test or something totally different? Well I wouldn't expect that a mosquito image appear on a text xml file, but it appears on the twitter 12719532503 status it appears. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Using @anywhere and the Twitter Search Widget
What is the url of your site? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: My applications were Suspended
Accounts can have DMs notifications turned off and if they don't they will arrive at the same email address. Plus they would probably have to violate the max DMs sent per day limit at some point and would hence not be truly dogfooding. Abraham On Fri, Apr 23, 2010 at 14:01, BJ Weschke bwesc...@btwtech.com wrote: That's a great idea. There's already web ticketing built into a...@twitter.com - put all the details in there and then just drop in a DM Your application has been suspended. Please refer to the following ticket ( bit.ly link) for more details. On 4/23/2010 4:22 PM, John Meyer wrote: On 4/23/2010 2:01 PM, BJ Weschke wrote: Hey Brian - Why don't you guys eat your own dog food and use Direct Messaging to the account that registered the app instead of email ? That way, you have some sort of audit trail for the notifications, no? When I worked through the issue that I had with one of my apps with you, I hadn't received an email about the original suspension either, or at least not that I could find. BJ One thing with that: 140-character tweets are good for a lot of things, but technical explanations of suspensions aren't one of them (unless you link together a web-ticket system with it). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Can our twitter app call /oauth/revoke?
On Wed, Apr 21, 2010 at 13:55, Dean Collins d...@cognation.net wrote: You already got provided those exaples you chose to steam roller over them. Basically same response when I said why restrict client apps runnign on desktops to oath if basic auth does the job and as a desktop client doesn’t have the issues of web apps. Parroting the pr spin doesn’t solve the problem. Cheers, Dean Lets see. The examples given so far are: 1) Google and Facebook do it: Both Facebook and Google provide API calls to revoke a user's access_token/session_key. 2) Consistency: Why would I *not* want to provide our users with a similar flow to remove/revoke this access that they previously granted. 3) And lastly for debugging: It would have been better if I could have revoked the access for her. Although for Shannon's specific example I doubt such a method would be useful as the oauth/revoke API call would probably have just returned unauthorized. As third-party developers we are all welcome to ask Twitter prioritize their man power for API methods we see as adding value. I don't see much value in an oauth/revoke method so I am pushing to be enlightened as to value I don't see. As I said I think https://twitter.com/account/connections#appname as a direct link would be useful for little work on Twitter's part but oauth/revoke would not. Abraham -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] [Feature Request] friends/screen_names and followers/screen_names
I recall his being brought up before and having it left as not being a high priority because of high resource cost. The ids method is pretty easy in all the friends/followers ids would be in a single column but for screen_names you have to get those ids then query the screen_name from another column. Circumstances may have changed though. Abraham On Fri, Apr 23, 2010 at 10:06, Orian Marx (@orian) or...@orianmarx.comwrote: It would be useful to have endpoints for retrieving user screen names 5000 at a time just like with friends/ids and followers/ids. The primary use case I see for this is for twitter clients to be able to easily provide screen name auto-complete based on a user's connections (without having to load up the full user objects using statuses/ friends and statuses/followers). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] statuses/show.json: profile_background_image_url erroneously populated for users with the background image disabled.
There are two related issues: http://code.google.com/p/twitter-api/issues/detail?id=1183 http://code.google.com/p/twitter-api/issues/detail?id=1183 http://code.google.com/p/twitter-api/issues/detail?id=1211 http://code.google.com/p/twitter-api/issues/detail?id=1211Abraham On Thu, Apr 22, 2010 at 14:03, James Wheare ja...@wheare.org wrote: In results from statuses/show.json, the user data returned sometimes contains a 'profile_background_image_url' for users that have chosen to turn off the background image on their profile. I've made an app that attempts to mimic the user's profile design as closely as possible and this is causing acute ugliness in some cases. e.g. http://www.exquisitetweets.com/tweets?ids=10795543407.10795729981.10796641044.10797050988.10797098108.10796710716.10797057786.10797742374 You'll notice that tweets from the user ru show the default theme's cloudy background, while on his profile the background image is hidden: http://twitter.com/ru It would be great if the API could either return an empty profile_background_image_url field in this case or provide an extra profile_background_image_hidden boolean field to indicate whether they've chosen to hide the image in their design settings. Thanks. - James -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] statuses/show.json: profile_background_image_url erroneously populated for users with the background image disabled.
Yeah, this is a sticky one. I have a branch to fix some of the issues around this, but getting it right may take some doing. ---Mark http://twitter.com/mccv On Fri, Apr 23, 2010 at 8:28 PM, Abraham Williams 4bra...@gmail.com wrote: There are two related issues: http://code.google.com/p/twitter-api/issues/detail?id=1183 http://code.google.com/p/twitter-api/issues/detail?id=1211 Abraham On Thu, Apr 22, 2010 at 14:03, James Wheare ja...@wheare.org wrote: In results from statuses/show.json, the user data returned sometimes contains a 'profile_background_image_url' for users that have chosen to turn off the background image on their profile. I've made an app that attempts to mimic the user's profile design as closely as possible and this is causing acute ugliness in some cases. e.g. http://www.exquisitetweets.com/tweets?ids=10795543407.10795729981.10796641044.10797050988.10797098108.10796710716.10797057786.10797742374 You'll notice that tweets from the user ru show the default theme's cloudy background, while on his profile the background image is hidden: http://twitter.com/ru It would be great if the API could either return an empty profile_background_image_url field in this case or provide an extra profile_background_image_hidden boolean field to indicate whether they've chosen to hide the image in their design settings. Thanks. - James -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] users lookup - user missing
From search, and now looking at the page I apparently missed this big warning: Warning: The user ids in the Search API are different from those in the REST API (about the two APIs /API-Overview). This defect is being tracked by Issue 214http://code.google.com/p/twitter-api/issues/detail?id=214. This means that the to_user_id and from_user_id field vary from the actualy user id on Twitter.com. Applications will have to perform a screen name-based lookup with the users/show/Twitter-REST-API-Method%3A-users%C2%A0show method to get the correct user id if necessary. My apologies for wasting your time. --Christopher On Thu, Apr 22, 2010 at 10:12 PM, Mark McBride mmcbr...@twitter.com wrote: The userid for elliottng appears to be 4696. How did you get the 8467 value? ---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 9:52 PM, stumm christop...@stumm.ca wrote: I'm doing a call on users lookup and for some reason it's saying IDs do not exist (for IDs I'd gotten from tweets that I got by doing a search). For example when looking up the user elliottng (who from a quick glance doesn't look like spam). The call I'm making is: http://api.twitter.com/1/users/lookup.json?user_id=8467 Strangely if I do the call with the users screen name, it seems to work. http://api.twitter.com/1/users/lookup.json?screen_name=elliottng Why are these users not showing up when searched by user ID? Thanks, --Christopher -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Verify user connect with @anywhere?
Does anyone have thoughts on this? :) Sorry to bump!
On Apr 15, 9:18 pm, Karate quantumkar...@gmail.com wrote:
I am wanting to use @anywhereto allow users to login to my website,
but I am curious about how to implement proper security.
Right now when a user hits the Connect With Twitter button on my
website and signs in via the popup window, the button changes to say
Connected with Twitter. So far so good.
I can then run things like:
screenName = twitter.currentUser.data('screen_name');
However, I want to be able to send the currentUser's id or twitter
username to my server to log them into my website as well. I want to
check their id/username against my database, and store it if it
doesn't exist, then log them in.
So, the response that I get from running:
twttr.anywhere(onAnywhereLoad);
contains their username/id and some other information, but if I sent
this to my server via javascript to login, there's nothing stopping
someone from making a fake request containing a different username to
login.
WithFacebook'sConnect API I get a cookie set that I can then use
with my secret to verify that the request is really fromFacebook, is
there an equivalent of this in Twitter?
Does this require me to use oAuth?
Again, all I'm trying to do is allow users to sign in to Twitter via
@anywhereon my site then send their username/id to my server to log
them into my application based on that username/id. I just need to be
able to validate that the data being sent to my server (username/id)
was really set by Twitter.
Any thoughts?
Thanks!
--
Subscription
settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] users lookup - user missing
No problem. It's something high on our priority list to get rectified. ---Mark http://twitter.com/mccv On Fri, Apr 23, 2010 at 8:17 PM, Christopher Stumm christop...@stumm.ca wrote: From search, and now looking at the page I apparently missed this big warning: Warning: The user ids in the Search API are different from those in the REST API (about the two APIs). This defect is being tracked by Issue 214. This means that the to_user_id and from_user_id field vary from the actualy user id on Twitter.com. Applications will have to perform a screen name-based lookup with the users/show method to get the correct user id if necessary. My apologies for wasting your time. --Christopher On Thu, Apr 22, 2010 at 10:12 PM, Mark McBride mmcbr...@twitter.com wrote: The userid for elliottng appears to be 4696. How did you get the 8467 value? ---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 9:52 PM, stumm christop...@stumm.ca wrote: I'm doing a call on users lookup and for some reason it's saying IDs do not exist (for IDs I'd gotten from tweets that I got by doing a search). For example when looking up the user elliottng (who from a quick glance doesn't look like spam). The call I'm making is: http://api.twitter.com/1/users/lookup.json?user_id=8467 Strangely if I do the call with the users screen name, it seems to work. http://api.twitter.com/1/users/lookup.json?screen_name=elliottng Why are these users not showing up when searched by user ID? Thanks, --Christopher -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Strange problems with Twitter API
From past few days, I am trying to get the EpiTwitter library work for
me. But, it is behaving in unusually.
I am on Fedora 12 with PHP 5.3.2. It's my development box.
Here are the issues I am facing.
1.When I made a simple script with the method *getAuthenticateUrl* and
accessed it from http://localhost/ , it wasn't working and threw
errors(below) . But when I accidently tried http://127.0.01./ it
worked.
Fatal error: Uncaught exception 'EpiOAuthException' in /var/www/html/
twitter/classes/EpiOAuth.php:397
Stack trace:
#0 /var/www/html/twitter/classes/EpiOAuth.php(367):
EpiOAuthException::raise(Object(EpiCurlManager), false)
#1
/var/www/html/twitter/classes/EpiOAuth.php(39): EpiOAuthResponse-
__get('oauth_token')
#2 /var/www/html/twitter/preview.php(34): EpiOAuth-
getAuthenticateUrl(NULL, Array)
#3 {main}
thrown in /var/www/html/twitter/classes/EpiOAuth.php on line 397
2.After successful authentication, when returned to my script, it
works fine for the first time,when it is actually redirected by
Twitter.But when I refresh the page, it throws the following error -
Fatal error: Uncaught exception 'EpiOAuthUnauthorizedException' in /
var/www/html/twitter/classes/EpiOAuth.php:395
Stack trace:
#0 /var/www/html/twitter/classes/EpiOAuth.php(367):
EpiOAuthException::raise(Object(EpiCurlManager), false)
#1 /var/www/html/twitter/preview.php(48): EpiOAuthResponse-
__get('oauth_token')
#2 {main}
thrown in /var/www/html/twitter/classes/EpiOAuth.php on line 395
Should this be problem with my server or cURL installation? When I
checked phpinfo(), cURL was enabled, but when I had a look in
Configure Command section, I saw this
'--without-curl'
Is there any relation of this with the errors?
Also, I was unable to access the responseText and the try-catch
combination with $e-getMessage(); didn't yeild any results.
Thanks in advance for your help.
Regards,
Kapeel S
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Testing Twitter API webapps
My explaination is more language agnostic, and works for an oauth web flow. But I like your RoR idea, and it sounds like there is support for localhost development to some extent. I suppose /authenticated is the controller. How the terms dev, stage, prod fit into the rails design paradigm is less clear. Can you clarify that or provide a simple example? Thanks for any insights. Patrick On Sat, Apr 24, 2010 at 1:25 AM, philip crawford philipha...@gmail.com wrote: You can use a callback URL like the following to develop locally. http://dev.local:3000/authenticated Then put your dev, stage, prod callback URLs in a config. Your app should work the same regardless of the server/environment it is running on. I also have different twitter accounts for dev/stage and prod. My prod twitter account is http://twitter.com/imby while dev stage are http://twitter.com/imbyTest That way the @imby lists and feed does not contain test tweets and whatnot. Again, this is contained in a config file so that prod = @imby and everything else = @imbyTest On Fri, Apr 23, 2010 at 12:19 PM, Patrick Kennedy kenned...@gmail.com wrote: Yes, Twitter requires a callback URL. Make a test page to display (or save to file) your oAuth tokens. Embed those tokens into your local test page (and remove that helpful test page on hosted server). Develop locally, and add if-then blocks, depending if you are local or remote. That way, you can develop locally, and upload same file, as it will work for the remote as well. When remote, instead of saved tokens, use the live tokens from the handshake process. ~PK On Fri, Apr 23, 2010 at 7:13 AM, kaps kap...@yahoo.com wrote: Hi, How do you folks test your Twitter apps before uploading them to your hosting servers? Doesn't the Twitter callback URL have to be a valid website? How can we test locally? Thanks, kaps -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- imby - in my back yard An Experiment in Local Professional Networking http://madison.imby.info/p/Philip.Crawford
Re: [twitter-dev] Strange problems with Twitter API
I also use epiTwitter. Using 'localhost' has worked for me, but
sometimes it breaks, and I now prefer 127.0.0.1.
As you note: after successful authentication with Twitter, it works
fine for the first time until page refresh. This means the oauth
tokens are not saved into session variables, a database, or cookies
for next use, such as on a page refresh. You need to save the tokens
for future access.
~Patrick
On Sat, Apr 24, 2010 at 11:20 AM, KPL kapil.sa...@gmail.com wrote:
From past few days, I am trying to get the EpiTwitter library work for
me. But, it is behaving in unusually.
I am on Fedora 12 with PHP 5.3.2. It's my development box.
Here are the issues I am facing.
1.When I made a simple script with the method *getAuthenticateUrl* and
accessed it from http://localhost/ , it wasn't working and threw
errors(below) . But when I accidently tried http://127.0.01./ it
worked.
Fatal error: Uncaught exception 'EpiOAuthException' in /var/www/html/
twitter/classes/EpiOAuth.php:397
Stack trace:
#0 /var/www/html/twitter/classes/EpiOAuth.php(367):
EpiOAuthException::raise(Object(EpiCurlManager), false)
#1
/var/www/html/twitter/classes/EpiOAuth.php(39): EpiOAuthResponse-
__get('oauth_token')
#2 /var/www/html/twitter/preview.php(34): EpiOAuth-
getAuthenticateUrl(NULL, Array)
#3 {main}
thrown in /var/www/html/twitter/classes/EpiOAuth.php on line 397
2.After successful authentication, when returned to my script, it
works fine for the first time,when it is actually redirected by
Twitter.But when I refresh the page, it throws the following error -
Fatal error: Uncaught exception 'EpiOAuthUnauthorizedException' in /
var/www/html/twitter/classes/EpiOAuth.php:395
Stack trace:
#0 /var/www/html/twitter/classes/EpiOAuth.php(367):
EpiOAuthException::raise(Object(EpiCurlManager), false)
#1 /var/www/html/twitter/preview.php(48): EpiOAuthResponse-
__get('oauth_token')
#2 {main}
thrown in /var/www/html/twitter/classes/EpiOAuth.php on line 395
Should this be problem with my server or cURL installation? When I
checked phpinfo(), cURL was enabled, but when I had a look in
Configure Command section, I saw this
'--without-curl'
Is there any relation of this with the errors?
Also, I was unable to access the responseText and the try-catch
combination with $e-getMessage(); didn't yeild any results.
Thanks in advance for your help.
Regards,
Kapeel S
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
