It is also very useful on Special:EditWatchlist.

@Anomie I've uploaded a simple patch that adds the autoMerge and fail options. For the overwrite option, I think it would be acceptable to merely null the basetimestamp and starttimestamp fields, since it seems that these two fields are only being used for conflict resolution?

@Anomie that link is no longer accessible, but I guess the if condition you were referring to is around L2242? Just changing that condition to if ( !$this->noAutoMerge && $this->mergeChangesIntoContent( $content ) ), and adding a noAutoMerge flag (set by ApiEditPage) would be acceptable?

Another pseudo-duplicate: T177150: Add IP range support to list=usercontribs API

@JTannerWMF I have written a patch for this. It is fairly simple. Could you review it?

Instead of adding yet another item in mw.config, it would also help if the timestamp in the page html were machine readable - enclosed in a span tag with a data-ts attribute or something with the mediawiki timestamp ("YYYYMMDDHHMM") in UTC.

In T234450#5669094, @Xaosflux wrote:

I think @Green_Cardamom is suggesting a userland "tool" (likely client-side javascript API shunt) to workaround this new limitation, such would not have any sort of direct database access?

In T234450#5622708, @MER-C wrote:

Why not make the higher limits a privileged action, just like it is in the API?

In T231357#5625810, @MaxSem wrote:

@dom_walden, looking at the above nomination:

• Log page - not sure if edit summary was present before
• Discussion page
• Template on the page itself
• Creator notification

Templates look to be working to me.

In T231357#5625610, @MusikAnimal wrote:

It's a wild guess, but I was wondering if what you're seeing is from https://meta.wikimedia.org/wiki/MoreMenu, which looks for AfD/MfD on every page, and maybe you misattributed the API call to Page Curation? I don't see any such API calls being made when in safemode.

It looks as if PageCuration is preemptively making an API call for getting prior AfD/MfD nomination page names on every single page (even on pages not in the new pages feed, and even in namespaces where it is not required). This isn't exactly a good idea performance-wise, is it? Shouldn't this be delayed until the user actually tries to mark the page for deletion?

Localhost URLs should be added to the CSP. Not being able to load javascript from a local server would severely impede development of user scripts and gadgets. Thanks.

@Reedy, @ItSpiderman can you look into this again, please. While no internal error appears now, I am still unable to to enable 2FA: the message "Failed to validate two-factor credentials" comes up every time. I have tried using both Google Authenticator as well as 2FA Authenticator apps.