They use the same protocol, but so far both of them have only implemented the server-to-server (federation) portion. Neither (to my knowledge) have implemented the client to server interactions.
Lemmy has its own API, which is completely separate from the ActivityPub spec. Kbin doesn’t have an API yet, but one is actively being developed.
I understand there might be a need to develop different server to client APIs if the services that implement activity pub are very different (lemmy / mastodon). But lemmy and kbin are basically the same shit in different colours.This would be a good case to use / reuse / develop a standard API for server-client communications, I would think so.
It’s entirely up to the developers to collaborate and implement according to the spec though. ActivityPub wasn’t really designed with this use-case in mind, so the spec has limitations that warrant a specialized API, or extensions to the AP spec.
For example, the outbox is an OrderedCollection. This is how you would list posts in a magazine/community. However, there’s no way to sort by other metrics such as hot, top, or trending. Even Mastodon has its own REST API.
Please, someone with more knowledge, enlighten me please:
If kbin and lemmy both use the same protocol “activity pub”, why can’t an app designed for lemmy not easily communicate with a kbin server?
They use the same protocol, but so far both of them have only implemented the server-to-server (federation) portion. Neither (to my knowledge) have implemented the client to server interactions.
Lemmy has its own API, which is completely separate from the ActivityPub spec. Kbin doesn’t have an API yet, but one is actively being developed.
I understand there might be a need to develop different server to client APIs if the services that implement activity pub are very different (lemmy / mastodon). But lemmy and kbin are basically the same shit in different colours.This would be a good case to use / reuse / develop a standard API for server-client communications, I would think so.
I agree, standardization would be good.
It’s entirely up to the developers to collaborate and implement according to the spec though. ActivityPub wasn’t really designed with this use-case in mind, so the spec has limitations that warrant a specialized API, or extensions to the AP spec.
For example, the outbox is an OrderedCollection. This is how you would list posts in a magazine/community. However, there’s no way to sort by other metrics such as hot, top, or trending. Even Mastodon has its own REST API.