[–] [S] 1 point 1 week ago

Indeed the API would have to have changed on open-meteo. Alternatively, it’s also possible that open-meteo started blocking Tor (the only network I will use).

I doubt it’s a Tor block though, because of this other problem: when I first installed Breezy Weather, I configured it to get weather for 6 different cities. It all worked for a while. I could switch to any of the 6 cities and it would fetch the weather. Then after a couple months it failed to fetch 5 of the cities (luckily the cities I did not live in). Now it fails to grab weather for any city. BW indicates an error-free fetch “0 mins ago”, but shows no data. In fact, I’m calling it a software bug because BW is likely failing to show the user an error.

So it looks like two problems: OM changing their API and BW not reporting an error.

  • source
  • parent
  • context
  • [–] 2 points 2 weeks ago* (1 child)

    Latest version (6.2.2)retrieves data from Open-Meteo. Sounds like maybe API changed and your version can't retrieve.

    Though that would be an Open-Meteo API change, wouldn't it?

  • source
  • [–] [S] 3 points 9 months ago*

    A couple yrs ago Google announced that it was discontinuing use of the caches. They were directly accessible and also accessible via 12ft.io. So loss of 12ft.io was expected at that point. But strangely I continued to enjoy access well after that announcement. I wasn’t sure what happened; wondered if it was just that Google discontinued caching new pages. It was a bit hit and miss.

    Google’s wording was bizarre because surely Google still needs the cache for indexing. I wondered if Google made a false statement where the reality was just removing public access to the caches, not actually discontinuing use of the caches.

  • source
  • parent
  • context