I’m on mobile right now. I tested and this does not happen on other kbin instances. It also seems to happen with some magazines but not others and I’m not sure why—best guess is some of the magazines are totally new to this instance and some are not.

  • Elevator7009@kbin.runOP
    1·
    1 year ago

    It also is unfamiliar to me. I have another kbin account on another instance where I subscribed to magazines that were definitely new to that instance, and I wasn’t sent to m/all. I’m not sure what could be causing this.

    There are still a couple of hacks in place to keep federation working smoothly, but I do anticipate official code changes in the near future will greatly improve the overall kbin experience.

    —this kbin.run post you made

    If these hacks were ones you wrote, it might be those?

    • debounced@kbin.runM
      2·
      1 year ago

      there’s a manual retry period i added for things that fail to federate correctly the first time, but yes… it’s a little sketchy right now. it could also be something with this latest development code. the comparison between kbin instances is a little bit of a pain right now since we don’t tag the releases with version numbers. i will say there are several federation improvements with pull requests ready to get merged into the code, but @ernest hasn’t approved them yet.