Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 578
    • Issues 578
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pleroma
  • pleromapleroma
  • Merge requests
  • !3524

Open
Created Sep 12, 2021 by Tusooa Zhu@tusooaContributor1 of 1 task completed1/1 task
  • Report abuse
Report abuse

Implement moving account

  • Overview 14
  • Commits 13
  • Pipelines 8
  • Changes 15

As title. Use POST /api/pleroma/move_account with password and target_account fields to make the move.

  • Already done Something to consider: the PATCH /api/v1/accounts/update_credentials endpoint ( !2773 (closed) ) takes ap ids instead of nicknames. Mastodon always uses nicknames for both adding aliases and moving accounts. Maybe it's beneficial to add another endpoint like /api/pleroma/add_alias that does take nicknames, in order to make user interaction more unified.
Edited Sep 13, 2021 by Tusooa Zhu
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: from/develop/tusooa/emit-move