Re: [twitter-dev] Re: Twitter API SSL certificate failing validation

Make sure in /etc/ssl/certs that you have a copy of the Verisign root CA file, just like in the java example above. If you're loading all files from /etc/ssl/certs you should be able to just drop in the http://curl.haxx.se/ca/cacert.pem file and that should fix your issue. -j On Wed, Jul 20, 20

[twitter-dev] Re: Twitter API SSL certificate failing validation

Pardon me, I have the same problem, but I seem to be missing something about the solution. My application is in Ruby on Rails, with a gem called "OmniAuth" doing the OAuth work. It was working just fine before this change, automatically fetching my certificates from /etc/ssl/certs directory. What

[twitter-dev] Re: Twitter API SSL certificate failing validation

John: Thanks much. This helps a lot. We very much appreciate you being able to get back to us with this info on such short notice. On Jul 18, 10:54 pm, John Adams wrote: > On Mon, Jul 18, 2011 at 8:17 PM, pgarvie wrote: > > Has Twitter done something with its SSL certificates lately? As in >

[twitter-dev] Re: Twitter API error on my website

> Hi Mohan, > > We are using a widget and it appears to still be happening, could this > be because of an increase in traffic to the site? > > It works and then the next time you go to the site it will have the > error again. > I would say this is most likely something to do with the base site from

[twitter-dev] Re: Twitter API error on my website

Hi Mohan, We are using a widget and it appears to still be happening, could this be because of an increase in traffic to the site? It works and then the next time you go to the site it will have the error again. Cheers Steven On Jun 26, 11:15 pm, Mohan Arun wrote: > "The Twitter API returned

[twitter-dev] Re: Twitter API changes

but currently i am getting all the information for them... when will i stop getting this info? On Jun 27, 7:45 am, kamesh SmartDude wrote: > hi, > the users who are already logged in should logout and relogin > againotherswise they will not get any data(not only DM's) because u > chaged the a

[twitter-dev] Re: Twitter API error on my website

"The Twitter API returned an error while processing your request. Please try again." Are you using a widget or you are using some custom code for feeding the tweets in your wordpress website? If you are using some widget, then most probably it will start working again after some time. Mohan --

Re: [twitter-dev] Re: Twitter API to Get the HashTags List

There are hundreds of thousands of unique hashtags in use, possibly millions. Collect tweets for your keywords, get the tags from the entities, put them into a database, and run a frequency distribution to find the most popular. On Tue, May 31, 2011 at 11:51 PM, Mohan Arun wrote: >> Hai All, >> >

[twitter-dev] Re: Twitter API to Get the HashTags List

> Hai All, > > Is there any API to get the Hashtags list which are used in twitter? To my best of knowledge, there isnt a way to do this. > i googled for it but i am not able to find any API for it. You can lookup the meaning of a given hashtag here: http://tagdef.com/ You could contact the dev

[twitter-dev] Re: [twitter-api-announce] A new permission level

Hi Matt, 1. xAuth apps are already approved by you guys and have a (I'm assuming) higher threshold to get access to. I'd really ask you guys to re-consider and allow xAuth access to DMs. Or at the very least allow clients to apply for exceptions to this rule. 2. Under 2 weeks is way too short

[twitter-dev] Re: [twitter-api-announce] Visual refresh of the OAuth screens

Here is a screenshoot of the new page. https://picasaweb.google.com/4braham/Screenshots#5600743120809142002 Note that app descriptions are now shown to users incase you were lazy (like me) and didn't include a real description. Abraham - Abraham Williams | InboxQ

[twitter-dev] Re: Twitter API Timeouts

Hi All - Since early yesterday (India time) I have been seeing significant 403 errors - Failed to search tweets: 403:The request is understood, but it has been refused. An accompanying error message will explain why. {"error":"since date or since_id is too old"} Neither of the above reasons

[twitter-dev] Re: Twitter API Timeouts

Looks like it is working as normal again now... Horrid way to find out our internal poller has a 10 minute timeout on a request though :D On Feb 28, 7:30 pm, Marc Mims wrote: > * Taylor Singletary [110228 06:57]: > > > Thanks for the reports -- we're looking into the timeout issue. > > I've be

Re: [twitter-dev] Re: Twitter API Timeouts

* Taylor Singletary [110228 06:57]: > Thanks for the reports -- we're looking into the timeout issue. I've been seeing this, too. To combat it, I've set my request timeout to 8 seconds and I use with Net::Twitter's RetryOnError trait (perl). Last year, at Chrip, one of the speakers said Twitter

Re: [twitter-dev] Re: Twitter API Timeouts

shows everything is fine though. >> >> Regards, >> >> Leon Meijer >> >> -- >> *From:* Naveen [mailto:knig...@gmail.com] >> *To:* Twitter Development Talk [mailto: >> twitter-development-talk@googlegroups.com] >> *

Re: [twitter-dev] Re: Twitter API Timeouts

twitter-development-talk@googlegroups.com] > *Sent:* Mon, 28 Feb 2011 11:36:57 +0100 > *Subject:* [twitter-dev] Re: Twitter API Timeouts > > > We have been seeing this behavior as well since early yesterday. > > We have a lot of connections (a noticeable percentage) simply >

Re: [twitter-dev] Re: Twitter API Timeouts

Development Talk [mailto:twitter-development-talk@googlegroups.com] Sent: Mon, 28 Feb 2011 11:36:57 +0100 Subject: [twitter-dev] Re: Twitter API Timeouts We have been seeing this behavior as well since early yesterday. We have a lot of connections (a noticeable percentage) simply timeout. We have

[twitter-dev] Re: Twitter API Timeouts

We have been seeing this behavior as well since early yesterday. We have a lot of connections (a noticeable percentage) simply timeout. We have tested various timeouts and work arounds and it appears as though the connections will happily be kept open indefinitely with no response if there is no t

[twitter-dev] Re: Twitter API is giving wrong tweet ID

I've checked what you said. Your advice is really helpful to me. Thank you very much. On Dec 7, 12:10 pm, Tom van der Woerdt wrote: > No, the tweets are fine. > > ActionScript (and any other ECMAScript language) can't handle numbers > larger than 53 bits. In a few days you'll see that the number

Re: [twitter-dev] Re: Twitter API is giving wrong tweet ID

No, the tweets are fine. ActionScript (and any other ECMAScript language) can't handle numbers larger than 53 bits. In a few days you'll see that the numbers will be wrong twice as much. A few weeks later this will duplicate again, and again, and again. To solve this issue, a _str field (id_

[twitter-dev] Re: Twitter API is giving wrong tweet ID

Yes, I think the implementation is correct, and I use ActionScript. Many of tweets are having correct ID, but some tweets are having wrong one. On Dec 7, 11:59 am, Tom van der Woerdt wrote: > Are you sure that your implementation is correct? It really sounds like > an issue with processing larg

[twitter-dev] Re: Twitter API

I have one question here... I know that we can fetch the recent posts from a user's account, however is it possible to fetch replies to a particular tweet? Please guide me on that. Thanks in advance!!! On Nov 29, 5:10 pm, Igor Kharin wrote: > Once you authorized an user and got his access token

Re: [twitter-dev] Re: Twitter API

Once you authorized an user and got his access token you're free to use all the API methods like statuses/mentions (replies): http://dev.twitter.com/doc/get/statuses/mentions Good luck! On Mon, Nov 29, 2010 at 5:35 PM, Tom Callahan wrote: > Thank you very muchit worked :-) > > Can you also p

[twitter-dev] Re: Twitter API

Thank you very muchit worked :-) Can you also please help me in more thing : How can I fetch the tweet replies from somebody's account? On Nov 28, 6:22 pm, Igor Kharin wrote: > Here's how "Sign in with Twitter" button > works:http://dev.twitter.com/pages/sign_in_with_twitter > > For end-use

[twitter-dev] Re: Twitter API search functionality

TweeterLookup.com did this email to twitter id lookup but has since closed down. I dont think twitter exposes this functionality in the search api and you cannot search by email id. But there are third party providers available that might have this data. Try the Flowtown API or Rapleaf API. htt

Re: [twitter-dev] Re: Twitter API Write Only Authorization

OAuth 2.0 allows a "scope" parameter. Twitter has plans for OAuth 2.0, so I'd assume that they will include this parameter in their OAuth 2.0 update. Just don't count on it anytime soon. Tom On 10/11/10 8:53 PM, Markanday Singh wrote: > Or may be full itemized authorization !! > > On Oct 11, 11

[twitter-dev] Re: Twitter API Write Only Authorization

Or may be full itemized authorization !! On Oct 11, 11:46 pm, Markanday Singh wrote: > Few APPs uses twitter API only for 2 reasons, > 1-Authenticate user and get their User Info (A READ) > 2-Occasionally Tweet On behalf of them (A WRITE) > > Just bring a category where an app is allowed to Authe

[twitter-dev] Re: twitter api throwing lots of technical errors

We are seeing same at Twitalyzer. Seems to be isolated to the search API but we haven't had a chance to dig in. The problems seem to be correlated to Twitter's announcement of the new search platform as well. Anyone else seeing lower rate limits on the search API last few days? @erictpeterson

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

I made a minor change to see if it will flush the cache. The policy is, as of 9/1/2010: During the beta testing period, sites are encouraged to first pull and cross-check test data from both Site Streams and the REST API to develop confidence in correctness and robustness. Once a Site Streams clie

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

John, That page still says exactly the same. On Aug 30, 5:24 pm, John Kalucki wrote: > It's cached. It'll update via a process that is mysterious to me. > > > > On Mon, Aug 30, 2010 at 1:21 PM, Dewald Pretorius wrote: > > John, > > > Is that page cached, because the third sentence of the first

Re: [twitter-dev] Re: [twitter-api-announce] Streaming API access limits increased

I am loving the terminology. -Doug Tangren http://lessis.me On Mon, Aug 30, 2010 at 9:33 PM, John Kalucki wrote: > Spritzer remains at 1%. We can't increase this one at the moment due to > technical reasons unrelated to capacity or policy. We'll probably leave this > at 1% for a while. > > Ha.

[twitter-dev] Re: [twitter-api-announce] Streaming API access limits increased

Spritzer remains at 1%. We can't increase this one at the moment due to technical reasons unrelated to capacity or policy. We'll probably leave this at 1% for a while. Ha. Totally unrelated to Snowflake. Related changes coming soon though. -John On Tue, Aug 31, 2010 at 4:30 AM, M. Edward (Ed)

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

I think you're missing my point. A signed agreement does not prevent anything for the evil-minded. At best it establishes the parameters for damage control by Twitter (revoking access, banning, etc.), except in this case Twitter won't have the forensics to determine who did the damage. On Aug 30,

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Try getting access to Site Streams without a signed agreement between your organization and Twitter prohibiting such shenanigans. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb "A mathematician is a device for turning coffee into theorems." - Paul Erdos Qu

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Ed, Developer responsibilities and developer agreements mean absolutely nothing to that person who wants to abuse users' DMs. In fact, they will probably trick users to authorize their app with a neat feature, and then in the background collect received and sent DMs. Twitter will not have the fo

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

It's cached. It'll update via a process that is mysterious to me. On Mon, Aug 30, 2010 at 1:21 PM, Dewald Pretorius wrote: > John, > > Is that page cached, because the third sentence of the first bullet > under Important Items still says *exactly* the same? > > On Aug 30, 5:15 pm, John Kalucki

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

John, Is that page cached, because the third sentence of the first bullet under Important Items still says *exactly* the same? On Aug 30, 5:15 pm, John Kalucki wrote: > Thanks. I've clarified the language. > > -John > > > > On Mon, Aug 30, 2010 at 12:42 PM, Dewald Pretorius wrote: > > John, > >

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Thanks. I've clarified the language. -John On Mon, Aug 30, 2010 at 12:42 PM, Dewald Pretorius wrote: > John, > > Perhaps you should then rephrase the following at > http://bit.ly/sitestream_doc > > "One Site Streams graduates to production, sites must only use the > REST API for data that is

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Quoting Dewald Pretorius : Here's another issue that probably needs to be considered. It applies mostly to DMs, because people will tend to use DMs for sensitive information, and would expect a certain level of privacy. Right now, an OAuth authorized site can query a user's DMs and do with tha

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

John, Perhaps you should then rephrase the following at http://bit.ly/sitestream_doc "One Site Streams graduates to production, sites must only use the REST API for data that is not available through User Streams or as a fall-back data source." It's in the first paragraph of Important Items. He

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

We're not forcing people over to Site Streams. If, on the other hand, if you start to consume Site Streams, we want you to stop regular polling on the REST API. If your service is modest, any excess delivery will be modest. Excessive options add complexity and slow development for what may be litt

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

This is super news. However, if you're going to force web services to use Site Streams when it is in production ("sites must only use the REST API for data that is not available through User Streams"), then please add the ability to subscribe only to certain elements. For example, we need the abil

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Desktop clients that support multiple accounts should continue to open multiple connections on User Streams. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Mon, Aug 30, 2010 at 12:00 PM, Tom van der Woerdt wrote: > My initial thought was that this was for applications like TweetDe

Re: [twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

My initial thought was that this was for applications like TweetDeck where users have multiple accounts, but the docs say that Desktop clients should keep using the normal User Streams. Will there be an update for the User Streams to support having multiple accounts, are the docs wrong, or do you r

[twitter-dev] Re: [twitter-api-announce] Announcing Site Streams Beta

Freakin' awesome. Nice job guys! Jesse On Mon, Aug 30, 2010 at 12:52 PM, Mark McBride wrote: > Site Streams, a new feature on the Streaming API, is now available for > beta testing. Site Streams allows services, such as web sites or > mobile push services, to receive real-time updates for a lar

Re: [twitter-dev] Re: Twitter API & the Basic Auth Shutdown: Everything you need to know.

Quick correction on some mis-typed dates in the summary section: - Beginning Aug 17, basic auth rate limiting will decrease by 15 requests on each week day (10% drop per weekday) - Aug 16, 8am Pacific - we'll shut basic auth temporarily off for 10 minutes - Aug 19, 5pm Pacific - we'll shut b

[twitter-dev] Re: Twitter API keys fail to verify

! This was it. @ Yeah. # Mmm k. On Aug 14, 3:06 am, Tom van der Woerdt wrote: > On 8/13/10 11:58 PM, Gurpartap Singh wrote: > > > > > > > Will talk in points: > > > # An existingOAuthappwhich already has xAuth access, works > > perfectly in the implementation. > > > # Created a newOAuthappwith Tw

[twitter-dev] Re: Twitter API & the Basic Auth Shutdown: Everything you need to know.

Thanks for a great job in transitioning... Incidentally, any chance of instituting having multiple aliases for a single user...so it is possible check timeline by checking an alias of a user in addition to just user id or name..I am asking because this has plenty of real world applications... Shob

[twitter-dev] Re: Twitter API HTTP Heading

Half of it - although I had originally replaced it. I'm trying to create a HTTP heading to send a tweet to my account (using GLBasic). Unfortunately the API documentation is no help in how this should be defined or what exactly to send. >From the scraps of a C# demo, I've got : send$ = "POST

[twitter-dev] Re: Twitter API SSL certificate failing validation was Re: Twitter4J and sun.security.validator.ValidatorException

I tryed both methods -Dtwitter4j.http.useSSL=false and System.setProperty("twitter4j.http.useSSL","false");. but they doesn help for me what i do wrong?

Re: [twitter-dev] Re: [twitter-api-announce] link wrapping on the API

Quoting DeWitt Clinton : Awesome, thanks for the quick response! Those are the right answers, too. : ) Though there's an inconsistency with returning 301's and also requiring every click to go through the t.co link (as required by the ToS). A 301 means that the redirect is cacheable by any i

Re: [twitter-dev] Re: [twitter-api-announce] link wrapping on the API

Hi Raffi, On 9/06/10 9:57 AM, Raffi Krikorian wrote: that would be an awesome service! Currently we use one our own services (http://metauri.com/) to do this for http://trendsmap.com/. In addition to the title, it also gives the content type, which can be useful in determining how, or if to u

[twitter-dev] Re: [twitter-api-announce] link wrapping on the API

Raffi: Never mind. I just saw the Twitter blog post. The motivation for this is to get metrics for Promoted Tweets and Resonance. Hence, the answer is: Suck it up. DeWitt: Yikes, discarding all shortens between t.co and the final link will seriously mess with the click stats of a few million peopl

Re: [twitter-dev] Re: [twitter-api-announce] link wrapping on the API

Awesome, thanks for the quick response! Those are the right answers, too. : ) Though there's an inconsistency with returning 301's and also requiring every click to go through the t.co link (as required by the ToS). A 301 means that the redirect is cacheable by any intermediary (because it is p

Re: [twitter-dev] Re: [twitter-api-announce] link wrapping on the API

that would be an awesome service! On Tue, Jun 8, 2010 at 4:50 PM, John Barratt wrote: > Hi Raffi, > > > On 9/06/10 8:57 AM, Raffi Krikorian wrote: > >> "url" : "http://t.co/s9gfk2d4";, >> "display_url" : "http://dev.twitter.com";, >> "indices" : [23, 43] >> > Any chance of getting the title of t

Re: [twitter-dev] Re: [twitter-api-announce] link wrapping on the API

> > *1)* Will the redirect from t.co -> domain.com be a 301 Moved Permanently > or a 302 Found response? > 301! > *2)* Will the t.co URL redirect point to the URL in the original tweet, or > will it point to the ultimate resolved URL? > > I.e., if I post "Check out my site at http://bit.ly/abcd"

[twitter-dev] Re: [twitter-api-announce] link wrapping on the API

Hi Raffi, On 9/06/10 8:57 AM, Raffi Krikorian wrote: "url" : "http://t.co/s9gfk2d4";, "display_url" : "http://dev.twitter.com";, "indices" : [23, 43] Any chance of getting the title of the resolved URL added in here too if available? Then we could display a link like : http://t.co/s9gfk2d4";

[twitter-dev] Re: [twitter-api-announce] link wrapping on the API

Hi Raffi, Interesting... A couple of quick questions: *1)* Will the redirect from t.co -> domain.com be a 301 Moved Permanently or a 302 Found response? *2)* Will the t.co URL redirect point to the URL in the original tweet, or will it point to the ultimate resolved URL? I.e., if I post "Check

[twitter-dev] Re: Twitter API - Grab profile pic URL

Whoop Whoop Just managed to sort the issue out... Basically twitter don't update the profile pic info for that API call unless you create a new tweet... I hadn't created any new tweet since changing my profile pic so it showing outdated data Just glad its fixed! Thanks for your help guys!

[twitter-dev] Re: Twitter API - Grab profile pic URL

Hey Mark, That API call gives me the right profile pic but only displays the last tweet. I am needing an API Call which gives me at least the last three tweets and all the user information. I am using the Drupal CMS Twitter Module. I can easily change the API call it uses but wouldn't be able t

Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers

Thanks!! - Original Message - From: "John Kalucki" To: twitter-development-talk@googlegroups.com Sent: Monday, April 26, 2010 12:34:35 PM GMT -08:00 US/Canada Pacific Subject: Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers Cu

Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers

Currently we deliver these to user streams. We'll probably conditional them, default off, before we go to beta. On Mon, Apr 26, 2010 at 12:32 PM, M. Edward (Ed) Borasky wrote: > On 04/25/2010 08:40 PM, John Kalucki wrote: >> The user endpoint is very similar to the filter endpoint. We're tuning

Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers

On 04/25/2010 08:40 PM, John Kalucki wrote: > The user endpoint is very similar to the filter endpoint. We're tuning > the parameters, but, yes, you can track and loc, just as on filter, > but you can't follow. > > Duplicated JSON isn't really a big concern, but I'll look into what we > can trim.

Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers

On 04/25/2010 08:40 PM, John Kalucki wrote: > The user endpoint is very similar to the filter endpoint. We're tuning > the parameters, but, yes, you can track and loc, just as on filter, > but you can't follow. Yeah, I figured I'd be unable to follow another 200 folks on top of the over 5000 I alr

Re: [twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers

The user endpoint is very similar to the filter endpoint. We're tuning the parameters, but, yes, you can track and loc, just as on filter, but you can't follow. Duplicated JSON isn't really a big concern, but I'll look into what we can trim. The markup is rendered once for all receivers. If the ru

[twitter-dev] Re: [twitter-api-announce] User Streams Preview Open To All Developers

On 04/19/2010 11:20 AM, John Kalucki wrote: > Experiment! > > -John Kalucki > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. > I think I saw this request go by, so I'll just add my vote for showing unfollows as well as follows. I just started testing with "curl" tonight. So far the

Re: [twitter-dev] Re: [twitter-api-announce] countdown to OAuth / basic auth removal / OAuthcalypse

it will be a while longer before streaming is converted. we'll of course, keep you as updated as possible! On Sun, Apr 25, 2010 at 11:36 AM, Dima Brodsky wrote: > Hey, > > What's the timeline like, if you know, for the streaming api? > > Thanks! > ttyl > Dima > > > On Sat, Apr 24, 2010 at 8:40

[twitter-dev] Re: [twitter-api-announce] countdown to OAuth / basic auth removal / OAuthcalypse

Hey, What's the timeline like, if you know, for the streaming api? Thanks! ttyl Dima On Sat, Apr 24, 2010 at 8:40 AM, Raffi Krikorian wrote: > hi all. > > you're going to be hearing a lot from me over the next 9 weeks. our plan > is to turn off basic authorization on the API by june 30, 201

[twitter-dev] Re: [twitter-api-announce] Early look at Annotations

I'd like to forward this to the Crisis Mapping / Disaster Response mailing lists I'm on. They're been very active with Twitter. Is that OK? On 04/16/2010 10:54 AM, Marcel Molina wrote: > Hey everyone. One of the things we talked about at Chirp is the new > Annotations feature we're working on. In

[twitter-dev] Re: [twitter-api-announce] Early look at Annotations

Developers can use reverse-FQDNs (like Java's packages) for their namespaces, which prevents collisions without actually requiring nesting. -James A. Rosen On Apr 16, 2:51 pm, Marcel Molina wrote: > More namespace nesting would of course increase people's ability to > taxonomize. It's a splipper

Re: [twitter-dev] Re: [twitter-api-announce] Early look at Annotations

On Fri, Apr 16, 2010 at 9:21 PM, dhavaln wrote: > but this will create islands of information and information retrieval > based > on annotations will be difficult for other applications. > i.e. amazon.com:book-rating{isbn:34345434, rating: 5} > > it should be easier for other applications to find

[twitter-dev] Re: [twitter-api-announce] Early look at Annotations

I feel what Marcel proposed is pretty cool, and does not need much change before rolling out the first version, to start discovering what needs to be improved based on real use. Rogue apps are a concern with or without annotations. It's the same problem as, say, spamming people with @mentions or #

[twitter-dev] Re: [twitter-api-announce] Early look at Annotations

but this will create islands of information and information retrieval based on annotations will be difficult for other applications. i.e. amazon.com:book-rating{isbn:34345434, rating: 5} it should be easier for other applications to find information based on annotations. On Apr 16, 11:59 pm, gabr

Re: [twitter-dev] Re: [twitter-api-announce] Early look at Annotations

We definitely want to have documents on dev.twitter.com with best practices and guildelines. That will be key. We're looking for everyone to help devise the rules of the road. On Fri, Apr 16, 2010 at 11:59 AM, gabriele renzi wrote: > On Fri, Apr 16, 2010 at 8:51 PM, Marcel Molina wrote: > > Mor

Re: [twitter-dev] Re: [twitter-api-announce] Early look at Annotations

On Fri, Apr 16, 2010 at 8:51 PM, Marcel Molina wrote: > More namespace nesting would of course increase people's ability to > taxonomize. It's a splippery slope though and we are trying to balance > expressiveness with simplicity. Providing for arbitrarily nested namespaces > increases complexity

Re: [twitter-dev] Re: [twitter-api-announce] Early look at Annotations

More namespace nesting would of course increase people's ability to taxonomize. It's a splippery slope though and we are trying to balance expressiveness with simplicity. Providing for arbitrarily nested namespaces increases complexity considerably both from an implementation perspective and a comp

[twitter-dev] Re: [twitter-api-announce] Early look at Annotations

> * What is an annotation more exactly exactly? > First off let's be clearer about what an annotation is. An annotation is a > namespace, key, value triple. A tweet can have one or more annotations. > Namespaces can have one or more key/value pairs. first, annotations are cool, thanks. But why tri

[twitter-dev] Re: Twitter API - users/search - Help Required

Oh! I forgot to say thanks to Nic Ross. Thanks to you also. On Apr 11, 10:06 pm, Raffi Krikorian wrote: > ok - sorry - i was thrown off by "ipad".  the results should change, but the > velocity of change may depend.  name search results are ordered so the > "best" results are further up -- new u

[twitter-dev] Re: Twitter API - users/search - Help Required

OK I got it. thanks for the support :) On Apr 11, 10:06 pm, Raffi Krikorian wrote: > ok - sorry - i was thrown off by "ipad".  the results should change, but the > velocity of change may depend.  name search results are ordered so the > "best" results are further up -- new users who get added to

Re: [twitter-dev] Re: Twitter API - users/search - Help Required

ok - sorry - i was thrown off by "ipad". the results should change, but the velocity of change may depend. name search results are ordered so the "best" results are further up -- new users who get added to the system may not make the top 1000 users that namesearch can return. as users are active

[twitter-dev] Re: Twitter API - users/search - Help Required

Raffi and Nic, thanks for replying :) Yes, I'm concerned with the user search and by mistake I wrote "ipad", I should have written some name! Now please let me know whether the result should be changed or I'll keep getting the stale result. I reckon twitter keep getting new users every next min

[twitter-dev] Re: Twitter API - users/search - Help Required

Ok don't take it here an example for "ipad" may be it was his mistake. Lets say take an example for any common names like "James" or "Chang" or "Chen" don't you expect there will be far more results than 1000 So, the point he is making here is will twitter keep the same result of 1000 users for ev

Re: [twitter-dev] Re: Twitter API - users/search - Help Required

Well, with name search the users are not going to change much. How many users do you expect to have the name "ipad" (even with the rate that users are being created). Am I confused? On Apr 11, 2010, at 1:01 PM, Nic Ross wrote: Sorry I didn't see my last reply so I am posting it again

[twitter-dev] Re: Twitter API - users/search - Help Required

Sorry I didn't see my last reply so I am posting it again @Raffi Krikorian I think Jimmy is asking for searching users not tweets. Look at his URLs they contain "users/search" and also "users/search" API call limits the result to 1000 (20 result each page) which he is mentioning. The search API

[twitter-dev] Re: Twitter API question??

I know it's obvious, but have you tried looking here? http://apiwiki.twitter.com/Twitter-API-Documentation Best, Eelke On Apr 4, 12:06 pm, Stuart Chaney wrote: > Hey guys, > > Long time PHP developer and am just getting into the twitter API. :) > > Quick question... How is this done?http://twitte

[twitter-dev] Re: Twitter API/PHP/Ajax Dev. Available

Is there a way to create something so you can see your Twitter and Facebook accounts in one place? I thought you could do it on Tweet Deck, but someone said no. We really need a tool like this to see emails, tweets, texts, FB posts all in one app/GUI. On Mar 27, 12:30 am, Adi wrote: > Hi friend

[twitter-dev] Re: [twitter-api-announce] Upcoming changes to the way status IDs are sequenced

Sequential ID generation is quite useful on my side, because I can trust these INT to compare tweets date (and sort them, for example). Because of the "random part" you're mentioning, the "bigger ID == Older" rule won't always be true. This can be quite problematic. All the best, Arnaud. Le 26

[twitter-dev] Re: Twitter API and ETags - No 304s?

On Feb 24, 1:20 pm, Tim Haines wrote: > Thanks for sending through the examples.  I must have been setting the > header incorrectly - missing the quotes or something.  It does indeed work > for favorites too, whether authenticated or not.. Good to hear... I was having the same problem. First I wa

Re: [twitter-dev] Re: Twitter API and ETags - No 304s?

Hi Phil, Thanks for sending through the examples. I must have been setting the header incorrectly - missing the quotes or something. It does indeed work for favorites too, whether authenticated or not.. Tim. On Wed, Feb 24, 2010 at 2:15 PM, philoye wrote: > On Feb 22, 1:31 pm, Tim Haines wr

[twitter-dev] Re: Twitter API and ETags - No 304s?

On Feb 22, 1:31 pm, Tim Haines wrote: > The Twitter API returns ETags, that seem to change when the content > changes and otherwise not. It doesn't seem to return 304's when the > same ETag is sent back to it though. > > Has anyone seen it send 304s? The API always seem to return no-cache and pa

[twitter-dev] Re: Twitter API and ETags - No 304s?

I noticed this too, also noticed that Twitter sends no-cache header and expiration far in the past, which is just another way to tell browser not to cache anything. You can find my recent post here under subject "Why do you sent no- cache headers" I don't know why they sending Etag then, looks li

[twitter-dev] Re: [twitter-api-announce] Changes to search results for trending topics

Hi Ryan, Digging up a rather old announcement from you, because this is exactly what I was looking for. But I am not sure if a special parameter is required to enable trend filtering. I just now added a "trends" feature in my app, and thus noticed that the search results for trends still shows so

[twitter-dev] Re: [twitter-api-announce] Social Graph API: Legacy data format will be eliminated 1/11/2010

I noticed the ruby TwitterOauth library needs a patch. On Dec 22, 2009, at 4:13 PM, Wilhelm Bierbaum wrote: > We noticed that some clients are still calling social graph methods > without cursor parameters. We wanted to take time to make sure that > people were calling the updated methods which

[twitter-dev] Re: Twitter Api-Problem

Hi Patrick, i found the failure: I forgot to add the oauth_token_secret to the Authorization header... Thank you for you help anyway! Best regards Julius

[twitter-dev] Re: Twitter Api-Problem

For oAuth, when I was working with a good library, I noticed it would not work (it would choke) if I did not use string_tags( ) on input. Maybe that will help. ~PK On Dec 12, 11:46 pm, julius wrote: > Dear all, > > I have a problem using the Twitter-API with my own OAuth library. My > own effor

[twitter-dev] Re: Twitter API call to statuses/followers.json / xml - protected users out of sync.

Hi, I am experiencing exactly the same behavior and described the problem for the statuses/friends call at http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c63e3288e76ed581 and in issue http://code.google.com/p/twitter-api/issu/detail?id=1121. Other calls to retrieve a

[twitter-dev] Re: Twitter API gives different results for different IPs?

We're getting ready to launch an avatar-centric app, and it would be great to have some idea what the status is of this issue. Thanks. h On Nov 21, 6:11 am, howard wrote: > I have 3 letters to suggest to you: > > CDN > > :-) > > Hope to hear good news soon! > > -H > > On Nov 20, 4:46 pm, Raffi

[twitter-dev] Re: Twitter API gives different results for different IPs?

I have 3 letters to suggest to you: CDN :-) Hope to hear good news soon! -H On Nov 20, 4:46 pm, Raffi Krikorian wrote: > hi howard. > > its on the list - we have a theory as to what is wrong, but that still   > needs to be investigated, tested, etc. > > please just continue to add color and

Re: [twitter-dev] Re: Twitter API gives different results for different IPs?

hi howard. its on the list - we have a theory as to what is wrong, but that still needs to be investigated, tested, etc. please just continue to add color and data to the thread on the google code tracker so that we have more information to look at. If you need ANY other help, just ask a

[twitter-dev] Re: Twitter API gives different results for different IPs?

If you need ANY other help, just ask and we can produce other test pages for you to accelerate the process. Just specify what you need and we can try to whip up a tool. OK? We're glad to help. Raffi, can you tell me where this is on your priority list, so that we can plan our development? The use

  1   2   3   >