Discussion around Planning API v1's Retirement

tweetizer_test · 2013-02-14T09:39:41.000Z

We have a website that offer users to display their timeline in their profile page. All they have to do is to fill in their user screen name, then we access their time line by JS and v1.0 API. We cannot ask them to create a widget themselves, shall we?

mar_chi · 2013-02-18T14:58:31.000Z

Hello, is the time frame of the blackout test known (as well as time zone of that time frame)? If yes, what is it?

episod · 2013-02-18T17:24:30.000Z

The first blackout test of unauthenticated requests will occur from approximately 9am to 10am PST on March 5th, 2013.

mar_chi · 2013-02-18T17:30:19.000Z

Thank you!

jbuckca · 2013-02-20T19:45:00.000Z

We’d love to use embedded timelines to replace our use of the unauthenticated search API, but there doesn’t seem to be an API available to create them. Is this coming down the pipe at some point? Maybe as an oEmbed endpoint, like https://dev.twitter.com/docs/api/1.1/get/statuses/oembed ?

KeithDPatch · 2013-02-21T01:43:00.000Z

How can you be retiring the API V1.0 when the Embedded Timeline samples with the API V1.1 on this officail page:

https://dev.twitter.com/docs/embedded-timelines

do not show. The API is broken for Twitter, just as it is for many of us.

How embarrassing!

@KeithDPatch ,
http://www.keithdpatch.com ,
http://blog.fuelcellnation.com

episod · 2013-02-21T15:54:07.000Z

We’ve definitely gotten a lot of requests for an API and it may come along some day, but I wouldn’t expect a dynamically-settable search widget any time soon. You would probably need to create your own server-side implementation for that.

episod · 2013-02-21T15:55:54.000Z

I personally have no trouble seeing the examples on that page.

There are a number of browser extensions/plugins out there, such as Adblock, that can conflict with the Javascript that loads our embedded timelines.

If you’re sure that you aren’t using a plugin like that that might be conflicting and you’re still having the issue, could you share the web browser, version, and OS you’re using?

dokfranco · 2013-02-21T18:18:06.000Z

I’m trying to replace the old search widget with the new embedded search timeline, but it behaves really strangely. When I preview it in the widget config page it gives me all the most recent tweets with my #digitalia hashtag:

But when I insert the code in my website the widget displays completely different search results, with many missing tweets:

osilviotti · 2013-02-21T19:43:10.000Z

The embedded timelines aren’t showing for me either on Firefox 19 or Chrome 24 - both with all extensions disabled. All I can see is a link which opens in a new window/tab labelled ‘Tweets by @twitterapi’ or ‘Favorite Tweets by @Support’

pasometo · 2013-02-22T07:52:43.000Z

Hi Taylor. I am trying to use version 1.1 for each request urls as version 1 is deprecated. I need to know how to authenticate each request using version 1.1.
FYI I am using scribe 1.3.0.

timwhitlock · 2013-02-25T13:26:00.000Z

I notice that parts of the Field Guide, such as this
https://dev.twitter.com/docs/platform-objects/tweets
contain API 1.0 JSON examples and links to 1.0 docs.

There is no warning on this page that the example resources are to be retired. Can you confirm that these links are not exceptions to the retirement of 1.0?

episod · 2013-02-25T16:18:37.000Z

We’re a little behind in updating certain areas of docs with pure-1.1 examples. In most cases where there are still references to v1 but no warning is presented that the doc describes deprecated content, the differences between the two versions are minimal or non-existent, beyond the formality of an API version change. All v1 resources are being retired.

episod · 2013-02-25T16:20:39.000Z

The Scribe library should be fully capable of negotiating access tokens, signing and making requests for API v1.1, as it’s an OAuth library agnostic to the APIs it interfaces with. The instructions included with Scribe, adapted with the knowledge you have of API v1.1’s auth & resource paths, should be adequate to getting you up and running. Is there a particular area you’re wondering about?

episod · 2013-02-25T16:21:46.000Z

Embedded Timelines don’t offer quite the same perspective on the Search index as the website or the search/tweets API. Some discrepancies are to be expected, especially just after creation of your new widget.

dokfranco · 2013-02-25T16:27:25.000Z

Is there any documentation explaining in what these discrepancies consist? The audience of our show comments during live events using #digitalia hashtag, and it would be very disorienting for them to send their message and not see them in the widget embedded on the webpage with our liveshow.

timwhitlock · 2013-02-25T17:17:07.000Z

Thanks Taylor. I just wanted to be sure, because I’m contacting a lot of clients running old code and don’t want to panic them with incorrect information.

m360digital · 2013-02-25T17:50:00.000Z

I have a few questions\concerns about the API 1.1 display ~~guidelines~~ requirements

As a design\digital agency, we’ve created a number of custom designed twitter feeds on our client websites using the user_timeline which often consist of the twitter logo and latest tweet only - nothing else - as in many cases we have felt things would either look too cluttered or stifle creative integration of tweets.

Can I check that from March we will have to display all the below information anywhere where twitter feeds are integrated into our websites?
Author avatar, username, actions (re-tweet, reply, favorite), correct linking timestamp etc etc as per https://dev.twitter.com/terms/display-requirements

That would be a shame because some of the best uses of designed feeds would look a whole lot worse if they had to conform such as the samples on: http://www.sitepoint.com/integrate-twitter-into-web-design/

Also, how will this be enforced and will developers receive any sort of notice that display requirements have been broken or will the app\token just cease to work? Will there be any more grace period?

The majority of sites I’ve seen with integrated feeds seem to not have upgraded to the new API with authentication let alone conform to the display requirements…

Thanks

Tom

pasometo · 2013-02-26T06:52:36.000Z

Thanks Taylor.I have figured it out.

episod · 2013-02-26T14:23:20.000Z

Yes, the display requirements apply to all scenarios in which Tweets and Twitter content are shown. Our platform operations team reaches out to developers and sites that are non-compliant with guidelines – make sure that the contact information associated with applications and accounts used with the API or widgets are up to date. Many of the widgets out and about today are based on our old legacy widgets or unauthenticated API calls, and many of those will just cease working once API v1 is fully retired.