[twitter-dev] Twitter API SSL certificate failing validation
Has Twitter done something with its SSL certificates lately? As in sometime this afternoon? We've been seeing a ton of sun.security.validator.ValidatorExceptions coming out of Twitter4J since about 5:30PM, USCentral. -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[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 j...@twitter.com wrote: On Mon, Jul 18, 2011 at 8:17 PM, pgarvie garvie.p...@gmail.com wrote: Has Twitter done something with its SSL certificates lately? As in sometime this afternoon? We've been seeing a ton of sun.security.validator.ValidatorExceptions coming out of Twitter4J since about 5:30PM, USCentral. The certificate for api.twitter.com previously used a wildcard certificate which was issued by Rapid SSL. We switched the API SSL certificate (after much testing) to a Verisign SSL certificate today and the IP to dedicated VIPs. If you are using Java, there may be a chance that you do not have the Verisign Root CA Certificate installed in the Java Keychain of your application. Make sure that exists. You'll need that to verify our certificate chain. You want this Root CA, which is available from Verisign (or in this file:http://curl.haxx.se/ca/cacert.pem) i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority - G2/OU=(c) 1998 VeriSign, Inc. - For authorized use only/OU=VeriSign Trust Network You may also need to clear your DNS cache and/or restart your application. I've seen Java's security layer not revalidate SSL certificates correctly until restart, but I know little about how your application functions. -John Twitter Security -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] friendships/destroy friendships/create error messages
Could be that it's just me, but when I call the friendships/destroy method on a screen name of someone not being followed, I no longer see the You are not friends with the specified user message. Instead I'm seeing a Successfully unfollowed screen name.. As well, when I call the friendships/create method on the screen name of someone already being followed, I'm no longer see the Could not follow user: screen name is already on your list. message. Here also, I'm seeing a Successfully following screen name now.. Anyone else experiencing this? Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: oAuth still working for everyone.?
Twitter4J is ok See this: http://www.springone2gx.com/blog/andrew_glover/2010/09/oauth_ing_twitter_with_twitter4j It's the parameters you pass to twitter.getOAuthAccessToken() On Dec 3, 12:13 am, Yusuke yus...@mac.com wrote: Hi, I had confirmed the error message several hours ago and was looking into it. And somehow I don't see the error now. Please give it a try once again. If the problem persists, please post the exception stacktrace to twitte...@googlegroups.com.http://twitter4j.org/en/index.html#mailingList Thanks, Yusuke On Dec 3, 10:09 am, Hector hvazq...@gmail.com wrote: Does anyone using twitter4j solve the oauth_verifier issue? Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: friends/ids returning more users than statuses/friends
Pretty much the same behavior with followers/ids and statuses/ followers: http://code.google.com/p/twitter-api/issues/detail?id=1033colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component This one was reported on 9/13, and the status is still New. Something along these lines was first reported and accepted back on 9/8, and may be related as well: http://code.google.com/p/twitter-api/issues/detail?id=1021colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component Hasn't been reported as resolved yet, so don't know what the status of it is. pfg On Sep 17, 5:54 pm, Mark Sievers mark.siev...@gmail.com wrote: For user 728293. friends/ids returns 154 ids where statuses/friends returns 153 users over 2 pages. The missing user is 15699041 who actually works in my office, and whose account is still active and unsuspended. Has anyone else noticed this behaviour or can explain it? M
[twitter-dev] Re: Followers Friends IDs Are Seriously MESSED Up!
Using Twitter4J, and what I've been seeing is last night, getFollowersIDs(), including suspended. This AM, the filtering of suspended accounts seems to be working again. On the other hand, getFollowersStatuses() doesn't seem to be filtering out the suspended accounts. pg On Sep 5, 7:36 am, Dewald Pretorius dpr...@gmail.com wrote: John, Just so we know, is this 5,000 thing going to be fixed over the weekend, or will we have to wait until Tuesday? Dewald On Sep 5, 12:35 am, John Kalucki jkalu...@gmail.com wrote: We're aware of the problem with the following API not returning more than 5,000 followers. Apparently this call has recently been unreliable was often timing out and returning 503s. A change to fix the 503s limited the results to 5000 followers prematurely. We're going to get this back to the 5000 followers, but with 503's state as soon as we can, but we're fighting several fires at once tonight. More in a few minutes. -John On Sep 4, 7:56 pm, Dewald Pretorius dpr...@gmail.com wrote: Not only do the social graph calls now suddenly, without any prior warning of announcement, return only 5,000 ids, it is messed up even when you do the paging as per the API documentation. Case in point. @socialoomph has 16,598 followers. If you page through the follower ids with page, you get only 12,017 entries. This is highly frustrating, and it has now completely screwed up my follower processing. It does not help that Twitter has rolled out something into production without any kind of testing, right before a weekend. Dewald
