Hi @[email protected]! You asked people to let you know if there was weird behaviour or bugs with tags.pub. I'm not sure if this is on the tags.pub end or on the @[email protected] end, but at the moment I seem to be able to federate exactly one outbound activity each time Bonfire restarts to tags.pub and then ask further pushes are rejected with a 400 error and a response about a missing Created field. Unfortunately I haven't found an easy way to see the outgoing request, so I don't know what info they're being signed with (I don't know if @[email protected] can suggest a way of me extracting that info?)
Discussion
@mavnn @Bonfire That's interesting. A missing `created` field would be an error with draft-cavage-12 signatures; they need to have a created stamp to avoid replay attacks. I wonder about the one-success-only issue; I bet that means that Bonfire is trying RFC 9421 signatures, they work, but it falls back to draft-cavage-12 signatures. I'll see if I can do some testing to make this work better.
@mavnn @Bonfire That's interesting. A missing `created` field would be an error with draft-cavage-12 signatures; they need to have a created stamp to avoid replay attacks. I wonder about the one-success-only issue; I bet that means that Bonfire is trying RFC 9421 signatures, they work, but it falls back to draft-cavage-12 signatures. I'll see if I can do some testing to make this work better.