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.

Free-form linking is T57705.

In T60193#629751, @Eloquence wrote:

Side note - it may be useful to consider a restricted namespace for OAuth consumer metadata, using ContentHandler, similar to Zero:, Campaign:, Schema:.

The task for that is T109156: Investigate converting OAuth to use ContentHandler.

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.

I've been wondering about the same thing recently. @Harej any thoughts how Toolhub and the OAuth management interface would interact? My original plan (which I haven't been able to work on for a long time) was T109156 - create a dedicated form with fields like description and URL for OAuth consumers, and use ContentHandler to display the information as a wiki page; but most (although not all) OAuth consumers are for Toolforge / Cloud VPS tools, and ToolHub covers largely the same functionality for those. So some kind of interoperability would be nice.

I don't have any short or medium term plans around integrating with OAuth metadata at the moment, but it is an interesting idea. I think I would want to first know how metadata in OAuth is handled and how it could be integrated into Toolhub tool record generation.

Right now there isn't much OAuth tool metadata to speak of (tool name, plaintext tool description, tool author name) but that needs to be changed as it results in a very poor user experience.