@Tchanders I just realized the acceptance criteria is missing a point: we should remove Special:InvestigateLog and redirect it to Special:CheckuserLog. Should I create another task to do that?

Thanks for the explanation @Mholloway. @jwang I agree that we can keep the data retained for longer in its current state without merging it with prefupdate. Thanks!

I agree that selection of text will be useful to more people at the moment. We should focus on that.

Adding this to our board. If it seems like it's not a good fit for our team, we may place it up for grabs later. :)

In T264359#6513983, @dbarratt wrote:

Can we get any metrics

This should be recorded under Schema:GuidedTour. Query for the tourName of checkuserinvestigateform (the initial form page) and checkuserinvestigate (after starting an investigation).

@dbarratt I think so! Should we stall this task until we have determined how anon identifiers will work post T262321: IP Masking ?

In T260466#6529836, @sbassett wrote:

@Urbanecm - based upon the comments starting at T260860#6523535, at the very least we'd need to see a solution for T264833 before any security review commenced, since that blocks deployment of the extension. Have we also confirmed a Foundation-based steward of the code? Is Community-Tech or Anti-Harassment filling that capacity, @Niharika?

@dbarratt Does the title rename make sense? Trying to get a sense of what we'll achieve from implementing this API endpoint.

@Tchanders Would this be a good contender for a new engineer onboarding task?

In T263756#6501992, @dbarratt wrote:

In T263756#6492822, @DannyS712 wrote:

To do this we will need a new table in the IPInfo extension that stores the user name and the timestamp when they set the user preference. If a user unsets the preference, their row can be deleted from this table.

@Tchanders perhaps instead store as the preference value the time it was set?

I was just about to ask why we wouldn't do that... I think we could have a hook handler for the preference that converts a "check" to the datetime (if it's being changed). When we check the preference (in the API) we'll also check the value of the preference.

Ping @Reedy! Any updates?

I tried to login to the ithenticate account but it says Please contact your account administrator with the code E503. I think you need to shoot them an email like last time, @eranroz. I see a past email where we were talking to Mark Ricksen about this.

In T264359#6513983, @dbarratt wrote:

Can we get any metrics

This should be recorded under Schema:GuidedTour. Query for the tourName of checkuserinvestigateform (the initial form page) and checkuserinvestigate (after starting an investigation).

Considering this task as resolved for now. We didn't get as many interviews as we would have liked. We might come back to do some more work on this in the future, time permitting.