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
15 of 27 tasks
rhaamo opened this issue Jun 21, 2019 · 1 comment
Open
15 of 27 tasks

ActivityPub support tracking issue and audit #67

rhaamo opened this issue Jun 21, 2019 · 1 comment

Comments

@rhaamo
Copy link
Member

@rhaamo rhaamo commented Jun 21, 2019

ActivityPub tracking:

Custom AP Context is in api/activitypub/vars.py and used for Audio create and update.

Frontend

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

Various to implement

  • /api/v1/instance
  • /.well-known/host-meta
  • Deactivation of broadcasting the federation (#142)

Mandatory Actor changes

  • Every Actor should have an User, with local=False
    Best way might be to change models.py::create_remote_actor() to create the User.local=true at the same time.
    Returning an actor, user, and editing functions using create_remote_actor() to handle thoses two and save them.

Timelines

  • Home "Your feed"

Sound (re)publishing

  • Create
  • Update (not handled in Pleroma or Mastodon)
  • Handle fetching the original activity if getting an Update for an unknown track
  • Delete
  • Boosts
  • Likes
  • Important for incoming track handling: Federates track (#283):
    • Genre (string)
    • Tags (array of string)
    • licence (dict{licid: integer, name: string})
    • artwork (string, url)

Sound incoming (#283)

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

To check:

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

Things:

  • We probably should compute and store the count of followings/followers/tracks for remote users instead of having "0" displayed
  • Check if user Updates are properly handled

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 added this to the v0.5 milestone Aug 26, 2019
@rhaamo rhaamo removed this from the v0.5 milestone Aug 26, 2019
@rhaamo rhaamo added this to the v1.0 milestone 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
@rhaamo
Copy link
Member Author

@rhaamo rhaamo commented Jun 4, 2021

Probably wise to reimplement ActivityPub entirely using https://github.com/dsblank/activitypub since little-boxes isn't maintained anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant