Not really sure what I'm saying, or what point I'm trying to make. I do think the world would be a better place if people consumed less caffeine.
The world might be a better place with you and I consuming less caffeine, but that's definitely not true for everyone.
I think that only applies if you drink coffee black, and that is a very small group of people. Also, I don't think caffeine is a bennefit. Decaf coffee works just as well.
I see that with chocolate too. There may be some benefits to eating chocolate, but calling "milk chocolate" chocolate should be a crime. "A glass and a half of full cream milk in every block" is the stupidest thing ever.
I don't look at the logs so I'm not annoyed. Problem solved.
The other problem is when you have a device like an old wrt54gl which has to perform unnecessary work (and therefore gets hotter than it needs to) when trying to deal with several password attempts a second.
Changing the port to something like and rate limiting it from unknown addresses makes a huge difference.
I agree with not looking at the logs though, or at least in the default configuration. How is knowing that someone failed to log in a useful thing to know? That's just the security system doing it's job and is just noise. What you want to log is the successful logins from remote IP addresses that haven't been seen before, or have previously been seen trying many incorrect combinations of username and password. That's a significant event.
How so? You lock up an account after a few password failures. Why would it matter where the attempt is made. They'd have to try getting in with other accounts.
David has to unlock his account a few times a week because of rules like this.
It's still just going after low-hanging fruit. Anyone weth any real awareness of security does now allow password-only SSH connections anyway. Key based auth and fail2ban is pretty much required these days. You can always add some port knocking to obscure it a bit if you don't like reading about failed access attempts.
There is nothing magical about keys, they are nothing more than very very long passwords that you can't type in if you ever need remote access from a machine that doesn't have your private keys on it.
If your passwords are good then ssh bots won't guess them, and fail2ban will make sure they don't get enough attempts to try.
They say to expect a Tunguska sized one once a century and this one wasn't that big. They mostly ocean explode or strike so there's few signs of them but an ocean strike can be worse than a land one given the water they displace. They've got to wake up and start properly funding the near Earth program. It still won't protect against rouges but at least they can map ones that cross our orbit.
Such a program was secretly implemented by the US over a decade ago, and they can indeed manipulate small asteroids. Ask yourself this - where did this one hit? Was it somewhere in America?
The justice system shouldn't be haggling over price.
They have suspects they are sure that did it. They have a method of determining which one, but they are dicking around because of cost?
Unacceptable.
Totally unacceptable. The possibilities are:
1. Let both men go free. Assaults will continue. And the innocent brother (assuming one is innocent) will be an outcast (so will the guilty one, but he deserves it so we don't care about him).
2. Imprison both men. Also unacceptable. Even if it turned out both are guilty it still needs to be proven.
3. Do the tests. Guilty party pays costs (TFS doesn't say if they are a millionaire or not, but lets assume they are). Justice is done.
The only problem is if the "at least €1M" escalates to "more than €10M" and still doesn't find the outcome beyond reasonable doubt.
Without vigilance, there might be a widespread problem with people getting these vaccines against their will.
Better than them drinking alcohol against their will, which is essentially what alcoholism amounts to.
This is a problem. The computer doesn't know what is going on. if i press "stop" the car should fucking STOP, because I'm the one who knows the circumstances. Trying to cater to dick-heads doing the wrong thing at the expense of people who get fucked over in an emergency is entirely the WRONG thing to do.
Do the math. There are more dickheads than people who find themselves in an emergency where pressing the stop button at 60mph is a sensible thing to do. In this litigious culture we've created the only sensible action is the one that will get you sued the least.
And even for you - presumably not a dickhead - you're probably still safer. You're more likely to be taken out by someone hitting the stop button at high speed and finding that suddenly their brakes and steering aren't as responsive than you are to find yourself in an emergency where you need to hit the stop button.
This car doesn't have a "key", it has a button that says "Start/Stop".
And no sensible car computer will let you press "stop" at 60mph.
If you have insurance, no reason not to get a doc's advice. That said, I have been using the workrave app for about 5 years now and I think it has saved me from significant deterioration. It has both 'nix and Windows implementations. Basically reminds you to take a micro break every 5 minutes and a coffee break every ten. I manage to keep working during these breaks. Usually it is a phone call or a convo with the boss or a colleague. And you can always count on a meeting as a good opportunity for a break.
Best piece of nagware out there IMHO.
Sounds like a neat idea. If you were actually getting a new coffee every 10 minutes you would probably approach a lethal dose pretty quick though
The global economy is worth almost $70 trillion dollars; a sudden influx of 0.27% of that amount would have negligible impact on the value of goods and services.
The realised possibility of mining asteroids might have an impact though. Eventually.
And also, haven't you seen a progress dialog go from "30 seconds remaining" to "2 hours remaining"? Dynamic recalculation sometimes doesn't help and just makes the problem appear worse.
This is a problem with the developers of the progress bar (and their managers). "2 hours remaining" isn't a progress report. "28% complete" is a progress report. It's more accurate, it never goes backwards, and it splits the workload more effectively: the computer can calculate how much it has done, and the human can do some simple extrapolation to guess how long it will take, in a human time scale. That's not "20 minutes" or "2 hours", that's "quick enough to sit and watch the progress bar", or "enough time to take a leak / make some coffee", or "time to check my email / facebook". "2 hours remaining... no wait, 5 seconds remaining... no wait, it'll never finish!" is bullshit coming out of the program, and we all know it. So just cut the bullshit and let the progress bars indicate progress.
But even that's wrong. 28% of what? Total number of files? Total amount of data? If you're copying a large number of files then the effort required to gather this info is significant too. Also, the computer does this so called "simple extrapolation" to determine how much time is remaining and it gets it wildly wrong so why do you think you'd be any better?
In most cases there already is a progress bar anyway, fwiw. There may be no % figure given, but that matters not so much. And many times i've seen the progress bar get almost all the way to the right and just sit there for ages.
At some Microsoft conference I attended the presenter just said 'fake it' (wrt progress bars, not "time remaining"). Take a vague stab at the amount of time the task will take, and make the progress bar fill 50% in half that time. Then do it again for the next 25%. And so on. If the task finishes just move the progress bar to 100%.
The computer is able to measure it's data throughput, read/write times, etc. Whether programmars actually do this measurment I don't know. But if the computer knows how fast it is reading or writing a disk or transferring over the LAN then there is no reason why it shouldn't be able to make those calculations. Even if the environment changes from task swapping or adding overhead or whatever then the measurement, being dynamic, can be recalculated on the fly and the 'finish time' updated accordingly.
Mandatory Car Analogy: I know that if my speedometer indicates 60 miles/hour, that in one minute I will have travelled one mile. That's predicting the future son!
Sometimes the measurement takes a significant chunk of the progress time so its best not to bother.
Windows tries to do this measurement sometimes ("Preparing to copy..." etc) and still manages to screw it up, and for all the bad things people say about Microsoft at the upper levels of management, the programmers there aren't stupid. If it hasn't been done in 25 years then it should be self evident that the problem is hard to solve.
Why it's hard to solve is an interesting discussion to have, but stating that it's not hard to solve flies in the face of many years of evidence to the contrary.
And also, haven't you seen a progress dialog go from "30 seconds remaining" to "2 hours remaining"? Dynamic recalculation sometimes doesn't help and just makes the problem appear worse.
And if you want a car analogy, a better one is your car telling you how many km you can do until your tank is empty.
Always draw your curves, then plot your reading.
