mirrors/fep
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-09 05:56:10 +00:00
Code Packages Wiki Activity

update FEP-bebd (#858)

Browse Source 
Based on feedback from here: https://aus.social/@kauer/116717973794956900

- Sending a `Reject` for invalid `InviteCode` usage is now `SHOULD` instead of `MUST`
- including an `invites` collection on actors accepting `InviteCode`s is not `SHOULD` instead of `MAY`
- `InviteCode` `name` property must form a valid url for webfinger purposes

Co-authored-by: MaddyUnderStars <46743919+MaddyUnderStars@users.noreply.github.com>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/858
This commit is contained in:
Madeline
2026-06-11 15:15:31 +02:00
committed by silverpill
parent b741a7dfbf
commit 5a8cadbde7
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fep/bebd/fep-bebd.md
+3 -2
View File
@@ -40,6 +40,7 @@ It MUST contain the following properties:
The document MAY contain additional properties.
The InviteCode `name` MAY be user-defined. It is RECOMMENDED that the `name` is a short, alphanumeric string.
If InviteCodes are to be dereferenceable via Webfinger as described below, the `name` MUST be able to form a valid URL.
As InviteCodes can be dereferenced via Webfinger, they MUST be unique per instance.
@@ -63,7 +64,7 @@ When an Actor receives a Follow activity containing an InviteCode:
3. The Actor MAY impose any additional restrictions to the InviteCodes use
4. If the InviteCode has been deemed valid, an Accept activity is automatically sent for the Follow as would be normal for an Actor not gated by an InviteCode.
If the InviteCode is not valid, a Reject activity MUST be sent.
If the InviteCode is not valid, a Reject activity SHOULD be sent.
#### Example Restrictions
@@ -88,7 +89,7 @@ When an Add, Update, or Remove activity is received by an Actor from an unauthor
### `invites` Collection
Actors that accept InviteCodes MAY include an `invites` field that resolves to a Collection containing valid InviteCodes for this Actor.
Actors that accept InviteCodes SHOULD include an `invites` field that resolves to a Collection containing valid InviteCodes for this Actor.
If present, the `invites` Collection MUST be private and only accessible to authorised Actors.
## InviteCode Dereferencing via Webfinger