Still compatible with Twitter?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Take the two-legged Twitter example file at 
http://code.google.com/p/oauth-php/source/browse/trunk/example/client/twoleggedt
witter.php.
2. Set the constants to match your account info.
3. Change the API URL to access the user_timeline (which requires 
authentication) instead of the public_timeline (which does not).
4. Run the script.

What is the expected output? What do you see instead?
Expected: A set of result data from the API.
Instead: Error code 401, "This method requires authentication." 

What version of the product are you using? On what operating system?
Revision 191 on Linux, not sure what kind.

Please provide any additional information below.
I implemented a connection to my user timeline based on the Twitter example 
script over a year ago and it was working fine. Then 10 days ago it suddenly 
started returning this authentication error for every request. Apparently 
something changed on Twitter's side that the current oauth-php is not 
compatible with.

I posted an inquiry on the Twitter developer site but that was not very 
helpful: 
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/5c1
dfe96f6405f85#

Original issue reported on code.google.com by arlole...@gmail.com on 21 Jun 2011 at 4:40

[GoogleCodeExporter]

I can confirm, that Twitters two-legged OAuth doesn't work any longer for this 
example.

To access user-specific data, 3-legged OAuth seems to be necessary (which is 
reasonable because an active user authentication step is required). If you 
implement 3-legged OAuth similar to the GDocs example, everthing works fine.

Original comment by andre.la...@googlemail.com on 5 Feb 2012 at 1:58