API v1 Retirement Discussion

benward · 2013-05-10T18:52:08.000Z

Hi Nick,

Thanks for the very detailed write up regarding the colour contrast issues. We take the accessibility of the widgets seriously, and it’s my intention that we ship things that make Twitter accessible to all; we already worked hard to include solid support for ARIA live regions, text fallbacks and contextual abbreviations. Following your issue, we shipped an update to embedded Tweets and timelines yesterday that adopts your recommended colour adjustments for the offset text, so all text in the widget should now at least meet the 4.5:1 recommended ratio in the standard themes.

The update also fixes a couple of missing :focus styles, and cleans up the focus styles in general.

Finally: The issue also raises concern about the keyboard focusability of Tweet actions. We will try to further improve that at some point as well, but the existing behaviour is as follows, and since the actions are not core content I do not believe this should be a blocker in assessing your WCAG compliance.

• Tweets that can be expanded (either an ‘Expand’ link, or ‘View ’ link) display the actions statically in the expanded state where they can be focused.
• In browsers supporting touch events the actions are toggled to always display, with increased padding to aid finger tapping.

This leaves the case of Tweets that do not have stats or media, and do not have an ‘expand’ link. Here, actions must be accessed by visiting the Tweet permalink. This gap in immediate access is one that we’ll look to improve upon in the future.

Please let me know if you have any other concerns. It means a lot to me that we ensure content from Twitter is universally available.

Thanks,

Ben

meni56 · 2013-05-12T11:13:23.000Z

Hi,
We are trying to find a way to view a twitter roll without logging in (as before), in a flex application.
How can this be done?
Logging in makes the feature weaker, and less usable. We used to require login only when posting a tweet.

Is there any way to do it ?
Thanks

Brukhar · 2013-05-22T13:12:00.000Z

Since API v1.1 was rolled out, I’ve been intermittently getting this error, but it’s not a HTTP410 so I can’t figure out why it started at the time 1.1 was released and why it’s only happening intermittently:


PHP Warning: DOMDocument::load(http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=becountedtoday) [domdocument.load]: failed to open stream: HTTP request failed! HTTP/1.0 400 Bad Request in \httpdocs\petition\global\index.php on line 492 PHP Warning: DOMDocument::load() [domdocument.load]: I/O warning : failed to load external entity "http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=becountedtoday" in \httpdocs\petition\global\index.php on line 492

Edit: Would love to know what code to change to make this work with 1.1

episod · 2013-05-22T14:36:20.000Z

That error looks like it’s more likely a API v1 rate limiting error than anything else.

RSS is no longer part of the API, so you’ll have to change to the JSON response format and consume that into a hashmap structure rather than as a DOM document. It looks like you’re making server-side calls without an end-user context, so using [node:13439] would probably be your best bet to retrieve https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=becountedtoday with – API v1.1 requires all requests to be authenticated.

riffraff · 2013-05-23T10:38:44.000Z

will there be another blackout test ?
That would be mightily useful in identifying if there is something not updated which escaped fell the cracks.

Arrogant_Twat · 2013-05-24T18:46:15.000Z

I don’t know if this is related to the blackout the other day, but around 12:00 on May 22 DMs stopped working for me in the web client. All iOS and OSX clients seem to work (Tweetbot and Twitter on iOS, Tweetdeck on OSX).

I don’t see how it can be related, but I’m at a complete loss. Every DM send from a browser window results in “Internal Server Error”. Guidance or redirection would be appreciated.

dhh05 · 2013-05-25T16:34:46.000Z

Is there any replacement for getting replies to tweet by api.twitter.com/1/related_results/show.json?id=337309045331460097
or is the get reply function simply abandoned in the new API ?

Sarasvati10 · 2013-05-27T17:54:26.000Z

well I thought I had no problems with the migration, but then my poor app started to give 0 http errors. I think it has been in black out for days and I haven’t realized. I am using both Math Harris and Abraham Williams’ libraries (php). I had modified them (or thought I had) successfully for the 1.1 Rest API. The app stopped working and there’s no way to get it back to work. I assume that the 0 error code just means that the cURL never made it to Twitter. Is it on Twitter’s side or is it me? If it is me, is it the server? Something changed in the past fes days and I don’t reflect the changes? I have no idea - been trying to find a solution all day, to no avail.

episod · 2013-05-28T14:45:22.000Z

We’ll let everyone know with a blog post and @twitterapi tweet if we’ll have another blackout test. It’s possible.

episod · 2013-05-28T14:45:57.000Z

No, the mostly undocumented related_results/show method from v1 isn’t available in API v1.1

prmdherlambang · 2013-06-06T08:17:00.000Z

Hi @episod as suggested to use api 1.1 , i just try to use api search 1.1 (https://dev.twitter.com/docs/api/1.1/get/search/tweets) using this query : https://api.twitter.com/1.1/search/tweets.json?q=twitter but return error. canyou explain why?
thanks.

socialtwatter · 2013-06-06T13:54:44.000Z

Any one know why search.twitter.com has gone dead [ or at least replying with 0 tweets ] .
I know it’s on teh way out with v1 - but it is not yet switch off day - and there are no test blackout listed for today - its been dead for about 10 hours now - killing the old twitter off the shelf javascript widget [ calls that domain for its json ]… and our backend calls to populate our own widgets…

… help …

socialtwatter · 2013-06-06T13:55:49.000Z

if it has suddenly gone dead [ with no error messages ] - confirm you are using https not http - this may help ( or may be a red herring - you decide :- )

episod · 2013-06-06T14:02:06.000Z

There’s a bug with the search API right now: [node:18242].

marcoslinde · 2013-06-06T18:16:00.000Z

I’m trying to get a bearer token, but am getting a 500 error. Below is the request; can you see what I’m doing wrong?
_request => bless({
_content => “grant_type=client_credentials”,
_headers => bless({
“authorization” => “Basic [credential created per https://dev.twitter.com/docs/auth/application-only-auth]”,
“content-type” => “application/x-www-form-urlencoded;charset=UTF-8”,
“user-agent” => “bfi”,
}, “HTTP::Headers”),
_method => “POST”,
_uri => bless(do{(my $o = “https://api.twitter.com/oauth2/token”)}, “URI::https”),
_uri_canonical => ‘fix’,
}, “HTTP::Request”),

nidhinbaby · 2013-06-06T19:23:00.000Z

Issues on getting search results, I am able to authendicate and get my timeline details using the url https://api.twitter.com/1.1/statuses/user_timeline.json

But, when I try the search using the URL https://api.twitter.com/1.1/search/tweets.json?q=%23freebandnames&since_id=24012619984051000&max_id=250126199840518145&result_type=mixed&count=4 I am getting an error “Could not authenticate you” with code 32

Can you please help to solve it, Thanks in Advance

episod · 2013-06-07T13:57:36.000Z

It’s not obvious to me what looks amiss here. Are you able to get a successful bearer token request using curl on the command line? If so, I recommend comparing that valid request with what you’re producing here and get it closer to matching.

episod · 2013-06-07T13:58:50.000Z

Most likely it’s an encoding issue in your OAuth signature basestring – or perhaps you’re not sorting the parameters in the basestring. Take a look at [node:204].

MRCTESTER · 2013-06-10T13:13:19.000Z

What time tomorrow will API v.1.0 be retired?

remarkUP · 2013-06-11T15:40:09.000Z

What time will API v1.0 be retired today? We’ve updated about 50 of our congressional house client that we were able to simply replace and customize the embeds but 10-20 use extensions such as Lifestream that use the old Twitter 1.0 and the developers are still working on upgrading the components for the newer 1.1. So once we know what time they will break, we will login and disable twitter on all those sites for now until hopefully we have a resolution later this month.