> If we were going to make something like this that is Django
> specific, we’d normally want to have a working, battle-tested third party
> implementation before considering merging it to core.
Let me try to reformulate it in different terms.
It’s not about some new big workflow.
It’s not about
Hi there,
Craig Smith is working on making cookie-based messages RFC compliant
(https://code.djangoproject.com/ticket/32191). Our prefered approach would
be to encode messages via `signing.dumps` and this is (excuse the wording)
where the shitshow begins. As it currently stands we cannot use
