I've been interested in this topic for a while, and I've found most people's responses to the question falls into 3 broad categories:
1) This is just tin-foil-hat paranoia. You're crazy. (This is by far the most popular choice.)
2) I'm unimportant. "They" wouldn't care about anything I do, so what does it matter?
3) Universal surveillance is a fact of life now. Deal with it, or move somewhere remote like Kamchatka and raise your children to believe civilization was destroyed by zombies.
Not in my jurisdiction. You're responsible for maintaining a safe distance to the vehicle in front of you, to allow for unexpected stops. It doesn't matter if they stop for a cat, a toddler, or hallucinated giant killer marmosets from outer space.
As far as I know, this is standard in driving laws across the U.S. Is there somewhere this doesn't apply?
I wound up doing this myself, after spending an undue amount of time struggling with a morass of insanely written Javascript. Fiddler proved indispensable for observing the actual interaction with the web server.
The goal, according to him, is to build models of every single person in the country, model the social graph, and be able to classify people as potential threats.
Another example of government waste and redundancy. We already have Facebook for this!
Foreshadowing aside, I neither expect nor care if my employer provides me with beverages. Not even coffee. If it's there, I'll probably take advantage of it from time to time, but it wouldn't actually influence my decision on where to work.
Yes, but it would have to be done on every system that I use to access my server. Also, not all systems use the standard openssh unix client, or they may not allow access to the user configuration files. So changing the port is just an annoyance, and it doesn't really accomplish anything. My real account is safe, and having a few failed login attempts for admin and root in my log file doesn't really bother me.
I am not advising against changing the port; it just has no value for me as I currently use SSH.
For a while, I put my home ssh server on port 443. It avoided the SSH credential guessing attacks, and still let me use a port that is allowed out by most firewalls.
However, I eventually went back to port 22, for several reasons. It's annoying to specify a port every time. A lot of networks transparently proxy port 443, which can cause problems with non ssl traffic. The login attempts were exclusively from bots trying known credentials, which will not work anyway. They are not a threat, just an annoyance.
Instead, I use the iptables limit feature to allow no more than 6 new TCP connections a second. This is more than enough for my purposes. Root login is disabled and I'm using a sufficiently complex password on my user account that I don't need to worry about brute-force guessing. Not that anyone has ever attempted such a thing on my home server, but now it will take too much time to be feasible.
I still get the login attempts, but they are much fewer now, and are no more than a curiosity in the auth.log file.
I have very little experience with Javascript. I come from a Python background. So please excuse my ignorance, but this doesn't sound like a designed language feature at all. These look like tricks that programmers discovered they could use to provide namespace separation.
Wouldn't it better if there were constructs built into the language to provide separate namespaces, in an obvious and coherent fashion?
1) This is just tin-foil-hat paranoia. You're crazy. (This is by far the most popular choice.)
2) I'm unimportant. "They" wouldn't care about anything I do, so what does it matter?
3) Universal surveillance is a fact of life now. Deal with it, or move somewhere remote like Kamchatka and raise your children to believe civilization was destroyed by zombies.