I encourage people to follow this site and The New Leaf Journal via feed. But while I welcome feed readers, I do not welcome bots and scrapers that fetch my feeds for the purpose of effectively re-publishing my articles without permission, especially for profit. I wrote about blocking one such manevolent crawler, RSS Amplifier’s rssamplifier.com reader, in a NLJ essay. I just added another one to my block list. RSSing sounds like a charming feed reader, but I found that it was scraping my NLJ feeds and re-producing “content” from my full-text feeds on its ad-supported website. I added it to my .htaccess and robot.txt block lists, where it joins RSS Amplifier. See my Codeberg commit for the .htaccess side of things and my entire lists on Codeberg and GitHub.

I discovered two new bots in my server logs last week: RSSAmplifierBot and BriskBot. They come from RSS Amplifier and Brisk News respectively. Bot sites are built by Profullstack, Inc. I discovered that RSS Amplifier, unbeknownst to me, had been crawling New Leaf Journal’s ATOM feed and re-publishing (albeit they would not describe it as such) the entire contents of my article under the RSS Amplifier banner (note it appears it took entire articles because I offer full-text feeds; it had truncated entries for sites that do not offer full text feeds). While the articles are attributed with links back to my original source, I do not approve of wholesale re-publishing (as should have been clear from my About Page). Worse yet, RSS Amplifier describes its purpose in part as making articles from around the web readily available for AI crawlers (live About Page) and they sell access to their data (live Training Data page). Brisk News appears to host articles from around the web with AI summaries, but there is less information about the project on site.

I present this information for the consideration of my fellow webmasters. I took it upon myself to block both RSS Amplifier and Brisk News at the server level and have a pending take-down request with RSS Amplifier. Alternatively, a webmaster who wants to be part of the collection may want to test whether the team responds to requests about data handling (RSS Amplifier does insist you can make a request to be in the directory but not have your site’s data sold, but I have my doubts on how that would work in practice). In any event, for those who are interested in learning more:

This site is hosted on the same server as The New Leaf Journal, and I use Cloudron to manage the server. Beginning around early spring last year, The New Leaf Journal began to crash once every few days when Cloudron health checks failed (I have not had any similar issues with this site, which is much lower traffic). I attributed the problems to bot traffic, and I think I was correct to do so. I tried many fixes, some of which worked for a time before the downtime problems returned. After having a few too many incidents in January, I bit the bullet and moved up a tier on our Hetzner VPS server (I had been on the higher resource tier prior from February 2022 through May 2023 before downgrading to a smaller VPS to save a small amount money, initially without any problems). I thought all was well until NLJ crashed again for three hours yesterday morning. I am not inclined to go up another tier, so I decided to see if I could find a more durable solution that did not involve changing how I run NLJ (I do not have time to sit down and work on that now) or spending more money (I would rather eat the occasional downtime at a point). I poked around and noticed that Cloudron has a built-in firewall separate from app-level settings (I use Jeff Starr’s 8G Firewall in the .htaccess files for both this site and NLJ for app-level protection). I figured that preventing the bots from hitting NLJ at all may reduce strain on the site, which was pushing my server’s CPU limits far more often than I would like. I found an up-to-date list of bad IPs from AbuseIPD maintained in a GitHub repository and dumped them into my Cloudron firewall (I noted that all of the recent malicious bots that had hit NLJ that day were included on the list). Did it have an effect? I present the following chart showing CPU and RAM usage for NLJ over the previous seven days.

Screenshot from Cloudron UI showing 7-day CPU and RAM usage for The New Leaf Journal from about noon on 01/23/26 through the same time on 01/30/26. There is a noticeable huge dropoff on the CPU and RAM charts beginning in the middle of 01/29/26.

What do you think? Thoughts? As an aside, I will note that Koko Analytics, the free and open source local page visit counting solution I use here and on NLJ, shows no noticeable drop in legitimate visitor traffic since I started using Cloudron’s firewall yesterday. I am crossing my fingers that keeping the Cloudron firewall up to date will resolve the NLJ issues I have been having.

The New Leaf Journal became inaccessable for about 1-2 minutes this morning. Fortunately, I opened the site almost immediately when it happened. I opened my server logs and found what was probably the offending bot/scraper so I could block it. I kept the server logs open to watch for any other questionable activity. I saw an interesting user-agent string.

Aug 22 11:22:46 [IP ADDRESS] - - [22/Aug/2025:15:22:46 +0000] "GET / HTTP/1.1" 200 63425 "-" "GodHatesMastodon"

My two sites are often crawled by Mastodon servers and Fediverse-related crawlers because both sites function as ActivityPub servers (you can follow this account on the Fediverse at @naferrell@social.emcafe.org). I had not previously seen the crawler GodHatesMastodon, but I understand through the grapevine that there are some questionable instances out there. Fortunately, there is no reason for anyone to hate The New Leaf Journal. As my friend and colleague Victor V. Gurbo once explained, “The New Leaf Journal is a family website.”

Filed an Issue Koko Analytics Recording SBInstitutionsBot/0.1 Requests as Visitors/Page Visits · Issue #296 · ibericode/koko-analytics by nafnlj (GitHub)
My Set-Up I run the non-pro version of Koko Analytics on my WordPress site. I disable cookies and exclude visits from all logged-in users. What Happened? On two separate days, Koko Analytics was sh...

On March `12 and 19, I received a highly unusual number of visitors and page views on The New Leaf Journal according to Koko Analytics. By “unusual,” I mean about 10X as many visitors as expected. No individual article had an unusual number of views and my Koko Analytics stats showed the usual list of referrers (mostly search engines) at usual referral numbers. I checked by server logs on the 19th and determined that the likely culprit was SBInstitutionsBot/0.1 (it appears to be a Japanese web crawler for AI), which was hammering my site with requests as I was seeing unusually high visitor numbers. I used Jeff Starr’s BBQ Pro firewall plugin to block the bot. My Koko Analytics stats quickly returned to normal. I reported the issue to Koko Analytics on GitHub, so I hope the relevant IP addresses are added to the do not count list if it turns out that my diagnosis was correct. (In any event, one of my former visitors, PoorlyConfiguredWebCrawler, was much better behaved than SBInstitutionsBot.)

I checked by 404 logs over at The New Leaf Journal. I found an interesting user agent among the myriad web crawlers:

PoorlyConfiguredWebCrawler

I appreciate that the crawler advertises that it is not well configured. You get the feeling that whoever released the poor thing on the internet is asking us to not be too hard on it. I did a bit of digging and learned it comes from a Swedish server, but information is otherwise scarce. According to my logs, it was only trying to crawl real articles (its only 404s were old links with no redirect) and did not seem to be misbehaving. Because it appears to be a well-behaved (albeit “poorly configured”) bot, I declined to stand athwart its crawling journey. I look forward to trying the Poorly Configured Search Engine it is clearly working toward.