I apologize, I need to make a change on the website and communicate it more clearly. Currently, the kbin API is disabled. I am considering the option of integrating with one of the existing APIs, but I need your opinion. Perhaps this is a good time and place to start a discussion :)
As a user, I see value in ensuring your API at the very least is “compatible with” Lemmy’s, as long as doing so doesn’t impact compatibility with other projects. Primarily because I see at least the Thread element of Kbin as very similar to the Lemmy experience, and I think it’d be healthy for the entire fediverse if efforts to make a tool/client for one of them could be easily retooled with minimal work or work as-is with the other.
I do worry this would prevent the Kbin project from having as much agency over how interactions are implemented and any future plans to expand the featureset, but as a non-developer I’m not sure how valid those concerns are when discussing building a compatible API.
Thank you for all the work and effort you’re putting in!
Add comment