You have just read a blog post written by Jason McIntosh. If you enjoyed it, please anonymously acknowledge your visit by tapping the little star button underneath it.
Thank you kindly for your time and attention today.
I thought I would be able to write a script that would parse my own Apache logs and output a daily summary of this blog’s subscriber count. Unfortunately, a few hours of research today suggests that this does not seem feasible, and I find myself rather discouraged at the state of bloggers’ ability to self-report right now.
Initially, discovering this old bash script by Marco Arment heartened me; while out of date (leaning heavily on an assumption of Google Reader still existing, which it doesn’t), it still performed operations in line with my own observations from skimming my logs. So, I set out to write a simple Perl program that would do something similar with 2015-style, post-Google Reader data.
Very soon, I discovered that several aggregators’ feed fetchers, most notably Feedly, do not adhere to the Google Reader-style “N subscribers” substring that more community-minded aggregators (e.g. NewsBlur and Feed Wrangler) place into their fetchers’
user-agent identifiers when making HTTP requests. Here’s a (truncated) example of NewsBlur’s fetcher visiting my site, this morning:
blog.jmac.org:80 184.108.40.206 - - [15/Feb/2015:05:39:14 -0500] “GET /atom.xml HTTP/1.1” 304 - “-” “NewsBlur Feed Fetcher - 3 subscribers - http://www.newsblur.com/site/5827127/jmacorg-blog”
And here is a subsequent request from Feedly:
blog.jmac.org:80 220.127.116.11 - - [15/Feb/2015:05:44:11 -0500] “GET /atom.xml HTTP/1.1” 304 - “-” “Feedly/1.0 (+http://www.feedly.com/fetcher.html; like FeedFetcher-Google)”
You can see the difference. Newsblur tells me not only how many human subscribers it represented at the time of its visit (three of ‘em), but also shares the precise URI representing this blog’s ID within its own service. Feedly, on the other hand, only links to its own FAQ webpage.
Feedly’s log-line also states “like FeedFetcher-Google”, as if the thing it tries to reassuringly compare itself to hasn’t been offline for well over a year. Writing this now I find it hard not to read this detail as a further indicator of basic uncaring for community standards on Feedly’s part. Sadly, I suspect they can afford to not care; circumstantial evidence suggests that they scored big from Google Reader’s demise. I know from personal experience that Feedly offered an attractive alternative for RSS-reading refugees in 2013, and various apps such as Reeder and NewsBlur made migration to Feedly very easy.
To be clear, I state here that I certainly cannot blame anyone for using Feedly, because I use it myself, every day. I just haven’t had any reason to look at it from a writer’s standpoint, rather than a reader’s, before today. I welcome visits from Feedly’s fetcher, even as I feel disappointed in this particular behavior.
As this 2013 article by Alex Knight of FeedPress notes, Feedly has been ignoring this ad-hoc but quite beneficial standard for years, and also ignores any requests to change their behavior. (That article also puts Digg, another frequent (and equally welcome!) visitor to my blog, into the same camp.) After I read Feedly’s FAQ, I started to write their customer support email to ask if they had any plans to make their user-agent strings friendlier, but the spirit left me before I could continue; it seemed like a waste of time. I wrote this blog post instead.
So, here are my choices for getting accurate blog reader counts:
¯\_(ツ)_/¯to the others, even knowing that Feedly alone probably accounts a significant proportion of my readership.
I feel a bit sad about the whole situation and would rather just remain ignorant for the time being, instead of sinking any more time, money or effort into this problem. While I would love to know exactly how many readers I have, the fact remains that I tell myself I primarily write for myself, and here I suppose I have an opportunity to act like I mean it.
If a page elsewhere on the web responds to or otherwise mentions this post, you may provide its URL here.