What is the source for the weather data?
ASCII Art Weather
91–100 of 106 posts
Re: ASCII Art Weather
#92[deleted]
Re: ASCII Art Weather
#93It says "ERROR".
Re: ASCII Art Weather
#94Nice! I like the aggregation into time blocks people tend to care about.
What's the definition of the probability of precip you're using? And how are you aggregating it? I ask because definitions can vary a lot and aggregation may not be straightforward.
Another thing to consider is how you interpret/convey wind direction. Usually weather data sources provide the direction the wind is coming from. And people seem split on if the arrow should point to the origin or direction, depending on their background. It's a shame there aren't more characters like ⎋ (with the arrow going the other direction) to better represent origin/direction.
Re: ASCII Art Weather
#95What's impressed me about this is how much faster it is than Web pages or Android apps. Really: just transmit the data necessary to convey your information. Your app is in the way. wttr.in on Android using Termux is actually pretty awesome.
Try looking at the source of the page. There's no way in hell anyone would call that "just" the data necessary to convey the information. The site is also unusable on mobile, because ASCII art unlike proper semantic HTML is not easily rescalable by the browser. And it's inaccessible by users relying on screen readers, ironically because of all the ASCII cruft.
Could you not wrap it all in a div and do something like:
#ascii-art {
font-size: 2vw;
overflow: hidden;
white-space: nowrap; }Re: ASCII Art Weather
#96Earlier quoted context omitted.
>The site is also unusable on mobile Not everyone wants their webpages to be seen on mobile, this one works perfectly in lynx. Does your website work in lynx?
I would go out on a limb and say yes. Any website designed with screen reader accessibility in mind would work with Lynx, which is a more capable browser than screen readers.
That's not really true: JAWS, the most popular screenreader, works with IE and Firefox.
You can have a single-page javascript app be totally accessible. You could also have an ASCII art app that renders perfectly in lynx be totally inaccessible to a screen reader.
Re: ASCII Art Weather
#97This is awesome!
But now I get:
> Sorry, we are runnig out of queries to the weather service at the moment. Here is the weather report for the default city just to show you, how it works. We will get new queries as soon as possible.
Can't you cache the data for an hour to prevent this from happening? Heck, just show me something even if it's fake as I love how the thing looks :)
Re: ASCII Art Weather
#98What's impressed me about this is how much faster it is than Web pages or Android apps. Really: just transmit the data necessary to convey your information. Your app is in the way. wttr.in on Android using Termux is actually pretty awesome.
Ok why not get Lynx on your Android device? the rule of of diminishing return applies.. at some point, the usability shortcoming of ascii interface out weights the payload penalty
I've installed w3m (through termux, which is both a terminal environment and apt-based installer).
I don't use it much but there are times when it's faster and cleaner than any other alternative. It often actually is superior to GUI presentation, except for the annoying tendency of text to run into the gutter.
I've been kicking around an idea for a FYWD browser. That might stand for Fine Young Western Dinosaurs or Fuck Your Web Design. It would offer a standard format, non-JS, uniformly presented readable Web page. Not intended for apps, but a sane set of presentation defaults for a given site.
Site-offered CSS would be ignored (or at best strongly deprecated). Straight-bog HTML 1 / HTML5 sites should render best. User could opt for specific stylesheets (e.g., night mode, large/small font), provided _locally_.
It'd be aimed at reading.
Something like Reader Mode on Safari or Firefox, but enabled by default.
(I use the latter, often intercept loading pages to hand-type in "about:reader?url=" before they fully load.)
Some other bits in mind as well, sort of mulling over the concept for now.
This codepen shows what a few basic rules can provide. Doesn't take much to make that work across a wide range of display sizes. http://codepen.io/dredmorbius/pen/KpMqqB
Re: ASCII Art Weather
#99What's impressed me about this is how much faster it is than Web pages or Android apps. Really: just transmit the data necessary to convey your information. Your app is in the way. wttr.in on Android using Termux is actually pretty awesome.
Try looking at the source of the page. There's no way in hell anyone would call that "just" the data necessary to convey the information. The site is also unusable on mobile, because ASCII art unlike proper semantic HTML is not easily rescalable by the browser. And it's inaccessible by users relying on screen readers, ironically because of all the ASCII cruft.
As noted, you can fetch the page via curl. Takes just over a second total.
Contrast ~6 - 60 for a typical web page these days (and yes, Firefox appears to be part of the problem, but I'm willing to trade a lot of speed for utility).
Re: ASCII Art Weather
#100Earlier quoted context omitted.
> Also, I would prefer this as a CLI application, not as a webpage. curl http://wttr.in/london Looks nice :)
Using curl removes the HTML tags? Nice feature (though a little obscure).
I think what they're doing is using the user agent header like the accept header, which makes sense for that specific idea, as the browser version is actually just kind of imitating a console. It currently doesn't work because they ran out of queries on their backend service, but I think they were not stripping html, but delivering a terminal text version with color escape characters.