In part four I mentioned that there would be a problem in the future with this solution.
In the second part of this series we created a simple function that generated a HTTP request to send to the Twitter API.
As part of that request we sent a username and password.
This known as “basic authentication”
Unfortunately just after I got this working the Twitter development team announced on google groups they are dropping support for basic authentication.
our plan is to turn off basic authorization on the API by june 30, 2010 — developers will have to switch over to OAuth by that time. between now and then, there will be a *lot* of information
I can understand why Twitter have done this as it’ll make the system far more secure.
Unfortunately this breaks my solution so I’ll need to take a look to see how i can use a different authentication method.
I’ve got till the end of June so hopefully I’ll get something sorted soon!
Just one final post on the way to wrap this up.The following two tabs change content below.Andy Parkes is Technical Director at Coventry based IT support company IBIT Solutions. Formerly, coordinator of AMITPRO and Microsoft Partner Area Lead for 2012-2013. He also isn't a fan of describing himself in the third person.