@pariscope Stick with kbin. It's more versatile because of its microblogging capabilities. And it definitely looks a shit ton better. And will eventually have a stronger developer community supporting it.
this post was submitted on 19 Jun 2023
3 points (100.0% liked)
Fediverse
8 readers
2 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 2 years ago
I tried both, and I prefer the look of kbin, but ultimately I went with Lemmy because I couldn't get kbin federation working. It's only a matter of time until kbins improves, when I first tried Lemmy it was really tough to install from source on bare metal so I went with lotide instead. Unfortunately, Lemmy's federation broke with lotide and kbin doesn't federate at all yet so I needed something in a hurry that works.
Another thing that could affect my choice would be the back-end. With the backend of kbin being php and the backend of Lemmy being rust, I expect that if you're hardware constrained federation could be more responsive on Lemmy. I experienced something similar when I moved from friendica (pure php) to pleroma (Erlang).
If it's not a question of setting up an instance, I'd prefer kbin, and later on I might set up an instance once it's had some time to mature.