New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Twitter API v1.1 #1099

Closed
adamcaudill opened this Issue Mar 5, 2013 · 4 comments

Comments

Projects
None yet
2 participants
@adamcaudill

adamcaudill commented Mar 5, 2013

This may already be addressed, but Twitter is running a blackout test of unauthenticated requests as part of the preparation for API v1.1. See here for more details:

https://dev.twitter.com/blog/planning-for-api-v1-retirement

As a result, we see a "Status updating..." message in the sidebar. Are there plans to switch to the new API, or will this feature just be retired?

@imathis

This comment has been minimized.

Show comment
Hide comment
@imathis

imathis Mar 5, 2013

Owner

@adamcaudill Am I right in thinking that Twitter will no longer offer an unauthenticated JSON API? If the only way to implement a Twitter stream involves embedding a timeline widget, Octopress will retire its Twitter timeline support.

Owner

imathis commented Mar 5, 2013

@adamcaudill Am I right in thinking that Twitter will no longer offer an unauthenticated JSON API? If the only way to implement a Twitter stream involves embedding a timeline widget, Octopress will retire its Twitter timeline support.

@adamcaudill

This comment has been minimized.

Show comment
Hide comment
@adamcaudill

adamcaudill Mar 5, 2013

@imathis Yes, that's correct. Per the page I linked to above:

Unauthenticated requests are not supported in API v1.1.

From previous comments I've seen you make, I assumed the answer was to retire the feature. It should be easy enough for people to use the official Twitter widget if they so desire.

adamcaudill commented Mar 5, 2013

@imathis Yes, that's correct. Per the page I linked to above:

Unauthenticated requests are not supported in API v1.1.

From previous comments I've seen you make, I assumed the answer was to retire the feature. It should be easy enough for people to use the official Twitter widget if they so desire.

@imathis

This comment has been minimized.

Show comment
Hide comment
@imathis

imathis Mar 5, 2013

Owner

That's what I assumed. That's too bad. App.net is coming along nicely, and I've built an app.net timeline widget which will be easy to install with Octopress soon. For cross-posters they could essentially start using this instead. Hah.

Owner

imathis commented Mar 5, 2013

That's what I assumed. That's too bad. App.net is coming along nicely, and I've built an app.net timeline widget which will be easy to install with Octopress soon. For cross-posters they could essentially start using this instead. Hah.

@imathis

This comment has been minimized.

Show comment
Hide comment
@imathis

imathis Mar 5, 2013

Owner

I'm closing this issue in favor of #1100.

Owner

imathis commented Mar 5, 2013

I'm closing this issue in favor of #1100.

@imathis imathis closed this Mar 5, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment