This proposal describes an ActivityPub extension to allow actors to publish a short status text, with optional expiration, link attachment, and history.
Some centralized communication services provide their users with the ability to set a status on their account, which is usually displayed on their profile and sometimes next to their name in other places in the UI. These are distinct from regular posts because they can not be interacted with in any way whatsoever, can't contain media attachments, and usually have a short character limit on the order of several hundred characters at most. Statuses are always visible to anyone who can see the actor itself.
Co-authored-by: Grishka <git@grishka.me>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/596
Co-authored-by: grishka <grishka@noreply.codeberg.org>
Co-committed-by: grishka <grishka@noreply.codeberg.org>
Two updates on FEP-B2B8 to respond to open issues: Discourage embedding "Read more..." links in the summary, content, and preview of an Article, and how to use the `sensitive` flag to indicate sensitive content.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/591
Co-authored-by: Evan Prodromou <codeberg@evanprodromou.name>
Co-committed-by: Evan Prodromou <codeberg@evanprodromou.name>
- Added "Assumptions" section.
- Added warning about media uploads.
- Don't allow clients to create public keys.
- Clarified that object must be fetched by its ID.
- Updated "Ownership" section to make it more aligned with FEP-2277.
- Don't use same-origin policy when authorizing access to protected resources.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/589
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
The reference to ActivityPub spec currently includes only ActivityPub editors.
According to [W3C guidebook](https://www.w3.org/guide/editor/role.html):
>The role of the editor is not that of author. They maintain the text of a current draft that the Group has agreed to and possibly to suggest concrete wording when none is forthcoming from the group.
I think it would be more appropriate to include all authors there.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/542
Reviewed-by: a <trwnh@noreply.codeberg.org>
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
- New registration process where keys are generated and stored by the server.
- C2S API requests are signed with identity key.
- Added `type` field to proposal metadata.
- Added reference to HTTP Signatures report.
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/564
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
This draft is still work in progress. I created the Pull Request to already share it with possible interested audience.
ToDo before removing WIP:
- [x] Anonymous Joins, indicate that such will always will be rejected. When supporting Organizers: `Join` has `to` or `cc` set to Organizer Collection of the Event.
- [x] Organizer collections
- [x] Move all definitions from https://event-federation/ns# to the w3c fep namespace of this fep. (https://codeberg.org/fediverse/fep/src/branch/main/fep/888d/fep-888d.md#defining-terms-associated-with-an-fep)
- [x] Collection of upcoming Events
- [x] Maybe define own "timezone" attribute...
- [x] Multiple banner images sizes: encourage to provide if available and give `width` and `height` attributes!
- [x] `organizer` or `organizers` (Use plural for `Collection` and singular for lists).
Co-authored-by: les <lesion@autistici.org>
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/430
Co-authored-by: André Menrath <linos@noreply.codeberg.org>
Co-committed-by: André Menrath <linos@noreply.codeberg.org>
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>
grishka
silverpill
silverpill
Evan Prodromou
André Menrath
ClearlyClaire
Tim Bray
devnull
a
Mauve Signweaver
trwnh