- 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>
- Clarified assumptions and moved them to Authentication section.
- Location SHOULD match object ID.
- Changed authentication rules for embedded objects.
- Fixed incorrect example in Authorization section.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/653
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
There are a few updates in this PR.
- Two new inverse properties, `pendingFollowersOf` and `pendingFollowingOf`
- Semantically versioned aliases for the context for future-proofing
- One section per term
- Implementations list
- Clarified examples
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/640
Co-authored-by: Evan Prodromou <codeberg@evanprodromou.name>
Co-committed-by: Evan Prodromou <codeberg@evanprodromou.name>
The main changes in this update have been made after a couple of incidents where people have
misunderstood the document and got the wrong idea:
- Added a summary to make it clearer that OWA is used in connection with other protocols, rather
than being an alternative to ActivityPub etc.
- Expanded the "Security Considerations" section. In particular, be more explicit about the
potential for impersonation attacks.
Also added "type: implementation" and updated the Implementations section to be compatible with
@silverpill's proposal here: https://codeberg.org/fediverse/fep/pulls/634
Co-authored-by: FenTiger <fentiger@mythik.co.uk>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/643
Co-authored-by: Mike P <fentiger@noreply.codeberg.org>
Co-committed-by: Mike P <fentiger@noreply.codeberg.org>
ActivityPoll is a proper subset of ActivityPub that excludes activity delivery, making it easier to implement for static Web sites or content management systems. It meets an equivalent need to RSS or Atom feeds.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/636
Co-authored-by: Evan Prodromou <codeberg@evanprodromou.name>
Co-committed-by: Evan Prodromou <codeberg@evanprodromou.name>
silverpill
trwnh
a
Dima Krasner
silverpill
devnull
ClearlyClaire
thisismissem
ilja
Evan Prodromou
André Menrath
Mike P