inxi -W ny (or any other location) stopped working and now shows (instead of the
local weather conditions):

Weather:
Message: Error: Your access to this resource has been blocked. Automated
requests or excessive use are not permitted. This is clearly stated in both
the help menu and man page. If you want a CLI weather tool for routine
use, try wttr.in, or use a weather widget. Remember, you never had a
"right" to this feature, it was just a little easter egg, mostly for sys
admins, which has instead been consistently abused. If you want to know
your local weather, look out your window, there it is.

It's not all that important and I know there are CLI alternatives, but the
sudden change intrigues me. No idea what really caused it. Certainly not
"automated requests or excessive use" by me.

Yrrah

On Wed, 27 Jul 2022 14:08:59 +0200
Yrrah <Yrrah-aolm@aolm.invalid> wrote:

> It's not all that important and I know there are CLI alternatives,
> but the sudden change intrigues me. No idea what really caused it.
> Certainly not "automated requests or excessive use" by me.

I also get this error and haven't used it ever.
I assume it is an error at the server side, not on your side.
Maybe the operator completely discontinued the service.

On Wed, 27 Jul 2022 14:25:52 +0200, Marco Moock wrote:
> On Wed, 27 Jul 2022 14:08:59 +0200
> Yrrah <Yrrah-aolm@aolm.invalid> wrote:
>
>> It's not all that important and I know there are CLI alternatives,
>> but the sudden change intrigues me. No idea what really caused it.
>> Certainly not "automated requests or excessive use" by me.
>
> I also get this error and haven't used it ever.
> I assume it is an error at the server side, not on your side.
> Maybe the operator completely discontinued the service.

my guess server checked your zip code I am in Texas.

$ inxi -W ny
Weather:
Message: Error: request-failure~204

[bittwister@wb ~]$ inxi -W tx
Weather:
Report: temperature: 33.2 C (92 F) conditions: Clear sky
Locale: current time: Wed 27 Jul 2022 02:54:15 PM CEST
Source: WeatherBit.io

[bittwister@wb ~]$ inxi -W ri
Weather:
Message: Error: request-failure~204

[bittwister@wb ~]$ inxi -W nh
Weather:
Message: Error: request-failure~204
[bittwister@wb ~]$

Yrrah wrote:
> inxi -W ny (or any other location) stopped working and now shows (instead of the
> local weather conditions):
>
> Weather:
> Message: Error: Your access to this resource has been blocked. Automated
> requests or excessive use are not permitted. This is clearly stated in both
> the help menu and man page. If you want a CLI weather tool for routine
> use, try wttr.in, or use a weather widget. Remember, you never had a
> "right" to this feature, it was just a little easter egg, mostly for sys
> admins, which has instead been consistently abused. If you want to know
> your local weather, look out your window, there it is.
>
> It's not all that important and I know there are CLI alternatives, but the
> sudden change intrigues me. No idea what really caused it. Certainly not
> "automated requests or excessive use" by me.

I tried it four or five times with different parameters and I got the
message "Error: You have exceeded maximum permitted use of this
resource." Guess you can only have one weather report per day...

I wouldn't worry too much about it.

On 7/27/22 08:08, this is what Yrrah wrote:
> inxi -W ny (or any other location) stopped working and now shows (instead of the
> local weather conditions):
>
> Weather:
> Message: Error: Your access to this resource has been blocked. Automated
> requests or excessive use are not permitted. This is clearly stated in both
> the help menu and man page. If you want a CLI weather tool for routine
> use, try wttr.in, or use a weather widget. Remember, you never had a
> "right" to this feature, it was just a little easter egg, mostly for sys
> admins, which has instead been consistently abused. If you want to know
> your local weather, look out your window, there it is.
>
> It's not all that important and I know there are CLI alternatives, but the
> sudden change intrigues me. No idea what really caused it. Certainly not
> "automated requests or excessive use" by me.
>
> Yrrah
>
>
inxi -W 4347778
Weather: Temperature: 15.9 C (61 F) Conditions: Moderate rain Current Time: Wed 27 Jul 2022 09:05:34 AM CDT
Source: WeatherBit.io

Weatherbit.io has downloadable csv files for major cities.
https://www.weatherbit.io/api/meta

Now I'm not saying this works good, I'm in Baltimore, I used the 4347778 code for Baltimore as shown by weatherbit.io
but the temp they return is 61 F and it's really 80 F by OpenWeather and my outdoor gauge.

Al

Yrrah wrote:
> inxi -W ny (or any other location) stopped working

inxi options allow you to change your weather source; personally I use
wttr.in 'directly' because it allows me to input my postal zip; because
in my geo area the weather varies greatly over a very short distance
from the desert or 'mountains' to the sea. I don't know the exact
syntax for inxi to use its alternates 1-4.

$ curl wttr.in/myzip?1

(myzip = my zip 5)

I use the ?1 so I will only get one day instead of 3.

https://github.com/chubin/wttr.in

--
Mike Easter

Mike Easter wrote:
> Yrrah wrote:
>> inxi -W ny (or any other location) stopped working
>
> inxi options allow you to change your weather source; personally I use
> wttr.in 'directly' because it allows me to input my postal zip; because
> in my geo area the weather varies greatly over a very short distance
> from the desert or 'mountains' to the sea.  I don't know the exact
> syntax for inxi to use its alternates 1-4.
>
Default inxi uses weatherbit.io which is currently working ok for me and
seems to accept my zip, 'tho it doesn't echo it.

Its 'default' determination of my location, presumably by IP, is very
far off; absolutely no good for weather. That is 'generally' the result
of websites which try to determine my location.

--
Mike Easter

On 7/27/22 11:18, this is what Mike Easter wrote:
> Mike Easter wrote:
>> Yrrah wrote:
>>> inxi -W ny (or any other location) stopped working
>>
>> inxi options allow you to change your weather source; personally I use wttr.in 'directly' because it allows me to
>> input my postal zip; because in my geo area the weather varies greatly over a very short distance from the desert or
>> 'mountains' to the sea.  I don't know the exact syntax for inxi to use its alternates 1-4.
>>
> Default inxi uses weatherbit.io which is currently working ok for me and seems to accept my zip, 'tho it doesn't echo it.
>
> Its 'default' determination of my location, presumably by IP, is very far off; absolutely no good for weather.  That is
> 'generally' the result of websites which try to determine my location.
>
>
I use the Weather (weather@mockturtl) applet and I have the exact geo location set. Works great.

Big Al wrote:
> I use the Weather (weather@mockturtl) applet and I have the exact geo
> location set.  Works great.

https://cinnamon-spices.linuxmint.com/applets/view/17

Very configurable; location, weather source.

Interesting discussions at the site.

Cinn adaptation of this
https://github.com/simon04/gnome-shell-extension-weather

--
Mike Easter

Mike Easter <MikeE@ster.invalid>:

> $ curl wttr.in/myzip?1
>
> (myzip = my zip 5)
>
> I use the ?1 so I will only get one day instead of 3.
>
> https://github.com/chubin/wttr.in

I switched to ansiweather:

https://github.com/fcambus/ansiweather

Data come from OpenWeatherMap, the same source as used by the Cinnamon weather
applet.

Yrrah

Yrrah wrote:
> I switched to ansiweather:
>
> https://github.com/fcambus/ansiweather
>
> Data come from OpenWeatherMap, the same source as used by the Cinnamon weather
> applet.

ansiweather will take my zip if I add my country us; but I like wttr.in
appearance/ display better.

--
Mike Easter

Bit Twister wrote:
> On Wed, 27 Jul 2022 14:25:52 +0200, Marco Moock wrote:
>> On Wed, 27 Jul 2022 14:08:59 +0200
>> Yrrah <Yrrah-aolm@aolm.invalid> wrote:
>>
>>> It's not all that important and I know there are CLI alternatives,
>>> but the sudden change intrigues me. No idea what really caused it.
>>> Certainly not "automated requests or excessive use" by me.
>>
>> I also get this error and haven't used it ever.
>> I assume it is an error at the server side, not on your side.
>> Maybe the operator completely discontinued the service.
>
> my guess server checked your zip code I am in Texas.
>
> $ inxi -W ny
> Weather:
> Message: Error: request-failure~204
>
> [bittwister@wb ~]$ inxi -W tx
> Weather:
> Report: temperature: 33.2 C (92 F) conditions: Clear sky
> Locale: current time: Wed 27 Jul 2022 02:54:15 PM CEST
> Source: WeatherBit.io
>
> [bittwister@wb ~]$ inxi -W ri
> Weather:
> Message: Error: request-failure~204
>
> [bittwister@wb ~]$ inxi -W nh
> Weather:
> Message: Error: request-failure~204
> [bittwister@wb ~]$

I'm not sure it has anything to do with where you're querying from. I'm
in the UK and get the same - weather report for "tx" and "Message:
Error: request-failure~204" for the others, and also for "uk" and "gb".
I think you just happen to be lucky to be somewhere that doesn't return
an error!

Having seen in the man page that it "maybe" supports UK postcodes
(equivalent of US zip codes), I tried that which gave reasonable
results. But "london", "england" and "united+kingdom" consistently
return "Message: Error: You have exceeded maximum permitted use of this
resource." Immediately trying "tx" and my postcode again still give
results, so the message doesn't actually seem to be related to the
number of queries I'm making.

I've never used this before, so don't really know how it's supposed to
work and just reporting what happens from here. I should probably stop
now before I really do get blocked from something ;o)

--
Mark.

On 7/27/22 4:17 PM, Mark Bourne wrote:
> Bit Twister wrote:
>> On Wed, 27 Jul 2022 14:25:52 +0200, Marco Moock wrote:
>>> On Wed, 27 Jul 2022 14:08:59 +0200
>>> Yrrah <Yrrah-aolm@aolm.invalid> wrote:
>>>
>>>> It's not all that important and I know there are CLI alternatives,
>>>> but the sudden change intrigues me. No idea what really caused it.
>>>> Certainly not "automated requests or excessive use" by me.
>>>
>>> I also get this error and haven't used it ever.
>>> I assume it is an error at the server side, not on your side.
>>> Maybe the operator completely discontinued the service.
>>
>> my guess server checked your zip code I am in Texas.
>>
>> $ inxi -W ny
>> Weather:
>>    Message: Error: request-failure~204
>>
>> [bittwister@wb ~]$ inxi -W tx
>> Weather:
>>    Report: temperature: 33.2 C (92 F) conditions: Clear sky
>>    Locale: current time: Wed 27 Jul 2022 02:54:15 PM CEST
>>    Source: WeatherBit.io
>>
>> [bittwister@wb ~]$ inxi -W ri
>> Weather:
>>    Message: Error: request-failure~204
>>
>> [bittwister@wb ~]$ inxi -W nh
>> Weather:
>>    Message: Error: request-failure~204
>> [bittwister@wb ~]$
>
> I'm not sure it has anything to do with where you're querying from. 
> I'm in the UK and get the same - weather report for "tx" and "Message:
> Error: request-failure~204" for the others, and also for "uk" and
> "gb". I think you just happen to be lucky to be somewhere that doesn't
> return an error!
>
> Having seen in the man page that it "maybe" supports UK postcodes
> (equivalent of US zip codes), I tried that which gave reasonable
> results.  But "london", "england" and "united+kingdom" consistently
> return "Message: Error: You have exceeded maximum permitted use of
> this resource."  Immediately trying "tx" and my postcode again still
> give results, so the message doesn't actually seem to be related to
> the number of queries I'm making.
>
> I've never used this before, so don't really know how it's supposed to
> work and just reporting what happens from here.  I should probably
> stop now before I really do get blocked from something ;o)
>
Are you suggesting that Usenet is manipulated, much like Google which
has an agenda based search results?

Do you think that predicting the weather has progressed, it was a mere
100 years ago that predicting the weather was divined by the entrails of
some animal, or a caterpillar on some leaf.

It is raining at the moment, and the prediction was sunny.

On 28/07/22 03:18, Mike Easter wrote:
> Mike Easter wrote:
>> Yrrah wrote:
>>> inxi -W ny (or any other location) stopped working
>>
>> inxi options allow you to change your weather source; personally I use
>> wttr.in 'directly' because it allows me to input my postal zip;
>> because in my geo area the weather varies greatly over a very short
>> distance from the desert or 'mountains' to the sea.  I don't know the
>> exact syntax for inxi to use its alternates 1-4.
>>
> Default inxi uses weatherbit.io which is currently working ok for me and
> seems to accept my zip, 'tho it doesn't echo it.
>
> Its 'default' determination of my location, presumably by IP, is very
> far off; absolutely no good for weather.  That is 'generally' the result
> of websites which try to determine my location.
>
>

Hmmm lower case 'w" works for me..
Uppercase --error

inxi -w
Weather: Temperature: 19.4 C (67 F) Conditions: Clear sky Current
Time: Wed 03 Aug 2022 11:43:25 (Pacific/Auckland)
Source: WeatherBit.io

greybeard wrote:
> Hmmm lower case 'w" works for me..
> Uppercase --error
>
> inxi -w

-w gives you a report based on what inxi's function tells weatherbit.io
is your IP. (while keeping that IP analysis silent)

When you use -W, there is no such 'automatic analysis' of your location
by IP; so you must feed the inxi -W command some more info, such as
yrraH reported had stopped working properly.

> -w, --weather Local weather data/time. To check an alternate location, see
> -W. NO AUTOMATED QUERIES ALLOWED!
> -W, --weather-location
> [location] Supported options for [location]: postal
> code[,country/country code]; city, state (USA)/country
> (country/two character country code); latitude, longitude.
> Only use if you want the weather somewhere other than the
> machine running inxi. Use only ASCII characters, replace
> spaces in city/state/country names with '+'.
> Example: inxi -W [new+york,ny london,gb madrid,es]

My current testing shows that if I give inxi -W my postal zip + my
country code (syntax as above), I get a report; again no echo of the
location I fed it.

--
Mike Easter