- Verification based on same-owner policy instead of same-origin.
- Provided examples of "provably associated with actor".
- Using v2 context.
- Recommending single integrity proof.
- Changed "URL" to "URI" in the description of `verificationMethod`.
- Removed eddsa-jcs-2022 stability warning.
- Added "Security considerations" section with a link to FEP-fe34 (non-normative).
- Added "Privacy considerations" section.
- Added link to eddsa-jcs-2022 test vectors.
- Added Gush to implementation list.
- Fixed link to Conversation Containers.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/700
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
- Specified origin computation algorithm.
- Specified how origins and owners should be compared.
- Refer to FEP-2277 when describing identification of public keys.
- Same-owner embedding can be trusted.
- Don't allow updates of public keys.
- Anonymous objects don't have owners.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/698
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
- Added "Discovery" section.
- Described how media can be deleted.
- Specified status codes for authentication and permission errors during media upload.
- Specified status code for inbox / outbox permission error.
- Changed recommended status codes for non-existent inboxes and outboxes.
- Updated `discussionsTo` attribute.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/691
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
- Recommend using separate domain for media if media type can't be verified.
- Moved implicit ownership examples to the "Ownership" section.
- Include `replies` collection as an example of implicit ownership.
- Clarified how update/delete permissions work.
- Require servers to limit access to objects when `proxyUrl` endpoint is used.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/683
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
- Require to check Content-Type after fetching from origin.
- Clarified how fetching from origin is related to access control.
- Require same-owner check during signature-based authentication.
- Updated examples in "Reciprocal claims" section.
- Changed discussion link.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/672
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
- Added a list of differences between FEP-ef61 and FEP-fe34.
- Use "DID subject" instead of "identity" when describing relationship between DID and actors.
- Recommending FEP-ae97 (SHOULD instead of MAY).
- Clarified requirements related to inbox and outbox endpoints.
- Changed `discussionsTo` attribute.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/668
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
This commit incorporates some suggestions from
https://codeberg.org/fediverse/fep/pulls/657.
- Improved `Emoji` object description.
- Clarified text in the "Uniqueness" section.
- Max. width MAY be limited.
- Improved "Microsyntax" section.
- The order of `Emoji` objects in `tag` is not important.
- Moved "Compatibility" section to the end.
- Added "Right-to-left text" section.
- Moved XSS protection info to "Web client considerations" section.
- Added a sentence about repeated emojis to "Compatibility" section.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/661
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
This exception had two purposes:
1. Provide consistency with the exception in other policies defined by GoToSocial
2. Provide an “escape hatch” to mentioned users allowing them to react to mentions of them
However:
1. GoToSocial's interaction policies define this exception only for replies, and not for the other sub-policies, so not having this exception for quotes would not actually make it less consistent
2. While useful, this “escape hatch” is not necessary, as it is still possible to reply to such posts
3. this exception reduces the usefulness of the quote authorization feature a little, and adds both implementation and UX complexity
Therefore, we think this exception causes more issues than it solves, and we are considering removing it, even though it is a significant change to a FEP draft that has been largely unchanged for a while.
Co-authored-by: Claire <claire.github-309c@sitedethib.com>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/660
Co-authored-by: ClearlyClaire <clearlyclaire@noreply.codeberg.org>
Co-committed-by: ClearlyClaire <clearlyclaire@noreply.codeberg.org>
Helge
silverpill
silverpill
Ryan B
sneakers-the-rat
rugk
trwnh
a
Dima Krasner
devnull
ClearlyClaire
thisismissem
ilja