Property talk:P9101

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Discord username
identifier for a person or bot on Discord

Represents	Discord username (Q105179066)
Applicable "stated in" value	Discord (Q22907849)
Data type	External identifier
Allowed values	^[^@#:\s][^@#:]{0,30}[^@#:\s]#\d{4}$|^[a-z0-9_\.]{2,32}$
Example	Pokimane (Q55956238) → pokimane#0001 Forsen (Q24204118) → Forsen#6593
Source	https://discord.com
Related to country	United States of America (Q30) (See 762 others)
See also	Skype username (P2893), Discord invite ID (P9078)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Database reports/Constraint violations/P9101 Map Random list
Living people protection class	property that may violate privacy (Q44601380)
Proposal discussion	Proposal discussion
Current uses	Total 82 Main statement 77 93.9% of uses Qualifier 3 3.7% of uses Reference 2 2.4% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9101#Scope, SPARQL

Format “^[^@#:\s][^@#:]{0,30}[^@#:\s]#\d{4}$|^[a-z0-9_\.]{2,32}$”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9101#Format, SPARQL

Citation needed: the property must have at least one reference (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9101#citation needed

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9101#Entity types

Conflicts with “website account on (P553): Discord (Q22907849)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P9101#Conflicts with P553, hourly updated report, search, SPARQL

Breaking change to Discord's username format will happen this month

Discord has traditionally had usernames in the format CustomUserName#1234, allowing users with the same name to be uniquely identified with a "discriminator" (four digits at the end). Discord has just announced that they'll be removing discriminators and requiring fully-unique usernames instead. Valid characters for usernames are also being limited to lowercase letters, numbers, full stops and underscores (a-z0-9_.).

This change will be rolled out "slowly over the course of several months", with users given the opportunity to migrate their account based on their account age (and a few other factors). Discord hasn't yet mentioned a deadline for this process.

In response, we'll need to adjust the regex format constraint for this property to allow for the new format. Eventually, all uses will need to be updated to whatever the person's new username may be. We can track progress with the constraint violation report. BEANS X2 (talk) 18:24, 3 May 2023 (UTC)

I've created a new regex that adds support for the new format: ^[^@#:\s][^@#:]{0,30}[^@#:\s]#\d{4}$|^[a-z0-9_\.]{2,32}$. The section after the pipe is for matching the new format: ^[a-z0-9_\.]{2,32}$. Once the first bots get migrated to the new format (verified bots are the first phase of migration), I'll update the regex in the constraint, unless there are any objections. BEANS X2 (talk) 10:47, 14 May 2023 (UTC)

I've just noticed that some Discord employees already have a new-format username, so I've updated the constraint regex. BEANS X2 (talk) 16:02, 17 May 2023 (UTC)