In the past days both Heinz and Ric alerted me that my RSS feeds wasn’t reachable for them. My log files quickly showed what was happening, Netnewswire, FeedBin and TinyTinyRSS were blocked by my hoster as ‘bad bots’ whenever they tried to reach my RSS feed:
[Thu Mar 26 03:43:49.372015 2020] [:error] [pid 501480] [client 95.143.172.147:48116] [client 95.143.172.147] ModSecurity: Access denied with code 403 (phase 2). Matched phrase "tt-rss.org" at REQUEST_HEADERS:User-Agent. [file "/etc/httpd/modsecurity.d/modsecurity_localrules.conf"] [line "2"] [id "350001"] [msg "Bad Bot Rule: Black Bot detected. "] [hostname "www.zylstra.org"] [uri "/blog/feed/"] [unique_id "XnwW5ZujCwgIM-xP-57OfAAAAAE"], referer: http://www.zylstra.org/blog/feed/
[Thu Mar 26 04:06:25.506843 2020] [:error] [pid 452702] [client 157.230.163.157:51478] [client 157.230.163.157] ModSecurity: Access denied with code 403 (phase 2). Matched phrase "Feedbin" at REQUEST_HEADERS:User-Agent. [file "/etc/httpd/modsecurity.d/modsecurity_localrules.conf"] [line "2"] [id "350001"] [msg "Bad Bot Rule: Black Bot detected. "] [hostname "www.zylstra.org"] [uri "/blog/feed/"] [unique_id "XnwcMZhpXdX8450kb5sLbgAAABI"]
[Thu Mar 26 05:45:54.289670 2020] [:error] [pid 681301] [client 69.172.186.78:39628] [client 69.172.186.78] ModSecurity: Access denied with code 403 (phase 2). Matched phrase "NetNewsWire" at REQUEST_HEADERS:user-agent. [file "/etc/httpd/modsecurity.d/modsecurity_localrules.conf"] [line "2"] [id "350001"] [msg "Bad Bot Rule: Black Bot detected. "] [hostname "www.zylstra.org"] [uri "/blog/comments/feed/"] [unique_id "XnwzggS4@-ngUalhqeVluAAAAA4"]
I submitted a ticket with my hoster Thursday but they have been unusually unresponsive this time. So for the time being I created a Feedburner RSS feed http://feeds.feedburner.com/InterdependentThoughts, so at least those that have this issue can resolve it. However Feedburner has been part of Google since 2007, which means the service hasn’t evolved apart from that it tracks your reading habits. So I’m on the lookout for a replacement service that does the same as Feedburner, except that it isn’t Feedburner, so sans the tracking.
[UPDATE 2020-03-30: the blocked feedreaders are now unblocked again. I’ll keep the Feedburner feed alive for now. Will likely rename it to something under my own domain [no longer possible], and my try to replace it with something like granary.io]
I don’t think I’ve been seeing your feed either! That’s using NetNewsWire on iOS.
There isn’t really an alternative that I would recommend. Hosting from your own site is the best solution. I guess people could subscribe to your Micro.blog feed.
It seems my micro.blog feeds don’t work (too many http redirects).
You’re right self-hosting is the best thing. Not doing away with that, just want to add a (temporary) alternative. Listed Feedburner now with the other RSS feeds in the sidebar.
@ton FeedPress perhaps? https://feed.press/ but since you are into self-hosting, why not fall back to the default WordPress feeds?
FeedPress
Your RSS feed works fine with The old reader: https://theoldreader.com/
You may want to set your temporary Feedburner up as a DNS CNAME, feeds.zylstra.org for example, so that when you find a post-Feedburner solution you can transparently migrate without a need to change the URL for your feed. Feedburner supports this as “MyBrand” (https://support.google.com/feedburner/answer/79586?hl=en).
That’s a good tip Peter! Thank you.
Alas “The MyBrand service is deprecated. Your existing domains will continue to work, but you cannot add new ones anymore after July 31, 2019“
In reply to https://www.zylstra.org/blog/2020/03/is-there-a-feedburner-alternative/.
Maybe https://granary.io could work? Not a feed hosting service, but a type of proxy that doesn’t store anything (and is typically used to convert one feed type into another). You should be able to use it to “translate” WordPress’s RSS to Atom—or WordPress’s Atom to RSS.
Thank you for the tip Jan. I tried it. Granary doesn’t do RSS->RSS it seems, leaving me with them parsing the HTML. That sadly means that most postings won’t get found (I don’t post everything on the frontpage). Ah wait, I could use the ATOM feed.
The resulting feed has a very odd mix of postings, missing the recent ones. Weird.
I read your RSS feed just fine with Feedly.com
Yes, oddly enough a few specific readers are getting blocked. Feedbin, NetNewsWire and TinyTinyRSS
Yes, it doesn’t make much sense. It’s only for specific feed readers though, based on the user agent that is set. I had it once before because the feedreader in question used the no longer existing Google Reader as user agent. Same seems to be true for why NetNewsWire is getting blocked. Others might have gotten blogged for the frequency with which it calls the feed URL.
In reply to https://www.zylstra.org/blog/2020/03/is-there-a-feedburner-alternative/.
Seems I was also no longer getting your updates. Requests from both my Aperture instance and Miniflux (self-hosted on another server) would just time out. (And work okay after switching to the FeedBurner feed,
although I might just try to set the user agent by hand.)