@csteipp my solution to T59457 actually means we can't add this to an existing message, because I'm using the message(s) in core. In that case, is this just a duplicate of T64686?

In T64687#1208264, @MarkTraceur wrote:

@csteipp my solution to T59457 actually means we can't add this to an existing message, because I'm using the message(s) in core. In that case, is this just a duplicate of T64686?

@MarkTraceur, not quite. Michelle's request was that we add another message into the dialog. We already add mwoauth-form-legal to the authorize form, it's just a blank message right now. Adding the app's name as a parameter and defining the message to Michelle's suggested wording would be the minimum implementation. It would be great to get UX input.

Defining the message as is gives,

UX input appreciated.

Change 303328 had a related patch set uploaded (by Dpatrick):
Note coverage under consumer privacy policy

https://gerrit.wikimedia.org/r/303328

So, now the problem is that we don't specifically collect a link to the consumer's privacy policy. And so, the link that appears just below this new message is confusing, and we don't have data to reconcile that (re. T64686).

Adding policy links would be a simple change, the problematic part is, what to do with existing consumers? That's T59631: OAuth developers should be able to change some of the parameters they registered an application with instead of having to submit a new application and that does not seem simple.

In T64687#2535018, @Tgr wrote:

Adding policy links would be a simple change, the problematic part is, what to do with existing consumers? That's T59631: OAuth developers should be able to change some of the parameters they registered an application with instead of having to submit a new application and that does not seem simple.

I guess we could just special-case adding a privacy policy where one did not exist before.

Change 303328 abandoned by Reedy:
Note coverage under consumer privacy policy

https://gerrit.wikimedia.org/r/303328