The trick here is to take some source of information online that's updated frequently and turn that into a historic record of every change made to that source, by setting up a GitHub repository and dropping a YAML file into it setting up a scheduled action.

Achieving the same thing with a time series database would require a whole lot more work I think - you'd need to run that database somewhere, then run code that scrapes and writes to it on a scheduled basis.

If you already have a time series database running and a machine that runs cron I guess it wouldn't be too much work to put that in place.

Git scraping also lets you easily track changes made to textual content, which I don't think would fit neatly in a time series database.