Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • biboumi biboumi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • louiz’
  • biboumibiboumi
  • Issues
  • #3456
Closed
Open
Issue created Jun 24, 2021 by Stephen Weber@singpolyma

Allow changing nickname on first connect if nick already in use

If I send <presence to="#room@biboumi/nick"><x muc> and nick is already taken on the network (tested using libera.chat) then I do get the <presence from="#room@biboumi/nick" type="error"><error><conflict> that I expect. However, if I immediately respond with a <presence to="#room@biboumi/nick_"><x muc> then instead of being joined with the alt nick, as I would expect, instead I get no reply and the remote disconnects me after some time.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking