If only there's a $PS1 version
didn’t this really come up when MS was designing PowerShell?
31–40 of 147 posts
If only there's a $PS1 version
didn’t this really come up when MS was designing PowerShell?
Earlier quoted context omitted.
That would be cool, but how would you condense the information enough that it's both useful and doesn't take up 2/3 of a line?
Emojis? For the current weather, a single emoji could convey quite a lot; e.g. a snowflake for sub-60 weather (I have a low tolerance for cold), a sun for 60-80, fire emoji for 80+... Now, I don't know if anyone truly needs the weather in their terminal prompt, but it is doable.
Remember with this kind of thing you're trusting the remote site with access to your terminal emulator. There have been various security problems with some more advanced terminals and escape sequences in the past[1][2]. Personally I think it's a cute thing and have implemented some similar little easter eggs to this via: curl ip.wtf/moo [1]: https://blog.mozilla.org/security/2019/10/09/iterm2-critical... [2]: https:/…
my idea is to limit the terminal’s cpu usage so that any breach does not spread quickly in the system, and maybe limit the terminal’s network access, but leave the shell out of it. idk if the last part is possible.
Earlier quoted context omitted.
Heh, I did the exact same thing. I actually did alias weather="curl wttr.in && curl v2.wttr.in && curl v3.wttr.in" so that it shows me the temperature chart and map as well. Well, v3's map isn't working so I commented that out for now but they say it should work in the future.
but this curls the app each time you invoke it!
I have to scroll all they way down to the buttom to find the information source -- WorldWeatherOnline. Does people not care about where their whether data is sourced from? Living in Japan, I have always been wary of these type of service, since I find a lot of them really inaccurate. And I just checked, Tokyo show 15C on that website, while high resolution current weather information from Japan Metrological Agency sh…
Seems to be mostly Airport data. Helsinki Airport is not in Helsinki, so this information is quite useless. Also we do not measure windspeed in km/h.
There's also `curl v2.wttr.in`, but imho I like the original better.
I like this command, as an alias, it combines all wttr.in's versions (v3 doesn't quite seem to work yet): alias weather="curl wttr.in && curl v2.wttr.in && curl v3.wttr.in"
The Bayern.sxl example works, and is a good way to prove to yourself that your terminal is compatible, instead of your hoped-for region not being indexed.
curl v3.wttr.in/Bayern.sxl
curl v3.wttr.in/California.sxlI have to scroll all they way down to the buttom to find the information source -- WorldWeatherOnline. Does people not care about where their whether data is sourced from? Living in Japan, I have always been wary of these type of service, since I find a lot of them really inaccurate. And I just checked, Tokyo show 15C on that website, while high resolution current weather information from Japan Metrological Agency sh…
I'll admit I'm just speculating because I don't know much about weather and weather data collection, but is it not possible there's a 3 degree difference between 2 different places of measurement in Tokyo (i.e. both are correct to some degree?)
I have to scroll all they way down to the buttom to find the information source -- WorldWeatherOnline. Does people not care about where their whether data is sourced from? Living in Japan, I have always been wary of these type of service, since I find a lot of them really inaccurate. And I just checked, Tokyo show 15C on that website, while high resolution current weather information from Japan Metrological Agency sh…
I think you are comparing a weather model with the current reading from a weather station.
Earlier quoted context omitted.
I like this command, as an alias, it combines all wttr.in's versions (v3 doesn't quite seem to work yet): alias weather="curl wttr.in && curl v2.wttr.in && curl v3.wttr.in"
v3 does work, but you need to guess the appropriate region. The Bayern.sxl example works, and is a good way to prove to yourself that your terminal is compatible, instead of your hoped-for region not being indexed. curl v3.wttr.in/Bayern.sxl curl v3.wttr.in/California.sxl
Remember with this kind of thing you're trusting the remote site with access to your terminal emulator. There have been various security problems with some more advanced terminals and escape sequences in the past[1][2]. Personally I think it's a cute thing and have implemented some similar little easter eggs to this via: curl ip.wtf/moo [1]: https://blog.mozilla.org/security/2019/10/09/iterm2-critical... [2]: https:/…
which begs the quotation: is there such a thing as a “firewall” for terminals? my idea is to limit the terminal’s cpu usage so that any breach does not spread quickly in the system, and maybe limit the terminal’s network access, but leave the shell out of it. idk if the last part is possible.