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

Federation things to implement later #698

Closed
7 of 9 tasks
Nutomic opened this issue May 5, 2020 · 1 comment
Closed
7 of 9 tasks

Federation things to implement later #698

Nutomic opened this issue May 5, 2020 · 1 comment
Labels
area: federation support federation via activitypub

Comments

@Nutomic
Copy link
Member

Nutomic commented May 5, 2020

Just a list of things that might be useful to implement later, but wont be implemented for the initial release.

various

  • create a comment view under /comment/1, which is identical to the comment's apub id (Add /comment/123 in UI lemmy-ui#505)
  • federate url of RSS feed for user/community (not clear that this is really needed, you might follow rss feed via federated instance)
  • Get rid of user and community refetch logic, add Update to accepted objects, and push those updates (including mod lists, user avatar changes, etc to other instances).
    • Update/Community added, but we still need the refetch logic, at least for compatibility with other projects
  • include reason in Remove activities
  • Comment create/update activity should include the creator of the parent post/comment in cc
  • http endpoints for post, community etc should only return local objects
  • properly federate images
  • write documentation
  • support different timezones Handle timezones #594 (fine as we are using UTC everywhere)

moved to #1220

  • pagination for collections
    • not needed, our only collection (community outbox) is limited to 20 items
  • add comments collection for posts to optimise loading (peertube example)
    • not necessary for now
  • outbox for community and user
    • community outbox added, but only includes limited number of posts, no votes or comments
  • ignore incoming activities that are not public
  • generate proper IDs for activites and implement routes for them (eg /federation/activity/something)
  • use proper context
  • convert text to html, put markdown into a seperate field
  • store and use URLs discovered from remote actors, instead of assuming everything is Lemmy (inbox, outbox, sharedInbox, followers) (see Discover sharedInbox #808)
  • implement tombstone for user
  • make sure that our implementation follows the activitypub spec
  • accept activities both via /c/{community_name}/inbox and sharedinbox (same for user)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@Nutomic
Copy link
Member Author

Nutomic commented Oct 22, 2020

I moved most of these tasks to #1220. Maybe the rest should also go into separate issues, because this is too broad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: federation support federation via activitypub
Projects
None yet
Development

No branches or pull requests

1 participant