Whenever I see a weather "app" I always think: "This is really a weather <i>display</i> utility" and then wonder about the quality / longevity of the service it depends on and how the information is provided.<p>What would interest me is an implementation that allows you to plug in different weather backends, so that having an API key to worldweatheronline, or screen-scraping weather underground, or building a bridge to your serial-port connected weather station all can target the same interface; to provide current conditions/historical conditions, a forecast, etc.<p>Are there standards for this, or is it mostly ad-hoc, the whim of the sites or commercial services which aggregate information and provide forecasts?
I live on the command line, so I really dig this sort of thing. And this one in particular looks very nice. I'm a fan!<p>If you're open to bug reports/feature requests:<p>* The image for clear weather is a bright sun, which is a little odd to see in the 'Night' column<p>* Many city names are duplicates. How do I know I've got the right one?
Way better than <a href="https://news.ycombinator.com/item?id=9503882" rel="nofollow">https://news.ycombinator.com/item?id=9503882</a> posted 7 days ago!
I like the utility, its convenient not to leave the command line.<p>On another note, was it really necessary to add the bit about the NSA? Hasn't that been played to death now?
A few years ago, you'd get notice by taking an old text-based service and wrapping it up in a web frontend. Now, the cool kids are taking web-based services and wrapping them up in text-based frontends.<p>Next thing someone will have the bright idea of transmitting data as sounds over VOIP services, and we can start setting up BBSes on skype...