Moved an RSS Feed to a new domain

In July, I announced moving to a new domain with the free certificate monitor.

I was not sure how this will go, as I am solely relying on RSS client behavior, and I never even thought about moving an RSS feed to a new domain name before. For a technical explanation how to achieve such a stunt, check the linked post.

In July, there were 278 domains that got queried at least once in the past 30 days.

Now, after the switch was completed and the old domain was shut off, there are 133 domains left. That’s a 50% loss of monitored domains.

As I described before, I see this as a technical exercise in trying my best to keep user impact low. At the same time, I think nobody critically depends on the service, so I accept that there’s some loss on the way.

I use the iPhone App Reeder 5.5.1, which, to my disappointment, did not respect any of the redirect directives. I am, in that sense, part of the loss.

There’s one particular netcup host with a particular high request rate with an RSS to Telegram Bot. If you read this, please reduce the number of requests, before I do it for you 😜