Closed wdenton closed 8 years ago
i'm curious to hear why this would be useful.
In the general case, it could be useful to split ranges belonging to the same country or government but still tweet them from the same account: e.g. scotland.json, wales.json, england.json, northern-ireland.json, then call them all for a UK-monitoring account. It would add granularity permitting flexibility without further scripting to reparse config files.
In my specific case, I want an easy way to make a single bot that be the sum of all these existing bots, and tweet everything seen in all the ranges. With this I could just specify all the existing range config files and let it go. :)
Yeah, as I've commented on the monsantoedits.conf, it really needs to be expanded to include all of Monsanto's subsidiaries: https://www.msu.edu/~howardp/seedindustry.html
And if subsequently similar accounts/conf files were created for Bayer, Dupont, Syngenta etc. and all their subsidiaries, they could also be combined into a GMOedits account without duplicating the conf files.
I think it would be useful to be able to specify an array of JSON range files in config.json, like so: