Skip to content

Conversation

@QuisVenator
Copy link

This changes the weather back to using lat/long when automatically determining location from IP. The reason for this is, that we one can not really guarantee that the city part we get from ipinfo will be recognized by wttr.in. For example for me, my IP resolves to Ciudad del Este. First I tried to address the issue with spaces in the city name, but found out that even correctly formatted this city is not recognized by wttr.in.

This should not break a users ability to use city in their config. Also, the only real change is on line 26, the rest is a renaming of the city variable to keep the code clean.

@soramanew
Copy link
Collaborator

I don't even remember why I changed this before... It used to use lat/long coords when I first made it

@nuknes
Copy link
Contributor

nuknes commented Nov 26, 2025

I don't even remember why I changed this before... It used to use lat/long coords when I first made it

I think it was when you made it configurable with a fallback to ip
#76

around this time
chubin/wttr.in#1093

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants