If anything, this would be a GOOD thing. You should not have any free flowing heavy metals in your blood. If you do, your kidneys are probably about to explode.
To turn it off (try it in an XP VM, if you refuse to believe truth): 1. Run TweakUI 2. Click on "General" (the second item in the left hand pane) 3. Scroll the "Settings" list in the right hand pane. 4. The next to last item is "Optimize hard disk when idle".
That only "backs up" against drive failure. What happens if something gets deleted? What happens if a process goes mad and scribbles all over something important? What if someone breaks in?
The only problem would be that just using https does not tell anything about the connectionsactual security.
Of course not. That's the job of the browser. It's not the protocol's fault the browsers don't do it. The CA break-ins are all political problems really - those who were trusted betrayed that trust in one way or another.
The.secure domain is only different because people can just assume it is secure, even before clicking.
You are forgetting about SSL?.secure will be mandatory vetted SSL, combined with it's own domain TLD? Eg, that certificate can't be used by a.com, which is not as vetted.
I see no reason why it should. All that does is set up an HTTP redirect (which if you think about it for more than half a second is pretty much exactly like clicking a link)
Slashdot Mirror
I suppose the point was that you weren't supposed to be able to register .pro domains without actually having some means to vette your profession?
I'm not the person to ask.
Wrong. The iron in hemoglobin is not magnetic.
The iron in your blood is not magnetic.
If anything, this would be a GOOD thing. You should not have any free flowing heavy metals in your blood. If you do, your kidneys are probably about to explode.
Certainly doesn't replace a backup, but that's good to know about.
I assume these shadow files are counted as free space? Eg, when you actually do need the room they "make way" for the new data?
I didn't say schedule.
To turn it off (try it in an XP VM, if you refuse to believe truth):
1. Run TweakUI
2. Click on "General" (the second item in the left hand pane)
3. Scroll the "Settings" list in the right hand pane.
4. The next to last item is "Optimize hard disk when idle".
The "value" of gold is just as arbitrary.
... as opposed to what? The Yen? Ruble? Yuan? Peso?
Newsflash: things are worth what people are willing to pay.
Dog shit would be worth $100/kg if people would buy it.
Unless we just don't hear about it, or they always go for those low hanging fruits figuring it's easier.
FYI, its "kudos"
Windows, since XP, defragments the filesystem when idle.
You can turn this off via TweakUI for XP, I know this. Not sure how to do so on Vista/7.
And if you are smart and have previous backups and/or incrementals, you can get what you need without bringing the virus along for the fun.
That only "backs up" against drive failure. What happens if something gets deleted? What happens if a process goes mad and scribbles all over something important? What if someone breaks in?
Can I have both? Can I have a drive that, on that one minute warning, immediately flushes it's cache and goes offline?
It would make recovery after replacement much smoother. Clone and go, no worries about incomplete writes etc.
Which is why DNSSEC is supposed to be enforced for it, because that stops those kind of shenanigans if people bother to implement it.
It is nonsense.
What is happening now doesn't go back and change what has already happened.
You must not be seeing the AC's whole post. It starts with this, which tells you exactly what it is:
Recall the ".pro" TLD? Supposed to be for "vetted professionals"?
... and how would it be detected or prevented? You don't seem to understand much of the actual technologies involved, here.
The only problem would be that just using https does not tell anything about the connectionsactual security.
Of course not. That's the job of the browser. It's not the protocol's fault the browsers don't do it. The CA break-ins are all political problems really - those who were trusted betrayed that trust in one way or another.
with PCI regulations enforcing
BWAHAHAHAHAHA!
If only you knew what an insider knew.
.con should be a CNAME to .com at the root (.) level :P
Erm, did you even read what you just quoted? The first sentence defines it.
Have you ever seen those domains used? No? That's my point. Nobody uses them because they are a pain in the ass.
The .secure domain is only different because people can just assume it is secure, even before clicking.
You are forgetting about SSL? .secure will be mandatory vetted SSL, combined with it's own domain TLD? Eg, that certificate can't be used by a .com, which is not as vetted.
I see no reason why it should. All that does is set up an HTTP redirect (which if you think about it for more than half a second is pretty much exactly like clicking a link)
Yet another case of "this is why we can't have nice things."