Nobody will care about this, but in case you do... here's a list of useragents out there in the wild. I dynamically produce my RSS feed with different tags for the audio for each client, so I can spot really quite well what app is using what useragent. https://podnews.net/article/sample-podcast-useragents
Nobody probably cares about this either, but https://podnews.net/_pages/podcast-analytics/parse-analytics.php now has a full sample of what happens if you look at the RSS useragent vs the audio useragent when it comes to identifying sources. Both use the OPAWG list.
@jamescridland Very interesting!
Would adding the ?utm_source=Podfriend (now that I can't set User-Agent in the html5 client) for audio files get Podfriend recognized? Or is that one a bit of a lost cause?
@martin For my infrastructure, ?podfriend would work. But I think this is worth trying to standardise somehow. To append ?_player=podfriend (with a leading underscore) to audio might be a way of doing that. I wonder where this lies - it's outside the scope of a namespace. Maybe lives in OPAWG?
@jamescridland Thank you James. I love these types of analytics when someone takes time to share. It helps make sense of log data. Saved a copy.
@dave That was relaxation coding, but next time I do it, my plan is to automate the logfile capture and analysis, and then output the parsed totals into a database somewhere. I would like to keep a similar page like this publicly visible with the last day's logs on it (since I suspect it might be a good testing ground).
Intended for all stake holders of podcasting who are interested in improving the eco system