@EnglishMobster This week, I will take a closer look at the topic, and additional options for the blocklist may be required. To be honest, I cannot guarantee that it will happen right away, but the improvements will definitely be gradually introduced. The priority, however, remains the stable functioning of the website and data security due to the significant changes prepared by contributors. I don't want to do anything faster than necessary, but I realize how important what you're writing about is.
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.
At the moment, I am the only admin on kbin.social - mainly because /kbin doesn't have a tested global administration by multiple admins/mods ;) It's something I'm currently working on. Sometimes, there are so many notifications and messages that responding would physically take up entire days. I can't reply to everything immediately, but I try to do it systematically. However, the best way to get in touch is through Matrix spaces. I feel that every problem will be properly addressed there, which is why I can allow myself to work calmly besides managing all of this ;) Another more reliable method is a contact form.
Hey, on Monday, the system for transferring magazines and submissions to moderators will be ready. I am currently working on it, which is why I need a moment of focus and isolation ;)
I'm still working on it because it doesn't happen to everyone, which is why it's not that simple. Before the release, the problem should already be resolved, so please have a little more patience :)
Currently, kbin has no delays in the queues. This may be due to not all streams being sent to us or an error in the federation. Over the next few weeks, this process will be improved.
The federation between the Mastodon instances I am using for testing is either immediate or takes a maximum of a few seconds. However, other instances may experience their own delays.
Hey, next week. There is still the matter of changing one js library, and we need to determine the minimum percentage of progress at which translations should be released.
Today, the clearing of some sessions was intentional. But I have heard about it before. Are you sure that you logged in with the "Remember me" option checked?
Hey, yep we are actively working on it. Some errors are difficult to reproduce and only become apparent on a larger scale. After the first release, it should be significantly better.
Yeah, absolutely. Choosing an instance is a mature decision that I hope many people will make. It would mean that the /kbin ecosystem is strong enough to handle it. However, for now, I would suggest sticking to larger instances that have been around for a while or those where the administrators are active on Matrix - like @melroy - they know /kbin best. In those cases, everyone can also get quick help from me by reaching out privately for a sufficient period of time ;)
Actually, I have a plan to improve the federation, but at this scale, I need to be super cautious. Just one mistake is enough to harm other instances. That's why I want to prioritize setting up robust testing environments first, so that the every changes in this regard are thoroughly checked and validated.
@EnglishMobster This week, I will take a closer look at the topic, and additional options for the blocklist may be required. To be honest, I cannot guarantee that it will happen right away, but the improvements will definitely be gradually introduced. The priority, however, remains the stable functioning of the website and data security due to the significant changes prepared by contributors. I don't want to do anything faster than necessary, but I realize how important what you're writing about is.