Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • P pleroma-support
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleroma-support
  • Issues
  • #27
Closed
Open
Issue created Feb 25, 2020 by Gidi Kroon@gidi

Many non-local type=Delete activities in db with local=true

Should I worry about the regular occurrence of rows in the activities table which seem to be Delete activities which are marked as local, but which I didn't do? I'm only a single use instance, so I would know. E.g. this one today. It looks like the post was deleted on the remote side. I found nothing of interest in logs around that time. I wasn't doing anything on the site.

Does this mean my instance is forwarding Deletes? Or is it just a glitch in storing the activity? Should I just ignore that kind of thing? I'm on the most recent stable version.

I noticed this when looking into the effect that when deleting remote users using the Admin FE, Delete activities for their posts are stored in that table with local=true as well and presumably sent out. I mentioned this here but found more recent occurrences in the database.

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