The Cloud-Services project tag is not intended to have any tasks. Please check the list on https://phabricator.wikimedia.org/project/profile/832/ and replace it with a more specific project tag to this task. Thanks!

Since it's just one database, the name doesn't matter a shortened version will do, e.g., "bier-db"

I think the differences in how they work could cause confusion in the future.
AddPortlet ist a function signature and addPortlertLink is a list of parameters.

Yes, manually approving new users would also be a solution, rather than imposing a limit. In any case, neither of these situations usually comes up very often, since very few people create an account and then delete it right away.

The goal is to prevent the vanishing of vandalism accounts, as in the example. LTAs are now specifically creating accounts for short periods of time and make a Account vanishing.

Yes,
I'm aware of that. However, these links are often created accidentally in the source code.
Links that are intentionally added point to the User namespace or the MediaWiki namespace and can therefore be distinguished.

OK, I think that doesn't make sense.
On Special Central Auth, for example, only the current block is displayed and the block hiszory in the log is also unnecessary long.

Johannnes newprojects have users with activity in incubator and stewards can override the restrictions for this user.
New projects use SRP for user permission assignment anyway.

Johannes in small Projekts is this only a discussion.
Example: https://iu.wikipedia.org/wiki/%E1%90%85%E1%90%83%E1%91%AD%E1%90%B1%E1%91%8E%E1%90%8A:%E1%96%83%E1%92%A1%E1%92%8B%E1%96%85

With Passkey config for Logging is no 2 Factor needed.
You can config a Passkey for Login and a Passkey for 2 Factor.
A Passkey config for 2 FA cant used to login without password.
Passkey for login is to Login directly.

"Perhaps there is a way to do it in a manner without breaking backwards compatibility."

@Awesome_Aasim
I think the feature you're whish for already exists.
(Not using Punycode, but using an ID)
Example:
[[:metawikipedia:Special:Redirect/userid/8127961|UserID:8127961]] https://meta.wikimedia.org/wiki/Special:Redirect/userid/8127961

This would be in conflict with existing accounts

OK, I don't think hwb is necessary hex colors + named colors + RGB, and maybe hsl as well

No, that's not instead, but rather log entries that would also need to be deleted. In cases of vandalism, log entries often need to be deleted as well, such as usernames or page titles. Example: Sthis page. https://af.wikipedia.org/w/index.php?title=Spesiaal:WeergaweSkrap&target=Spesiaal%3ALogboek&type=logging&ids=676034%2C377266
collapsibility is optional, but you can also leave it out.

tha passkey login has not a 2 factor

@Awesome_Aasim You can already log in using Passkey.
To do this, you need to enable a two-factor authentication method, such as OTP or a second key.
After that, you can log in using Passkey. When logging in with a password, you need a second factor, the Passkey login works without a second factor.
Please note that you cannot set the same passkey as both a login and a 2FA key at the same time.

I think last activity (logs and edits) would better.

interface shows the page similar to a non-existent user

I don't think that's the intended , nor do I think it makes sense to compare hidden users with non-existent user.
Even if the user is hidden, they still exist. You just can't find them unless you know their exact name. But the edits are also displayed. Why shouldn*t the logbook links and nuke be displayed?

https://gerrit.wikimedia.org/r/c/operations/puppet/+/1263948

@Ivan-r per Userscript

However, it would make sense to implement this using two icons. Global and local are two different scopes.
In many situations, all you need to know is whether a user is blocked globally or locally. There’s no point in retrieving all the information of the info card here.

@kostajh for info
https://phabricator.wikimedia.org/rECHU1b7f1bf1362bd4ebeb0e08218f683bdd8d464680

@Raymond This is standard. Some Goofball is trying out passwords. That's not rare, often, these are just trolls who wanted to trigger notifications. In the past, such reports came across several projects. With a secure password, it is safe to ignore such notifications. If the user is unsure, you can point out the 2-factor authentication to them. With a secure password, you can ignore such notifications.

or so fully integrated with all
https://gitlab.wikimedia.org/wikibayer/Missbrauchsfiltererweiterung/-/commit/34dfebc829816d90747f7a2a21591f1961932806
https://gitlab.wikimedia.org/wikibayer/Missbrauchsfiltererweiterung/-/commit/c902d5bd144d33af1dd03fc1334226830b2b5463#

This could be easily implemented via an API change. Example api.php?action=query&list=abuselog&aflpageid=1

OH. i have misunderstood the bug report.

This filter does not only filter out entries from temporary accounts, as this filter is not for this, although temporary accounts fall under this filter.

@dom_walden This is not a Bug. This is by design. The version or logbook links only display the IP address with which the edits were made. You can use the [[T374869 ]] Autoreveal-Function or Special:IPInfo or a userscript (Example:User:WikiBayer/TempAccountInfoTooltip.js) or search more IPs and Accounts.,

I think that the behavior is currently intentional. I strongly doubt that this is a bug. @Johannnes89 This behavior is also present in the abuse filter extension with global Filters. See

I have thought on the Special:Contributions and equip this note with Sysop functions. See images for Example.(Normal users should only see the count of temporary accounts.)

A creation restriction only iss a little help with this goofball. It uses proxys.
But a note like “5 other temporary accounts have used the same ip address in the last few days” would simplify detection. As you can then immediately see that there are several TempAccounts. In my opinion, the note should be displayed for every user (alternatively only for registered users).

TitleFactory ?
Example
( I have not test the edit.)

It's not a error IP info is only possible if there is a version that has not been deleted. :-(

Normally you would have to contact the respective developer for user scripts, but if I look at the version history, Hotcat is no longer actively maintained. Edits in the last years were made by many individuals and are rather small.

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.