Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
pleroma
pleroma
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 413
    • Issues 413
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 65
    • Merge Requests 65
  • 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
  • #811

Closed
Open
Opened Apr 12, 2019 by Feufochmar@feufochmar

ActivityPub C2S: Inbox and Outbox contents are incorrect

According to the ActivityPub specification, the outbox contains all the activities published by an actor and the inbox contains all the activities received by an actor.

Currently when a GET request is done on the outbox, the outbox only contains the public activities, even when the actor is authenticated (with an OAuth bearer token for instance). When an actor is authenticated and is reading their outbox, the actor should be able to see all the activities, not just the public ones.

When a GET request is done on the inbox, the inbox contains the home timeline. So it also contains activities published by the actor, and not just the activities received by the actor. The home timeline is the merge of the inbox and the outbox. When using the ActivityPub C2S protocol, the home timeline should be built on the client side by fetching the inbox and the outbox, not on the server side by fetching the inbox.

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