@[email protected] I'm looking into the fact that my instance isn't federating to tags.pub anymore, and the error I'm getting is from github.com/evanp/activitypub... (where the signature checking code changed around the time I started getting errors)
I'm looking at the Bonfire code and it appears we're caching information about what signatures to send; is it possible that because I already followed @[email protected] before the changes at the #tagspub end, my instance is sending the wrong signature? And if so, is there anything I can do to 'refresh' the cache?
