Serendipity Forums

I noticed the other day that my timeline wouldn't show up in the sidebar. It's normally set to use Javascript for output format, now all that's showing is the "follow @mangek009" image. If I instead switch to PHP output, I get the error message "Problem, accessing twitter at the moment.
Please reload later.."

Anyone else having these problems? Did Twitter change something in their API (or something?) that cause the plugin to break?

Mangek wrote:Did Twitter change something in their API (or something?) that cause the plugin to break?

I can't explain it very well technically, but yes, Twitter's new API changes limit the number of calls 3rd-party clients (like the sidebar plugin) quite drastically. Basically, it seems like Twitter is detemined to shut out as many of those as possible by March or May(?) 2013.

YL

Anyone else having these problems?

Ich habe das gleiche Problem.
Gibt es schon irgendwo Hinweise, wie eine Lösung aussehen könnte?

Thomas

Twitter basically broke their whole API to make it as hard as possible for Client and API developers to embed Twitter into other things.

I'm really mad at them.

Regards,
Garvin

yellowled wrote:..Twitter's new API changes limit the number of calls 3rd-party clients (like the sidebar plugin) quite drastically...

YL

garvinhicking wrote:Twitter basically broke their whole API to make it as hard as possible for Client and API developers to embed Twitter into other things...

Regards,
Garvin

Well that's a bummer. I guess there's no easy way to fix it either, since it'll require keys and what not, I suppose.

Mangek wrote:I guess there's no easy way to fix it

There's no way to fix it, period. This will limit all client-like applications, sidebar plugins as well as Twitter clients. Everything.

YL

yellowled wrote:There's no way to fix it, period...

Ow.

Hi!

Well, the Javascript solution I think should still work. Supposedly they changed the JSON location URL, or some part of the format, making it impossible to render.

Someone would need to look at this, but at the moment I am still too pissed at twitter to be able to dive into this with a neutral, productive state of mind.

Best regards,
Garvin

Hi!

I just committed a hotfix to GIT. This allows to at least utilize the API again. The JS mode should work, based on per-user client.

The PHP mode has quite strict API call limits for the server, so we would need to switch to 0Auth authentication as soon as possible to bump the limit a bit more.

Until then, the JS mode is the recommended way to embed the twitter timeline in the sidebar, because this will then apply the API rate limit to the Visitor, not the server.

Regards,
Garvin

garvinhicking wrote:I just committed a hotfix to GIT. This allows to at least utilize the API again. The JS mode should work, based on per-user client.

Oh nice, thanks!

I've only really used the JS mode. Are/were they much different?

I spend my weekend in upgrading the micro blogging plugin to Twitter API 1.1 (man, this rate limiting and so sucks!). The sidebar plugin and the main plugin should be done, I think. Where the plugins used old API calls (sidebar and tweetback stuff) it is optional (because you have to chosse the twitter acc to use for calls and rate limiting), calls that were already using OAuth are upgraded to 1.1 just like this.

Before releasing it to Spartacus I like to search for some brave betatesters.

Hi!

Please post a link, I would also like to test it on my blog.

Thanks,
Garvin

The beta version is available at my testblog server at the moment.

I released a new version of the microblogging and oembed plugin to Spartacus. Both lifted to Twitter API 1.1. The beta tests looked good, hope everything will be fine on other blogs, too.

blog.brockha.us wrote:I released a new version of the microblogging and oembed plugin to Spartacus. Both lifted to Twitter API 1.1. The beta tests looked good, hope everything will be fine on other blogs, too.

Code looks good (and complicated, though)

I haven't been able to try it out myself yet, but - will people who use the old version, do they need to setup something after the upgrade, or will it use existing tokens already existing?

If not, it might be nice to create a message on the backend (eventhook "backend_frontpage_display) with the plugin telling users to upgrade the OAuth, if some prerequisites are missing to use API 1.1?

Or does it simply use API 1.0 by default, and if users switch ti API 1.1 on their own, they will be able to enter their tokens?

Regards,
Garvin