I’m reading the ActivityPub spec here and it seems pretty fit for client-to-server communications. Yeah, it might be somewhat bulkier than your typical rest api, but it's more universal, which begs the question: why do mastodon and lemmy both decided to implement custom (and incompatible) APIs for their clients to talk to the servers? Wouldn’t it be more straightforward if e.g. my voyager app talked ActivityPub to lemmy.world which then talked ActivityPub to lemmy.ml or something.

What am I missing?

you are viewing a single comment's thread
view the rest of the comments

[–] skullgiver@popplesburger.hilciferous.nl 6 points 1 year ago* (last edited 9 months ago) (1 children)

[This comment has been deleted by an automated system]

[–] farcaller@fstab.sh 2 points 1 year ago (1 children)

I wouldn't quite call Lemmy's protocol much friendly either. I'm trying to implement it and it's a bit of a mess, honestly. There's absolutely no documentation, private database specifics leaking into the public interfaces, and an absolutely horrendous authentication scheme.

[–] skullgiver@popplesburger.hilciferous.nl 3 points 1 year ago* (last edited 9 months ago)

[This comment has been deleted by an automated system]