Today we released Mbin v1.8.0! It has been already 1 month since we released v1.7.4.

This is the v1.8.0 release of Mbin and it is a feature packed one like always ;).

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.

You also still might want to double check if you are using the latest Nginx configs (v1.8.0 has now additional regex improvements).

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.

Melroy

EDIT: There is a more detailed post here.

  • melroy@kbin.melroy.orgOPM
    3·
    5 days ago

    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.
    • Reason of the attack: Unknown
    • TheObviousSolution@kbin.melroy.org
      1·
      5 days ago

      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.