I'm currently working on solving this problem.
Issues like the one that occurred are typically resolved within an hour, hence this post - mainly to quickly inform that work is underway on it. But you're right, I'll strive to improve communication in the future. Your examples gave me something to think about, thanks.
I don't quite understand what you mean. The problem is that in such a case, it's challenging to provide a specific estimate. That's why I occasionally provide updates in case the work is prolonged. It seems to me that this is how it works. Issues arose without any interference in the code or infrastructure. I addressed hardware problems, but it turned out that wasn't the only issue. Throughout this entire period, I've been attempting to ensure that the instance operates as smoothly as possible. It should be significantly better now, but I'm still actively working on it. Unfortunately, taking a holiday break here doesn't help either.
Yeah, It's true. Since Sunday, I've been noting errors that I'm still working on resolving. It doesn't make it easier that it's the post-holiday period, and due to travels and security measures, it's not the easiest task. I'm working to get everything back to normal as soon as possible.
https://kbin.social/m/kbinDevlog/t/729349/RTR-49-On-site-work
By default, it's 11MB if I remember correctly. However, during the recent issues with the instance, we could modify this value at the server level. Once Piotr is back, I'll verify and restore the default values.
Additionally, the suspension of other work was a conscious decision on my part. I believe that the code at this stage needs to be deeply refactored, and that's exactly what I am doing. Solid foundations are the only option for the project to survive and grow in the long term, and to be properly scalable. Adding more blocks to what I have always considered a prototype (which forks do) makes no sense to me.
Hey, I will get back to this thread and the comments at the beginning of next week. I am able to quickly address some of the issues you mentioned in your post. Changes will undoubtedly be implemented gradually, but for now, the redesign of the ActivityPub module takes higher priority. Once that is completed, the development of the frontend part of the platfrom will truly pick up pace.
@Damaskox Could you send me the URL from the notification via private message, please?
@Damaskox Pagination? I plan to fix that in the coming days.
My priority is definitely the development of kbin-core, especially now that work on the app has started. For now, I prefer to focus my attention on adapting the API to the latest features. It may turn out to be necessary sooner than expected ;)
@testing Can you repeat your tests regarding tags between kbin and other instances? It should be significantly better ;)
@testing Thanks for the summary. I will check those cases.
(https://kbin.social/u/testing) Can you repeat your tests regarding tags between kbin and other instances? It should be significantly better ;)
@ernest I'm trying to reply to a federated toot and the add comment button changes to "sending" for a while then comes back without posting anything.
@bluGill it should be okay now
@ernest I'm trying to reply to a federated toot and the add comment button changes to "sending" for a while then comes back without posting anything.
@bluGill I will check what's happening, there seems to be some issue.
You can find it in the options in the sidebar.
Hey, I still have one blocker before publishing the API on kbin.social related to infrastructure. The issue is dragging a bit, but by the end of today, I'll try to launch the API on my second instance so that you can familiarize yourself with the structure, docs, and I can make any necessary corrections as quickly as possible. Thanks!
