The real challenge isn't how to do it, but how to do it so that someone who is reading your code doesn't realize the data is still available. That's the really tricky part.
While its generally true that the public key should be public, the issue then becomes just how do you know whose public key you are getting? You should attempt to authenticate that the key you have is indeed their key.
Actually, building houses in relatively pristine factories and assembling them on-site (modular housing) is becoming quite popular, even for higher end houses.
Maybe I just like Big Booms, but I think it might be quite interesting to try to slam this into the moon. Obviously they'd need to do the math to make sure it's not going to affect the moons orbit, but the moons gravity should be strong enough to keep most of the debris contained. We could probably learn a lot from observation, and if we have an active presence on the moon we could inspect the aftermath directly.
Most importantly of course: It would be a really big boom!
This is a common myth and it's false. If the GPL was invalidated all the code would be owned by it's authors and thier would be no legal way for anyone to use the code without the authors permission. The only time something becomes public domain is after a very long time or if the Author intentionally and legally releases it.
Althought there is plenty of useless crap that flows through digg and its cousins, chances are that any news that does interest me is going to show up there, no matter where it's from.
Science is only correct on questions which are within it's scope to answer. It can't answer (or provides what most people feel are inadequate answers) the questions that tend to matter the most to people. Questions like: "What is the meaning of life?", "Why do people suffer?", "Is there a God?" Science assumes, but can not prove (so far anyway) that supernatural things don't exist. I think the public became very disenchanted with science when they realized it couldn't answer these sorts of questions. They forgot that it provides very good answers to questions that may not be quite as profound, and some scientists seemed to think they can provide authoritative answers to those questions.
We really shouldn't kid ourselves though, for the most part, a life based on hard science just doesn't make most people happy. Given a choice between being correct and being happy, I'll choose being happy every time, and so will almost everyone else.
Actually the judge just said that they now had to start storing that information, which is very different. They were not penalized for not having them until that point. It was actually a pretty reasonable decision.
Unless there is a law that says you must keep logs (which I'm sure there are in many cases) you are perfectly free to wipe them until there is a court case, at that point you would probably have to keep them or be accused of destroying evidence.
I would think that once you got safely back to your home country you could sue them for any of your own documents that were copyrighted (preferably using the strongest way your country has to register a copyright).
I believe you are on to the real way to take care of drop-catchers. Simply don't publicize all the domains that expire. It's been a while since I've looked into the details, but I'm pretty sure plenty of registrars will provide a list of all domains about to expire and possibly even list domains that have just expired. If you simply outlaw the publication of expired or about to expire domains that would largely take care of the problem. You might need to take an extra step and not even include expiration information in whois information. The registrars would fight this though, they get most of their money from the drop-catchers.
There is a plugin for firefox to switch the current page to IE rendering, and can be done a a per-tab basis. I'm pretty sure you can specify certain sites to always load in IE mode. It might do the trick for you, it usually did for me when I needed IE, but not always.
Somebody went Googling for Comcast problems and didn't pay attention to the dates.
I know, it can sometimes be hard to figure out how old the information on a website is, but these are web forums with dates on each post! Those dates say 2005 and 2003! This is just a little bit old.
What's really strange is that the MS PowerShell is actually pretty impressive. It's a lot like most *nix shells except that it passes objects around instead of strings. It feels vaguely similar to Interactive Ruby to me. There are actually tasks in Exchange 2007 that can only be done in the shell (not in the gui) and many tasks are easier in the shell. They've even mimicked most of your standard bash commands. It knows what ls, ps and man are (among others).
It appears to me that MS is quite committed to letting people run gui-less servers now, and their doing a pretty decent job of it so far. They're doing a lot better job of that than they are with Vista.
Actually, some of the anti-spam laws may be the biggest problem for Comcast since they are sending data with false sender information. They can probably legally drop all the traffic they want, but forgery is a much bigger issue.
Well, there really isn't any disagreement that the NIV is a more textually accurate translation of the original Hebrew and Greek (although there is slight disagreement as to how important this is), as well as using more modern language (lots of disagreement on that one).
In general though, even the NIV isn't considered to be that accurate of a translation anymore. When it comes to accuracy to the original languages the NRSV (New Revised Standard Version) and NASB (New American Standard Bible) seem to be the most respected. Of course, the hardcore scholars just learn Greek and Hebrew.
Personally I rather like the New King James Version. It sacrifices some textual accuracy for literary flow. It makes for a very readable text which is still more 'accurate' than either the KJV or NIV.
We shall see what HL7 does. It has had a huge impact on the financial and billing side of things (although I still have to occasionally hand-edit hl7 files that aren't quite right), but it hasn't done much yet for the clinical side. The problem is that so much medical documentation is still very freeform. It's slowly getting much more standardized in physician offices, especially specialist offices, but general practitioners and (especially) inpatient hospital visits are still extremely freeform (and simultaneously drowning in thousands of different official forms).
That medical records are going electronic is a certainty, and generally a great thing. The question of if there will be any centralization of records is up in the air and industry trends are mostly against that. Most of the major Electronic Medical Records packages couldn't even export your data from one hospital and import it into another using the exact same vendor, much less try and import it from a different vendor. For most electronic records packages, if you ask for a copy of it you're just going to get a series of images or maybe a pdf, because that's all the export abilities the packages have. There are plenty of organizations (especially the govt) pushing for standardization, but it's going to be really difficult to pull off.
Slashdot Mirror
My 2-year old loves it...
http://www.hitachigst.com/hdd/research/recording_head/pr/PerpendicularAnimation.html
The real challenge isn't how to do it, but how to do it so that someone who is reading your code doesn't realize the data is still available. That's the really tricky part.
While its generally true that the public key should be public, the issue then becomes just how do you know whose public key you are getting? You should attempt to authenticate that the key you have is indeed their key.
Actually, building houses in relatively pristine factories and assembling them on-site (modular housing) is becoming quite popular, even for higher end houses.
Link to book "Modular Mansions" on Amazon:
http://www.amazon.com/Modular-Mansions-Sheri-Koones/dp/1586857126
Wrong. It is broken by design:
A Cost Analysis of Windows Vista Content Protection: http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html
Summary: Vista is spending a significant amount of resources making sure you aren't doing anything it doesn't like.
Maybe I just like Big Booms, but I think it might be quite interesting to try to slam this into the moon. Obviously they'd need to do the math to make sure it's not going to affect the moons orbit, but the moons gravity should be strong enough to keep most of the debris contained. We could probably learn a lot from observation, and if we have an active presence on the moon we could inspect the aftermath directly.
Most importantly of course: It would be a really big boom!
This is a common myth and it's false. If the GPL was invalidated all the code would be owned by it's authors and thier would be no legal way for anyone to use the code without the authors permission. The only time something becomes public domain is after a very long time or if the Author intentionally and legally releases it.
Well, until now it was generally consdiered an un-exploitable error. Now it's not. That changes things.
Well, someone else wanted to do it and then discovered that it's patented, so it's obviously not terribly unusual.
Althought there is plenty of useless crap that flows through digg and its cousins, chances are that any news that does interest me is going to show up there, no matter where it's from.
Check out MythBusters. One of them (I think it was Grant) beat the fMRI lie detector. None of them beat the traditional polygraph.
Science is only correct on questions which are within it's scope to answer. It can't answer (or provides what most people feel are inadequate answers) the questions that tend to matter the most to people. Questions like: "What is the meaning of life?", "Why do people suffer?", "Is there a God?" Science assumes, but can not prove (so far anyway) that supernatural things don't exist. I think the public became very disenchanted with science when they realized it couldn't answer these sorts of questions. They forgot that it provides very good answers to questions that may not be quite as profound, and some scientists seemed to think they can provide authoritative answers to those questions.
We really shouldn't kid ourselves though, for the most part, a life based on hard science just doesn't make most people happy. Given a choice between being correct and being happy, I'll choose being happy every time, and so will almost everyone else.
Actually the judge just said that they now had to start storing that information, which is very different. They were not penalized for not having them until that point. It was actually a pretty reasonable decision.
Unless there is a law that says you must keep logs (which I'm sure there are in many cases) you are perfectly free to wipe them until there is a court case, at that point you would probably have to keep them or be accused of destroying evidence.
IANAL
I would think that once you got safely back to your home country you could sue them for any of your own documents that were copyrighted (preferably using the strongest way your country has to register a copyright).
I believe you are on to the real way to take care of drop-catchers. Simply don't publicize all the domains that expire. It's been a while since I've looked into the details, but I'm pretty sure plenty of registrars will provide a list of all domains about to expire and possibly even list domains that have just expired. If you simply outlaw the publication of expired or about to expire domains that would largely take care of the problem. You might need to take an extra step and not even include expiration information in whois information. The registrars would fight this though, they get most of their money from the drop-catchers.
In most states the companies do not pay the unemployment benefits, the state does, so that part won't hurt IBM at all.
There is a plugin for firefox to switch the current page to IE rendering, and can be done a a per-tab basis. I'm pretty sure you can specify certain sites to always load in IE mode. It might do the trick for you, it usually did for me when I needed IE, but not always.
I believe the idea is to store them as data-DVD's, where it's just another way to store the bytes, in whatever format you want.
Somebody went Googling for Comcast problems and didn't pay attention to the dates.
I know, it can sometimes be hard to figure out how old the information on a website is, but these are web forums with dates on each post! Those dates say 2005 and 2003! This is just a little bit old.
What's really strange is that the MS PowerShell is actually pretty impressive. It's a lot like most *nix shells except that it passes objects around instead of strings. It feels vaguely similar to Interactive Ruby to me. There are actually tasks in Exchange 2007 that can only be done in the shell (not in the gui) and many tasks are easier in the shell. They've even mimicked most of your standard bash commands. It knows what ls, ps and man are (among others).
It appears to me that MS is quite committed to letting people run gui-less servers now, and their doing a pretty decent job of it so far. They're doing a lot better job of that than they are with Vista.
Actually, some of the anti-spam laws may be the biggest problem for Comcast since they are sending data with false sender information. They can probably legally drop all the traffic they want, but forgery is a much bigger issue.
Well, there really isn't any disagreement that the NIV is a more textually accurate translation of the original Hebrew and Greek (although there is slight disagreement as to how important this is), as well as using more modern language (lots of disagreement on that one).
In general though, even the NIV isn't considered to be that accurate of a translation anymore. When it comes to accuracy to the original languages the NRSV (New Revised Standard Version) and NASB (New American Standard Bible) seem to be the most respected. Of course, the hardcore scholars just learn Greek and Hebrew.
Personally I rather like the New King James Version. It sacrifices some textual accuracy for literary flow. It makes for a very readable text which is still more 'accurate' than either the KJV or NIV.
We shall see what HL7 does. It has had a huge impact on the financial and billing side of things (although I still have to occasionally hand-edit hl7 files that aren't quite right), but it hasn't done much yet for the clinical side. The problem is that so much medical documentation is still very freeform. It's slowly getting much more standardized in physician offices, especially specialist offices, but general practitioners and (especially) inpatient hospital visits are still extremely freeform (and simultaneously drowning in thousands of different official forms).
That medical records are going electronic is a certainty, and generally a great thing. The question of if there will be any centralization of records is up in the air and industry trends are mostly against that. Most of the major Electronic Medical Records packages couldn't even export your data from one hospital and import it into another using the exact same vendor, much less try and import it from a different vendor. For most electronic records packages, if you ask for a copy of it you're just going to get a series of images or maybe a pdf, because that's all the export abilities the packages have. There are plenty of organizations (especially the govt) pushing for standardization, but it's going to be really difficult to pull off.