6
These points are not a priority, but relatively easy to achieve. They will gradually appear on the instance in between working on significant things. It's worth following https://kbin.social/m/kbinDevlog
The aggregate view is in preparation still.
12
Hi @maegul , I just wanted to let you know. It's not perfect yet, but it's something I'll be working on in the coming months after the first release. Thanks for pointing
(media.kbin.social)
Hi @maegul, I just wanted to let you know. It's not perfect yet, but it's something I'll be working on in the coming months after the first release. Thanks for pointing it out, it's a relatively simple change, but it makes a significant difference in the overall experience.
https://kbin.social/sub/active
https://kbin.social/sub/microblog/active
https://kbin.social/sub/comments/active
This feature stopped working for some reason during the development of these software. In the coming weeks, I'll be working intensively to improve communication in the fediverse, including moderation.
Yep, another way is to choose abandoned from the list of magazines, soon it will be more sensibly sorted ;)
96
kbin.social update
(media.kbin.social)
The instance has been updated to the latest version of the code. For the next few hours, there might be issues with communication in the fediverse. We are working on it, and everything should return to normal shortly. I'll keep you updated.
https://kbin.social/m/kbinDevlog/t/613299/kbin-RTR-8-The-update-of-kbin-social-and-plans-for-the
It wasn't entirely intentional, it was actually my mistake. But I held off on pushing the hotfix for a while. It was a development branch, so these kinds of bugs were permissible - in this case, it just changed the order of related posts, nothing serious. It was quite easy to spot and fix. Slow and cautious acceptance of pull requests, something I spent a lot of time on, was the main accusation from the creators of forks. Hastily accepting them was a problem for me. I personally considered a consensus similar to that, but now I see it doesn't make sense. Someone needs to take responsibility. Personally, I believe that forks are the best thing that could have happened to the project.
2
/kbin RTR#5 Transfer request for ownership of abandoned magazines
(media.kbin.social)
This update introduces the ability to request the takeover of abandoned magazines. The karab.in instance has been updated to the latest version of the code, which prepares for the kbin.social update after some tests.
- list of abandoned magazines (owner hasn't logged in for a month)
- the ability to submit a request for taking ownership of a warehouse @todo
- section in the administrator panel where one can reject or confirm the takeover of a magazine @todo
Time remaining for the kbin.social update: ? days.
This week, I've been dealing with cleaning up instances from spam. Several hundred accounts were removed, along with several thousand posts - these were massive operations. It's possible that due to the volume of requests, other federated instances hit rate limits. I see that some of them are still in the queue with a "fail" status. I will gradually resend them after some time. Along with the update of kbin.social and the first release of kbin, new modeartion options will be available, including spam blocking (such as global blocking domains), a new reporting panel for moderators, and improved federation between instances. I will also address abandoned instances and ensure that each one has at least a few active moderators. I know how urgent this issue is, and it's my top priority. I just need a bit more time as Piotr and I are preparing for the update.
Hi there, I'm currently working on solving the problem. There will be significant changes this month. I know it's taking longer than I initially announced, but this will be a really solid release. The contributors have made an incredible work and I didn't want to miss anything.
https://kbin.social/m/kbinMeta/t/381108/Lots-of-new-spam#entry-comment-2209332
It took me from 4 to 6 minutes, I can't determine exactly. I think this is about more than just copying and committing a file - one needs to label specific files or sections of the code. I'm not sure how exactly this should look, so I'm waiting for a consultation.
Currently, all I need is a bit more time ;) I'm gradually granting additional permissions and sharing responsibility with contributors. We still need to establish a some policy. If it speeds up work on /kbin, I'm okay with that. They are great and experienced developers. However, it's important to remember that they all do this in their free time.
@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.
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?
ernest
joined 2 years ago
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.