[twitter-dev] Re: Draft of List API documentation
I think it should work for any request. Not sure though. Give it a try ;-) On Thu, Nov 5, 2009 at 5:48 AM, Paul Kinlan paul.kin...@gmail.com wrote: Can you confirm that _method=DELETE only works on POST's and not GET's? Paul 2009/11/3 Marcel Molina mar...@twitter.com A work around for environments that don't support the DELETE request method is, I believe, to pass a parameter called _method with the value DELETE. In other words _method=DELETE. On Mon, Nov 2, 2009 at 11:26 PM, wilfred yau wld991...@gmail.com wrote: It there any method to delete user from list other then using DELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call DELETE (which only GET and POST). So, will twitter provide POST or GET method API to delete? Thanks On Oct 16, 3:04 pm, Marcel Molina mar...@twitter.com wrote: Hey folks. As some of you have likely read we're starting to do some private beta testing of our new lists feature. We're not quite ready to open it up to everyone but we've made some headway on the API and wanted to share some details of what we've got so far. There are a handful of things on our todo lists so don't consider this signed and sealed just yet. You may notice this API is a bit of a departure from the rest of the API. It's a bit more, errr, REST than the rest. First off, here's the current payload for alist: ?xml version=1.0 encoding=UTF-8? list id1416/id nametall people/name full_name@noradio/tall-people/full_name slugtall-people/slug subscriber_count0/subscriber_count member_count3/member_count uri/noradio/tall-people/uri modepublic/mode user id3191321/id nameMarcel Molina/name screen_namenoradio/screen_name locationSan Francisco, CA/location descriptionEngineer at Twitter on the @twitterapi team, obsessed with rock climbing amp; running. In a past life I was a member of the Rails Core team./description profile_image_urlhttp://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no.../profile_image_url urlhttp://project.ioni.st/url protectedfalse/protected followers_count40059/followers_count profile_background_color9AE4E8/profile_background_color profile_text_color33/profile_text_color profile_link_color0084B4/profile_link_color profile_sidebar_fill_colorDDFFCC/profile_sidebar_fill_color profile_sidebar_border_colorBDDCAD/profile_sidebar_border_color friends_count354/friends_count created_atMon Apr 02 07:47:28 + 2007/created_at favourites_count131/favourites_count utc_offset-28800/utc_offset time_zonePacific Time (US amp; Canada)/time_zone profile_background_image_urlhttp://a1.twimg.com/profile_background_images/18156348/jessica_tiled/profile_background_image_url profile_background_tiletrue/profile_background_tile statuses_count3472/statuses_count notificationsfalse/notifications geo_enabledtrue/geo_enabled verifiedfalse/verified followingfalse/following /user /list === Lists === POST '/:user/lists.:format' Creates a newlistfor the authenticated user. Parameters: * name: the name of thelist. (required) * mode: whether yourlistis public of private. Values can be 'public' or 'private'. Public by default if not specified. (optional) Usage notes: :user in the url should be the screen name of the user making the request to create thelist Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=tall peoplemode=privatehttp://twitter.com/noradio/lists.xml POST/PUT '/:user/lists/:list_slug.:format' Updates the specifiedlist. Takes the same parameters as the create resource at POST '/:user/lists.:format' (:name and :mode). Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -d name=giantsmode=publichttp://twitter.com/noradio/lists/tall-people.xml GET '/:user/lists.:format' Lists your lists. Supported format: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml GET '/:user/lists/memberships.:format'Listthe lists the specified user has been added to. Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/memberships.xml DELETE '/:user/lists/:list_slug.:format' Delete the specifiedlistowned by the authenticated user. Parameters: * list_slug: the slug of thelistyou want to delete. (required) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORD -X DELETEhttp://twitter.com/noradio/lists/tall-people.xml GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specifiedlist. Parameters: * list_slug: the slug of thelistyou want the member tweet timeline of. (required) * next/previous_cursor: used to page through results
[twitter-dev] Re: Draft of List API documentation
Status timelines paginate with the page parameters. Social graph resources such as the members in a list use the cursor parameters. We're looking to rationalize all this as we move to new systems but for now there are different interfaces. You use the same mechanisms for the list statuses timeline as you do for all other status timelines. On Thu, Nov 5, 2009 at 7:05 AM, Milen mi...@thecosmicmachine.com wrote: I think that all methods which refer to lists should use the id, not the slug. As people have mentioned, the slug can change, so in order to reliably delete a list, you will have to fetch its slug and then issue a delete (or you risk getting an error as the slug might have changed in the meantime). I also tried to page through the statuses in a list but it seemed that: - next_cursor / previous_cursor had no effect on what was returned - cursor=-1 or anything else didn't have an effect Can anyone shed some light on how we're supposed to do paging? Thanks, M On Oct 16, 7:04 am, Marcel Molina mar...@twitter.com wrote: GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specified list. Parameters: * list_slug: the slug of the list you want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Draft of List API documentation
We will support specifying a list by both id and slug indefinitely. Though we recognize the short comings of finding by slug since they are prone to changing, there are use cases where finding by slug is a lot more convenient. So we'll be supporting both. You never *have* to search by slug :-) On Thu, Nov 5, 2009 at 7:05 AM, Milen mi...@thecosmicmachine.com wrote: I think that all methods which refer to lists should use the id, not the slug. As people have mentioned, the slug can change, so in order to reliably delete a list, you will have to fetch its slug and then issue a delete (or you risk getting an error as the slug might have changed in the meantime). I also tried to page through the statuses in a list but it seemed that: - next_cursor / previous_cursor had no effect on what was returned - cursor=-1 or anything else didn't have an effect Can anyone shed some light on how we're supposed to do paging? Thanks, M On Oct 16, 7:04 am, Marcel Molina mar...@twitter.com wrote: GET '/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specified list. Parameters: * list_slug: the slug of the list you want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Is image shrinking broken?
I've passed this issue along to the team that owns the image resizing code to see if they have any insights into what the issue might be. On Mon, Nov 2, 2009 at 9:25 PM, TCI ticoconid...@gmail.com wrote: I am noticing an increase in the number of avatar images which do not get shrinked in the smaller versions. It is most noticeable in the twitter.com homepage as the images load very slowly from top to bottom. How are your clients handling this? In my case I am assuming the shrinking is working and therefore my page load times are being affected. Example: http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4__bigger.jpg http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4__normal.jpg http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4__mini.jpg are all the same... -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: getting Authenticated feeds using java script
Perhaps if you switch to OAUTH you can make calls in javascript without worrying about sending the user's password in plain text and avoid having the pop-up login window. On Nov 5, 2:22 am, anix ani...@gmail.com wrote: Hi Friends, i was trying to access few of the user authenticated feeds like friends feeds. since u need to authenticate to get it, i was using CURL in php which work perfectly fine. only problem is rate limit, if multiple people login to the same page and try to access there feeds it will get rate lime of 150. i tried calling the link in javascript it ask for a authentication window /after authenticating it gives me the xml / json file and it counts the rate limit for the system which is calling the link and not the server. Problem in javascipt is the windows login window and the problem with CURL is rate limit sets to PHP servers IP address. Please any one have some work around to avoid any of the above condition.
[twitter-dev] Re: How to automatically return to my app from a Twitter registration
The OAUTH method has a return URL that you give Twitter when you register your app. After user authentication, Twitter POSTs variables back to that link so you can store the keys for the user and start making calls. On Nov 4, 4:48 pm, dhynesok dhyne...@yahoo.com wrote: I've seen where, from a Twitter app, I can first be sent to Twitter to register, and then be automatically returned to my app when the registration at Twitter is completed. My app is web-based so I assume I would use a link to the Twitter signup page that also has a link back address to my Twitter app's url. How can I do this? Thanks, David Hynes
[twitter-dev] Re: My application for whitelisting has been rejected for no reason!
There's a bug in the whitelisting system that's not properly passing along the reason for rejection. Try emailing a...@twitter.com with the username you submitted the request under, and someone from the Platform team will look up the reason for you. On 2009-11-05, at 1:47 PM, Nish wrote: Hi, Today i submitted by application to twitter stating that we are developing a Twitter application similar to socialoomph and asking to whitelist 3 of my IPs, I also explained them how am going to use them. However to my shock i got a email today stating its rejected and No reason was mentioned! (see below) Please Help! Hi Nishanth Chandran, Thanks for requesting to be on Twitter's API whitelist. Unfortunately, we've rejected your request. Here's why: Please address the issues above and submit another request if appropriate. The Twitter API Team
[twitter-dev] Re: Background images on a0.twimg.com giving access denied
To follow up I've been told that this is the most critical bug they
are working on right now. So it's being worked on. I'll pass along
updates as provided.
On Wed, Nov 4, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote:
Thanks for reporting this. I've forwarded this to the team responsible
for the S3 uploading.
On Wed, Nov 4, 2009 at 10:28 AM, Kevin kevinh...@gmail.com wrote:
We are uploading Twitter backgrounds via the API. We noticed today new
attempts to upload seem to be successful, but the profiles show no
background image. Looking at the page source, it shows a new
background image URL:
background: ... url('http://a0.twimg.com/profile_background_images/
bg12573586264055.jpg') ...;
However, opening that URL returns an error:
?xml version=1.0 encoding=UTF-8?
ErrorCodeAccessDenied/CodeMessageAccess Denied/
MessageRequestId20FB3BC5AEC2A2D5/RequestIdHostIdKheAYU8E/puKx
+qm5jtF9YeLLfc/NHcoCr6q2iOWZy2OR3tbtouA3Fo5aTrHUrZn/HostId/Error
It would appear Twitter is not adding the S3 access key query string
to these background image URLs, or the images are being put into S3 as
private items.
Hope to see a fix soon.
Regards,
Kevin Hunt
Bubble Fusion Labs
--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio
--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio
[twitter-dev] Re: My application for whitelisting has been rejected for no reason!
You think they would at least give you an issue number or something. -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Nish Sent: Thursday, November 05, 2009 11:48 AM To: Twitter Development Talk Subject: [twitter-dev] My application for whitelisting has been rejected for no reason! Hi, Today i submitted by application to twitter stating that we are developing a Twitter application similar to socialoomph and asking to whitelist 3 of my IPs, I also explained them how am going to use them. However to my shock i got a email today stating its rejected and No reason was mentioned! (see below) Please Help! Hi Nishanth Chandran, Thanks for requesting to be on Twitter's API whitelist. Unfortunately, we've rejected your request. Here's why: Please address the issues above and submit another request if appropriate. The Twitter API Team No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.424 / Virus Database: 270.14.50/2481 - Release Date: 11/05/09 07:37:00
[twitter-dev] Re: Streaming Api - Keywords matched
A little late to this convo, but I disagree with the need for this feature. It adds extra complexity to twitter that really should be on the application level, and, since the streaming API only returns one tweet, even if it matched two or more keywords that you are watching, it'd add extra load on them so they can determine all of the matches. It'd be nice for them to do this, but honestly, I feel this is an application specific need, and thus, the application should implement it. -1 -Joel On Tue, Nov 3, 2009 at 3:01 PM, John Kalucki jkalu...@gmail.com wrote: The Streaming API and the Search indexer both tee off the same point in the new status event pipeline. New statuses are born in the web containers and queued for a cluster of processes that begin the offline processing pipeline. This first process does many things, including routing statuses to various subsystems (timelines, SMS, various backing stories, etc. etc.). This process also determines if the updating user is public or protected and if they are filtered from search. If the user is both public and unfiltered, the status is enqueued to both Search and Streaming. See also: http://apiwiki.twitter.com/Streaming-API-Documentation#ResultQualitynbsp The Streaming API then syndicates all these statuses. The Search system may or may not sort, filter, and otherwise rank statuses for relevance based on various heuristics, including, but not limited to: phase of the moon, state of tides, the DJIA, etc. Roughly: Complete corpus search: Streaming Low-latency results: Streaming Accurate keyword counts: Streaming (tally both statuses and limit messages) Complex queries: Search Historical queries: Search -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 11:02 am, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: It would help if John Kalucki (hello) would clarify the difference between what is visible via streaming as opposed to what is visible via search. I've been operating under the assumption that streaming is warranted when an app needs a different or more powerful search than the current one (e.g. nested boolean expressions), or is interested in seeing tweets before they are filtered out by twitter's spam detection (dealing with the tweet removal protocol, etc).) As a developer it would help us if you could paint out what the twitter data pipeline looks like, and where the various apis plug in, so that we know what we get when we plug in there. I assume, for instance, that search is farther downstream than the various firehose/stream apis, but I've little idea (or documentation) on what steps the data is as it moves down the pipe Would Twitter be open to shedding some light?. jeffrey greenberg tweettronics.com On Nov 3, 9:59 am, Fabien Penso fabienpe...@gmail.com wrote: I agree, however it would help a lot because instead of doing : for keyword in all_keywords if tweet.match(keyword) //matched, notify users end end we could do for keyword in keywords_matched // same as above end for matching 5,000 keywords, it would bring the first loop from 5,000 to probably 1 or 2. You know what you matched, so it's quiet easy for you just to include row data of matched keywords, I don't need anything fancy. Just space separated keywords would help _so much_. On Tue, Nov 3, 2009 at 3:15 PM, John Kalucki jkalu...@gmail.com wrote: The assumption is that client services will, in any case, have to parse and route statuses to potentially multiple end-users. Providing this sort of hint wouldn't eliminate the need to parse the status and would likely result in duplicate effort. We're aware that we are, in some use cases, externalizing development effort, but the uses cases for the Streaming API are so many, that it's hard to define exactly how much this feature would help and therefore how much we're externalizing. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Nov 3, 1:53 am, Fabien Penso fabienpe...@gmail.com wrote: Hi. Would it be possible to include the matched keywords in another field within the result from the streaming/keyword API? It would prevent matching those myself when matching for multiple internal users, to spread the tweets to the legitimate users, which can be time consuming and tough to do on lots of users/keywords. Thanks.
[twitter-dev] Streaming API statuses/filter access increase request
Hello, Several days ago we (Cliqset) made a request via the API whiltelisting form for an increase to our default 'statuses/filter' follow user limit (400). The request came back today as rejected with no content in the 'reason why' section. Is there some way we can resubmit directly? We currently have several thousand users whom we'd like to roll out to use the streaming API which we've tested thoroughly but are currently limited to 400. Any assistance would be greatly appreciated. Thanks! Darren Cliqset.com
[twitter-dev] Re: flagged as dupe post when string is unique (ideas?)
as noted by other people on this list, twitter is currently rejecting tweets that match either your last update, or an update you recently sent. unfortunately, the API is currently silently failing but it is on the short list to have the API return an error code instead. Can you confirm what match means? Is it same character sequence or is it similar character sequence? I ask because John Kalucki wrote Is the posted status similar to any other status created by that user? above in response to a question about duplicate rejection. Thanks, -andy On Nov 3, 3:35 pm, Raffi Krikorian ra...@twitter.com wrote: Is the posted status similar to any other status created by that user? Does the above imply that similar will trigger the dup detector? Argh! Please don't tell me that you're now rejecting similar tweets Url shorteners can easily generate similar urls, so if someone is in the habit of tweeting check this out followed by a shortened url, the tweet text is likely to be similar even though the actual url is different. Heck, urls that are similar often point to very different web pages. There are lots of other cases where similar tweets can actually be very different, and thus should not be rejected as duplicates. (I've heard of a project that tweets data that is guaranteed to be unique but is reasonably likely to be similar because of aggressive encoding.) as noted by other people on this list, twitter is currently rejecting tweets that match either your last update, or an update you recently sent. unfortunately, the API is currently silently failing but it is on the short list to have the API return an error code instead. -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi- Hide quoted text - - Show quoted text -
[twitter-dev] Re: crossdomain
OK, the crossdomain policy now only allows your flex application to access the API. You are not allowing flex appication access your API? How come the change again today. This morning it was working fine. On Nov 4, 9:30 am, John Kalucki jkalu...@gmail.com wrote: Search team is aware of the issue. Working on it. I don't have an update from them yet. -John On Nov 4, 8:56 am, Tzahi Sofer tzahi.so...@gmail.com wrote: Hi, I get a 404 on calls to search.twitter.com/crossdomain.xml. It's been like this since last night. any ideas? Thanks, Tzahi.
[twitter-dev] Re: historical trends
Well, trends shown on Twitter itself have self-reinforcement effect: once a trends breaks into the Top 10, it's snowball after that. Thus, it's not sufficient to just study tweets when identifying trends. Breaking into the Top 10 is a major event. Thus I suggest Twitter carefully records when it changes the Top 10 display and provides it via an API! This is a separate, computational processing which affects almost every Twitter user's behavior, and is thus important to preserve and study. Cheers, Alexy
[twitter-dev] Oauth and (lack) delegation
Does Twitter (or anyone else) have thoughts around the lack of delegation in Oauth and the announced deprecation of basic authentication? Currently, to enable an API that allows web services to interact with Twitter on its behalf (e.g. TwitPic, yFrog, etc.) one has to rely on basic authentication (the twitter client passing the user¹s username password to the web services API), as delegation is not possible via Oauth... If a user authenticates with my application via Oauth, there¹s no way I can have a 3rd party API do anything on behalf of that user... Similarly, if I want to develop an API to my Twitter web service, I would have to develop that with basic authentication, but what¹s the point: * knowing that basic auth is going to be deprecated in the (near) future * so many apps are now based on oauth and wouldn¹t be able to use my API because they can¹t authenticate I¹m sure other devs have run into this. Does Twitter have any thoughts around this? How do you expect to maintain a 3rd party app/API eco system after basic auth deprecation? Looking forward to everyone¹s feedback..
[twitter-dev] Changes to search results for trending topics
Today on the Twitter Blog we announced that we will be changing search results for trending topics to improve the quality. It used to be that trends were a great way to quickly see what was going on on Twitter, but they have begun to get fairly noisy due to the sheer volume of tweets. We wanted to improve that experience and will start returning what we think are the best results. This doesn't mean that tweets are getting dropped from the index, instead we are just making intelligent decisions on which ones to return for searches on popular topics, beginning with trending topics. If you make a more specific search, you can still get to all the tweets. So for you, the developer, this means that if you will see better quality results over the search API for trends, but you won't be getting every tweet that matched the search term. If you still do want to get every tweet matching a trend, we recommend you check out the Streaming API (http://apiwiki.twitter.com/Streaming-API-Documentation). In the end, this is a change that is good for developers and end-users, but we wanted to notify you as you might be seeing some slightly different behavior via the API. Please let us know if you have any questions -- we are happy to answer. Ryan
[twitter-dev] Re: Streaming API statuses/filter access increase request
Email a...@twitter.com with the info, and someone will get back to you. Also, please, in the future, read the archives before submitting stuff like this. There have been DOZENS of emails exactly like this posted in the past, including one just a few hours ago. On Thu, Nov 5, 2009 at 15:26, Darren Bounds (Cliqset) dbou...@gmail.comwrote: Hello, Several days ago we (Cliqset) made a request via the API whiltelisting form for an increase to our default 'statuses/filter' follow user limit (400). The request came back today as rejected with no content in the 'reason why' section. Is there some way we can resubmit directly? We currently have several thousand users whom we'd like to roll out to use the streaming API which we've tested thoroughly but are currently limited to 400. Any assistance would be greatly appreciated. Thanks! Darren Cliqset.com -- Internets. Serious business.
[twitter-dev] Re: Oauth and (lack) delegation
Hey Marcel, Good to hear Twitter is thinking about this issue. It sounds like timing is kind of open ended at this point? I would obviously love to be part of the conversation and help test things out etc. I did find a couple interesting discussions/ideas while researching this issue, that you may or may not yet be aware of: http://groups.google.com/group/oauth/browse_thread/thread/bdf8b99e84a8aaef/7 7409186172e23ba?#77409186172e23ba http://hueniverse.com/2009/03/taking-oauth-beyond-the-3rd-leg/ From my perspective, and I'm not a security expert, oauth expert or any other kind of relevant expert, I could imagine a workflow where an app can request a one-time-use-only token from Twitter that it can pass on to another 3rd party app for one time use. So, for example, you have a Twitter client, let's call it Tweetie, and a 3rd party service with API, let's call it TwitPic (I'm not related to either)... - Tweetie requests a one-time token from Twitter. The one-time token is restricted to the user it is requested for, and the application it is requested for. - Tweetie performs an API request to TwitPic, passing on the one-time token. - In turn, TwitPic can perform an API request to Twitter on behalf of the Tweetie user (e.g. Post a picture), using the one-time token as an additional oauth parameter. One-time tokens are expired upon use or within X minutes after been granted. A new one-time-token for a App1/App2/User combination cannot be granted until an earlier granted token has either expired or been used. And since such one-time tokens are specific to Requesting App, Receiving App and the User, abuse is not likely as any of the 3 parties could restrict one of the other 2 parties from requesting or receiving a token... Also, since both the Requesting App and Receiving App are tied to the token, Twitter can display a combined client attribute with the resulting tweets (e.g. 1 minute ago from Tweetie via TwitPic) Anyway - I'm sure there are plenty of drawbacks, other concerns or things I'm overlooking - but just wanted to get the conversation started... What other, perhaps equally high level options has Twitter or anyone else come up with? Thanks, Michael. On 11/5/09 4:55 PM, Marcel Molina mar...@twitter.com wrote: We've got a project lined up to come up with an answer for OAuth app delegation problem. We haven't done a deep dive into what the approach might be yet so we don't have any ideas yet. Would be glad to have the conversation with those who are interested and have ideas. On Thu, Nov 5, 2009 at 4:20 PM, Michael Steuer mste...@gmail.com wrote: Does Twitter (or anyone else) have thoughts around the lack of delegation in Oauth and the announced deprecation of basic authentication? Currently, to enable an API that allows web services to interact with Twitter on its behalf (e.g. TwitPic, yFrog, etc.) one has to rely on basic authentication (the twitter client passing the user¹s username password to the web services API), as delegation is not possible via Oauth... If a user authenticates with my application via Oauth, there¹s no way I can have a 3rd party API do anything on behalf of that user... Similarly, if I want to develop an API to my Twitter web service, I would have to develop that with basic authentication, but what¹s the point: knowing that basic auth is going to be deprecated in the (near) future so many apps are now based on oauth and wouldn¹t be able to use my API because they can¹t authenticate I¹m sure other devs have run into this. Does Twitter have any thoughts around this? How do you expect to maintain a 3rd party app/API eco system after basic auth deprecation? Looking forward to everyone¹s feedback..
[twitter-dev] Re: waiting for whitelisting
You can request whitelisting here: http://twitter.com/help/request_whitelisting On Wed, Nov 4, 2009 at 11:27 AM, twittme_mobi nlupa...@googlemail.com wrote: Hello, Sorry for posting this again. but I have problems with my mobile twitter site, which is in production since 4 months now and alreay widely used.The problem is that my hosting company changed my outgoing IP without notifying me and now i reach the time limit and the users are complaining.It is very annoying so i would kindly ask the twitter guys to have a look. My new IP is 99.198.100.139 for http://twittme.mobi and i would like to have it whitelisted. Thanks.
[twitter-dev] Re: Question about versioning
Did I miss the announcement that Twitter was planning to implement versioning? I don't recall that. Jesse On Thu, Nov 5, 2009 at 11:23 AM, DeWitt Clinton dclin...@gmail.com wrote: That doesn't quite work, as sometimes parameters and response values are tweaked for existing calls, not just new areas of functionality. See http://apiwiki.twitter.com/REST+API+Changelog for examples. For the most part things have been backwardly compatible, which is to be applauded. I think all I'm requesting is what's already been announced -- that there is an explicit version id in the API, and that those methods remain stable. Then I can release a 1.0 version of the libraries that are hard-coded to the v1 endpoints, a 1.1 version hard-coded to the v1.1 endpoints, etc, and a 'dev' version of the libraries against the current beta endpoints. We went through exactly this process in developing the Google Data APIs, and while my takeaway from that experience is that you can never plan early enough for versioning, it's still better to do later than never, which sounds like Twitter's current plan (good!). I'm just asking when we can plan to target explicit versions. -DeWitt On Thu, Nov 5, 2009 at 10:10 AM, Jesse Stay jesses...@gmail.com wrote: I don't think Twitter has versions right now - you should look at what the Net::Twitter libraries for Perl are doing though. With those, you tell it which components of the library you want to include when you're instanciating your initial $twitter object. So if you want to include search functionality, you tell it to include the search components. If you want to include list functionality you tell it to include the list components. Keeps it nice and lightweight for when you need it to. Jesse On Thu, Nov 5, 2009 at 7:36 AM, DeWitt Clinton dew...@unto.net wrote: Hi all, I'd like to sync the version numbers and release cycles of a few twitter libraries (python-twitter http://code.google.com/p/python-twitter/ and java-twitter http://code.google.com/p/java-twitter/) up with the version of the Twitter API itself. I'll admit that I've fallen way behind on the maintenance of each, partly because the Twitter API itself is a moving target (not a bad thing, just hard to keep in sync with). What's the expected timing of when we can rely on a stable versioned endpoint for v1, v2, etc, and bleeding-edge API versions? In theory we'd do parallel releases on major/minor releases, and keep a dev branch open for the latest-and-greatest-and-beta-est version of the Twitter API. -DeWitt
[twitter-dev] Re: Geocode Problem
Hi, thanks for the reply.. its just that when i tried the coordinates, 1.397185,103.807068 on this website http://www.google.com/maps, it shows me that it in on an area in Singapore. Am i getting the information wrongly? On Thu, Nov 5, 2009 at 5:14 PM, Rich rhyl...@gmail.com wrote: Those coodinates are in the middle of the ocean according to Google Maps so that might very well be why it doesn't work. On Nov 5, 3:03 am, pipigu85 pipig...@gmail.com wrote: Hi, i was looking through the twitter search api to find something that could limit my search to Singapore and thought geocode could help. I tried the link in the example and it was able to work but when i replace it with singapore's coordinates taken from google maps, a HTTP 403 Forbidden error appears. Could someone help? thks This is the link i was trying out with to narrow search down to Singapore: http://search.twitter.com/search.atom?geocode=1.397185%2C-103.807068%...
[twitter-dev] api.twitter.com not returning compressed data
API calls to http://twitter.com/ with Accept-Encoding:gzip in the headers are returning compressed data, while calls to http://api.twitter.com/1/ with the same headers do not. You can demonstrate this with cUrl: curl --basic -u user:pass --header Accept-Encoding:gzip, deflate http://api.twitter.com/1/statuses/friends_timeline.json vs. curl --basic -u user:pass --header Accept-Encoding:gzip, deflate http://twitter.com/statuses/friends_timeline.json In the second example, you will get garbled response indicating that the data is compressed, whereas in the first you will get clear text. (Note: if you use --compress instead of --header then cUrl will decompress the response so you'll have to use Wireshark or some other network sniffer to see the raw data). We tracked this down because one of our users in Europe reported a big perf hit after we switched to the versioned endpoint. (see http://code.google.com/p/tweetsharp/issues/detail?id=104) I hope this isn't by design. Jason Diller Tweetsharp Contributor
[twitter-dev] Can't post more than 140 characters in status
I am using twitter API in my rails site that automatically tweet my updates in twitter using curl command. But problem is that i have to post very long text (more than 140 chars). How can i do this? Suggestions are welcomed
[twitter-dev] Search using special characters
When doing a search, is it possible for the ! character to be considered part of the query? For example, I want to differentiate between hey!, hey!! and hey!!!. Currently the API returns all results containing hey regardless of which one I search for (with or without quotes). Thanks.
[twitter-dev] Re: api.twitter.com not returning compressed data
We've confirmed this and reported it to our operations team. We've identified the problem and are actively fixing it. Thanks for the detailed report. I'll let you know when the gzip compression is restored. On Thu, Nov 5, 2009 at 7:19 PM, Jason Diller jdil...@gmail.com wrote: API calls to http://twitter.com/ with Accept-Encoding:gzip in the headers are returning compressed data, while calls to http://api.twitter.com/1/ with the same headers do not. You can demonstrate this with cUrl: curl --basic -u user:pass --header Accept-Encoding:gzip, deflate http://api.twitter.com/1/statuses/friends_timeline.json vs. curl --basic -u user:pass --header Accept-Encoding:gzip, deflate http://twitter.com/statuses/friends_timeline.json In the second example, you will get garbled response indicating that the data is compressed, whereas in the first you will get clear text. (Note: if you use --compress instead of --header then cUrl will decompress the response so you'll have to use Wireshark or some other network sniffer to see the raw data). We tracked this down because one of our users in Europe reported a big perf hit after we switched to the versioned endpoint. (see http://code.google.com/p/tweetsharp/issues/detail?id=104) I hope this isn't by design. Jason Diller Tweetsharp Contributor -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Getting user info from REST interface using name and not screen name
There is no API for that at the moment. We're developing an API for people search though. On Thu, Nov 5, 2009 at 6:38 PM, Kripashankar krip...@gmail.com wrote: Hi, I am developing a small prototype and would like to know the following. 1. How can I get info about a user given only the name and not screen name ? Example: http://twitter.com/users/show.xml?screen_name=aplusk gives me info about ashton kutcher but let's say I don't know the screen name but only know the name Ashton Kutcher. How can I get the corresponding screen name and id, or the user info with just the name ? The api http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show doesn't seem to take name as a parameter. BTW, I noticed two user info http://twitter.com/users/show.xml?screen_name=aplusk http://twitter.com/users/show.xml?screen_name=ashtonkutcher So I am not sure which is the right one as well for Ashton Kutcher. Any help much appreciated. Thanks! -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: api.twitter.com not returning compressed data
The configuration has been fixed. The configuration updates should be pushed out to all servers tomorrow morning PST. On Thu, Nov 5, 2009 at 8:20 PM, Marcel Molina mar...@twitter.com wrote: We've confirmed this and reported it to our operations team. We've identified the problem and are actively fixing it. Thanks for the detailed report. I'll let you know when the gzip compression is restored. On Thu, Nov 5, 2009 at 7:19 PM, Jason Diller jdil...@gmail.com wrote: API calls to http://twitter.com/ with Accept-Encoding:gzip in the headers are returning compressed data, while calls to http://api.twitter.com/1/ with the same headers do not. You can demonstrate this with cUrl: curl --basic -u user:pass --header Accept-Encoding:gzip, deflate http://api.twitter.com/1/statuses/friends_timeline.json vs. curl --basic -u user:pass --header Accept-Encoding:gzip, deflate http://twitter.com/statuses/friends_timeline.json In the second example, you will get garbled response indicating that the data is compressed, whereas in the first you will get clear text. (Note: if you use --compress instead of --header then cUrl will decompress the response so you'll have to use Wireshark or some other network sniffer to see the raw data). We tracked this down because one of our users in Europe reported a big perf hit after we switched to the versioned endpoint. (see http://code.google.com/p/tweetsharp/issues/detail?id=104) I hope this isn't by design. Jason Diller Tweetsharp Contributor -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Authentication not required for Twitter REST API Method
The API description says that authentication is supposed to be required, but it is not. I don't know if this is a typo or if something is wrong, but you don't have to be authenticated to get the updates of a twitter list by ATOM (or any other format, for that matter). Not that I'm complaining: http://www.dizzysoft.com/twitter/twitter-lists-text-messages
[twitter-dev] Re: Mobile Twitter Client OAuth
You can do exactly that already. Set it to browser auth, redirect it to your own webserver and get your webserver to redirect to your own url scheme, forwarding on the callback token. Trust me, it will work just fine! On Nov 6, 5:20 am, Ji Lee mr.ji.hoon@gmail.com wrote: Hi, It seems that the current OAuth for desktop apps require that the user copy the 7-digit number, and paste into the client. This is fine for the desktop, but it doesn't work too well for the mobile device, as copy/paste is a rather cumbersome to do... Flickr OAuth seems to provide a mechanism which allows the desktop client to retrieve the token using a separate URL. Is there a URL for retrieving the token after user return to the client application? Would commerial key help? Another possibility is to allow for a callback URL scheme, such as myclient:// as the callback URL, which my app could register itself to handle. Curretly, the twitter website does not seem to accept such URLs. Thanks, -Ji
[twitter-dev] Re: Can't post more than 140 characters in status
You can't without using a 3rd party service. Twitter only allows 140 characters. On Nov 6, 3:43 am, shyam khadka shyamkkha...@gmail.com wrote: I am using twitter API in my rails site that automatically tweet my updates in twitter using curl command. But problem is that i have to post very long text (more than 140 chars). How can i do this? Suggestions are welcomed
