Twitter's recent updates to its API rules will present quite a few problems for us:
In version 1.1, we will require every request to the API to be authenticated.
Could be solved with adding oAuth-support, but the bigger problem is the new rules also states that tweets can not be mixed in with content from other social networks which sort of defeats the whole purpose of ddEventz.
We will officially turn off the endpoints for API v1.0 on March 5th, 2013
So in a couple of months our plugin will stop working.
My suggestion is that we completely drop support for twitter. It's a shame, but it's to big of a hassle to keep the plugin inline with the "developer rules of the road".
What do the rest of you think?
Twitter's recent updates to its API rules will present quite a few problems for us:
Could be solved with adding oAuth-support, but the bigger problem is the new rules also states that tweets can not be mixed in with content from other social networks which sort of defeats the whole purpose of ddEventz.
So in a couple of months our plugin will stop working.
My suggestion is that we completely drop support for twitter. It's a shame, but it's to big of a hassle to keep the plugin inline with the "developer rules of the road".
What do the rest of you think?