You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got this e-mail recently from OpenWeatherMap that they want to discontinue the API that ansiweather makes use of too: "One Call API 2.5 to be discontinued soon". Super short notice of just ~1 week (Oct 7, 2024 it goes down). They assume everyone has instantly time to fix their tools, I assume. This breaks my own "low temperature alert" script, but I remembered "ansiweather" in my /usr/local/bin, so I was checking out what it does: sadly uses the same "service". 😅
They offer a new v3 API, but they want payment (credit card, I guess?) information up-front. Not very "Open" in my book. Simply another service that gets the ensh*ttification treatment. 😐
How do you plan to workaround this issue with ansiweather? What's the plan forward here, if any?
The text was updated successfully, but these errors were encountered:
I got this e-mail recently from OpenWeatherMap that they want to discontinue the API that ansiweather makes use of too: "One Call API 2.5 to be discontinued soon". Super short notice of just ~1 week (Oct 7, 2024 it goes down). They assume everyone has instantly time to fix their tools, I assume. This breaks my own "low temperature alert" script, but I remembered "ansiweather" in my /usr/local/bin, so I was checking out what it does: sadly uses the same "service". 😅
They offer a new v3 API, but they want payment (credit card, I guess?) information up-front. Not very "Open" in my book. Simply another service that gets the ensh*ttification treatment. 😐
How do you plan to workaround this issue with ansiweather? What's the plan forward here, if any?
The text was updated successfully, but these errors were encountered: