It's usually "cleaner" if you either don't out-source sensitive data or if you out-source it in a way that is either 100% encrypted and you hold the only keys or if it's stored in an "identifiable" physical place ("it's on THAT set of hard drives, and it's being processed on THAT set of CPUs" etc.) that isn't shared with other users.
No, Br'er Rabbit, don't tell the world we are hiding our data, they might get copies and make sure the whole world has access to it, no, don't do that Br'er Rabbit.
OK, that may not work in an outdoor area like an oil-well site or industrial plant and you might have to turn your nice windowed office into a windowless fortress, but it is possible to stop cell phones without resorting to jammers.
Tinfoil hat = cellular-blocking paint or other building-covering. It's not necessarily cheap but it's probably cheaper than FCC fines.
Those neighborhoods where demand for high-quality service is "high" will get cheap Internet.
To make up for lost revenue in "Google Fiber" cities, nationwide ISPs will likely scale back infrastructure improvements elsewhere and/or raise prices where they still have effective monopolies/cartels.
They will also be more careful about investing "for the long term" if they know someone like Google can come in at any time and make their investment worth less than they expected it to be.
I once worked for a company where you had to put in years in the industry (and usually the company) before you got to the upper echelons of the "technical" (non-management) career chain.
Yes, you might get some shortcuts if your boss thought you were a "golden child" but before you made your way to the upper decks, you had to prove yourself over and over again with a lot higher of a success ratio than a "normal" person would have.
This pretty much stalled the careers of those whose gold was just a thin veneer before they hit the highest ranks.
Until the only jobs I can get don't pay a living wage or are so physically or emotionally hazardous that either regulation or unionizing is the best way to stop it, I do NOT want to work in a union shop.
Unions are great to keep employers from treating people as less than human. They are great if employers are making you sacrifice your family. They are great if employers are paying you $7.25/hour and think you should be grateful your job isn't outsourced to $OTHER_COUNTRY.
But that's not the world I live in.
As a person with a technical background in a metro area that isn't deep in recession, I have options. I can CHOOSE to work for a startup 24/7 and sacrifice my family and personal life for stock options that might never be worth anything. I can CHOOSE to freelance and actually make a survivable wage. I can CHOOSE to work for another company knowing that any full-time job I get will earn me several times the US federal poverty level for 1 person and enough to maintain a middle-class lifestyle for a family of 4.
As long as I and others in the industry have those choices, I don't see the benefits of unionizing outweighing the downsides.
If so, taller people, who tend to be heavier than shorter people, will sue for discrimination based on the "handicap" of being tall.
They may not have to sue the airline, they may sue the regulatory agency asking for a court order for the agency to rescind the permission it granted the airline to use this fare structure.
With a few exceptions, like not calling the police when you know a serious crime almost certainly WILL happen if you don't or when it's one of those "mandatory reporting" crimes like child abuse, you have the moral right to not speak up. Free countries generally give you the legal right to do so as well.
Now, on its face, the law that says you have to report if you KNOW that a compartment you are being asked to build WILL almost certainly be used to transport drugs falls into this category.
HOWEVER, transporting drugs is not the same as transporting cash, and I'm not sure he knew for certain that the secret compartment he built would be used to transport drugs, as opposed to contraband or even legally-obtained currency.
Morally speaking, the proper charge in cases like this, where you are providing an otherwise-legal service to someone who you reasonably suspect has non-specific felonious intent, is not conspiracy or failure to report. Rather, it's a special case of "aiding and abetting," where the punishment should be based on the lesser of what YOU got out of it (i.e. how much you stood to gain, with some minimum fine if you were "just helping a friend" and didn't gain anything) or the severity of the crime that you enabled. If you net $5 for selling a "suspicious" guy a gun and he winds up shooting the President and your participation didn't rise to the "normal" rules of being a co-conspirator, you shouldn't get much punishment, as you didn't gain much. In fact, your punishment on this charge may be less than the punishment you got for not doing proper background checks on the buyer. If you net $1M for giving a guy a gun and he is arrested for a minor felony gun-possession charge, your punishment on "aiding and abetting" should also be very light, as no serious crime was committed.
If you just want "archival, for the next 5-10 years, then redo it all over again as technology changes" then the other answers in this thread are what you want.
If you want "archival, for 20+ years, without having to do it over every 5-10 years" then some form of human-readable plain text or at least representeded-as-plain-text-for-attachments is what you want. Make sure all file attachments are in well-documented formats (e.g. JPEG) so someone will be able to write a decoder for them 20 years from now if one isn't readily available. If they aren't, be sure to store file-format information with your archive.
If you want "archival, for 200+ years" the you want all of the above, stored on archival media that are likely to be readable 200+ years from now along with a description of how to interpret html and file attachments. Archival paper, archival microfilm, archival "etched onto plastic but microscopicly" media, etc. are what you want.
If you want "archival, for 20,000+ years" then talk to the people who are working on how to label long-term (10,000+ -year) nuclear waste storage dumps, they may have some ideas that work.
If you want "archival, 2M+ years" then I'm out of ideas. Look me up in 2M+1 years and tell me what you found that worked for you.
Do "It's in the Bible, therefore it's true" literalists do with passages like Mark 16:9-20 and other verses where scholars disagree about whether the text is "in" or "out"?
What happens when two Bible literalists who disagree about whether a given passage is "in" or "out" debate? Do they call each other heretics?
Is that the marginal cost of production, the amortized cost of production (i.e. sunk costs spread out over the entire production run), or the amortized costs of production, marketing/sales, support (warranties aren't free, folks), etc.?
Those people definitely seem to be out of touch with reality there, at least politically speaking.
Kind of reminds me of people who try to claim allodial title to their land without the recognition by the international community as a sovereign state to back it up.
You can even do it on a per-user or even per-subdirectory basis by using NTFS mount points, but that can be a bit more confusing if you forget what's mounted where.
Some programs have their own notion of what a "user" is and store all users' data in a central location OUTSIDE of where Windows stores its user profiles.
This MAY wind up being on the C:\ drive.
"Temporary" copies of user data may also wind up on the Windows system drive, Windows Boot drive, or even the C:\ drive (yes, even if you "Boot" from "D:" some old programs have C:\ hard-coded into them, sigh).
And of course, pagefile.sys, hiberfil.sys, and similar files are by default also on the Windows system drive or Windows Boot drive.
There are no doubt many other one-off cases to watch out for as well. The moral of the story: Know your software and what it is really doing behind the scenes or be prepared to be surprised.
It's usually "cleaner" if you either don't out-source sensitive data or if you out-source it in a way that is either 100% encrypted and you hold the only keys or if it's stored in an "identifiable" physical place ("it's on THAT set of hard drives, and it's being processed on THAT set of CPUs" etc.) that isn't shared with other users.
No, Br'er Rabbit, don't tell the world we are hiding our data, they might get copies and make sure the whole world has access to it, no, don't do that Br'er Rabbit.
OK, that may not work in an outdoor area like an oil-well site or industrial plant and you might have to turn your nice windowed office into a windowless fortress, but it is possible to stop cell phones without resorting to jammers.
Tinfoil hat = cellular-blocking paint or other building-covering. It's not necessarily cheap but it's probably cheaper than FCC fines.
Those neighborhoods where demand for high-quality service is "high" will get cheap Internet.
To make up for lost revenue in "Google Fiber" cities, nationwide ISPs will likely scale back infrastructure improvements elsewhere and/or raise prices where they still have effective monopolies/cartels.
They will also be more careful about investing "for the long term" if they know someone like Google can come in at any time and make their investment worth less than they expected it to be.
Reading only half a headline can make your head spin.
I once worked for a company where you had to put in years in the industry (and usually the company) before you got to the upper echelons of the "technical" (non-management) career chain.
Yes, you might get some shortcuts if your boss thought you were a "golden child" but before you made your way to the upper decks, you had to prove yourself over and over again with a lot higher of a success ratio than a "normal" person would have.
This pretty much stalled the careers of those whose gold was just a thin veneer before they hit the highest ranks.
Until the only jobs I can get don't pay a living wage or are so physically or emotionally hazardous that either regulation or unionizing is the best way to stop it, I do NOT want to work in a union shop.
Unions are great to keep employers from treating people as less than human. They are great if employers are making you sacrifice your family. They are great if employers are paying you $7.25/hour and think you should be grateful your job isn't outsourced to $OTHER_COUNTRY.
But that's not the world I live in.
As a person with a technical background in a metro area that isn't deep in recession, I have options. I can CHOOSE to work for a startup 24/7 and sacrifice my family and personal life for stock options that might never be worth anything. I can CHOOSE to freelance and actually make a survivable wage. I can CHOOSE to work for another company knowing that any full-time job I get will earn me several times the US federal poverty level for 1 person and enough to maintain a middle-class lifestyle for a family of 4.
As long as I and others in the industry have those choices, I don't see the benefits of unionizing outweighing the downsides.
HP can call theirs the OpenHighPile. RackSpace can call theirs OpenRackStack, etc.
Universities need accreditation.
Will future journals need accreditation or at least some kind of "grade" from a recognized, trusted "grader?"
FAT Crab People.
Government to admin: Delete this article or suffer the consequences, and don't tell anyone why, or suffer additional consequences.
Admin: *delete article*, leaving bogus or meaningless log entry.
Wikipedia editors: *Open deletion review and/or file a formal complaint against administrator*
Fellow administrators: Why did you delete the article?
Administrator: "I can't tell you" or simply silence.
End result: Article restored, administrator possibly loses administrator privileges. Administrator's wiki-reputation unjustly in shambles.
http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Bulletin_des_administrateurs
Translated:
http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Ffr.wikipedia.org%2Fwiki%2FWikip%25C3%25A9dia%3ABulletin_des_administrateurs
Scroll down to
Wikimedia Foundation elaborates on recent demand by French Governmental agency to remove Wikipedia content
Version as of 1 April, still current as of a few minutes ago:
http://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Bulletin_des_administrateurs&oldid=91565146
Translated:
http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Ffr.wikipedia.org%2Fw%2Findex.php%3Ftitle%3DWikip%25C3%25A9dia%3ABulletin_des_administrateurs%26oldid%3D91565146
The US government recently gave them permission to use this fare structure for flights to/from American Samoa.
They've been billing this way in Samoa proper since last year.
Memo to self: Preview when copy-and-pasting with non-standard characters.
That was supposed to be Andr(e')-Marie Amp(e`)re, sort of.
If Collin Cunnigham plays André-Marie AmpÃre, who will play Charles Coulomb?
Does the ADA apply to American Samoa?
If so, taller people, who tend to be heavier than shorter people, will sue for discrimination based on the "handicap" of being tall.
They may not have to sue the airline, they may sue the regulatory agency asking for a court order for the agency to rescind the permission it granted the airline to use this fare structure.
With a few exceptions, like not calling the police when you know a serious crime almost certainly WILL happen if you don't or when it's one of those "mandatory reporting" crimes like child abuse, you have the moral right to not speak up. Free countries generally give you the legal right to do so as well.
Now, on its face, the law that says you have to report if you KNOW that a compartment you are being asked to build WILL almost certainly be used to transport drugs falls into this category.
HOWEVER, transporting drugs is not the same as transporting cash, and I'm not sure he knew for certain that the secret compartment he built would be used to transport drugs, as opposed to contraband or even legally-obtained currency.
Morally speaking, the proper charge in cases like this, where you are providing an otherwise-legal service to someone who you reasonably suspect has non-specific felonious intent, is not conspiracy or failure to report. Rather, it's a special case of "aiding and abetting," where the punishment should be based on the lesser of what YOU got out of it (i.e. how much you stood to gain, with some minimum fine if you were "just helping a friend" and didn't gain anything) or the severity of the crime that you enabled. If you net $5 for selling a "suspicious" guy a gun and he winds up shooting the President and your participation didn't rise to the "normal" rules of being a co-conspirator, you shouldn't get much punishment, as you didn't gain much. In fact, your punishment on this charge may be less than the punishment you got for not doing proper background checks on the buyer. If you net $1M for giving a guy a gun and he is arrested for a minor felony gun-possession charge, your punishment on "aiding and abetting" should also be very light, as no serious crime was committed.
Now I have to open every article to read it.
At least I knew they would be worth reading.
Next year go for funny + !annoying.
Nevermind, that just sounds sick.
If you just want "archival, for the next 5-10 years, then redo it all over again as technology changes" then the other answers in this thread are what you want.
If you want "archival, for 20+ years, without having to do it over every 5-10 years" then some form of human-readable plain text or at least representeded-as-plain-text-for-attachments is what you want. Make sure all file attachments are in well-documented formats (e.g. JPEG) so someone will be able to write a decoder for them 20 years from now if one isn't readily available. If they aren't, be sure to store file-format information with your archive.
If you want "archival, for 200+ years" the you want all of the above, stored on archival media that are likely to be readable 200+ years from now along with a description of how to interpret html and file attachments. Archival paper, archival microfilm, archival "etched onto plastic but microscopicly" media, etc. are what you want.
If you want "archival, for 20,000+ years" then talk to the people who are working on how to label long-term (10,000+ -year) nuclear waste storage dumps, they may have some ideas that work.
If you want "archival, 2M+ years" then I'm out of ideas. Look me up in 2M+1 years and tell me what you found that worked for you.
Do "It's in the Bible, therefore it's true" literalists do with passages like Mark 16:9-20 and other verses where scholars disagree about whether the text is "in" or "out"?
What happens when two Bible literalists who disagree about whether a given passage is "in" or "out" debate? Do they call each other heretics?
Is that the marginal cost of production, the amortized cost of production (i.e. sunk costs spread out over the entire production run), or the amortized costs of production, marketing/sales, support (warranties aren't free, folks), etc.?
Those people definitely seem to be out of touch with reality there, at least politically speaking.
Kind of reminds me of people who try to claim allodial title to their land without the recognition by the international community as a sovereign state to back it up.
You can even do it on a per-user or even per-subdirectory basis by using NTFS mount points, but that can be a bit more confusing if you forget what's mounted where.
Some programs have their own notion of what a "user" is and store all users' data in a central location OUTSIDE of where Windows stores its user profiles.
This MAY wind up being on the C:\ drive.
"Temporary" copies of user data may also wind up on the Windows system drive, Windows Boot drive, or even the C:\ drive (yes, even if you "Boot" from "D:" some old programs have C:\ hard-coded into them, sigh).
And of course, pagefile.sys, hiberfil.sys, and similar files are by default also on the Windows system drive or Windows Boot drive.
There are no doubt many other one-off cases to watch out for as well. The moral of the story: Know your software and what it is really doing behind the scenes or be prepared to be surprised.