I wouldn't mind providing an error callback url which Twitter posts
error messages to. Asking users to report a message back to the
application owner is only great in theory.
Here are my $.02.
* Message should include the application which made the invalid
* It doesn't really need to have many details about the problem.
Merely mentioning OAuth would be plenty sufficient.
* Encourage the user to go back to where they came from (there were,
after all, trying to do something)
On Jul 27, 6:05 pm, goodtest <goodtest...@gmail.com> wrote:
> sounds good, its way better than "Whoa There" :)
> On Jul 27, 5:51 pm, Andrew Badera <and...@badera.us> wrote:
> > On Mon, Jul 27, 2009 at 8:38 PM, goodtest <goodtest...@gmail.com> wrote:
> > > I totally agree. They should simplify it and say something like: "You
> > > are not passing all required parameters or not encoding them properly"
> > > or anything that makes more sense.
> > That's not going to make any more sense to users.
> > It needs to be simple and imperative.
> > "We've experienced an OAuth [authorization [optional]] problem, sorry for
> > the difficulty! Please let the administrators of [requesting app] know that
> > they provided duplicate or incorrect OAuth request information."
> > --ab