General notes based on reviewing Linter API: (https://www.mediawiki.org/wiki/Extension:Linter#API)

Assuming we go forward with using the Linter extension to store/query this, we can roughly think of the set of matching lints, in order of detection (and thus lint id order), make a global queue.

We can match items within that category's 'queue' starting from a certain lint id with list=linterrors and lntfrom=, which allows for 'picking up' from the queue in order to avoid duplicates. If no items are found, we've hit the end of the queue and should restart from the beginning.

Matching records will include the page, the lint id (for later reference), the source location as of the linted edit, and the name of the image file. This could allow for showing a thumbnail of the relevant image along with the page title before loading the entire page source or parsoid HTML.

We can also randomize the input of each client by pulling a series of items instead of a single one (lntlimit=), and then selecting a random item within it to display, so that two fresh instances next to each other don't see the exact same data.

Of note is that modified pages may end up recreating their lints, so pages may move from the start of the queue to later in the queue over time, and may thus re-appear but at the end, never near the beginning.

This logic can be done by the API client on both Android and iOS implementations, and should have no major database performance implications, but may still lead to a general overemphasis on pages in the starting position if they don't get kicked off the queue by edits (eg they look to confusing to fix and nobody else edits the page).

Things to consider:

• is there a stricted randomization requirement? (might be hard)
• or additional requirements like deny-lists of categories? (probably not hard)
• skip/retry needs?

Starting at a semi-random position in the queue might be feasible, or might require an additional server-side modification to do efficiently

It might also be worth explicitly surfacing the idea of selecting several items and allowing the user to choose one or ask for another bunch (not all items may be obvious how to deal with).

Note there's a possibility people will be too grumbly about adding this to the linter extension in which case we'd do the exact same thing but store it in a similar table with a similar api and a different name. I'd prefer to avoid that though.