I was browsing 196 recently and I noticed that stuff between slrpnk and blahaj weren’t federating between the 2 properly.
From slrpnk (another lemmy instance) there looks like there hasn’t been a post in 196 since yesterday but checking from blahaj it’s as alive as always.
I then checked from lemmy.world, beehaw, sopuli.xyz, and lemmy.zip to see if it was just an issue with slrpnk but it appears to be widespread as all of those other instances have the same issue.
Hopefully me making a post here isn’t an issue (and that it federates properly) but I figured reporting a bug wouldn’t be an issue.
There will absolutely be federation issues for a bit due to having to reset the activitypub key pairs for every lbz user and community. Cotent is federating out, as you can see non lbz users interacting with some of the recent 196 posts. The issue is most likely that the keys are still being cached by remote instances, and until those keys fall out of their respective caches, things are going to be inconsistent.
I think I understand lol
Basically each instance has a way of signing it’s data between each other (and you had to change blahaj’s signature) and the memo about the change still needs to reach other instances which will take some time to riffle out through the network of instances?
And we’ve basically gotta wait until those old signatures fall out naturally before things sync up properly again?
Close! Basically, once the remote instance has verified a signature, they cache it, so they don’t have to double check with the host instance every time. But when the keys change, and the remote instance is hosting a cached copy that doesn’t match anymore, you run in to problems, until the cached copies expire, and the remote instance refreshes their keys.
yesyes i noticed super low like counts and comments too. odd ~
