https://dev.twitter.com/blog/planning-for-api-v1-retirement

[carasmo]

Apparently any script using the api (I'm really confused) won't work. Right now there's a blackout showing what it will be like when they retire this, what does this mean to the users of the sea of cloud scripts?

[RiccardoRics]

Hi, i've modified the function "build_api_url()" adding the 1.1 api path where required.

EG:
return proto+"//"+s.twitter_api_url+"/1/"+s.username[0]+"/lists/"+s.list+"/statuses.json?page="+s.page+"&per_page="+count+common_params;

to

return proto+"//"+s.twitter_api_url+"/1.1/"+s.username[0]+"/lists/"+s.list+"/statuses.json?page="+s.page+"&per_page="+count+common_params;

EDIT: That's not working anymore, i'm reading the twitter API 1.1 to find a solution.

[purcell]

Duplicate of #330 and #264

[purcell]

In particular, please see #264 for related discussion.

[ghost]

It appears they require authentication from now on, so unfortunately it's not just a matter of hitting the correct url

https://dev.twitter.com/docs/api/1.1/overview#Authentication_required_on_all_endpoints