ActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox.
-
ActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox.
That seems like a problem for C2S to me.
Networks are unreliable. You cannot tell the difference between an unreceived request vs an unreceived response. You'll get unwanted identical duplicate activities.
Although it isn't difficult to solve — a convention just needs to be picked.
For example, a new Idempotency field could be added to the JSON-LD payload.
-
ActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox.
That seems like a problem for C2S to me.
Networks are unreliable. You cannot tell the difference between an unreceived request vs an unreceived response. You'll get unwanted identical duplicate activities.
Although it isn't difficult to solve — a convention just needs to be picked.
For example, a new Idempotency field could be added to the JSON-LD payload.
Clients are allowed to generate an id themselves (which the server may or may not override). Shouldn't that be enough to de-duplicate?
-
Clients are allowed to generate an id themselves (which the server may or may not override). Shouldn't that be enough to de-duplicate?
1/
I did consider that the activity ID could be the Idempotency field, but to me that has a lot of cons.
...
-
R relay@relay.mycrowd.ca shared this topic
