To store files close to a petabyte, you need a petafile, obviously.

The Court ruled in Banks v Manchester that case law cannot be copyrighted. The ruling was that writings by a government official, acting in their official capacity, are owned by the public and cannot have copyright protection. That case also brought up a question relevant to this case. Under federal law citizens and residents may hold copyright. Georgia is probably neither, and therefore arguably cannot hold copyright.

In the Banks case, the state had contracted with someone else to produce indexes, etc. The deal was that if the company wrote these extra pieces, they would have copyright protectionfor a couple of years - they didn't get paid to write them, but were allowed exclusive right to sell their version with indexes, etc. The indexes and such were the original work of that citizen. That original work, but not the law itself, could be copyright the author.The finding in this Georgia case may hinge on who wrote the annotations. If government officials wrote them, it's public domain. If a private company wrote the annotations in order to sell them, they may be allowed to do so. HOWEVER, the fact that the STATE is suing indicates the state claims copyright for themselves, and the state will probably lose.

Also, the Court will probably want the law to be accessible, so they'll likely find some logic to rule against the state. Consider the Obamacare care case. The court ruled that the IRS "penalty" for not having insurance is a tax, and therefore within the powers granted to the feds, while also ruling is NOT a tax, and therefore didn't have to originate in the house of representatives. So in the very same ruling they said "it's a tax ... it's not a tax". Translation: we don't want to go head to head with the Obama administration on this one. They sometimes FIND a way to rule whichever way they want to rule, whether of makes any sense or not.

In ten years you've not had any servers with any kind of network problem, firewall issues, or "won't boot" kind of issues? Clearly any of those would prevent you from using SSH, so would have to be fixed from the console (possibly with a KVM extending the console physically).

I suppose if you only manage one server and never touch it, it might never have any network problems or boot failures.

Your refrigerator, washing machine, and other household appliances run on inductive motors which use a thousand watts or so to generate electromagnetic fields strong enough to pull the magnets in the motor strongly enough to move 80 pounds of water and clothes. So those are electromagnetic fields in the kilowatt range.

Charging your phone requires around five watts or so. So the power levels, the amount of electromagnetic energy, is quite small - much smaller than the difference between a large washing machine and a small one.

If you live in an apartment, your neighbors also hqve a refrigerator on the other side of the drywall, an air conditioner with a couple of large motors, etc. Not to mention wireless routers and devices, cordless phones, microwave ovens, etc. Oh, qnd you carry an electromagnetic transmitter in your pocket, one inch from your junk.

There are certain higher frequency ranges which have some risk, but these devices probably won't use those frequencies. Lower frequencies are generally better for short distance because you get the "near field", the more efficient inductive transfer rather than the less efficient radiative field.

What's relevant here is the password/passphrase you'd use if you were at the console, using a keyboard attached to the machine. So ssh keys, while a good idea, don't apply in this instance.

Note to exploit this would require that you used a dumb password on that critical server, connected it's management ports directly to the internet, and failed to use any monitoring software like fail2ban.

In such a scenario, so sshd is going to save you. Any will have some imperfection. On our critical servers, sshd runs on a non-standard port, so script kiddies never find it, we use good passphrases they wouldn't guess anyway, we installed fail2ban so they'd get blocked when they started trying, and recently we starting putting ssh behind an openwrt vpn. So there are four reasons we're not worried. Try using at least two of these four protections:

Good passphrases (not "qwerty" or "admin")
Non-standard port
Fail2ban
If you're really serious, vpn first

The local numbers show that admissions did not increase during the period in which fracking was introduced, and that certain zip codes (rural areas) has higher admissions first, then later got wells. As wells were built, health improved - probably because it brought jobs, which improves the local economy.

The study authors say there was no fracking in 2007, and lots in 2011.

They then say (quoting):
"The inpatient rates are relatively stable from 2007â"2011 Indeed, the average overall inpatient prevalence rates for 2007â"2011 are, respectively, 15.18, 15.30, 14.86, 14.00, 14.25"

So the introduction of fracking did NOT increase hospital admissions. Indeed, over the four year that the economy in the area got a boost from fracking, people got healthier, according to the numbers in the study.

Then then do a bunch of gymnastics to discover, then obscure, the fact that oil wells tend to be located in more rural areas, and people's health tends to be slightly worse in those areas.

> It isn't clear that there were lots of options from the video - perhaps move ahead a foot but it seems like that would at best delay the crash). There were two cars stopped at the light, the Google car was behind it

The way most people drive, they wouldn't have any option to avoid the crash. According to the video, though, the Google car did better. It did as taught is advanced driving classes and left enough room that it could have pulled to the right, into the turn lane, and even driven away, as it detected the fast-moving car approaching from behind. That's taught as a more safe way to stop - think car jackings, a cement truck coming up fast from the rear, or an ambulance trying to get through. You can get out of the way or leave the area entirely if you leave six to eight feet between you and the car ahead.

> My partner uses Mac with _MS_Office_ on it, and I have to correct every document

I have people using different versions of MS Word and I too have fix documents, using Libreoffice to convert them to a newer version of Word. The new version of Word doesn't import older Word documents correctly, but Libreoffice does.

Think about your statement- you said you have to use MS Word because MS Word breaks things. If your partner used Libreoffice, you wouldn't have to correct every document. Just try it and see if it's not better than what you're currently doing.

Jobs have been automated millions of times. Every time, it's the same cycle, with on variation that happens often, but not always. The demand for goods and services is not perfectly elastic, so increased productivity for a specific task very often results in fewer people being employed at that precise task. As an example, milking machines mean that fewer people are needed to milk cows.

However, prices ARE somewhat elastic, so as the increased productivity reduces the price of milk relative to substitute goods, more milk is purchased. That increases the demand for dairy inspectors, milking techs, cheesemakers, etc. The net result is that a portion of the workforce moves from the simple job which a machine can do (and which is low paid) to the jobs which require human judgement, such as dairy inspectors.

We've been through this for every machine we have. The industrial revolution is the period in which many, many tasks formally done be humans began to be done by machine. And the standard of living improved by an order of magnitude.

For hundreds of years now we've been getting more and more machines every month. We've done, and the results are in.

>. There have been a couple of subjects, my Ph.D is in Applied Mathematics, where I can trace it to the source (or what appears to be the source) where somebody either did not know, made a mistake, was willfully negligent, or just failed to communicate well.

That reminds me of some .htaccess rules I posted back in the 1990s. Several other web sites immediately copied-pasted it, without link or attribution. A couple of weeks later, I found an error in my code and fixed it. I couldn't fix the dozen or so sites, some very popular, who copy-pasted me, nor the hundreds of sites who copy-pasted from the first generation of copiers. Seventeen years later, most sources which show how to prevent hot linking still include my original error - an error I corrected in 1998. Which means most web sites which attempt to prevent hotlinking are affected by that error I briefly had on my site.

So yeah, I'm the erroneous source. :)

What fine are you talking about? This isn't a case about a crime. If you bump my car in a parking lot and it costs $200 to fix, you owe me $200. It doesn't matter how my you make - if you dent my car, you get it fixed, simple as that. That's called "damages". Same here - the plaintiff claims that Apple's conduct caused financial damage to their business, so Apple needs to make it right by paying the amount of the damage. It called "making the plaintiff whole", restoring them to the same condition they would be in had the event not occurred.

Splendid post. You might, however, want to include a potentiometer with those microphone jack leads. That way you won't be applying 120 volts to an input designed for less than 100 MILLIvolts.