I built Bugle, an ActivityPub server with Laravel and PHP. These are my notes on how it all works to the best of my understanding
  • savjee@lemmy.worldEnglish
    5·
    1 year ago

    Amazing blog post! Been reading the ActivityPub spec and found it rather lacking. It’s only when you add WebFinger and signed messages that things start to make sense.

    • savjee@lemmy.worldEnglish
      6·
      1 year ago

      And a followup question: wouldn’t it be more efficient for big instances to use WebSockets to federate? Making a HTTP request for every action your users take seems unnecessarily wasteful.

      • robb@apollo.townOPEnglish
        3·
        1 year ago

        Yeah it’s definitely very busy in terms of the amount of requests that’s get made. I’m not handling a bunch of them that I don’t need but there’s shitloads all the time.

      • RandomBit@lemmy.sdf.orgEnglish
        3·
        1 year ago

        I think that would only work when the number of instances is small. Two solutions to this might be:

        • have instances act like relays where the home instance of a community notifies 10 instances and then each of those instances notifies 10 instances, etc.
        • batch updates on a timer such that once a minute all posts, comments, boosts, etc within a minutes are buffered and sent together.