If you change the access level, the keys don't. You will have to create
new user credentials. There are multiple ways of doing this, the easiest
one being simply re-creating the application on dev.twitter.com, this
time with proper settings. A different option would be to revoke access
(Settings -
There was plenty of notification on when Basic Auth was going to be
discontinued.
On 9/4/2010 9:29 PM, mikesouthern wrote:
I'm finding it fairly hard to laugh and relax, to be honest.
I'm not a developer. I just use perl scripts to automate my twitter
feeds.
Receiving a notice telling me
On 9/4/10 11:05 PM, Dustin Shea at demonicpa...@gmail.com wrote:
There was plenty of notification on when Basic Auth was going to be
discontinued.
Dustin, I can't comment on what notification you received, and am glad you
received it.
I can only comment on the notification that *I* received:
My notification may have been due to the fact that I've been a member of the
Dev List for some time thus foresaw this coming and I think it was mentioned on
the old Twitter API wiki. I took notice do to the fact I was working on a TCL
twitter app for an IRC eggdrop bot that was using Basic
* mikesouthern gb1...@cox.net [100904 19:56]:
I'm not a developer. I just use perl scripts to automate my twitter
feeds.
For perl devs, the move to OAuth is really quite easy, especially for
automated scripts.
Register an application at http://dev.twitter.com. Grab the consumer
key and secret,
