> “well my use case for wfh involves uploading 1 TB a day”, but no, that’s not normal
1.2 / 30 = 40GB a day. Seems fairly low to me. Considering families with children attending online school as well, then clump in streaming services such as Netflix.
The point still stands, it shouldn't be allowed. It's a natural area for animals and it is a dangerous location. Those well trained/equipped who would normally explore areas like this would be fine -- but this could encourage people with less experience to venture into these areas unprepared for what they will face.
That terrain in Utah is no joke and many people have gone missing in those areas.
>The department has not disclosed the exact location of the monolith, fearing explorers may try to seek it out and "become stranded". The big horn sheep wildlife officials were counting are native to many parts of southern Utah, where the terrain is rugged.
I built something similar to this[1] for when I'm dealing with hosts I don't have complete control of -- to block outgoing connections. Now it seems there might be a more widespread use case.
Custom DNS servers are available on Big Sur. My home network uses pfSense as a gateway for LAN. This gives more options blocking outbound connections or routing connections thru a VPN connection based on certain conditions.
There are other tools available as well to collect 'cloud' data. Such as Magnet AXIOM Cloud[1] and Cellebrite UFED Cloud[2]. These still require legal process in most cases.