-
Notifications
You must be signed in to change notification settings - Fork 138
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 with Lemmy #945
Comments
It's so nice if the federation is achieved!
It's because currently blog's inbox is not implemented in spite of On image, you're right. We will fix it. |
It would be great if you could implement the Group inbox and implement following for it. Lemmy cant follow Person accounts, so in the current state there would be very little interaction between both platforms. |
Yup. I want to do so. |
…date-deps into main Reviewed-on: https://git.joinplu.me/Plume/Plume/pulls/945 Reviewed-by: trinity-1686a <trinity-1686a@[email protected]>
Hi, lemmy dev here. i saw your release announcement yesterday, and decided to have a look how Plume federation works. Turns out its very easy to make it compatible with Lemmy, as you also use groups. After a few changes its already working from the Lemmy side, you can fetch and view Plume users, groups and articles.
See here for an example: https://ds9.lemmy.ml/post/27751
PR in Lemmy repo: LemmyNet/lemmy#2258
But there is a problem with activities, the ones sent from Lemmy are rejected:
It looks like the activity is not routed correctly, maybe because of the content-type header? In our case its
application/activity+json
.Another problem, i noticed some groups like https://blogs.kitaitimakoto.net/~/ArticlesEssays/ have a nested object with type Image and no url. This might be happening because the user hasnt set any avatar. I think it is incorrect, and should instead be encoded by leaving the image field out, or setting it to null.
Btw i tried to open this issue on your gitea, but still didnt get any confirmation mail.
The text was updated successfully, but these errors were encountered: