httpstatuses VS wttr.in

https://httpstatuses.io Is still my favorite.

http.cat is amusing, but https://httpstatuses.io is my quick and simple goto reference.

It's a nice tool for sure, wonder though if you have come across https://httpstatuses.io/ too - quick, easy, ad-free, static app, https://github.com/httpstatuses/httpstatuses

I sold httpstatuses.com in... 2016 I think, maybe 2017, and the acquirers kept it as-is until 2022. Someone (not me) recently relaunched the site (as it was opensource) under a new domain -- https://httpstatuses.io -- so if you can replace ".com" with ".io" in your muscle memory, you can get the original site!

Their blog post about relaunching: https://jkulton.com/2022/reviving-httpstatuses

I went ahead and git cherry-picked the commits off that old PR into the new project then deployed, dark mode should now be supported. Here is the PR with the changes.

wttr.in is unfortunately not accurate in many cities in the world, check their github issues

The difference with weafetch is that it has its own config file which can just be configured and not touched anymore. When using wttr.in with curl, any custom changes you want to get from the output will need to be typed in everytime.

What about https://wttr.in/ ?

The source of the data that are presented: https://github.com/chubin/wttr.in

I don't recommend using wttr.io at all, their current provider shows inaccurate information for many cities, including Berlin. (source)

Oups the last link was incorrect it should have been https://github.com/chubin/wttr.in. I pull the info and store it in a txt file then I reference with cat or sed. That way it's super quick.

See https://github.com/chubin/wttr.in