• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


  • I always love seeing “quirky” innovations

    I say quirky as in “there’s already an established way of doing it that everyone is using, but I’m gonna build my own totally different thing”, similar to how Linus created Git because the established way was not good enough for his taste. Who knows, graph-based UIs for chats might be the next big thing !

    Sadly, the network effect makes it hard to have people adopt a new messenger (I can’t even get relatives to move to Signal…). I wish Matrix wasn’t such a pain to make clients for. If your graph UI was able to show me all my conversations across all my matrix rooms and bridges, I’d be using it for sure





  • Debian is already noiriously lagging behind latest package versions (that’s how they make it so stable : they freeze all package versions when they release a new version of Debian, and only backport security fixes).

    Either your AI was trained before Debian 13 came out, or it is giving you really bad advice. I can’t think of a single good reason to use an older Debian for a fresh install…



  • I’ve been in a similar situation, and I’m also blocking large ranges of IP addresses in addition to running Anubis in front of my most scraped services (Git/forgejo and Lemmy)

    I came up with a hacky python script that watches my fail2ban logs, counts bans for IP ranges going from /28 to /8, applies some heuristics (based on range size n and how offending IPs are split between the 2 /(n+1) subranges) I came up with to detect ranges that should be blocked, the issues a log line that is picked up by fail2ban to manage bans of increasing length on récidive.

    It’s quite contrived and I often fear it will be too agressive and block something I rely on, but it has been working really wellin my experience.

    It will initially block a lot of small ranges, but over time the ranges will grow larger. Smaller ranges having a lower threshold helps it block only the narrowest ranges needed, which gives some time for larger ranges that contain them to drop out of fail2ban’s watchlist.

    I should clean up this mess and make it a git repo, maybe even try to have it merged in fail2ban