mirrors/fep
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-08 13:35:51 +00:00
Code Packages Wiki Activity

FEP-5219: Update proposal (#880)

Browse Source 
- Specified how actors with same privileges must be ordered.
- Added "Compatibility" section.
- FEP-1b12 moderators and FEP-5219 administrators are equivalent.
- Added "Delete group" to "Privileges" table.

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/880
This commit is contained in:
silverpill
2026-07-06 17:18:07 +02:00
committed by silverpill
parent bb072bab31
commit 958bd28fd6
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fep/5219/fep-5219.md
+8 -3
View File
@@ -46,14 +46,12 @@ Affiliations can be specified using the `affiliations` collection attached to a
- `subject`: the identifier of an actor.
- [`relationship`](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-relationship-term): the affiliation name (`admin`, `moderator`, `member`, `outcast` or a custom affiliation identifier).
The `affiliations` collection is sorted from most privilege to least privilege.
The `affiliations` collection is sorted from most privilege to least privilege. When two actors have the same privileges but different power levels, the actor with the higher power level MUST be placed first.
When adding a `Relationship` for a custom affiliation, a fallback representation SHOULD also be included. This fallback representation MUST specify an affiliation from the default set that has equal or fewer privileges compared to the custom affiliation.
Consumers MUST ignore relationships that represent unsupported affiliations.
The `affiliations` collection supersedes the collection of moderators defined in [FEP-1b12]. Consumers MUST read the `affiliations` collection when both collections are present.
Example of an `affiliations` collection:
```json
@@ -136,6 +134,7 @@ Semi-private group actors MUST have a `participants` property pointing to the co
| Add or remove members | `Add` or `Remove` | Yes | Yes | No | No | No |
| Add or remove moderators | `Add` or `Remove` | Yes | No | No | No | No |
| Update group metadata | `Update` | Yes | No | No | No | No |
| Delete group | `Delete` | Yes | No | No | No | No |
This list of privileges is not exhaustive. Additional privileges MAY be associated with the affiliations from the default set.
@@ -147,6 +146,12 @@ Recipients of a group activity SHOULD resolve the group's `affiliations` collect
All participants are allowed to update and delete their own posts, and to remove themselves from the group. Actions that affect other participants MAY be authorized if the actor has the necessary privileges.
## Compatibility
The `affiliations` collection supersedes the collection of moderators defined in [FEP-1b12]. Actors in this collection have an `admin` affiliation.
Consumers MUST read the `affiliations` collection when both collections are present.
## References
- Christine Lemmer-Webber, Jessica Tallon, Erin Shepherd, Amy Guy, Evan Prodromou, [ActivityPub], 2018