Last modified: 2014-01-23 03:33:31 UTC
It's great that each action performed by an OAuth consumer is tagged as such. It would also be nice if the consumer description page was a bit more user-friendly. As an example: https://commons.wikimedia.org/wiki/Special:OAuthListConsumers/view/90b858d7d1179a1b4eee89956e735e80 What I'm missing on this page: * A link to https://commons.wikimedia.org/wiki/User:Danmichaelo * A link to https://commons.wikimedia.org/wiki/Commons:CropTool * A link to http://tools.wmflabs.org/croptool/ * A link to a bug reporting mechanism * A link to the source code The callback link in this case is identical to the tool link, but it doesn't have to be. So I'd recommend including the following in the consumer metadata: * author URL (username URL or website) * tool description / usage instructions URL * tool URL * bug reports / feedback URL * source code URL Once we have a bit more metadata, we can clean the special page up and make it less technical and more understandable, since we can reasonably expect users to visit these pages from the Tag: links in recent-changes/contributions. I understand that consumers may not have all required information by the time they're requesting a token, and in some cases, not all of it will be applicable or required. So all of the above could be optional, and supplied later.
Side note - it may be useful to consider a restricted namespace for OAuth consumer metadata, using ContentHandler, similar to Zero:, Campaign:, Schema:. Perhaps even integrating with the metadata that feeds into http://tools.wmflabs.org/ for a Tool: namespace, since there's likely to be a fair bit of duplication. If something like that sounds like a good idea, it may be worth a separate bug to track. CCing Yuvi (who implemented Campaign:) & Marc-Andre for this reason.
Hi Erik, This is a slightly more general request of bug 56946, which was from the feedback from Jared/UX. I think the discussion on that bug, and your notes here bring up a decision about how much flexibility we want to give the developers vs. enforcing a standard set of metadata / page naming / page design. I'll ping Dan on that.
I'll leave a note here since I was thinking about filing a similar bug. When I'm looking at the list of connected apps the information on what is actually connected is very limited. My immediate question was "who is this non-linked 'jalexander' dude who runs this tool? While obviously my username is global we do not, yet (and god knows when that will complete ;) ), have fully unified accounts for everyone and so it is in theory possible someone with a local account (where someone else owns the global account of that name) could propose a consumer. In that case someone looking at the connected list would have no idea which user it was.
