Skip to content

Comment on I Wrote an Activitypub Server in OCaml: Lessons Learnt, Weekends Lostparent

Comments

I think this is the wrong way of looking at it. If you're doing the whole stack, sure you will end up implementing quite a few things.

But consider that you can write a generic ActivityStreams server without supporting any of the ActivityPub activities. Now you have a generic platform to build on.

Tack on a tiny bit of support for e.g. addressing etc. as found in ActivityPub and you have what you need for federation.

With that generic platform, doing what you're suggesting is a matter of implementing a handful of Activities that mutates Objects and Collections.

What the author did is the equivalent of implementing a mailing-list manager by first writing a mail server from scratch instead of just writing the bits managing the list and sends, because he didn't have that lower level layer to build on.

There is indeed a lot of missing tooling to work with ActivityStreams/ActivityPub, that makes it painful now, and unfortunately a lot of ActivityPub implementers takes the same tack as the author and builds one big monolith instead of first building that lower layer.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.