827 karma · joined October 13, 2011
Having said that, do use HTTPS when possible, but keep in mind some corporate environments force proxies that can see your traffic anyway.
As far as APIs, the good ones will hash your secret key together along with other data unique to your HTTP request, in particular the headers and the datetime. This is a good idea because: 1. you are not sending your secret key in clear text 2. it makes it difficult for a man-in-the-middle attack because they cannot just take your hash from one of your requests since it will be invalid after received or if some time has elapsed.
For an example, see how Knox sets up requests for Amazon AWS: https://github.com/LearnBoost/knox
Sorry but this statement doesn't ring true to me, because I know of several cases where two brothers have had divergent success outcomes based on their personalities and the choices they've made.
There's also MANY ways to forge your own connections in life.
Also, the one comment you're referring to referenced an OD patient being physically restrained by medical staff -- are you going to tell me this is sufficient anecdotal evidence to make her a threat to other students?
[1] http://www.nursingtimes.net/survey-finds-worrying-number-of-...
Certainly in this case the girl wasn't a direct threat to anyone else, the only threat I see here from the University's perspective is to their image as an institution that admits "cutters".