Post AbPIkhC29oDtGhrPDk by maegul@hachyderm.io
(DIR) More posts by maegul@hachyderm.io
(DIR) Post #AbPIkhC29oDtGhrPDk by maegul@hachyderm.io
2023-11-02T04:51:54Z
0 likes, 0 repeats
@tchambers > Joining ActivityPub would have been a big engineering effortGenuine 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?
(DIR) Post #AbPIkiKvuCw4ob21jM by hrefna@hachyderm.io
2023-11-02T05:01:57Z
0 likes, 0 repeats
@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 implementers3. 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
(DIR) Post #AbPIkjCofs2NViF3ia by jenniferplusplus@hachyderm.io
2023-11-02T19:19:02Z
0 likes, 1 repeats
@hrefnaI 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
(DIR) Post #AbPIklFj41YLrJcPWy by hrefna@hachyderm.io
2023-11-02T05:12:51Z
0 likes, 0 repeats
@maegulYou can get a feel for the number of steps involved here: https://socialhub.activitypub.rocks/t/guide-for-new-activitypub-implementers/479That's before dealing with the layers of interop to work with anyone else, or specifications that are implemented based on old versions, etc.@tchambers