Yes. It's a good idea, and I thought about it as well - will apply it in my case ASAP as well. By the way, which user agent do you think it's the "safest" from the point of view of preferably getting the same data as without it?
WebParser DOES use a User Agent string, it is "Rainmeter WebParser Plugin".Yincognito wrote: ↑June 17th, 2020, 6:56 pm Yes. It's a good idea, and I thought about it as well - will apply it in my case ASAP as well. By the way, which user agent do you think it's the "safest" from the point of view of preferably getting the same data as without it?
Ok then, thanks!jsmorley wrote: ↑June 17th, 2020, 7:01 pm Well, I just go to one of the many "What is my User Agent" websites and use the same as my Firefox browser uses. That is part of the point for me. As for trying to ensure you get the same thing that you would get with the default "Rainmeter WebParser Plugin", while not sending that particular string, I don't know. Might be able to just use "Four Score and Seven Years Ago" or something. The point presumably is to have the User Agent string be "unknown" to the site. Not sure I would do that, as I can well imagine that any "known" User Agent string would be flagged as a "browser" and that's good, they assume you are seeing their advertising. Any "unknown" User Agent string, including our default, would likely be flagged as an "application", and that might be more of a black mark in their eyes.
Yeah, just applied setting the user agent and analyzed the results. Setting the user agent makes no difference in what is otherwise received by WebParser's Debug=2 option, the two files are identical, at 976 993 bytes. Saving the page source from the browser creates a similar UTF-8 document that is significantly different from the other two, at 1 306 773 bytes. It's not just the adds or whatever, it's also what I mentioned earlier in this or another thread ... the applicationId at the start of the document. I might be mistaken on this one, but if that's a way to detect if one is accessing weather.com using a browser or not (as the 2 WebParser documents had the same applicationId value - the same as the last time I checked it out using WebParser, i.e. ending in 989 -, different from what the browser produced), then I'm not sure setting the user agent is of much use.
"applicationID":"296284162"Yincognito wrote: ↑June 17th, 2020, 8:17 pm Yeah, just applied setting the user agent and analyzed the results. Setting the user agent makes no difference in what is otherwise received by WebParser's Debug=2 option, the two files are identical, at 976 993 bytes. Saving the page source from the browser creates a similar UTF-8 document that is significantly different from the other two, at 1 306 773 bytes. It's not just the adds or whatever, it's also what I mentioned earlier in this or another thread ... the applicationId at the start of the document. I might be mistaken on this one, but if that's a way to detect if one is accessing weather.com using a browser or not (as the 2 WebParser documents had the same applicationId value - the same as the last time I checked it out using WebParser, i.e. ending in 989 -, different from what the browser produced), then I'm not sure setting the user agent is of much use.
Just curious, can you temporarily set a Debug=2 in your environment and then CTRL+F (i.e. find) the applicationId value in the downloaded WebParserDump.txt, to see if it also ends in 989?
Yep. At first, I was surprised, because I expected to end in 989 in order to point out at Rainmeter (i.e. the same application), then tried with your default settings in your skin (i.e. 3 day forecast) and got something ending in 226, then changed to the 15 day forecast and got the same ending as you, aka 162 (I'm talking about endings here only to simplify the matters, as the latter means I got the same applicationId as you for the 15 day forecast, i.e. 296284162).
So, eventually, I have no idea what this means, but my impression is still that weather.com has other means of differentiating between the browser and a specific application apart from reading the user agent (or maybe the applicationId for the broswer fluctuates in a similar manner as well?). I might be wrong with this or talk about something that isn't / won't be really relevant ... or not. We'll see. 
A resounding second!Active Colors wrote: ↑June 26th, 2020, 9:55 am Thank you jsmorley for this skin and keeping it updated and other people for the common effort to keep this updated and simple for other users. Much love.
There is no way to do this that is just a click or two. You are going to have to edit the skin.
Code: Select all
[MeterAllBackground]
Meter=Shape
Shape=Rectangle 0.5,0.5,169,322,12 | Fill Color #BackgroundColor# | StrokeWidth 1.5 | Stroke Color #FrameColor#
X=0
W=170
H=323