So he connected her to the WiFi but didn’t set up the proxy he knew was required and just expected her to figure it out from there? Wtf? At no time in history would I expect a rando to even know what a web proxy is, let alone the address of this particular one.
I also found it ironic that they call out https as something desirable and how kids can’t describe why that is, but they don’t have Let’s Encrypt or something else setup for the very site where the otherwise great writeup is shared.
That said, it’s possible that the network had an automatic configuration script for the proxy that would have configured on connection under Windows systems and he just wasn’t aware that it would require manual steps on OSX? Still a bit ironic, but maybe excusable? I feel like if I managed a network with a proxy that would automatically configure on connection, I would understand the limitations of that setup, but that’s assuming a lot? I’d love to see their explanation on why that was her fault rather than theirs all the same, because the first thing I do after getting someone connected to a network is attempt to access something unlikely to be cached just so I can validate that the task was completed successfully.
I assumed that maybe (since they were colleagues) that they had some sort of training or provided documentation that says “set this proxy to connect”. And a tech literate person would know how, or figure out how to set the proxy. And this user did not.
So he connected her to the WiFi but didn’t set up the proxy he knew was required and just expected her to figure it out from there? Wtf? At no time in history would I expect a rando to even know what a web proxy is, let alone the address of this particular one.
I also found it ironic that they call out https as something desirable and how kids can’t describe why that is, but they don’t have Let’s Encrypt or something else setup for the very site where the otherwise great writeup is shared.
That said, it’s possible that the network had an automatic configuration script for the proxy that would have configured on connection under Windows systems and he just wasn’t aware that it would require manual steps on OSX? Still a bit ironic, but maybe excusable? I feel like if I managed a network with a proxy that would automatically configure on connection, I would understand the limitations of that setup, but that’s assuming a lot? I’d love to see their explanation on why that was her fault rather than theirs all the same, because the first thing I do after getting someone connected to a network is attempt to access something unlikely to be cached just so I can validate that the task was completed successfully.
I assumed that maybe (since they were colleagues) that they had some sort of training or provided documentation that says “set this proxy to connect”. And a tech literate person would know how, or figure out how to set the proxy. And this user did not.
If your kid can’t use wireshark, what’s the point?