Conversation

Notices

1. Embed this notice
   maegul (maegul@hachyderm.io)'s status on Friday, 03-Nov-2023 17:26:36 JST maegul

   • Tim Chambers

   @tchambers
   > Joining ActivityPub would have been a big engineering effort

   Genuine and naive question: Is engineering against ActivityPub too hard?

   Any time I hear about the task, it’s difficult and often not worth it. Is this an impediment to the ecosystem? Could generic AP software be viably made and shift this, by perhaps at least covering a decent subset of the spec?

   • Embed this notice
     Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Friday, 03-Nov-2023 17:26:33 JST Jenniferplusplus

     in reply to

     • Tim Chambers
     • Hrefna (DHC)

     @hrefna
     I feel like people don't really grasp how long the ramp up is, and how completely impossible it is to implement federation incrementally. Maybe a visual will help some people?

     I've been at this for 4 months, and only just now approaching the "federated" starting line when I can work on app features instead of activity pub & friends.

     @maegul @tchambers

   • Embed this notice
     Hrefna (DHC) (hrefna@hachyderm.io)'s status on Friday, 03-Nov-2023 17:26:34 JST Hrefna (DHC)

     in reply to

     • Tim Chambers

     @maegul

     From my perspective, major challenges are:

     1. You cannot implement the spec as written and interoperate with mastodon (or any other major fediverse solutions)

     2. There isn't an official test suite or a reference implementation. This situation is improving, but it still haunts new implementers

     3. Interoperating with anyone is "whackamole driven development" because of the way extensions are handled and what is/is not implemented.

     4. There's almost no incremental path.

     @tchambers

     Fediverse Report repeated this.