https://bugzilla.wikimedia.org/show_bug.cgi?id=57505
--- Comment #3 from Chris Steipp <[email protected]> --- This was actually the intended feature originally, but the UX team asked us to simplify the /authorize screen, including not doing this feature when we brought it up once. We could probably get away with adding an "Advanced" option that takes power users to an /authorize screen with more options though. Liangent's particular use case is probably not the best use of this, however. In general, it would be best to design different versions of the bots for the major categories of different users, and each bot would have its own OAuth Consumer key. Similar to Liangent's idea of allowing apps to add permissions, another feature that has been requested for a while is to make it possible for Consumers to upgrade the rights, and have a better UX for doing this. That's why we have the Consumer version number set by the app developer. The flow would probably look something like: * The Consumer would send the user back to /authorize * We see the user has already authorized a previous version of this Consumer * We prompt the user that <app name> would like "more permisssion" (or something like that), showing them the added and removed grants * User grants the new set of permissions, and we automatically revoke the old authorization -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
