fxomt@lemmy.dbzer0.com to Fediverse@lemmy.worldEnglish · 8 hours agoPiefed has feeds now!piefed.socialexternal-linkmessage-square51fedilinkarrow-up1138arrow-down10file-text
arrow-up1138arrow-down1external-linkPiefed has feeds now!piefed.socialfxomt@lemmy.dbzer0.com to Fediverse@lemmy.worldEnglish · 8 hours agomessage-square51fedilinkfile-text
minus-squarenutomic@lemmy.mllinkfedilinkEnglisharrow-up13·7 hours agoAh 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.
minus-squarejollyroberts@jolly-piefed.jomandoa.netlinkfedilinkEnglisharrow-up11·6 hours agoFor 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: Send a Follow request for a Feed Accept a Follow request (this is automatic for public feeds) Reject a Follow request (this is automatic for private feeds) Announce an Add of a Community to a Feed Announce a Remove of a Community from a Feed Send a Delete of a Feed to subscribers
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: