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 647
    • Issues 647
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • 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
  • #316
Closed
Open
Issue created Oct 10, 2018 by chloe@ary

Private accounts can still be followed without validation by other local accounts

It's my first report here so i'm sorry if i do anything wrong, i searched for a similar issue but did not find anything relevant to my case.

So here's the thing : Someone on my instance has a private account, someone else on the instance also has their account set to private, when one tries to follow the other the whole validation step is just skipped and they can both see followers-only posts from each other. I created accounts on the instance to test this and can confirm it happens every time i retry, even with my main account. There's nothing in the journalctl on the server and no other error message.

Assignee
Assign to
Time tracking