wttr.in: Unknown Location

A little bit more details: from time to time we reach the top data source capacity daily limit (as today), and so we can’t do nothing about, but just wait. We could increase the capacity permanently, but it would cost much more than it costs now; many users proposed many times to fund the service via patreon etc; maybe that is the way to go, but I am not sure how many are willing to do it for real. Just out of curiosity, my question to them who read the thread: would you support the service with $1/month if it would reduce number of outages by 80%? (serious question)

Now this is for real. Will be not available for the next 4 hours. Stay tuned. I will update you, as soon as it is back online

Thank you @MAGICCC wttr.in is back

@chubin Only saw this just now. All 3 seem to work well now

~ curl wttr.in

Follow @igor_chubin for wttr.in updates

~ curl v2.wttr.in
Unknown location; please try ~[my coordinates]
Follow @igor_chubin for wttr.in updates

~ curl wttr.in/[My location]?format=1
Unknown location; please try [my coordinates]~

Note that in the last one, there’s no newline at the end

I don’t use wttr.in so much but a dollar wouldnt hurt if its help you. I do it with a different project here on GitHub for its Patreon page

For many reasons, but mainly because of it’s absolutely free nature (free as in freedom and free as in beer) combined with high popularity (~20M queries daily).

Regarding error message: agreed, I will fix it

Well, if someone runs curl and this error occurs, it shows your coordinates. I’d say it’s undesired and a significant privacy risk. (What if someone is streaming it, blindly sending the output somewhere, idk). Doesn’t seem particularly relevant either. (I pipe the output of the query straight to my status bar, you can say this is a stupid thing to do on my part, but still…)

Should be fixed; please test