This is a work-in-progress document describing Mastodon's proposed way of representing quote posts, users' choices regarding whether their posts can be quoted and by whom (quote policies), and a mechanism for servers to verify compliance with such policies.
This document describes protocol considerations, which do not necessarily translate directly to User Experience considerations. For instance, the use of the approval mechanism described in this document does not imply that the user's approval is manual.
Co-authored-by: Claire <claire.github-309c@sitedethib.com>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/545
Co-authored-by: ClearlyClaire <clearlyclaire@noreply.codeberg.org>
Co-committed-by: ClearlyClaire <clearlyclaire@noreply.codeberg.org>
Hey folks, we at [Distributed Press](https://distributed.press) have been working on making a bridge between peer to peer or "dweb" protocols and ActivityPub implementations over the past year and wanted to solidify our approach so that others can interoperate.
Here's is an initial draft explaining our work. We also have some live sites and implementations linked from there for those curious to try them out.
For anyone attending DWeb Camp in August, my colleagues will be there to chat about it in person if you're curious.
Co-authored-by: Mauve Signweaver <mauve+git@mauve.moe>
Co-authored-by: Mauve Signweaver <contact@mauve.moe>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/379
Co-authored-by: Mauve Signweaver <rangermauve@noreply.codeberg.org>
Co-committed-by: Mauve Signweaver <rangermauve@noreply.codeberg.org>
This FEP introduces inverse properties for the most important collection properties in ActivityPub. These provide two main benefits: first, navigating from a collection to the object it is a property of; second, two-way verification of the relationship between the object and the collection.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/537
Co-authored-by: Evan Prodromou <codeberg@evanprodromou.name>
Co-committed-by: Evan Prodromou <codeberg@evanprodromou.name>
- Added `endpoints.gateways` to the list of `gateways` alternatives.
- Specified optional publishing of gateways as DID sarvices.
- Added note about ActivityPub compatibility.
- Added warning about changing URI scheme.
- Added `type` to proposal metadata.
- Changed "Controller Documents" to "Controlled Identifiers" and added that spec to "References".
- Removed Data Integrity standard from "References".
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/529
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
- Added section describing cross-origin relationships.
- Removed note about "other ways to establish trust".
- Clarified what "authentication" means.
- Specified that location must be the last in the chain of redirects.
- Clarified what "authorization" means.
- Made "Ownership" a sub-section of "Authorization".
- Added `type` to proposal metadata.
- Updated discussion link.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/526
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
clarifications made:
- the `rdfs:label` of `as:context` is roughly "was created in relation to", citing James Snell in a github issue explaining the intended usage of the `context` property.
- most usages of the concept of a "context" include behavior where deleting a context deletes anything within that context. this is not a requirement or recommendation, but it is called out as possible behavior.
- exactly how to participate in a context or copy an existing context is protocol-dependent and left out-of-scope of this FEP; to be followed up on in future FEP efforts
- examples are simplified to leave out protocol details and focus on publishing and consuming context. a new example 4 is added for demonstrating the extension point for "canonical collections".
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/523
Co-authored-by: a <a@trwnh.com>
Co-committed-by: a <a@trwnh.com>
I've made two changes:
1) Update the FEp to use the`template` property (used in oStatus and defined by RFC-6415) instead of the `href` property (which is the only option in the WebFinger spec)
2) Clarified definitions of `on-success` and `on-cancel` to state that these are Workflow commands which might be URLs, but might also be an action like `(close)`
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/513
Co-authored-by: Ben Pate <ben@pate.org>
Co-committed-by: Ben Pate <ben@pate.org>
ClearlyClaire
Tim Bray
devnull
a
silverpill
silverpill
Mauve Signweaver
Evan Prodromou
trwnh
Ben Pate
Steve Bate
Helge
Mike P