Looping in @Cparle, as I might have outdated information on AI-generated content handling on Commons.

I don't know anything more than what you're posted above ¯\_(ツ)_/¯

Hmm - I had intended to work on this myself, and did do some work on it, but I have higher priority things going on right now. Don't know who else might do it, which is why there's no team tagged

AFAICS we don't fit into any of the pricing categories listed on the VIA pricing page, and I expect that a h.264 streaming licence would still be free for us

+1 to @Krinkle - I can't see a compelling justification for the additional complexity being introduced here, and I don't think this approach helps get around it any legal issues

@Jeff_G and @GPSLeo there has been a bunch of work on watchlists since the last comment on this ticket - are you still experiencing problems?

Yeah. Lower uptake than we were hoping for! Might be interesting to also run the query for users with over 1k pages in their wishlist?

You're querying users who've had a revision since Jan 1 2024, I was querying users who'd had an edit since Jan 24 2026 - my rationale is that if a user hasn't been active since watchlist labels were deployed they won't even know about the feature, so it doesn't make sense to count them. So my count of active users with large watchlists is 56780 (as opposed to your 114464)

Added some tags, should get picked up in the next wishathon, also will flag it with CommTech to see if anyone can pick it up sooner

And is a prefixed wildcard going to be okay, performances-wise?

Think we'll need to talk to @Ladsgroup

A <bdi> instead of a <span> maintains the directionality though. @Mooeypoo any thoughts?

@GMikesell-WMF how it's displayed on the actual Special:EditWatchlist page is ok now right? The problem is with the modals? That looks like a problem with the codex checkbox, I added a subtask T417979

In T416172#11634338, @Sadads wrote:

I wanted to endorse this request I have always had thousands of articles on my list, and it makes no sense to manually go through and do it. It would be particularly useful to have the search support the various special words in the search index -- (i.e. incategory) so that you could batch edit, based on existing metadata.

@GMikesell-WMF when I said this

Resolved now @Aklapper - thank you!

Ah! Ok - maybe instead of this ticket then I'll create one to record whether you've already dismissed the popup in your global prefs rather than your local prefs. Does that make sense?

I'm boldly declining this. If people automatically dismiss the popup and never even find out that watchlist labels exist then the work on it was wasted.

do you know what happened to the Display watched changes, as seen in the Other issue section?

I can see it on beta enwiki? Is it still missing for you? I wonder is there something different in our preferences that means you don't see it ...

@Scyrme and @Jonesey95 - we removed sort-by-expiry because the database queries underlying it are approximately 100 times slower. Slow database queries clog up the database connections and make the wikis slower for all logged-in users, so we try really hard to minimise them.

Maybe we could allow searching by labels too?

Oh weird, this only works if you have this checked in your preferences (which I did have checked, but turns out it's not default)

@JSengupta-WMF did you intend the 5th row down to say "in 11 months X days"?

Calling @tstarling ! Can we close this?

Moving back into QA as I can't reproduce

@JSengupta-WMF the project is done so I presume this is done too, so I'm boldly closing the ticket

@JSengupta-WMF the project is done so I presume this is done too, so I'm boldly closing the ticket

@TheresNoTime is this done for all wikis now? Can we close the ticket?

I don't see the problem with Test Case 2? You removed a label on the 2nd page, and the list stays on the second page - where's the problem?

Test case 4

@Cparle Oh I see now. If that is the case though, shouldn't we have the option to revert and have the first page available so we can have it back to what it was? The only way I can get it back to what it was is if I change the Namespace then back. This is regarding having 20 items to be back on the first page besides 13 since my total is 33

Maybe we should, but this is the way the pager component works and changing it is outside the scope of this ticket.

@JSengupta-WMF updated

Test case 1:
We agreed not to separate the namespaces into different tables, but it seems like the figma hasn't been updated. I pinged @JSengupta-WMF on slack about this

@JSengupta-WMF ☝️ ?

Erm ... so can we consider this done? Or @tstarling are you fixing this so it'll work in postgres?