That's a very good way to avoid helping, and to waste time. If you read just part of the code at the top of the conversation, you may have seen the signature based being constructed.
Trying to be constructive, Twitter Dev Team, please add more tools to test the OAuth/xAuth stuff. Many examples are wrong or simply incomplete so you can't try with them. If the examples are part of the API, this is definetely wrong. It takes to to errors, and waste time. Please help on find out what's going on with the code. Today Twitter team has included a hard synchronization requirement in every OAuth requests (including xAuth). Now I have something else to worry about, and no help... I'm thinking about giving up. This is too confuse and heavy to test. Regards, Herman On 6 sep, 20:21, Cameron Kaiser <spec...@floodgap.com> wrote: > > What do you mean? > > When you sign an OAuth (or xAuth) request, you use a base string composed of > various components of the request itself. The OAuth spec goes into this in > detail, and there are many helpers to show you how the base string is > constructed. If you construct it incorrectly, your signature will be wrong. > > -- > ------------------------------------ personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- Violence is the last refuge of the incompetent. -- Salvor Hardin > ----------- -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en