Discussion around List IDs becoming 64-bit integers


#1

This is a discussion topic for you to ask any questions or report concerns about the upcoming upgrade to 64-bit integers for List IDs. This affects those using the Streaming API’s User or Site Streams APIs, as well as those working with the REST API. See this [node:23307, title=“blog post”] for more information.


#3

Hi,
We have integrated our java based web application with twitter using twitter4j jar.
It was working fine.
But after December 10, 2013 New SSL certificates deployment, we are getting following exception when communicating with Twitter.
We don’t make any changes in my code.

sun.security.validator.ValidatorException: PKIX path building failed:sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

So which changes we have to made to work it again.

Thannks in advance.


#4

Hi,

Are you planning to fix list-creation related issues in the mean time?
cf.
“lists/members/create_all returns 404 if any user_id is invalid” https://dev.twitter.com/issues/383
"Duplicate List when create" https://dev.twitter.com/issues/1412

These make programmatic management of lists very difficult.


#5

Make sure you have the latest root certificates for SSL. Please see [node:4598].

The GeoTrust Global CA can be downloaded from -http://www.geotrust.com/resources/root-certificates/

The Root CA Cert that you’ll need is http://www.geotrust.com/resources/root_certificates/certificates/GeoTrust_Global_CA.pem

We do not recommend having this CA Certificate as the only certificate in your software. We recommend having all of the major roots (Geotrust, Verisign, Digicert, Symantec) so that changes in the future do not impact your software.


#6

Is there a beta tier or staging resource against which to test our apps prior to any breaking changes being deployed to Twitter REST API prod?