Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ActivityPub support tracking issue and audit #67

Open
rhaamo opened this issue Jun 21, 2019 · 0 comments

Comments

@rhaamo
Copy link
Member

commented Jun 21, 2019

ActivityPub tracking:

Frontend

  • Handle correctly remote users (IDs) vs local users (username) (#155)

Various to implement

  • /api/v1/instance
  • /.well-known/host-meta

Timelines

  • Home "Your feed"

Sound (re)publishing

  • Create
  • Update (not handled in Pleroma or Mastodon)
  • Delete
  • Boosts
  • Likes

Sound incoming

  • Create
  • Update
  • Delete
  • Various listing
  • Boosts
  • Likes

To check:

  • Actor Delete properly sent (to=)
  • Sound Delete properly sent too (to=)

Missing in frontend:

  • Comments tab on track
  • Likes tab on track
  • Boosts tab on track

Reports

  • handle the same AP implementation as mastodon
  • implement AdminFE pleroma backend endpoints
  • leverage the AdminFE reports support #127
  • add reporting modal in UI for end-users (logged-in)
  • Note: this would needs to add an Instance Actor, which would be used for the report origin user, so the reports are not tied to the real user for privacy reasons.
@rhaamo rhaamo modified the milestones: v0.5, v1.0 Aug 26, 2019
@rhaamo rhaamo changed the title ActivityPub support tracking issue ActivityPub support tracking issue and audit Oct 3, 2019
@rhaamo rhaamo added the Backend label Oct 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.