Nothing posted from Lemmy to a Fedia magazine is federating out to that magazine/community on other Lemmy instances. I don’t think it is working for kbin either.

eg. https://fedia.io/m/ukdtt/t/143141/DTT-licence-updates-26-Jul-2023 - posted from feddit.uk to a fedia.io magazine (and has successfully reached the home instance), has not turned up on https://rabbitea.rs/c/[email protected]

Checking other magazines I don’t think this is working properly for any of them, but don’t know if it is just fedia or a wider kbin problem.

Anyone else seen similar?

@jerry

  • dannekrose@kilioa.org
    1·
    1 year ago

    @chris

    This is by design. ActivityPub is a push model and it’s a Push-once (in general).

    What that means is that the instance that the creator/author of the content is on will push the content to all the other instances that it knows are subscribers to the “account/magazine” that the content is being pushed to.

    What that means is:

    • Feddit.uk will push the content to Feddia.io because that’s the “destination” account/magazine.
    • Feddit.uk will push the content to any instances that is also happens to know subscribe to the magazine “ukdtt”
    • Fedia.io will not re-push the content to all the instances that subscribe. That’s the responsibility of the instance that the content “originated” from, not Fedia.io
    • e569668@fedia.io
      0·
      1 year ago

      This is something I have been wondering; but does that mean kbin/this instance is not involved at all?

      For the post in question, the original url is https://feddit.uk/post/771973 , a lemmy instance. OP is asking why it isn’t getting sent to rabbitea.rs, another lemmy instance. Is feddit.uk responsible for sending it there? But how would it know about rabbitea.rs subscribers? And surely the destination magazine must be involved somehow to run rules on like, banned users? otherwise that means any external user banned by fedia could continue to post forever with no way to stop them and it would still federate out everywhere

      • chris@fedia.ioOP
        2·
        1 year ago

        Yes, this doesn’t make sense. How I thought it worked is that the originating server would push the new article to the home instance, and the other instances then pull from there (or the home server pushes; whatever, same net effect). If that isn’t how it works, I don’t see how it can work, as every server which posts to a magazine would need to know who subscribes to it. Certainly in the case of Mastodon, it doesn’t have a concept of this, yet can post to communities/magazines and the comments federate out (maybe comments work differently though? There doesn’t appear to be a problem with comments as far as I can tell)