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 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.

Soon I will try to craft a post about whom exactly we owe these changes to. Today there's already too much excitement for one evening ;)

spoiler: https://codeberg.org/Kbin/kbin-core/activity

For the next few hours, the website may be slow. We are working on a fix.

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.

Wow ;) I'm incredibly lucky to have come across people like you. The authors of those posts are actually right - managing /kbin is a significant challenge nowadays. It requires extensive knowledge and experience to keep it under control. But also I've never hidden that fact - the information about it is placed at the very top of the repository's readme ;) However, as I mentioned, a lot is changing very quickly https://kbin.social/.... And we're all working hard on it, to improve and automate as many things as possible. Thanks to all of you, I believe I can face it head-on, and together we can create a better place. Better internet. Not just this instance, but cooperation between platforms is the key here.

Unfortunately, there are delays occurring again - I've decided that smooth website operation will be the priority this time. There are approximately 450k tasks waiting in the queue, and everything will be handled, but it will take some time. Today, we're also conducting final tests of the new infrastructure. It's taking a while because we're documenting templates that can later be used by others to create their own instances. I hope these are the last issues we have to endure ;)

Thanks for everything.

Yeah, the pace is still crazy, but it's a completely different mental comfort when you're aware that you're not alone ;)

Ok, so in the next few days, I'll be testing some things. It might be a bit worse for a while, but it will definitely speed up the problem-solving process. I'll be grateful for any feedback. I'm unable to reproduce it in local/testing environments, so it might be an issue with the cluster.

Thanks, once I deal with the formalities that need to be taken care of first, I feel like next week will bring a downpour of improvements in the release, thanks to the contributors.

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

Top sorting is already available on the testnet. It will be further improved over time.
https://lab2.kbin.pub/

Thanks for that, it's true, I need to remember especially about that last point. Later, I will write a few words about what was happening behind the scenes during these days. I wasn't there alone. Not anymore ;)

kbin is much older; it was a side project. Recently, I took it more seriously :)

I don't know yet. I can't wait to start getting to know all of them ;)

I apologize for causing you trouble. I'm trying to resolve the situation as quickly as possible, but apart from the usual spammers, there have also been organized campaigns where, for an hour on Sunday mornings, our instance was flooded with spam from hundreds of accounts. This, of course, is causing federation issues. I've changed my priorities regarding the roadmap, and additional tools will be released soon. I will also ensure additional moderation. I will also get in touch with admins from other instances - my absence was due to personal issues I mentioned recently. Thanks for your understanding, and best regards.

Now I really have to get back to my tasks, as I still have a lot to do today. But tomorrow morning, I will answer your questions. Cheers!

Hey, a month ago I would have simply pressde the button and not thought too much about it. Now the situation looks completely different. I have bookmarked all the discussions I came across, and next week I will read every single post to have a complete picture. I owe you that.

However, we need to think about additional privacy features, as priorities have drastically changed in recent weeks, and I will have to carefully consider that. Now that I have dealt with infrastructure issues, I will focus on the most important matters.

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.

How can I turn it on?

It seems to me that there are several factors. Firstly, the instance was created recently, about 1-2 months ago. There wasn't even an official instance opening, you know, with cake and confetti ;) During this time, I've been observing people on the Fediverse. It's unlikely that any follows were given by chance. Later on, wonderful people who discovered kbin did the rest. That's how it is in the Fediverse. In the beginning, not everything is easy and obvious, but if you put enough heart and effort into it, it pays off in the future.

I receive support from the people here, and I also want to clearly communicate and report expenses. I feel a sense of responsibility. Many magazines have been abandoned, and that also needs to be addressed.

Thank you for the work you've put in, guys. Life can really knock you off your feet sometimes, and I'm pretty sure Hariette has a good reason to be offline now. II really hope everything works out for her and one day she'll be able to come back.

As for myself, at the beginning of the year, I plan to dust off the drawer and return to my mobile client that I started some time ago, and develop it in my free time. If someone likes /kbin feeling, I'm pretty sure they'll also enjoy this app ;)