Aha! I now have a number of failed HTTP Message Signatures from #ActivityPub servers.
The most common cause seems to be Date failures. The message was created with over 30 seconds of difference to when it was signed.
For example
```
Signature: 2024-03-17 19:46:07
Published: 2024-03-17 19:44:45
```
I don't know if 30 seconds is too stringent. It's what Mastodon uses, I think https://github.com/mastodon/mastodon/commit/1618b68bfa740ed655ac45d7d5f4f46fed6c8c62
Should I reply with a specific HTTP code?
Terence Eden /
npub1lh…aa5ll
2024-03-17 20:21:11
in reply to nevent1q…r5lc
Author Public Key
npub1lh05slh2nk6h5m3jp7qwtjmrmegtah6nj626g8qdg3a7ds3kg0ss9aa5llPublished at
2024-03-17 20:21:11Event JSON
{
"id": "ec54e9092210732a4222c1fb54e2092bb72095b78f0db7aa6526b9d093121e5b",
"pubkey": "fddf487eea9db57a6e320f80e5cb63de50bedf539695a41c0d447be6c23643e1",
"created_at": 1710706871,
"kind": 1,
"tags": [
[
"e",
"46154d44254924c4affd06cc63741767b9894e6c63c33ab66c13e6d0e675da6f",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"activitypub"
],
[
"proxy",
"https://mastodon.social/users/Edent/statuses/112112885511437693",
"activitypub"
]
],
"content": "Aha! I now have a number of failed HTTP Message Signatures from #ActivityPub servers.\n\nThe most common cause seems to be Date failures. The message was created with over 30 seconds of difference to when it was signed.\n\nFor example\n```\nSignature: 2024-03-17 19:46:07\nPublished: 2024-03-17 19:44:45\n```\n\nI don't know if 30 seconds is too stringent. It's what Mastodon uses, I think https://github.com/mastodon/mastodon/commit/1618b68bfa740ed655ac45d7d5f4f46fed6c8c62\n\nShould I reply with a specific HTTP code?",
"sig": "82983e7ddac833a8c6c68975d3fb9fcd675aeafbf41766b1ee5b538a54c88c034575fac8fc4f186ffd110d49a0401ae60f35c0c9cab6aabe7f5b91334af1b2f1"
}