Example: wgGlobalGroups, now only contains groups that are active in the wiki. Scripts no longer have to check whether the group is active on the wiki via an API request.

yes

I have removed default in most GSwikis, in [[ https://lo.wikipedia.org/w/index.php?title=%E0%BA%A1%E0%BA%B5%E0%BB%80%E0%BA%94%E0%BA%8D%E0%BA%A7%E0%BA%B4%E0%BA%81%E0%BA%B4%3AGadgets-definition&diff=106574&oldid=105014 | LoWiki ]]the gadget was only in the gadget definition, but did not exist, here I have removed all bad gadgets completely.

In T356008#9535140, @matmarex wrote:

@WikiBayer Would it work for you if, instead of adding a whole new mw.config option, we would omit the groups that aren't active on the current wiki when generating 'wgGlobalGroups'?

@matmarex You are right that you can query the scripts the rights, the problem is that the rights are the same whether you are in a global group or in a local group. If you use the global.js and want to distinguish which user group in the wiki you use, you need the groups.

done per SRM request

In T320439#8306215, @Aklapper wrote:

Which particular types of page(s) would this be displayed on?

There is also no reason why checkusers can just call the logbook for no reason at all.
Nobody should have this right, because this logbook gives conclusions about viewed pages of the respective users of the toll. At most, entries from individual users that are queried via CU should be visible.

@Niharika It should be possible to check all IPs that were active in some way. No matter if this was a logbook entry or an edit that was deleted.

@TheresNoTime https://meta.wikimedia.org/wiki/Talk:IP_Editing:_Privacy_Enhancement_and_Abuse_Mitigation/Archives/2021-11#What_about_global_rights_holder

This problem affects all Admins/Global Rollbacker/Stewards
See https://de.wikipedia.org/wiki/Spezial:Letzte_%C3%84nderungen?hidehumans=1&hidecategorization=1&hideWikibase=1&tagfilter=mw-rollback&limit=50&days=7&urlversion=2

@Jpita
I have tested with an article that I could not publish.

The error no longer occurs in the morning. I can now publish translations again, the Javascript error is no longer available.

@Aklapper I use Firefox (linux)