C2S: Fetching from sharedInbox #3384

Open
opened 2025-11-30 04:26:37 +00:00 by mediaformat · 2 comments
Member

The sharedInbox endpoint is typically used to deliver public activities with the Server to server protocol.

I've tried fetching (with Bearer token) public activities from this endpoint, to construct a federated timeline. I'm assuming this is unimplemented.

The `sharedInbox` endpoint is typically used to deliver public activities with the Server to server protocol. I've tried fetching (with Bearer token) public activities from this endpoint, to construct a federated timeline. I'm assuming this is unimplemented.
Author
Member

sharedInbox endpoints SHOULD also be publicly readable OrderedCollection objects containing objects addressed to the Public special collection. Reading from the sharedInbox endpoint MUST NOT present objects which are not addressed to the Public endpoint.
https://www.w3.org/TR/activitypub/#sharedInbox

> `sharedInbox` endpoints SHOULD also be publicly readable `OrderedCollection` objects containing objects addressed to the [Public](https://www.w3.org/TR/activitypub/#public-addressing) special collection. Reading from the `sharedInbox` endpoint MUST NOT present objects which are not addressed to the Public endpoint.\ > https://www.w3.org/TR/activitypub/#sharedInbox
Author
Member

For what it's worth, I disagree that the endpoint SHOULD be publicly readable, I would make make it readable via Auth (Bearer tokens).

For what it's worth, I disagree that the endpoint SHOULD be publicly readable, I would make make it readable via Auth (Bearer tokens).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma#3384
No description provided.