OAuth download should not be required if it is already available

OK, what about facebook modules? They are a lot and require facebook library so should they be integrated in a single module? Just because of this reason, the external libraries are not committed with modules code. I think users can easily get help after watching #720074: 2-3 small issues.

One more thing is that the module's functionality is totally different from OAuth so its integration with OAuth will kill its existence and functionality.

The project page should be updated in this regard.

this is a sensible request. the same conflict issue has been happening with SIMPLEPIE libraries in several modules, particularly FEEDS and ACTIVITY STREAM and both projects changed the library requirements to avoid conflict.

so please explain why cant POSTITEVERWHERE support the OAuth module to avoid not just redundancy but having the module break completely?

Subscribe. I would love feedback if anyone feel there's a shortcoming in the OAuth module. Our goal with version 3.x of it is to integrate the OAuth flow tightly with Drupal and make it familiar to Drupal developers so that they easily can make use of it without having to know every single detail of the protocol. It's not a library wrapper - it's a Drupal module. We're currently a rather small group working on it so all thoughts and suggestions on how to approve it is appreciated - it can only make the module better.

Related to this is perhaps also #698458: Work on a shared social network API.