I thought that my instance is having problems with sending posts to other instances, especially lemmy instances, so I tried something and these are my observations:

When I post an article to @kbinMeta not all servers that subscribed to the magazine get that article (seemingly). It of course appears at https://kbin.social, but not necessarily on other servers. This is not necessarily by design, it might be, that kbin.social is just struggling to keep up, but I’ve waited for about an hour and it did not show up on other servers and there are other posts from kbin.social users in kbinMeta at htts://lemmy.ml that got posted after I posted my article, but mine isn’t there.
However when I mention a user from another server in a comment this server instantly gets the comment that mentions the user from said instance including the article, which was previously not present on the server.

So here is my Theory:

  • I post something to @kbinMeta -> kbin.social gets the post (-> kbin.social broadcasts it to servers that subscribed to the magazine)
  • I post something to @kbinMeta and mention a specific user from https://feddit.de
    • -> kbin.social gets the post (-> kbin.social broadcasts it to servers that subscribed to the magazine)
    • -> feddit.de gets the post directly

The part thats in paranthesis I am not sure about. Maybe it gets done and maybe not. If it is done then the queue on kbin.social for outgoing messages is just huge and a message is waiting for over an hour to get processed

Maybe some of you know more than me. I just that and this is my observation.

  • isiloron@kbin.social
    2·
    1 year ago

    Here is the documentation for server to server delivery in the ActivityPub protocol.

    I think you are correct. If there are recipients in the “to”, “cc”, “bto”, “bcc” and “audience” fields, the activity will be delivered more quickly. Mentioning someone in a post is a way to add a recipient.