home.social

#sharedinbox — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sharedinbox, aggregated by home.social.

fetched live
  1. The ActivityPub specification does not have an example of the "sharedInbox" field in use.

    Although it does say "An optional endpoint..." — I suspect a lot of people won't know (with confidence) that it can go under the "endpoints" field. For example:

    "endpoints": {
    "sharedInbox": "https://social.example/inbox"
    },

    Especially if the person is still trying to understand ActivityPub, and isn't aware of the "endpoints" field yet.

    #ActivityPub #DeSo #FediDev #FediDevs #Fediverse #SharedInbox

  2. The ActivityPub specification does not have an example of the "sharedInbox" field in use.

    Although it does say "An optional endpoint..." — I suspect a lot of people won't know (with confidence) that it can go under the "endpoints" field. For example:

    "endpoints": {
    "sharedInbox": "https://social.example/inbox"
    },

    Especially if the person is still trying to understand ActivityPub, and isn't aware of the "endpoints" field yet.

    #ActivityPub #DeSo #FediDev #FediDevs #Fediverse #SharedInbox

  3. @Mike__happy @tor

    Yes, there exist a #SharedInbox to reduce traffic. So if you would have 1000 followers on #server B and you are on server A, it is just one #message for one #toot between A and B.

    Usually #federation starts with the first #follower. So if you are on server A and noone follows you on instance B, your toots will not be federated.

    But... it would be possible to search on B for the full URL to fetch an unknown toot from another instance.

  4. @Mike__happy @tor

    Yes, there exist a #SharedInbox to reduce traffic. So if you would have 1000 followers on #server B and you are on server A, it is just one #message for one #toot between A and B.

    Usually #federation starts with the first #follower. So if you are on server A and noone follows you on instance B, your toots will not be federated.

    But... it would be possible to search on B for the full URL to fetch an unknown toot from another instance.

  5. Can someone explain to me what happens when I publish a toot on #Mastodon?

    If I had 1000 followers on server B, would there be a network communication for each follower or does Mastodon use something like a #sharedInbox? Or is there something like a #relay?

    If I had no followers on server B, would my toot still be forwarded to server B? Could my toot then be found on server B e.g. via a hashtag search?

    #activitypub #askfedi #askfediverse

  6. Can someone explain to me what happens when I publish a toot on #Mastodon?

    If I had 1000 followers on server B, would there be a network communication for each follower or does Mastodon use something like a #sharedInbox? Or is there something like a #relay?

    If I had no followers on server B, would my toot still be forwarded to server B? Could my toot then be found on server B e.g. via a hashtag search?

    #activitypub #askfedi #askfediverse

  7. I got around to reading the ActivityPub spec. and it's pretty nice! I'm wondering how implementations decide when to create a shared inbox. Seems like a potentially interesting algorithm.

    #activitypub #sharedinbox

    @cwebber