pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2022-09-11T09:06:58Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/2937DOCS: Maybe document using c2s-API somewhere2022-09-11T09:06:58ZIljaDOCS: Maybe document using c2s-API somewhereWe have c2s api. It's not that difficult, but I also don't think we really have documentation for it. Would be nice to have. I'm not exactly sure where or how it's best to document, though.
This is a working example to post an event (ch...We have c2s api. It's not that difficult, but I also don't think we really have documentation for it. Would be nice to have. I'm not exactly sure where or how it's best to document, though.
This is a working example to post an event (change url and bearer token)
```sh
curl 'https://<instance.tld>/users/<username>/outbox' -X POST -H 'Content-Type:application/ld+json; profile="https://www.w3.org/ns/activitystreams"' -H 'Authorization: Bearer qsfqsdfqshudfqsdhufqusdhf' -d '{ "@context": "https://www.w3.org/ns/activitystreams", "type": "Create", "object": {"type": "Event", "content": "minimal AP C2S Event", "to": "https://www.w3.org/ns/activitystreams#Public", "cc": [] } }'
```https://git.pleroma.social/pleroma/pleroma/-/issues/2721Problem: Pagination may cause posts to be skipped in federation2021-07-22T02:57:02ZDavid SterryProblem: Pagination may cause posts to be skipped in federationThis isn't confirmed but coming out of a discussion about ActivityPub collections at https://socialhub.activitypub.rocks/t/implementing-paginated-inbox-collections/1919/4?u=weex in the section Example Inbox Implementations, @mag there su...This isn't confirmed but coming out of a discussion about ActivityPub collections at https://socialhub.activitypub.rocks/t/implementing-paginated-inbox-collections/1919/4?u=weex in the section Example Inbox Implementations, @mag there supposes that the way pleroma does pagination may cause some posts to be skipped if a post is made while fetching is going on. Opening this to track investigation.https://git.pleroma.social/pleroma/pleroma/-/issues/2220AP C2S: Exposing Bookmarks2020-10-07T14:59:19ZHaelwennAP C2S: Exposing BookmarksActors can have a `streams` field to present collections, I think we should use it like this:
```json
{
"streams": [
{"type": "OrderedCollection", "name": "Bookmarks", "id": "https://example.org/users/alyssa/collections/bookmarks"}...Actors can have a `streams` field to present collections, I think we should use it like this:
```json
{
"streams": [
{"type": "OrderedCollection", "name": "Bookmarks", "id": "https://example.org/users/alyssa/collections/bookmarks"},
…
]
}
```https://git.pleroma.social/pleroma/pleroma/-/issues/811ActivityPub C2S: Inbox and Outbox contents are incorrect2020-10-06T16:34:39ZFeufochmarActivityPub C2S: Inbox and Outbox contents are incorrectAccording to the ActivityPub specification, the outbox contains all the activities published by an actor and the inbox contains all the activities received by an actor.
Currently when a GET request is done on the outbox, the outbox only...According to the ActivityPub specification, the outbox contains all the activities published by an actor and the inbox contains all the activities received by an actor.
Currently when a GET request is done on the outbox, the outbox only contains the public activities, even when the actor is authenticated (with an OAuth bearer token for instance). When an actor is authenticated and is reading their outbox, the actor should be able to see all the activities, not just the public ones.
When a GET request is done on the inbox, the inbox contains the home timeline. So it also contains activities published by the actor, and not just the activities received by the actor. The home timeline is the merge of the inbox and the outbox. When using the ActivityPub C2S protocol, the home timeline should be built on the client side by fetching the inbox and the outbox, not on the server side by fetching the inbox.https://git.pleroma.social/pleroma/pleroma/-/issues/741ActivityPub C2S: Request to the URL of the conversation's ID returns blank HT...2020-10-06T16:29:25ZYuri VolkovActivityPub C2S: Request to the URL of the conversation's ID returns blank HTML page instead of JSON conversationUsing v.47.06 of AndStatus (see https://github.com/andstatus/andstatus/issues/499#issue-389014088 ) I'm requesting a conversation by its id. Receive HTML page as a response instead of expected JSON with a collection of activities.
url:'...Using v.47.06 of AndStatus (see https://github.com/andstatus/andstatus/issues/499#issue-389014088 ) I'm requesting a conversation by its id. Receive HTML page as a response instead of expected JSON with a collection of activities.
url:'https://pleroma.site/contexts/cebf1c4d-f7f2-46a5-8025-fd8bd9cde1ab'; response:'<!DOCTYPE html><html lang…';
Please implement!
Original Activity, from which I discovered the conversation ID:
```json
{
"type": "Create",
"to": [
"https:\/\/www.w3.org\/ns\/activitystreams#Public"
],
"published": "2019-03-10T18:46:31Z",
"object": {
"url": "https:\/\/pawoo.net\/@pawooAndStatusTester\/101727836012435643",
"type": "Note",
"to": [
"https:\/\/www.w3.org\/ns\/activitystreams#Public"
],
"tags": [
{
"type": "Mention",
"name": "@AndStatus@pleroma.site",
"href": "https:\/\/pleroma.site\/users\/AndStatus"
},
{
"type": "Hashtag",
"name": "#c2s",
"href": "https:\/\/pawoo.net\/tags\/c2s"
},
{
"type": "Hashtag",
"name": "#activitypub",
"href": "https:\/\/pawoo.net\/tags\/activitypub"
},
{
"type": "Hashtag",
"name": "#mastodon",
"href": "https:\/\/pawoo.net\/tags\/mastodon"
},
"c2s",
"activitypub",
"mastodon",
"nsfw"
],
"tag": [
{
"type": "Mention",
"name": "@AndStatus@pleroma.site",
"href": "https:\/\/pleroma.site\/users\/AndStatus"
},
{
"type": "Hashtag",
"name": "#c2s",
"href": "https:\/\/pawoo.net\/tags\/c2s"
},
{
"type": "Hashtag",
"name": "#activitypub",
"href": "https:\/\/pawoo.net\/tags\/activitypub"
},
{
"type": "Hashtag",
"name": "#mastodon",
"href": "https:\/\/pawoo.net\/tags\/mastodon"
},
{
"type": "Hashtag",
"name": "#c2s",
"href": "https:\/\/pleroma.site\/tags\/c2s"
},
{
"type": "Hashtag",
"name": "#activitypub",
"href": "https:\/\/pleroma.site\/tags\/activitypub"
},
{
"type": "Hashtag",
"name": "#mastodon",
"href": "https:\/\/pleroma.site\/tags\/mastodon"
},
{
"type": "Mention",
"name": "@AndStatus",
"href": "https:\/\/pleroma.site\/users\/AndStatus"
}
],
"summary": null,
"sensitive": false,
"published": "2019-03-10T18:46:31Z",
"inReplyToStatusId": "9gOorJogMWlBFNw1fE",
"inReplyToAtomUri": "https:\/\/pleroma.site\/objects\/7afcd0f7-f540-4f56-b7db-7ceac0ae4861",
"inReplyTo": "https:\/\/pleroma.site\/objects\/7afcd0f7-f540-4f56-b7db-7ceac0ae4861",
"id": "https:\/\/pawoo.net\/users\/pawooAndStatusTester\/statuses\/101727836012435643",
"conversation": "https:\/\/pleroma.site\/contexts\/cebf1c4d-f7f2-46a5-8025-fd8bd9cde1ab",
"context": "https:\/\/pleroma.site\/contexts\/cebf1c4d-f7f2-46a5-8025-fd8bd9cde1ab",
"content": "<p><span class=\"h-card\"><a href=\"https:\/\/pleroma.site\/users\/AndStatus\" class=\"u-url mention\">@<span>AndStatus<\/span><\/a><\/span> I do see your post via <a href=\"https:\/\/pawoo.net\/tags\/mastodon\" class=\"mention hashtag\" rel=\"tag\">#<span>Mastodon<\/span><\/a> site.<br \/>Please check via <a href=\"https:\/\/pawoo.net\/tags\/activitypub\" class=\"mention hashtag\" rel=\"tag\">#<span>ActivityPub<\/span><\/a> <a href=\"https:\/\/pawoo.net\/tags\/c2s\" class=\"mention hashtag\" rel=\"tag\">#<span>C2S<\/span><\/a> how two attached images may look like 👇<\/p>",
"cc": [
"https:\/\/pawoo.net\/users\/pawooAndStatusTester\/followers",
"https:\/\/pleroma.site\/users\/AndStatus"
],
"attributedTo": "https:\/\/pawoo.net\/users\/pawooAndStatusTester",
"attachment": [
{
"url": "https:\/\/img.pawoo.net\/media_attachments\/files\/013\/102\/220\/original\/b70c78bee2bf7c99.jpg",
"type": "Document",
"name": null,
"mediaType": "image\/jpeg"
},
{
"url": "https:\/\/img.pawoo.net\/media_attachments\/files\/013\/102\/261\/original\/104659a0cd852f39.jpg",
"type": "Document",
"name": null,
"mediaType": "image\/jpeg"
}
],
"atomUri": "https:\/\/pawoo.net\/users\/pawooAndStatusTester\/statuses\/101727836012435643",
"actor": "https:\/\/pawoo.net\/users\/pawooAndStatusTester"
},
"id": "https:\/\/pawoo.net\/users\/pawooAndStatusTester\/statuses\/101727836012435643\/activity",
"context_id": 30464285,
"context": "https:\/\/pleroma.site\/contexts\/cebf1c4d-f7f2-46a5-8025-fd8bd9cde1ab",
"cc": [
"https:\/\/pawoo.net\/users\/pawooAndStatusTester\/followers",
"https:\/\/pleroma.site\/users\/AndStatus"
],
"actor": "https:\/\/pawoo.net\/users\/pawooAndStatusTester",
"@context": [
"https:\/\/www.w3.org\/ns\/activitystreams",
"https:\/\/pleroma.site\/schemas\/litepub-0.1.jsonld"
]
}
```lainlainhttps://git.pleroma.social/pleroma/pleroma/-/issues/792ActivityPub C2S: Error 400 when posting non-activity objects not wrapped into...2020-10-06T16:28:52ZFeufochmarActivityPub C2S: Error 400 when posting non-activity objects not wrapped into a Create activityWhen posting an object that is not an activity to the user's outbox, it is expected that the server wraps it in a Create activity (See https://www.w3.org/TR/activitypub/#object-without-create ).
Currently, Pleroma responds with an error...When posting an object that is not an activity to the user's outbox, it is expected that the server wraps it in a Create activity (See https://www.w3.org/TR/activitypub/#object-without-create ).
Currently, Pleroma responds with an error 400 (Bad Request), with the message "Unhandled activity type". When wrapping the same item inside a Create activity, Pleroma accepts the request.
Ex: Unwrapped note causing an error:
{"@context":"https://www.w3.org/ns/activitystreams","type":"Note","to":["http://localhost:4000/users/test"],"cc":[],"summary":"Test note","content":"A small note"}
When wrapped in a Create activity, no error, the note is created:
{"@context":"https://www.w3.org/ns/activitystreams","type":"Create","to":["http://localhost:4000/users/test"],"cc":[],"object":{"@context":"https://www.w3.org/ns/activitystreams","type":"Note","to":["http://localhost:4000/users/test"],"cc":[],"summary":"Test note","content":"A small note"}}
Tested on commit 5499750054081a4d4ac8a8b7b75dfd0a81f2a455 from develop.lainlain