Show newer

While some of the addresses have timed out of the ban list, that peaked just shy of 3000.

I've had a few ideas about different approaches to a live logging mode that I might add to the program later to make things a bit more convenient, but as things are now it's far from the worst option out there.

Show thread

New article up on CRUCS about my experience using this at CRG Retreat. While I didn't have this use case in mind at all while developing the software, CRUCS makes a pretty decent manual logging app if you don't have your machine set up to log data automatically (or if you're using someone else's roaster and don't have a good way to exfiltrate your own data).

crucs.net/articles/using_crucs

Definitely made the right call skewing my pulls light on the new Tanzanian coffee. It's inoffensive as a medium roast, kind of funky in a bad way as a dark roast, but there's a nice broad range of light roasts that were quite good. It'll probably end up being the lightest thing on my shelf at least for a little while.

Yesterday's production test batches turned out nicely. I'm reserving the coffee to use to sort out blend recipes, but hopefully those coffees can hit the shelf tomorrow. Still have another 36 cups to taste before deciding on how I want to roast the new decaf arrivals.

Ban list is up to 2376. The overly aggressive bots are still showing up with new addresses, but the rate those are getting through is a lot slower now, almost approaching what would have been reasonable behavior that wouldn't have prompted me to make a filter to ban them on sight.

Almost (but not quite) all of those are IPv4 addresses, so if we really needed to claw back some allocations to get more productive use of the space, these would be a good start IMO.

Roasted product development batches of new coffee arrivals. I now have 63 distinct cups of coffee to taste and evaluate.

Any bets on how high the ban count will get by the end of the day?

Still have no idea why TikTok would care about my little Gitea server at all, but if anybody there is upset that I'm banning their bot, just check out the repos like a normal person.

As of morning, bot traffic is massively reduced with 1517 IP addresses blocked. There's still a very slow trickle getting insta-banned, but it looks like I don't have to add anything else to the filter for now.

>400 blocked. The bots have to run out of addresses eventually, right?

Repos have been put back public for humans (or better behaved bots). Banned IPs are now up to 218.

Well, I gave the bots every chance to not be raging asshats but now I've dropped the ban hammer on 148 IP addresses and counting. Bot wants to crawl my server? Sure, don't care. Bot wants to do that so aggressively I got alarm bells ringing from the huge surge in traffic? Well now you get nothing.

Temporarily setting all repos on code.typica.us to private since I don't have time right now to sort out a better block to the current bot attack. If a human needs something from there, let me know.

Show older
Typica Social

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!