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.
@Mnmalst Yeah, I am well aware of what you're talking about, and I am trying to maintain a balance. I knew that it could look like this at a certain stage, but I didn't expect it to happen so quickly ;) I assumed I would have a bit more time to prepare and acquire knowledge. Now I have to improvise. I make mistakes, but I try to fix them and always keep an eye on the big picture. That's all I can do. Working with pull requests is great, I enjoy learning new things from others, and it's also fun to discover bugs together. At least for now. ;-) But I always emphasize that my priorities are my milestones, which keep me afloat, so I care about organizing our collaboration as quickly and effectively as possible. However, we also need to get to know each other a little better.
You are writing from your instance, so it's @ernest@kbin.social. In the future, there will probably be some sort of suggestion when mentioning people, similar to Mastodon.
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.
Hey, I think there's a lot of truth in that. I don't want to force anyone to stay here ;) I believe that kbin can be a stepping stone to a wider fediverse, which is great. However, I'm trying to keep the entry barrier as low as possible so that everyone can find their place here. The rest will come with time. Currently, we're working with contributors to make setting up and maintaining your own instance less of a nightmare, and it should change for the better soon.
Sorry for that, but not all content is marked as +18. Tomorrow, I will limit the display to posts from this instance.