What part of the world do you live in? I am located near Salt Lake City, Utah and the Xfce weather app looks fairly accurate when compared against google's weather results. I was even able to find the exact information for the small town I live in, which I didn't expect to happen with this plugin.

1 members found this post helpful.

I run -current, and PA poses no issues for me. It very well may be that running 14.2 may be the primary cause of the troubles. Like yourself, I cannot reproduce their troubles. It's not that I doubt they're telling the truth, it's that their situation may be unique to them.

1 members found this post helpful.

West Coast of the U.S. Just for chuckles I've re-installed it and at the moment it is off by four degrees. The source is apparently some outfit out of Norway (?) and has never been accurate.

To be fair, Accuweather has been off so often I've started calling them the NSAA, the Not So Accurate Accuweather.

OTOH, The Weather Underground is usually spot on and has more reporting stations. One is just two blocks away.

One advantage of YAWP is the ability to pick from different reporting services.

1 members found this post helpful.

The Californian coast (where I, too, live) is rife with microclimates which makes weather representation tricky and weather prediction next to impossible.

This has driven me to wunderground, despite its many faults. It lets me pick a weather station nearest the area which interests me, which sometimes puts it in the same microclimate.

3 members found this post helpful.

Regarding discontinued support in KDE, I know it is possible to run some old apps by installing the needed libraries in someplace like /opt. Is this likely not possible for YAWP?

2 members found this post helpful.

Expectation leads to disappointment.

I call Accuweather Accuguess since it is off more often that not in predicting the weather. Anyway, I got curious and added the xfce weather plugin to the panel and find that these days it is spot on for my use. It reports the weather with the same details as the airport in Thunder Bay and that is what I have found to be most accurate

1 members found this post helpful.

Because April 1 has passed and I live in the US (where and when net neutrality is dead) I am interested in knowing if Slackware will support DNS Encryption anytime soon? It can be built now but the prerequisites have a few requirements not currently available as a SlackBuild such as libssl-dev and possibly libyaml-dev. It might be nice if some form of DNS Encryption was available in Extra.

1 members found this post helpful.

There's libsodium in -current now, what else do you need? Nettle, dnsmasq.. it's shipped.
You could add in COPTS= section of dnsmasq Makefile -DHAVE_DNSSEC and point it to dnssec enabled resolver :443 (It'll work)
Maybe ask in requests thread if there's something else..

Thanks, elcore, but after further research I've decided to build a Raspberry Pi dedicated DNS server. I may try Current on it but this will likely be an all Summer project as I play around with different configurations. Apparently performance varies quite a lot.

I had some down time this week and was bored so I tried Alien Bob's newest Slackware live with Plasma5, and I have to say the newest version of KDE5 seems much more snappy and responsive than the version I tried a year ago. I am really liking it and am now looking forward to using it in Slackware 15

That has been my experience as well Daedra. It's gettin' good

@enorbert
Encrypting your DNS won't really help that much, your direct https connections will be still visible for your ISP and the DNSCrypt services available for you ATM are all commercial and might share your "browsing habits" profile, especially if they catch you authenticated on some pages that are provided through their services - correlation (part of the core business nowadays). It might help you only in case your ISP directs you (through DNS) to some more crappy servers for your content requests, that's if you're not a "special" premium user, but a regular one.
Privacy related, your only option to protect it is using tor as your DNS resolver, a little slow and you'd be unable to control the resolver on the other end (tor exit node). Alternatively, get a VPN account and use DNSSEC through it on your preferred DNSSEC enabled root nameservers.
Interesting read (long):
https://arstechnica.com/information-...encrypted-dns/

Good choice! I'm using unbound with DNSSEC for years now on x86 and recently also on several ARM Raspberry Pi boards (Pi2B&PiZero) and it simply rocks, at least for the SoHo requirements. It shouldn't take you more than a weekend to get used with the Raspberry Pi & Slackware ARM, documentation/experience/support is mature - https://www.linuxquestions.org/quest...kware-arm-108/
Here you can find a small benchmark test for a Raspberry Pi2B loaded with Slackware ARM -current, running unbound 1.7.0 peered with 4 root nameserves from Europe talking only DNSSEC, the unbound process was not going over 0.7% CPU usage:
http://s000.tinyupload.com/?file_id=...35022930784988
- tool used: https://www.grc.com/dns/benchmark.htm

-----
Apart from sharing some experience with enorbert, my main point with this post is to suggest to include unbound in Slackware 15. It's fast, stable, widely adopted and very easy to configure. Thanks!

https://en.wikipedia.org/wiki/Unbound_(DNS_Server)
Unbound has supplanted the Berkeley Internet Name Daemon (BIND) as the default, base-system name server in two BSD-based open source distributions, where it is perceived as smaller, more modern, and more secure for most applications.

3 members found this post helpful.

Thank you, abga, good information.

Where can I get one that reads:

Ubuntu [Ŭ-ˈbʌn-tű ] - An African work meaning Slackware was too hard for me.

2 members found this post helpful.