Based on the feedback in T180080#3748420, instead of getting all the pages a user has edited, we should take the revisions that are being displayed and query the API to see if the page has ever been edited by the other user. This may result in more requests, the requests will be faster since they can be executed in parallel.
As an alternative to doing this we could T180546: Create an API for Interaction Timeline and then this task can be implementing an endpoint to get the revisions.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • TBolliger | T166807 Epic ⚡️ : Interaction Timeline | |||
| Resolved | • TBolliger | T179607 Interaction Timeline V1 | |||
| Resolved | dbarratt | T179702 Interaction Timeline V1: Full date range support & infinite scroll | |||
| Resolved | dbarratt | T180156 Interaction Timeline should make simpler requests to determine if pages have been edited |
@dbarratt — is there any urgency behind this, or is this just a tracking ticket?
I would imagine we should tackle this if/when we focus on improving the speed performance of the Timeline.
Yeah this is a performance improvement, wasn't sure if there was an existing ticket. If there is, feel free to merge. :)