I can reproduce this (output: WARNING: querypage module does not support a namespace parameter) and suspect rPWBCbdeea71e129f0bc9b1a36e75388dfc576c7275ce is behind this.

Apparently, all backslashes need to be escaped, which is the actual problem of the error. While \b is backspace character, \c is nothing.

Finally, thanks for your effort @Nikerabbit!

Yes! \o/

I assume no,

Now errors can be located easily using codesearch.wmflabs.org and some smart regexes:

For reference, I had already made an abuse filter in 2017 to prevent this behavior on Wikidata. Since the beginning of Wikidata, the only standard to request deleting an item is filing one on Wikidata:Requests for deletions.

I think this was caused by my script which marks disambiguations in statements. I have just changed it not to run on Lexemes for now.

Per https://www.wikidata.org/wiki/Special:ListGroupRights#user, every logged in user should be able to apply a change tag. You have already managed to do so.

I have got another test case:

this hack

Ideally, notifications would update completely independently (T34284).

T147178#3567967

Indeed, it does not (T155109). But you can make it in two steps: first create the claim and then add the tag via action=tag&revid={data.pageinfo.lastrevid} (with "data" being JSON of the response).

Wikidata administrators can create it for you.

See also T176391: remove and prevent spam on lexeme test system.

Is this T67846: wbeditentity: try to use appropriate autocomment instead of the generic one?

Is this done?

Another strange behavior: FuzzyBot refreshed content but also changed a translation where the content had already been updated.

Procedure: add ** Special:NewLexeme|special-newlexeme to MediaWiki:Sidebar.

https://github.com/urbanecm/weapon-of-mass-description/pull/3