@paolafrancesca commented on GitHub:
@drnextgis seems that http://transfer.sh is down. I cannot do anything about that since the service is still managed by @nl5887 , I only take care of the codebase
@brodjieski commented on GitHub:
The rule for sysprefs_wifi_disable is identified as a "manual" control (as listed in the tags: field). This means that there is no automated check or fix…
@grismemj commented on GitHub:
Ok, thanks. I wasn’t necessarily expecting this since the checks and fixes are usually just simple or compound commands…
From: Dan Brodjieski @.***> Date…
@brodjieski commented on GitHub:
Yes, it will make it work... but if you are running the script remotely over Wi-Fi, you will get disconnected when it gets disabled. It's marked as manual as a…
@brodjieski commented on GitHub:
I agree. The way the current check is written, it only accounts for the network interface named "Wi-Fi". If the name of the interface is anything else, it will…
@erefneb commented on GitHub:
This is incorrectly marked as manual. The rule does in fact have a working fix. Simply removing the manual tag from the rule will make this work.
-- Eric…
@erefneb commented on GitHub:
If I have a disable wifi rule on my baseline, I would expect it to disable wifi.
-- Eric Benfer @.***
On Jan 21, 2022, at 12:13 PM, Dan Brodjieski…
@brodjieski commented on GitHub:
Documentation on the manual tag has been added to the wiki.
@grismemj commented on GitHub:
I would argue the point of being able to customize the rules for your environment is to allow these types of differences to be handled. So I think it is reasonable…