Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pleroma
pleroma
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 372
    • Issues 372
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 56
    • Merge Requests 56
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Pleroma
  • pleromapleroma
  • Issues
  • #726

Closed
Open
Opened Mar 11, 2019 by lain@lambadalambdaOwner
  • Report abuse
  • New issue
Report abuse New issue

Ephemeral / Expiring posts

Ephemeral posts are posts that only exist for a while and are automatically deleted after.

I'd suggest to use two mechanisms simultaneously.

  1. Make the originating server send a Delete message once the expiration date is reached
  2. Add an expires date field to the Note object itself, analog to published. Servers who know about this should periodically delete all notes which have an expires data that's in the past.

This could still miss some deletions (like relayed public posts) but should catch the majority of cases.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pleroma/pleroma#726