On desktop kbin is 5x better than vanilla lemmy.
But on mobile I have several FLOSS lemmy clients. They all have their pros n cons. Their development is spread out with different projects. Work and the responsibility are distributed from the main lemmy maintainers.
The kbin webapp is pretty good, but not as good as a native client. There is of course only one.
My feeling is that designing for clients (having an API) imposes some kind of discipline on projects. Like you can’t just do whatever willy nilly.
My other feeling is that kbin is setting up to be like iCloud whereas lemmy is more akin to sftp.
Thoughts?
There are mobile apps in development and the API is coming along.
Kbin is still just a prototype though, but it’s moving along nicely.My other feeling is that kbin is setting up to be like iCloud whereas lemmy is more akin to sftp.
I’ve no idea what that analogy even is, but I think the differences are mostly technical (PHP vs Rust) and UX.
Both implement AP a bit differently, but at the end of the day, they’re still AP aggregators.
And that’s ignoring the political issues around lemmy’s codebase ofc.Are you talking about the dev?
There are a lot of technical (PHP vs. Rust) and user experience (UX) differences, but I don’t understand the comparison. They may have various approaches to AP implementation, but ultimately, they are both AP aggregators. Of course, that doesn’t take into account the political concerns surrounding Lemmy’s codebase. mini crossword
