-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Federating with Lemmy - Don't boost comments #18069
Comments
I'm sorry, but this bug report doesn't make any sense. If you follow the community, you'll get all of the posts the community makes in your home timeline. If the community is sending us |
FYI cc @Nutomic in case you missed Nightpool's comment :) |
@aschrijver Thanks for the heads up! @nightpool I dont see how the inbox filtering is related, it seems to be for delivering activities in case the original sender couldnt deliver them. In this case the problem is that Mastodon receives and displays activities from Lemmy (Announce/Create/Note) which the user doesnt want to see. This is due to a recent change in Mastodon, previously it didnt accept activities with this type at all. |
So... whose fault is it? |
Also experiencing this issue. Hope we can find a solution! |
+1 |
Same problem here. It's very annoying. Started a week or so ago for me on fosstodon.org |
Not sure how what something "seems to be for" is relevant. This mechanism, Inbox Forwarding, is the way every single other ActivityPub server implements reply forwarding to distribute replies to their activities. It's specifically said in the text of the spec to be designed to solve the ghost reply problem, which is the exact same problem Lemmy is trying to solve (i.e. "for groups to send activities to their followers"). If Lemmy wants to use boosts instead then that's their prerogative, but it's pretty clear that most users are annoyed by that decision. |
Sorry if the last response actually did send a notification, but just in case, uh, paging @Nutomic! (Also, pardon the bump! I figured replying to this instead of making a new issue would probably be the least annoying way to ask if there was a way for lemmy and mastodon to coexist in a way that takes over your timeline less, and figuring out if this was even the right place to ask about that) |
@Archenoth What do you ping me for? Federation is working fine between Lemmy instances, and is completely in line with the Activitypub standard. Its not my concern if Mastodon doesnt support this properly, Im not getting paid to solve their problems. |
@Nutomic the tl;dr version is that @nightpool's comment seemed to suggest the ball is in Lemmy's court again, so I was wondering if you'd seen it, since this is where the most recent conversation about this problem has been (Sorry if you had ^^') The less-tl;dr version is that , even though both this issue and the original one in the Lemmy repo are closed, the original issue @UserThre3 reported in both places still remains! If you follow a lemmy community of mostly any size from mastodon, it will overwhelm your feed by boosting all activity inside every post into your feed--enough traffic to completely monopolize your feed if you don't follow thousands of people
However, the suggestion to use Inbox Forwarding as a way to federate replies without needing to |
Oh! And the ping was because it seemed like this issue might fall through the cracks since both sides were mutually okay with waiting for a fix from a project that didn't feel like there was anything to do So I was hoping drawing your attention here would either lead to either a "Mastodon needs to do X for this to work" or a "Oh! Lemmy would need to X for this to work" so that we could figure out a way for Mastodon and Lemmy to interact in a usable way (Because this issue seems to be a pretty common reason for people not doing that) Sorry for the extra inbox traffic ^^' |
I think I explained this already before, but gonna clarify it once more: The Activitypub standard allows many different ways to implement the same functionality, so what Mastodon and Lemmy are doing is both in line with the standard. Specifically Lemmy implements FEP-1b12 which is the de facto Fediverse standard for group federation. Im not sure if inbox forwarding would work for Lemmy. There is a high chance it wont because Lemmy has to forward much more complex data than only simple So the solution here is for Mastodon to implement group support according to FEP-1b12, and render group posts differently from microblogging posts. There is #19059 which goes in this direction, although for some reason it implements group federation in a way thats intentionally incompatible with Lemmy, and hasnt been updated in a year. To be honest I doubt that posting this will really change anything. Mastodon maintainers probably wont read this, and they dont seem to have any interest to improve Lemmy compatibility. But maybe I will be proven wrong. |
Oh, damn. Yeaaaah I think it makes total sense why that would be a no-go ^^' Thank you for explaining! (And hopefully the masto-side eventually ends up being able to handle this more gracefully!) |
Steps to reproduce the problem
Discussion on Lemmy github re. this issue LemmyNet/lemmy#2224
Expected behaviour
Nothing. Comments should be attached to the post.
Actual behaviour
Comments gets boosted in the same way as community posts
Specifications
Mastodon 3.5.1
Lemmy 0.16.3
The text was updated successfully, but these errors were encountered: