Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 646
    • Issues 646
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 89
    • Merge requests 89
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #2423
Closed
Open
Issue created Jan 15, 2021 by Claire@ClaireContributor

Private posts can only be boosted by explicitly setting boost privacy to private

When boosting through the mastodon REST API (/api/v1/statuses/:id/reblog), private posts can only be boosted if the visibility parameter is explicitly set to private, which is not done by MastoFE or most Mastodon clients. Indeed, in such cases, Mastodon sets the announce visibility to private, but Pleroma returns a 404 error.

I am not sure why this happens, as CommonAPI.repeat should be handling that case through the public_announce? helper, but obviously something goes wrong.

Additionally, it would be nice if the error returned by Pleroma in case the visibility is invalid would not be a misleading 404 error.

Assignee
Assign to
Time tracking