# content
@Bonfire@bonfire.cafe 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 @_followback@tags.pub 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?

# source.content
[@Bonfire@bonfire.cafe](https://bonfire.cafe/pub/actors/Bonfire) I'm looking into the fact that my instance isn't federating to [tags.pub](http://tags.pub) anymore, and the error I'm getting is from [github.com/evanp/activitypub...](https://github.com/evanp/activitypub-bot/blob/426f6d84afb4ee8894bb69e54ff03d9af4e346cb/lib/httpsignatureauthenticator.js#L155) (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 [@_followback@tags.pub](https://tags.pub/user/_followback) before the changes at the [#tagspub](https://bonfire.mavnn.eu/hashtag/tagspub) end, my instance is sending the wrong signature? And if so, is there anything I can do to 'refresh' the cache?