Particularly see the Twitter test code
issue ...it's going wrong for what looks (to me) like some
changes in the twitter service, or the account access or
something else. In any event, please assign the bug to
yourself if you
Twitter changed its user/password login and now we need to
go through the oAuth protocol. This is all fine and dandy but
is looks like quite some work to get to know oAuth and how to
let it sing with the REST services.
I have found a nice library  called Scribe that aids in
getting request and response tokens in place but this will not
be done before 3.4 is released.
I suggest to get rid of the failing tests for now since
they do not prove that the REST services are not working, only
that we are addressing twitter in an unsupported way.
ecf-dev mailing list