#62

We’ll be announcing the next date and time soon. We’re targeting it for a bit later this month.

#63

We have over a couple 100 different clients who use various implementations of Twitter Embeds. The most common use case is clients using the original twitter embed from the goodies page to display the users latest tweet. Some clients use various plugins to display there tweets.

So my first question is what is the easiest way to search all our servers to determine which clients are using a Twitter API that will be retired. For instance if we grep all the servers for “

Which allows for displaying 1 latest tweet from a users account. Since it has a j/2/ rather than j/1/ does that mean it uses the new code and will not be part of the depreciated code?

Thank you.

#64

Now that thousands of websites that use the profile widget are showing empty widgets, do you have any plans to offer similar functionality with 1.1? Many community and profile websites allow users to embed a profile widget on their page simply by entering their twitter screen-name. Not being able to programmatically generate a profile widget breaks many, many existing websites.

And the Embedded Timeline feature is not really useable since it requires the user to go in and set up an Embedded Timeline and specify domains and then copy each code one a time. This is not user-friendly for most people. When do you plan to offer a similar widget that can be generated programmatically?

#65

I really hate to do this, but I feel that to point out how these display rules are detrimental I need to note a few websites which are violating these display requirements.

This can possibly provide some good transparency of whether these rules are being enforced fairly for all (it will be seen if these are forced to change their practices or are given a free pass to continue in violation whereas “regular” developers have their access revoked). It will also highlight the difficulty in getting sites to change their layouts to conform to these new requirements.

and the list continues, and I am by no means singling any of these sites out as being “bad”, they just don’t conform to the requirements which all sites must now change their layouts and formatting to conform to (if anyone knows of more large sites, please comment with them as well).

#66

Hello,

Thanks for bringing these to our attention. We strive to provide as equal enforcement across the ecosystem as possible; unfortunately, we are not omniscient and we welcome any and all user-submissions for compliance review. I can’t comment on whether or not another service is in compliance with our Rules, but we do actively listen to submissions to our helpdesk (Platform) as well as this forum. Please feel free to continue letting us know about potentially non-compliant services—either here on these forums or via our helpdesk—and we will review these sites for compliance. If you are developing a service and have concerns over whether the features you are implementing are compliant with our Rules, we would also love to hear from you before these features are released to help guide you through your implementation.

Thanks,
@truebe
Twitter Platform Operations

#67

Any update on this? Now that the date is set for May 7th, it would be good to know what our path forward will be.

#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.