Why do I say #ActivityPub is overly complex and difficult to implement?
I'd need to get into some very geeky weeds to explain exactly why and I'm not going to do that on a thread. But, suffice to say, there's only a small number of full-featured Fedi implementations out there for a reason. And every single one of them is using a protocol implementation directly tied to their overall implementation.
This has been pointed out before:
> Playing with ActivityPub. https://macwright.com/2022/12/09/activitypub
[contd]
In fact, the closest thing we have to an ActivityPub *Reference Implementation* is the Express ActivityPub Server, which hasn't been updated recently and is only a *partial implementation*:
> https://github.com/dariusk/express-activitypub
I probably don't need to make the following point if you are a coder, but for the peanut gallery: Every substantial and mature protocol comes with a *Reference Implementation* as a testbed. And, by extension, this means ActivityPub is neither substantial nor mature.
[contd]
