About Kbin - why don't Kbin instances automatically grab updates if a magazine from another instance is out-of-date?
For example, if I (on kbin.run - which is Mbin, but for the purposes of this let's just assume it's Kbin) go to a random magazine on kbin.social, I will often see a prompt that the magazine may be incomplete and that I should visit the original instance for all the content.
Why doesn't the request to that magazine automatically trigger a "pull" from that instance for that magazine, or at least cause it to check if the number of threads is the same (and conditionally pull on that)? I would think by pulling the changes then, magazines would never be out-of-date.
I get that it would be a lot heavier of a load on the servers, but in combination with good caching techniques (maybe setting a time of 1 day or something until the next pull occurs, idk) I feel like that could be mitigated.
Is this maybe an implementation detail of ActivityPub?
Thank you!
![](https://kbin.life/media/cache/resolve/entry_thumb/23/02/2302eb29c1931049394b25b088ec7609e537b9499d7e4512f63604fe011024af.png)