I've got several reports lately that users get You are not root when in fact they are. The cause of this is that they have no internet connection and lib.sh won't load, which causes the the wrong error to appear. As soon as the fix their network connectivity the scripts load without any issues. We should make this failsafe instead somehow, or at least show that it's their connection that is failing rather than telling them that they are not root.

Maybe we should include lib.sh locally, or include the functions of network_ok is_root directly in the scripts instead of fetching them from lib.sh?

Do you have another solution in mind @morph027