The official lemmy community for Voyager, an open source, mobile-first client for lemmy.
๐
Hello,
I have seen mentioned in some comments that this app has kbin support. Is that true?
I can see kbin posts through federation. But I am not able to add a kbin instance through the app or log into one.
I would love to see that happening!
Thank you!
Regards,
I don't see anywhere on the Voyager readme that is supports kbin instances. kbin and Lemmy are two different backbends that have similar looking front ends. The federation between them is through activitypub, which is why you can see content from kbin instances. I think you would need an app designed for working with kbin directly.
Yeah I didn't see it on the readme either but on forums posts promoting the application (not from developers that I know of). I suppose that misled me.
I am aware they are two different backend but still, I am pretty sure it's possible. Maybe not easy, but I bet it would be possible. For instance, take a look at fedilab. You can see, and interact with mastodon, lemmy, pleroma, friendica and even peertube.
Yeah it's definitely possible but it means you're supporting multiple APIs and the main dev(s?) for Voyager may not want to take on the extra responsibility. You could always PR it in though :)
I assume that if you created a Lemmy account and subscribed to all the kbin communities (magazines?) you were interested in that would mostly cover you? I think the federation works?
Does Kbin have any other functionality there that wouldn't work?
if only kbin could keep itself up without bugging out after every few clicks.
If kbin releases API docs, a JS client on npm, and then dogfoods it like Lemmy does, Iโd be happy to look into it. :)
(But even then, API differences would make this very hard to do well and probably not worth the effort.)
The reason Lemmy has such a great app ecosystem is the backend and front end are completely separate, with a published client layer for communication.
Mbin too please
No app is working with kbin.social yet, because the instance has not opened its API yet. Check /kbin compatibility against https://kbin.earth or any Mbin instance
