FEP-5219: Groups and permissions has been updated:
https://codeberg.org/fediverse/fep/pulls/895/files
- The items in the affiliations collection are now required to be full Relationship objects with id, attributedTo and object properties. I think these objects should be self-contained and exist independently of the collection.
- Access to the collection MAY be limited (for example, when the group is private).
FEP-5219: Groups and permissions has been added to the FEP repository.
RE: https://mitra.social/objects/019e87e9-62a6-71d1-8edc-3a8a63e96c9f
Updating FEP-5219: Groups and permissions: https://codeberg.org/fediverse/fep/pulls/908
I added two flags that indicate whether a group is private, semi-private or public: canFollow and canParticipate. These flags are similar to ones used in interactionPolicy pattern but I think interaction policies don't scale well.
There is now a thread on SocialHub if you prefer it for FEP discussions: https://socialhub.activitypub.rocks/t/fep-5219-groups-and-permissions/8855
Minor FEP-5219 update: https://codeberg.org/fediverse/fep/pulls/880
I started implementing this FEP in Mitra, here's how an affiliations collection looks like:
https://mitra.social/ap/actors/019f0e0d-b949-7600-aa86-0df8e275c291/affiliations
Updating FEP-5219: Groups and permissions:
https://codeberg.org/fediverse/fep/pulls/916/files
The biggest change here is the replacement of "follow" and "participate" privileges with "view" and "create". Follow and Join are now described separately in the context of follower/participant statuses (which are not privileges - they are used for addressing activities).
