the-archive-public VS ultra-weather

Thanks! The game here is written in Inform7, and it was so difficult to make progress that it took me three years on and off to finish the game. So if you do it that way, beware :)

Abridged story: https://github.com/statico/the-archive-public/blob/master/Th...

Backend server: https://github.com/statico/glulxe-httpd

I tried sharing a couple of my web apps:

- HN the way I want to read it: https://hw.leftium.com/

- Source code: https://github.com/Leftium/hckrweb

- Weather forecast compared to last two days' weather: https://github.com/Leftium/ultra-weather#readme

One of the reasons I built https://uw.leftium.com/ was so I could see the previous two days' weather.

It uses the DarkSky API, but also supports other weather API's: https://github.com/Leftium/ultra-weather#readme

Great idea. It should be simple to add. Just need to connect the variable that controls C/F display with the logic that handles other query string parameters.

https://github.com/Leftium/ultra-weather

If you're referring to https://uw.leftium.com/, tap the temperature in landscape mode ;)

The app defaults to F because it gives the more "human" temperature range.

I've investigated and tried several (free) weather API's for my web app: https://uw.leftium.com.

Open-Meteo looks pretty good! The only thing that seems to be missing for me is precipitation probability. The weathercode is sort of a proxy for this... I'm also interested in sunrise/sunset times; direct_radiation is kind of a proxy for this.

Kudos for providing optional historical data with the same API call for the forecast. Many weather API's don't provide historical data, and even if they do, it requires extra calls. My weather app charts the previous two days of weather with the forecast for comparison. I feel this gives a more intuitive sense of the weather vs. raw numbers because weather is very relative. ("Warm" vs "cool" depends on your location and season.)

In addition, I am in the process of adding AQI forecasts, which requires even more network calls. It seems like this is on the roadmap for open-meteo. I was surprised to find there are so many different standards for AQI. Curious to know which one you plan to use.

One possible suggestion for optimizing the output format: sending seconds since the Unix epoch would save a few bytes per timestamp. I'm not sure if this would make any noticeable difference with gzip compression. The current datetime format is much more human-readable and may save a conversion before displaying.

These were the best (free) weather API's I could find. It's interesting how the three different weather forecasts can disagree so much:

- https://openweathermap.org/api

- https://www.visualcrossing.com/weather-api

- https://darksky.net/dev (deprecated)

When I find the time, I will add open-meteo as to my app! I'll probably have more feedback then.

The app hit the DarkSky API free tier limit, so it's displaying mock data. There is a little message at the bottom. (Probably didn't snow two days ago, either...)

This API still works: https://uw.leftium.com/?api=openweather