[twitter-dev] Re: Whoa There! - Users don't really know whats going on.
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 request * 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 wrote: > sounds good, its way better than "Whoa There" :) > > On Jul 27, 5:51 pm, Andrew Badera wrote: > > > On Mon, Jul 27, 2009 at 8:38 PM, goodtest 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
[twitter-dev] Re: Whoa There! - Users don't really know whats going on.
sounds good, its way better than "Whoa There" :) On Jul 27, 5:51 pm, Andrew Badera wrote: > On Mon, Jul 27, 2009 at 8:38 PM, goodtest 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
[twitter-dev] Re: Whoa There! - Users don't really know whats going on.
On Mon, Jul 27, 2009 at 8:38 PM, goodtest 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
[twitter-dev] Re: Whoa There! - Users don't really know whats going on.
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. On Jul 27, 4:25 pm, Peter Denton wrote: > Hey, > I did some usability testing and 10 out of 10 people did not understand the > "Whoa There" statement. > > - First, probably only engineers/devs are going to understand what a > "token" is. > - Second, stating that "it was probably an honest mistake" is a > completely misleading, irrelevant statement. 'Honest mistake' infers some > type of a human choice, but its a system/technical conflict, without > intent. > > I know this has been brought up before, but I have been trying to > legitimately test these things on users, and it failed. Is there any chance > for customization of error reporting at this level? Will you accept text > considerations? > Another part of my testing was to simply describe the errors and let people > describe to me what that means in there head. In that sense, no one presumed > guilt on the apps behalf. > > Thanks > Peter
