The first vertical dashed line corresponds to T271344#6833606, i.e. 1.36.0-wmf.27 -> wmf.30 deployment on group2 wikis.

Moreover, ChangesListHooksHandler::onOldChangesListRecentChangesLine is supposed to add some CSS classes (damaging, ores-highlight), but they cannot be found in the recent changes list as well. So I suspect from the code that the problem is in ChangesListHooksHandler::getScoreRecentChangesList (used in ChangesListHooksHandler but not in ContributionsHooksHandler).

I don't know how to submit translations for them, {{edit request}}?

They are translatable on Wikidata:

Whether it's a bug depends on whether the bot includes bot=1 in requests.

When I started working on this, I realized the following. Filter updates are much less common than filter runs (which happen in real time). So the cache will usually contain only a few entries if any. If we attempted to update the key for every filter after every action, it would be a no-op in 95-99%. Therefore, we should also have a cache entry which tells for which filters it makes sense to update the cache entry (probably one key for each filter group). @Daimona What do you think?

putting global variables in a fake "filter 0" would be a simple option that also denies the need for schema changes

I believe there is an error in Module:WikidataIB.
If you expand {{#invoke:WikidataIB|getValueByLang|P856|qid=Q1071969|fwd=ALL|osd=no|maxvals=1}} (used in Infobox software), it returns https://www.gnu.org/software/bison/, https://savannah.gnu.org/projects/bison/. These are two values, despite maxvals=1.

Still does not work in either backend (old and grouped)...

I requested one more improvement to improve compat. with BCE dates. But it solves a todo, it isn't really high priority: https://github.com/wmde/Time/pull/148

Well, I had some dirty untested stuff before I created the task, but don't have time to rebase it now. Feel free to go ahead.

My ideas are related to privacy. We have different privilege levels for viewing and editing public and private filters. If someone cannot see/edit private filters, but can create a public filter, they should probably see the shared variables. So they would have to be public. Per description:

I think this is T61973. I believe Pywikibot should not handle this exception in any way (but a dedicated subclass wouldn't harm).

Patches are welcome.

rEWLE8282b1aa3ce468810b535cc966049f47c8381013

Verified, they are not shown on Special:NewPages.

FYI, I have just disabled all section links on the page in the task description using the magic word. But before doing so, I verified this was still the problem (described in detail by @matmarex above).

https://gerrit.wikimedia.org/r/c/mediawiki/extensions/AbuseFilter/+/623836

In T246549#6077161, @srishakatux wrote:

@Dvorapa I've a couple of getting started questions related to this task. Should the code changes take place in the script file core/scripts/listpages.py in https://gerrit.wikimedia.org/r/#/admin/projects/pywikibot/core? Should the main() function be expanded to handle an additional argument related to custom text? Please share any other tips for getting started on this task.

For Lexemes, the lemma is still escaped, but that seems to be due to the {{PAGENAME:}} magic word, which also wikitext-escapes its argument, and would require a different fix.

I think this is StructuredDiscussions (Flow).

wmf.21 is out, so I think we can apply it. But I'm afraid it will now be possible to break this with stuff like {{ or }}.

Yes, otherwise nobody will be able to look at them.

Key:amenity is a regular page, not an item. You should be able to access the item through:

I manually checked all listed items but none of them has been edited since I created the filter.

My workaround would be simply wrapping the text AND my signature <small>Text... --~~~~</small> but the reply tool also appends another signature because it isn't at the end...

Exactly, the filter tags all edits to tour items. Their list is inside the filter and can be amended by a Wikidata admin.

Created filter 138, which tags edits as tour-item. Feel free to amend the list of items if necessary.

I really meant item._content. You can also print claim.toJSON().