astra/owpengram-server
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Merge branch 'fix/username-resolve-floor'
Some checks failed
CI / Go tests (push) Has been cancelled
Details
CI / Admin web build (push) Has been cancelled
Details
CI / Grammy store bot (push) Has been cancelled
Details
CI / Docker main topology smoke (push) Has been cancelled
Details

Browse source
This commit is contained in:
Astra 2026-09-17 15:51:18 +01:00
commit 86c1ebc5de
1 changed files with 11 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

16
internal/domain/collectible_username.go
View file

@ -15,12 +15,18 @@ import (
// the same global registry, so occupancy checks and username resolution have a
// single source of truth.
//
// The editable slot keeps the service-level 5..32 length rule. Collectible names
// are minted by the operator and may be shorter: short names are precisely what
// a collectible market distributes. They still have to be syntactically
// resolvable by clients, so the character rules are identical.
// The editable slot keeps the service-level 5..32 length rule for
// self-service (account.updateUsername / channels.updateUsername); the admin
// path can go as low as 3 (see users.minUsernameLenAdmin /
// channels.minChannelUsernameLenAdmin). Collectible names are minted by the
// operator and may be shorter: short names are precisely what a collectible
// market distributes. Every kind of username still has to be syntactically
// resolvable by clients (contacts.resolveUsername, the public web landing
// page), so this floor doubles as the resolvability floor for the whole
// registry -- it must stay <= the lowest floor any write path can produce,
// currently 3.
const (
MinCollectibleUsernameLength = 4
MinCollectibleUsernameLength = 3
MaxCollectibleUsernameLength = 32
// MaxPeerCollectibleUsernames bounds the collectible rows a single peer can
// hold. The TL usernames vector is rendered in full by clients, so the bound