7
Why do federated articles end up in m/random?
(kbin.social)
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
Thanks! But why is this the case? Is it a technical limitation of ActivityPub? Or just a rough edge of the kbin code? (No idea if lemmy instances have the same issue)
@wahming
Without looking at the exact full data exchange, I can't say for certain. I don't even know if the trigger is as I think it might be.
But you can get a sense of where the information for the magazine account is by looking at this sample payload of what it looks like when a new Article/Thread is created and federated out. There is no "inReplyTo" because this is the initial thread/article, but it would point to the direct url for a previous content, not the magazine.
Just realised your hypothesis doesn't work, as many of the posts I see ending up in m/random have 0 comments, thus there is no way they could have been referred to by a comment/reply before they were federated.
@wahming
For Sure. It might not be comments, but some other way the thread shows up without the magazine information. I have seen the same thing you describe but I haven’t been able to capture data on it. I have a few ideas on how to test different scenarios but I need to figure out how to capture the raw data as well to verify.