It brings an extensive bookmarking system, signup request support, signup notifications, extended markdown rendering, custom notification settings to set magazines, users, threads and microblogs to default, loud or muted, setting a default sort for the front page and comment lists, a new image delete command for admins and documentation changes.
I want to thank all the contributors! We can't do it without you all!
Mbin takes a lot of time to develop, maintain and improve. Created as a successor of /kbin, but still going strong ever since. If you would like to support this work or cover the server costs, please consider donating. Thank you.
do you have any idea how/why this is happening? maybe they're using some broken client?
i also noticed that my first comment in this thread has (so far at least) not appeared in fedia.io's view of it; maybe it won't make it to your mbin instance either?
so, i am posting this comment in a reply to a comment from your mastodon account instead, in hopes that it might reach you there.
Correct, I did enable this login option for now, to reduce the impact on application level. Sorry about that.
The attack has been ongoing from Feb 8 2025, until today still. It comes in waves, I dunno who is attacking me or why. I use my firewall to block some of the origin countries where the attacks are coming from. However, the Botnet is located in basically very country on the planet. I migrated to OpenResty and will implement additional anti-DDos measures as well as optimizing Mbin further to reduce CPU overhead.
TLDR;
Attack started at Feb 8 2025, and still continues
Attacker is using a botnet from across the globe
Attacker is using valid GET requests with legit user-agent strings
Attacker is using both mobile and fixed line ISP types, so these are devices behind various ISPs across the globe. No cloud infrastructure is used.
Thanks for the detailed answer. I imagined it was due to something like that. Sounds like a "homebuilt" DDOS platform if its coming from any compromised device, so it could be any number of BS reasons, just simply testing out their botnet, or stressing the server to probe for specific vulnerabilities.
I think I exactly set showAvatar on true within the comment section or something? My bad, I will try to solve this asap again. Obviously this is not wanted :)
Unfortunately your software came to my attention because I observed what I think might be a bug in it: 100% of the posts by https://lemmy.ml/u/badwetter@kbin.melroy.org have broken links (at least over here on the lemmy side).
Interestingly I see that the links in this post i'm commenting on (which was made a week ago) are not broken, and I also see that one of that other user's posts (also with a broken link) is from 3 months ago, so, apparently this is not happening to everyone all the time - but somehow that user at least is having an ongoing problem.
Btw, it is also unfortunate that the permalink (accessible from lemmy's view with the fediverse icon) for each post and comment from your mbin instance takes me to a login page, so I would need to make an account there to see if their links are also broken on the mbin side.
The settings are (from left to right): muted, default and loud.
Default respects your global notification settings, while the other two modify it. They are processed hierarchically, meaning a muted user commenting on a loud thread which belongs to a muted magazine will not trigger a notification, while a loud or default user would. Another example: a muted thread in a loud magazine will not trigger a notification for new comments unless the commenting user is set to loud.