Supposedly, it's to prevent vandalism from people who would connect to the online interface... why you would use the online interface in a public setting is another question lolI don't have VLC installed and I don't quite get why an username and a password would be needed in this case, but maybe the username in your original attempt must not be blank, from Rainmeter's point of view (it wouldn't be the first case, as it doesn't like empty regex captures either)? :???:
If I don't find out the reason why it's not working, I guess I'll eventually use this, I'll just tell users to copy both the .inc with the measures and the .lua file (day 11 of wishing for a LineN option for Script measures without some loadstring hack)As for base64 encoding and decoding, Javascript has the btoa() and atob() functions to do it and you can fetch stuff from an address there too, via XMLHttpRequest() or fetch(), but of course you're not using WebView to be able to use these. For Lua, this might be a reasonable solution:
http://lua-users.org/wiki/BaseSixtyFour
For email skins, both field will always have to be filled, in this case, username can be left alone, while I could just add a username and call it a day, this will probably prop up in other places in the future againUnfortunately, I don't have an answer to your last question, since I didn't work with HTTP Auth in WebParser yet, given that I didn't need it for any email skin. :(
The thing is, it works in CMD's curl but it dosen't work in Powershell's Invoke-WebRequest?????????????????
I'm too lazy to look in the code, but I'm pretty sure it's not working in Rainmeter because the library WebParser (and by extension Powershell) uses (System.Web.Whatev) also has this incorrectly, so technology older than me beats newer (supposedly better) technology again.
Statistics: Posted by Jeff — Today, 9:56 am