Skip to content
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

Sample PDTwitterTest less useful due to Twitter API v1.0 retirement #74

Closed
glyethan opened this issue Jun 26, 2013 · 4 comments
Closed
Assignees
Labels

Comments

@glyethan
Copy link

Posting a GET request to https://search.twitter.com/search.json?q=@square results in 410 GONE code due to retirement of Twitter's v1.0 API: https://dev.twitter.com/blog/api-v1-retirement-final-dates

While this is indeed a sample network response for us to examine via PonyDebugger, its not as helpful an example as it would be with some twitter data responses + data loaded into the tableview.

As well, it's a bit misleading -- I was expecting some twitter search results, and the error initially lead me to think I wasn't running the sample correctly, or had mysterious ponyd configuration problems.

@ghost ghost assigned wlue Jun 26, 2013
@wlue
Copy link
Contributor

wlue commented Jun 26, 2013

I'm pretty sure that Twitter won't have any more public endpoints, and I also don't think that it's a great idea to store tokens in the app, nor require users to add tokens just to run a test app, so we probably will have to change the test app. I'm open for suggestions.

@glyethan glyethan reopened this Jun 27, 2013
@glyethan
Copy link
Author

Well, I hacked in using Google's deprecated (but not disabled) old web search API that doesn't require an API key:
https://developers.google.com/web-search/docs/reference#_intro_fonje

I just display the result URL, title and content fields, and use the URL as the "id" for the CoreData integration part.

Granted, it's not as interesting as the Twitter sample would have been, but it might be a decent stop-gap solution until someone comes up with something better.

(accidentally clicked close issue earlier... oops!)

@viteinfinite
Copy link

The example app now relies on github apis. HTH.

@glyethan
Copy link
Author

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants