![](https://media.kbin.social/media/83/99/839930ebc974914aaa2380dde7099c15fa6af3a1b01cc75057a1961f6e3b0588.png)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
Actually a lot is changing in /kbin, and this recent period has brought the most changes in months. Slowly we are coming back to life, and this time I will be better prepared.
Working on /kbin
https://fedidb.org/software/kbin
Actually a lot is changing in /kbin, and this recent period has brought the most changes in months. Slowly we are coming back to life, and this time I will be better prepared.
That’s true, it is visible. But this information is public, and anyone who has their own instance also has access to it. The interface is consistent with Mastodon and other platforms where you can view likes and boosts. There are several ways to improve this - completely hide this information in the threads section, hide the activity of users from remote instances, or exclude Lemmy’s instances from the activity… but still… It’s just covering up one’s eyes.
When I played with kbin, Yunohost was a gamechanger.
In the latest thing with Reddit’s /kbin, it was still in the early prototype phase (and remains so to this day). Prior to this, practically only I and a few friends were using it. It wasn’t ready to handle the sudden creation of dozens of instances or accommodate thousands of users. Additionally, real-world issues emerged that demanded my immediate attention. I made the decision to take a step back instead of getting caught up in a race, opting to build solid foundations, which is exactly what I’m doing now. In my opinion, this will be better for the project and potential contributors, ensuring that their work will be utilized to the best possible extent.