-
-
Notifications
You must be signed in to change notification settings - Fork 890
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
Labels
area: federation
support federation via activitypub
Comments
Nutomic
added a commit
that referenced
this issue
Oct 3, 2020
dessalines
pushed a commit
that referenced
this issue
Oct 5, 2020
… and similar (ref #698)' (#110) from read-only-local into main Reviewed-on: https://yerbamate.dev/LemmyNet/lemmy/pulls/110
I moved most of these tasks to #1220. Maybe the rest should also go into separate issues, because this is too broad. |
Nutomic
added a commit
that referenced
this issue
Oct 27, 2020
dessalines
pushed a commit
that referenced
this issue
Oct 27, 2020
dessalines
pushed a commit
that referenced
this issue
Oct 27, 2020
…in cc (ref #698)' (#122) from comment-parent-cc into main Reviewed-on: https://yerbamate.dev/LemmyNet/lemmy/pulls/122
15 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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(Add/comment/1
, which is identical to the comment's apub id/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)Update
to accepted objects, and push those updates (including mod lists, user avatar changes, etc to other instances).Remove
activitiescc
moved to #1220
pagination for collectionsadd comments collection for posts to optimise loading (peertube example)outbox for community and userignore incoming activities that are not publicgenerate proper IDs for activites and implement routes for them (eg /federation/activity/something)use proper contextstore and use URLs discovered from remote actors, instead of assuming everything is Lemmy (inbox, outbox, sharedInbox, followers) (see Discover sharedInbox #808)implement tombstone for usermake sure that our implementation follows the activitypub specaccept 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.
The text was updated successfully, but these errors were encountered: