Lemmy and kbin communicate using activity hub protocol, that doesn't mean they communicate with app using the same protocol (AKA API).
So it is not necessarily trivial to let a Lemmy app support kbin.
Exactly this, they don't use the same API. It would be a pretty big effort to get Kbin working on Jerboa, it's likely that mobile apps specific to that will pop up soonish.
API support in KBin is currently on the roadmap but disabled (for now). Hopefully once there's a working API for KBin, an app will materialize. I have my suspicions that there still won't be interop (you can use a Lemmy app for KBin or a KBin app for Lemmy) for a long time, but I definitely think it will make KBin instances a more attractive link aggregation community solution
I don't understand; I can access Kbin magazines from Jerboa. What am I missing?
The discussion is about API access to KBin from an app, which is totally different from federation between instances and services.
Because KBin had more features than just what's available with federation because it's a separate codebase than Lemmy. I'm starting to get it now, thanks for the help!
Lemmy and kbin communicate using activity hub protocol, that doesn't mean they communicate with app using the same protocol (AKA API).
So it is not necessarily trivial to let a Lemmy app support kbin.
Exactly this, they don't use the same API. It would be a pretty big effort to get Kbin working on Jerboa, it's likely that mobile apps specific to that will pop up soonish.
API support in KBin is currently on the roadmap but disabled (for now). Hopefully once there's a working API for KBin, an app will materialize. I have my suspicions that there still won't be interop (you can use a Lemmy app for KBin or a KBin app for Lemmy) for a long time, but I definitely think it will make KBin instances a more attractive link aggregation community solution
I don't understand; I can access Kbin magazines from Jerboa. What am I missing?
The discussion is about API access to KBin from an app, which is totally different from federation between instances and services.
Because KBin had more features than just what's available with federation because it's a separate codebase than Lemmy. I'm starting to get it now, thanks for the help!