I heard often about activityPub being challenging to implement.

Now I know part of this is because, if you are building on activityPub, you want interop with existing platforms such as mastodon, and they do their own thing.

But ignoring that aspect, what is so hard about activityPub? What could have been done better?

I am a software developer, so feel free to use software dev concepts and terms when explaining. Thanks!

    • RobotToaster@mander.xyzEnglish
      10·
      3 months ago

      the protocol doesn’t define how to ensure activities propagate to every server.

      Outboxes are kinda that, but as I understand it mastodon’s implementation is deliberately defective.

    • JackbyDevEnglish
      1·
      3 months ago

      Unless two instances had the exact same set of servers they’re federated with then I wouldn’t expect any given content to have the same number of likes/comments/etc when viewed from different instances.

    • diffieQ@lemmy.worldEnglish
      1·
      3 months ago

      What were some of the reasons as to why you “found it impossible to set up everything properly” re: C2S implementation? I’ve been trying to figure out why the C2S isn’t being adopted, as I think it solves many of the fediverse’s current UX challenges