-
-
Notifications
You must be signed in to change notification settings - Fork 889
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
Remove unused apub audience field (fixes #5278) #5315
Conversation
My understanding is audience is how Lemmy knows which community to slot new posts into? Does Lemmy use to/cc instead? |
Yes for posts it determines the community from to or cc fields. For comments it uses in_reply_to to get the associated post, and gets the community from there. And for votes and other actions, it gets the community from the associated post/comment. |
Thanks, this will simplify NodeBB code so it won't need to track the community. I think there may be a use case for it down the line, though. Let me think on it a bit (though this doesn't affect the merging of this PR) |
One other note would be to amend FEP 1b12 with respect to this change 👍 |
258091d
to
002a578
Compare
The FEP is already finalized, so I dont think there is any possibility to change it (other than creating a new FEP which wouldnt make sense either). |
Reading this, it sounds like Lemmy traverses up the Semi-relatedly, this is where |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@julianlam And context collection can have the same Regarding 1b12, it doesn't require |
@dessalines Removed it from the comment and test case. The other occurences in |
This field doesnt serve any real purpose and can be removed.