That's not an HTTP signatures algo - you must be talking about linked data signatures. It's not spec-compliant to require LD signatures, and even the best practices report says they're only useful...
We are on the older cavage draft 10 of http signatures before the hs2019 fake algorithm thing
@thatonecalculator you think CalcKey might be responding 202 on a POST that's not properly signed?
guppe_guppe.1.xhcrfzlyz8jj@guppe-test
Another note: I think we could do a separate FEP for ID-less undo. I really like @trwnh 's proposal to
UndoaBlockwithout anidbut with the rightobject. We could do that for...
I think from a Server's POV the main consideration is dropping interactions from blocked actors --> i.e. getting a list of all blocked actors
For a Client, the main consideration is being...
The activitypub-express library (and projects based on it like Immers Space and [Guppe groups](https...
I've determined that this is due to guppee not properly implementing secure fetch/authorized fetch, which is entirely a problem on their end, not ours. Calckey requires secure fetch, for (as the...
Went back in after rate limit expired and limited to 1 replica, but I still couldn't renew. It just sat for a few minutes waiting for the ACME challenge until it was eventually killed by docker...
Closing this as the changes are in. No worries about credit, my commit is in the history anyway
Here's an example of the error: https://github.com/immers-space/immers/actions/runs/3378969630/jobs/5609903444
And here's a commit where I worked around it temporarily: https://github.com/immers...