pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2021-07-21T16:00:36Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/2107Use object validators for AP C2S2021-07-21T16:00:36ZHaelwennUse object validators for AP C2SThis is mostly a tracker issue so I don't forget and other people can know when AP C2S gets more usable again.
Object Validator would allow to only federate activities/objects according to our schema thus avoiding to federate broken obj...This is mostly a tracker issue so I don't forget and other people can know when AP C2S gets more usable again.
Object Validator would allow to only federate activities/objects according to our schema thus avoiding to federate broken objects and allowing more than the current one restricted to (Create+)Note and stuff like back-dating (probably within some configurable restriction).HaelwennHaelwennhttps://git.pleroma.social/pleroma/pleroma/-/issues/794ActivityPub C2S: Audience is changed by Pleroma when posting a Create activity.2020-05-19T13:18:52ZFeufochmarActivityPub C2S: Audience is changed by Pleroma when posting a Create activity.When posting a Create activity in the user's outbox, Pleroma changes the audience when recording the activity. The contents of the ``to`` field of the original activity sent by the client is recorded in the ``cc`` field, and the ``to`` f...When posting a Create activity in the user's outbox, Pleroma changes the audience when recording the activity. The contents of the ``to`` field of the original activity sent by the client is recorded in the ``cc`` field, and the ``to`` field is empty, unless ``to`` contains ``https://www.w3.org/ns/activitystreams#Public``, which remains in the ``to`` field.
I'm testing on a local instance on commit 5499750054081a4d4ac8a8b7b75dfd0a81f2a455
Example 1: the client posts a note with ``to`` set to ``["http://localhost:4000/users/test"]``, and ``cc`` set to ``[]``. Pleroma records the note with ``to`` set to ``[]`` and ``cc`` set to ``["http://localhost:4000/users/test"]``.
Example 2: the clients posts a note with ``to`` set to ``["http://localhost:4000/users/test"]``, and ``cc`` set to ``["http://localhost:4000/users/feufo"]``. Pleroma records the note with ``to`` set to ``[]`` and ``cc`` set to ``["http://localhost:4000/users/test","http://localhost:4000/users/feufo"]``.
Example 3: the clients posts a note with ``to`` set to ``["https://www.w3.org/ns/activitystreams#Public","http://localhost:4000/users/test"]``, and ``cc`` set to ``[]``. Pleroma records the note with ``to`` set to ``["https://www.w3.org/ns/activitystreams#Public"]``, and ``cc`` set to ``["http://localhost:4000/users/test","https://localhost/users/feufo/followers"]``.
I haven't tested the ``bto`` and ``bcc`` fields.
I'm unsure if this is the expected behaviour, as the ActivityPub spec does not say much about this. For direct/private messages, this can be a bit annoying, as the produced messages are not displayed in the notification timeline in the Pleroma front-end. However, I noted that if the message is public, it is displayed in the notification timeline.