Yeah, the pace is still crazy, but it's a completely different mental comfort when you're aware that you're not alone ;)
I appreciate the concern, and it seems to me that kbin is no longer just one person ;) Currently, kbin is a team of wonderful people who handle development work, devops, project management, and more. Additionally, Piotr helps me with administering kbin.social. There will be significant changes here soon, things are happening quickly. But to be honest, I wasn't fully prepared for such substantial growth, and it will probably take some time before everything stabilizes. But... this is just the beginning ;) What's important is that the snowball starts rolling, regardless of whether kbin, Lemmy, or Mastodon gains the most users. We all win in this situation.
Top sorting is already available on the testnet. It will be further improved over time.
https://lab2.kbin.pub/
Sorry for that, but not all content is marked as +18. Tomorrow, I will limit the display to posts from this instance.
It's possible that this is a consequence of the latest Lemmy update, in which a lot has changed. I have noted that kbin has some issues with request signature in communication with certain instances. I will try to check it tomorrow first thing in the morning.
In such important tasks, I would like to engage in community-driven development. When I start planning these tasks, I will come to you with my whiteboard and sketch out the individual stages. Together, we will look for the advantages and disadvantages of such a solution, the weak and strong points. This is to jointly make a decision on whether the change makes sense on kbin.social but also in the perspective of the entire federation. It can be a great fun ;)
All the things you mentioned are in the roadmap. However, we can either do it quickly and potentially encounter issues in a few weeks or months, or take a bit more time for a more thorough approach. I've decided to move away from playful prototyping. From now on, every change will be tested before it's approved for kbin.social - it's no longer just my code (https://lab2.kbin.pub/). I'd like to close this thread for you... but can we just agree not to respond in it anymore? ;p
I just need a little more time. There will likely be a technical break announced tomorrow or the day after tomorrow. Along with the migration to new servers, we will be introducing new moderation tools that I am currently working on and testing (I had it planned for a bit later in my roadmap). Then, I will address your reports and handle them very seriously. I try my best to delete sensitive content, but with the current workload and ongoing relocation, it takes a lot of time. I am being extra cautious now. The regulations are quite general, and I would like to refine them together with you and do everything properly. For now, please make use of the option to block the magazine/author.
I'll try to take care of it today and potentially clean up the activity. For now, I've limited the traffic from that instance. I'm currently working on additional tools for moderators.
@blazera Hey, can you show me an example? I'll try to verify it.
How can I turn it on?
When I played with kbin, Yunohost was a gamechanger.
I think it's necessary to monitor the situation and how they will handle moderation, but for now, I would prefer to do it from a distance from kbin. There is currently a significant issue with moderation, and disturbing content can remain up for too long. I'm working on improving this issue as well.
@LollerCorleone thanks for that.
It should be fixed. If you could note it down and let me know, please :)
mobile / desktop?
It seems to me that she did it very gently ;)
I will definitely check it out! Thanks