While the actor is a Group and you can follow it, no posts are Announced. All the federation of posts is still driven by the individual communities within the feed. You’ll need to modify Lemmy to add the logic of subscribing to the constituent communities when you receive an Accept.
Also there are Add and Remove activities sent out whenever the feed owner manages the list of communities within which would need to be handled.
For the federating its a new kind of AP actor. I’ll be putting in a FEP for it in the near future, but its basically a “Group” that only cares about the “Following” collection.
Hmm so the Feed actor mainly consists of a following collection and uses Add/Remove activities. This really sounds like it should be a Collection and not an actor.
While the actor is a
Groupand you can follow it, no posts areAnnounced. All the federation of posts is still driven by the individual communities within the feed. You’ll need to modify Lemmy to add the logic of subscribing to the constituent communities when you receive anAccept.Also there are
AddandRemoveactivities sent out whenever the feed owner manages the list of communities within which would need to be handled.Documentation still to come…
Ah its more complicated than I thought. We also have a similar or same feature on the roadmap, when I get to that it can federate with Piefed.
For the federating its a new kind of AP actor. I’ll be putting in a FEP for it in the near future, but its basically a “Group” that only cares about the “Following” collection.
You can see example json for the AP interactions here: https://codeberg.org/rimu/pyfedi/src/branch/main/docs/activitypub_examples/feeds
The AP interactions for a Feed are:
Hmm so the
Feedactor mainly consists of a following collection and uses Add/Remove activities. This really sounds like it should be aCollectionand not an actor.