You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2019. It is now read-only.
The best solution for client-side Twitter API implementation is a simple proxy wrapper around the API. This will make your existing code or plugin work again with the new Twitter API.
Yep, solutions like this have been written and discussed in #264, and that issue is linked to from the README and http://tweet.seaofclouds.com/, so I'll close this: perhaps you'd like to post the above link to that discussion?
The best solution for client-side Twitter API implementation is a simple proxy wrapper around the API. This will make your existing code or plugin work again with the new Twitter API.
I've written one for .NET/C#:
http://www.timacheson.com/Blog/2013/jul/twitter_api_proxy
I've also written one for classic ASP which can easily be tw
eaked to work in similar scripts e.g. PHP, or indeed VB, etc:
http://www.timacheson.com/Blog/2013/jun/asptwitter
Alternatively could just use an existing proxy service like YQL.
The text was updated successfully, but these errors were encountered: