An organiser's edits to a group's event follow its server
Mobilizon's organiser sends the Create, Update and Delete of an event attributed to the group, which announces the Event itself. PrivaPub refused the organiser's activities as misattributed (400) and kept the event through the group's Announce, so an edit was lost and a deletion left the event in place. An object attributed to another account of the actor's own server is now that server's to vouch for: created or edited as the server has it, under the account it is attributed to, and deleted once the server answers 404 or 410. Attributed to an account elsewhere, it is still refused. Checked against Mobilizon 5.2.4 in the pasture. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw
This commit is contained in:
1 parent
7f6837ccb1
commit
2d293a6148
8 files changed
+102
-3
No files matched your search
@@ -178,7 +178,8 @@ group www-data and reaches the private mongod; `sudo -u www-data` works too.
|
||||
- an activity is queued once per id, but an id that comes back carrying another type, actor or object is a second
|
||||
activity, not a copy (Friendica's ids are `uniqid()`, which two of its processes can share), and is queued apart;
|
||||
- the activity's `id`, and any object it creates, updates or deletes, is on the actor's origin; a cross-origin
|
||||
object is refetched from its own origin.
|
||||
object is refetched from its own origin. One attributed to another account of the actor's server (Mobilizon's
|
||||
organiser and the group's event) is taken as that server has it, and deleted once it answers 404 or 410.
|
||||
5. **Status codes:**
|
||||
- bad or missing signature: **401**;
|
||||
- malformed or forged body: **400**;
|
||||
|
||||
Reference in new issue
Block a user