Human Web CollectiveActivityPub specifications don't seem to provide a way to do Idempotent POSTs to your outbox
submitted by
@reiver ⊼ (Charles) :batman: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.
@reiver I don't know if it's a manifestation of the Dunning-Krueger effect, or the universe just makes folks think of the same things at similar times, but someone out there seems to has questions about idempotency keys being the solution.
blog.dochia.dev/blog/idempoten
@mariusor
I skimmed the article.
I think he could deal with some of the issues he has with payments. But he needs a more complex way of storing state about the steps the software has to go through.
And, he also needs a way for the payment system (or any other external system) to support both queries and undo.