In T322916#9209033, @Novem_Linguae wrote:

Perhaps it'd be better to let our people work on this (WMF Moderator Tools team talking to their contact at Newspapers.com) instead of Wikipedia Library users interfacing with Newspapers.com directly. Interfacing with them directly might just confuse and bother their customer service reps.

https://wikipedialibrary.wmflabs.org/ is down.

I asked for confirmation that the issue is resolved for this user, but haven't heard anything back yet. Marking resolved unless I hear otherwise>

When we set this proxy-based access up Newspapers.com did some work to get us around Captchas. It looks like they might have changed something causing that to now fail again. We're going to contact them to see if they can resolve the issue, we don't think we can do anything on our end.

I added the 250 edits question because I imagine that new editors are more likely to be on mobile but then drop off, and therefore not be engaged with the Automoderator project - we're really targeting experienced users, so that's a breakdown that I think would be more useful to us.

Confirming that I'm seeing this too.

Marked as temporarily unavailable in the library, linking to this task. We'll update as we investigate this issue.

In T345092#9202673, @ashley wrote:

The linked Google Docs document isn't publicly viewable. Presumably it should be.

In T346916#9200330, @KCVelaga_WMF wrote:

@Samwalton9-WMF

• I am not sure if I understood the first point completely. Let's consider an edit, which is reverting a previous edit, in which case, "edit itself is a revert of a previous edit" would be TRUE. Can you elaborate more on what you mean "by this user"?

In T346916#9185862, @KCVelaga_WMF wrote:

@Samwalton9-WMF

Regarding random sampling, how balanced should the dataset be across all of the dimensions? If we want to ensure a minimum across a some or all of the dimensions, I'd suggest a stratified random sample.

New daily logins for the library look fine, so I don't think this is a total outage of TWL notifications.

We've received an OK for the mockups here and the mitigations we've placed on linking of IP addresses to temporary accounts.

Vertical alignment achieved.

https://github.com/WikipediaLibrary/TWLight/pull/1204

Second PR improving the general state of the resources app: https://github.com/WikipediaLibrary/TWLight/pull/1203

Agh, looks like I wasn't quick enough in getting a solution in place and we missed a few days of edits. Unfortunately there's no good solution to this right now.

PR for views.py specifically: https://github.com/WikipediaLibrary/TWLight/pull/1202

I identified this while working on the above task, where I'm already doing too much refactoring, so parking this slightly-bigger refactor here for later.

In T343716#9146340, @Xaosflux wrote:

Instead of all the manual processes, can this just have them fill in the form that already loads this to the workflow? That will take care of all the workflow, the only programming would be to put in something to generate the newname (perhaps just something like hash(username&&timestamp)

That is, just send them to:

https://meta.wikimedia.org/wiki/Special:GlobalRenameRequest?reason=RTV&newname=Renamed_user_a1b2c3d4e5f6

Looks like this is resolved, though the flickr2commons exclusion didn't go through for some reason. I'll look into that soon.

I was wrong in the task description. The issue was a lack of include_invalid, but it was in emails/tasks.py. Since INVALID isn't a status where we send emails this change makes no difference to the operation of email sending, but does solve this error.

I couldn't reproduce this locally - I just set up my local environment fresh and ran the script, cleared my database, then ran it a second time, and didn't get the issue either time. There's some randomness involved in the scripts, so I wonder if this only happens under certain conditions.

In T345796#9151546, @Bharatswamy wrote:

In T345796#9148692, @Samwalton9-WMF wrote:

It looks to me like when we added the generic "TWL Team" account for invalidating applications that we no longer need, we neglected to add creation of that account to the example data scripts, so when some bundle applications get invalidated as part of generating the data, the account can't be found.

Okay, I think I got the issue somewhat, can I work on this ticket?

Hi and thank you for your interest! Please check thoroughly https://www.mediawiki.org/wiki/New_Developers (and all of its communication section!). The page covers how to get started, assigning tasks, task status, how to find a codebase, how to create patches, where to ask general development questions and where to get help with setup problems, and how to ask good questions. Thanks a lot! :)

It looks to me like when we added the generic "TWL Team" account for invalidating applications that we no longer need, we neglected to add creation of that account to the example data scripts, so when some bundle applications get invalidated as part of generating the data, the account can't be found.

Added flickr2commons to the hashtags exclusion list. We'll give this a week or so and see if we've caught up.

Dropped all flickr2commons data, so the script is already starting to play catch up.

So the best solution might be to attach a new volume to the Cloud instance, and store the database there (if such a thing is possible) but that goes beyond my current abilities, and I'd rather not have to drag our team's engineers into working on this. An alternative option would be to trim the database a little. The current top hashtag is flickr2commons (2.7 million entries; 38% of database rows). The tool already times out if you try to load a search for flickr2commons, and flickr2commons edits can be easily tracked via tags since they're only happening on Wikimedia Commons.

Hoping to look into this on Friday.

In T345234#9130079, @Addshore wrote:

In 0.20.0 I removed any suggestions of running the commands with sudo as it complicates things internally.
See https://gitlab.wikimedia.org/repos/releng/cli/-/blob/main/CHANGELOG.md#v0200

If you just run mw update I'm pretty sure it will download the file and output a command you can sudo with to get the update in the location of your binary

In T331058#9129465, @RHo wrote:

In T331058#9128363, @Umherirrender wrote:

In T331058#9127613, @RHo wrote:

I'm confused because it seems from my testing and screenshots and the comment from @Umherrirrender that is *is* possible to mute IP editors currently. Based on the current behaviour and the use case for people wanting to be able to mute folks who don't have a named account, would it make sense to proceed with T344647: Named users should be able to Mute a temp account ?

I have not written that it is possible to mute temp accounts. Maybe my text was not accurate, here a more accurate text:
You have muted named accounts with the prefix "IP ...", there is a small list of them under https://es.wikipedia.org/wiki/Especial:ListaUsuarios/IP or https://en.wikipedia.org/wiki/Special:ListUsers/IP

Sorry if it was unclear, That's what I meant, that it seems it is possible to mute iPs.