#68

If you have bulk embedded timeline needs, it’d probably best for you to roll your own implementation using the REST and Streaming APIs.

#69

I don’t know about anyone else, but as a designer who takes pride in my work, I REFUSE to put the new Fugly twitter timelines on client websites. If there’s not going to be a way for me to customise the look/feel of tweets to match my designs, there’s not going to be a timeline/feed on them.
Not sure why twitter would want to jeopardise their traffic like this, but have fun trying to convince advertisers to chuck money at you when numbers go down. I mean, that’s what monetising the site’s all about, right?
Happy to authenticate til I’m blue in the face, hell, I’ll sign a contract in blood if you need it… but I’m not putting that on my design.

#70

Will this widget continue to work? Because it still is and it would be GREAT if it could keep working.
http://widgets.twimg.com/j/2/widget.js

#71

This widget is among those currently deprecated and ultimately retiring in May 2013.

#72

Hi… First off I should say that I’m by no means a developer, so I’m a little unsure about what I’ve been reading. I only discovered something was going on with the Twitter API recently when I was thinking about perhaps placing a second feed somewhere on my website.

I could describe in detail how I use my twitter feed, but best thing you can do is take a look on my website at www.wmphoto.co.uk. It’s just a simple feed in a bar down the right hand side of my page. The two important things about it are 1) it has been coloured to match my website and my corporate colours, and 2) It fits nicely into the social bar on the right, because I want it to be there, in it’s own special place, visible without having to scroll down but leaving plenty of space for photographs.

From what I read this is about to stop being functional and I will have to create one of the new style widgets, which 1) are non-customisable and 2) are much wider. This will necessitate a redesign of my whole website if I have to do this, and it might be that I decide I no longer have room for twitter on my homepage.

Can anyone advise?

#73

Started designing a few new sites with the impression that in-depth CSS styling the Twitter embed was still possible, but nope, not anymore. Why would you abandon the API 1.0 method that millions of designers and developers were using to style their feed to fit the style of their sites in favor of such a big and ugly new embedded iframe format? You do realize that designers and developers might throw out adding Twitter to their sites all together over this? The fact that you’d have to create your own entire API scripts just to style the feed with CSS is absurd.

#74

I have few webapps using GET http://search.twitter.com/search.json and to this day (April 24) they still work. Is the final deadline for this also May 2013 ?
Or will this Public Search API will remain because it so amazing to be able to use it ?

#75

The old “v1” search API at search.twitter.com/search.json is among the APIs that are now deprecated and will stop working on May 7, 2013.

#76

Do you know what time of day the API be stopped on the 7th? Thanks

#77

Currently I use;

var TwitterContent = new TWTR.Widget(twitter_settings);

TwitterContent.render().start();

and

TwitterContent.render().setUser(hash).start();

are these also included to be retired on May 7th?
Thanks

#78

We currently have about 100 or so Congressional Clients whose sites have been created over the past 6 years and the majority of them show a single latest Tweet from each Congress(wo)man’s official account.

Some clients also show a list of their latest tweets.

With the House now requiring all Twitter API 1.0 to be updated to the newer version we are starting that process. Aside from the few sites that list multiple tweets, which we can simple replace with the new embed, for the majority of our sites that use the old standard twitter code to show the latest tweet, what is the new preferred embed code for this? We can’t seem to find any easy way of simply adding count=1 to the twitter timelines other than using javascript to hide the additional tweets which certainly isn’t ideal.

Thanks in advance.

#79

Yes, that’s what we call the “legacy widgets” that use unauthenticated API v1 requests – they’ll stop working once retirement happens. (now scheduled for June 11, 2013).

#80

We introduced a new feature to [node:10248] last week that allows you to set the count for a widget, allowing you to do the equivalent of count=1. In the anchor tag, add this property: data-tweet-limit=“1” and you’ll achieve that behavior.

#81

Awesome! Thanks Taylor.

#82

I am new to this as well. I can’t determine what I need to do to migrate from 1.0 to 1.1. Do I simply delete my existing application and re-create it with an access token? How can I verify that I am using version 1.1?

#83

Your API keys represent your application regardless of which API version you’re using – you don’t need to regenerate your tokens to be API v1.1-ready.

What you do need to do is take a look at all the Twitter-related code you use – whether you wrote it yourself or you’re using a library – and verify that it’s making requests to the v1.1 API that’s documented on this site. Sometimes this means you just need to upgrade the library you use. In some cases you have a lot more work to do.

#84

Hi, I’m using the new widget in Wordpress (realized I needed not to use the old one), and trying to get my twitter feed working. It’s not working. I’ve generated the code and copied/pasted twice. The second time I read that I had to use just the long string of numbers. I couldn’t copy just the numbers - only the whole URL I guess (sorry, folks, not a developer at all) and deleted what I didn’t need. It still doesn’t work. Since I only did this today I’ve not used the old version of the widget, so it’s not like I’ve had a twitter feed at this point, but I’d like to have one. Would appreciate some advice. Thanks,

#85

Hello do you have now an answer to that question, and also can you please guide me to a method to get public tweets for a certain user without being authenticated?
like the old https://api.twitter.com/1/statuses/user_timeline/user.json what is the replacement for this
thanks a lot

#86

When you don’t have a user context, use app-only auth to connect to /1.1/statuses/user_timeline. You’ll have a limited rate limit to work with though, so you’ll want to use some form of caching.

#87

Did you guys write a code that would adapt to the current code so that website’s that are embedded can continue uninterrupted? Or, do we have to completely redesign our embedded twitter?