You rather missed the entire point. The system disk, and EFI, are read-only, controlled from OUTSIDE of the operating system. You use the SAN or hypervisor to set it read-only. Sure Windows knows how to write FAT32, but that doesn't make it able to write to media which doesn't accept writes.
In his first two years, when the dems had full control,of the houee and senate, he made the economy significantly WORSE. When unemployment is high is not the time to focus on adding historical new burdens to hiring, such as Obamacare. You may remember his campaign commercials on radio when he planned to "go after companies". That's not how you stimulate business.
You can't blame that on republicans obstructing his agenda when his party had full control of the house, senate, and white house.
Things started to get closer to normal only AFTER the republicans started checking his war on business.
BIOS is dead. With EFI, most of the boot code is in the efi partition, on the "disk" which is read-only courtesy of your san, hypervisor, or the fact that it's a cd-rom.
There is a limited firmware on the motherboard which loads the initial efi file. That could, in theory, be compromised, except that if you virtualize, you could also set that read-only in the hypervisor. So your virtual machine pretty darn safe. The host machine needs to be secured , but it doesn't need an operating system, just a hypervisor. That's quite a bit safer than running a full desktop OS.
That said, it's not too hard to have a version such that you know it's unaltered when you boot each morning. You do basically a live CD, booting from a read-only lun.
Just as you separate a normal user USING the machine from an administrator account UPDATING the OS, you can have the OS basically read-only during use and set it to writeable only when you need to update the software. That change is done outside of the OS, either via the NAS or the hypervisor.
In that way, you can come in eqch morning knowing your Windows system hasn't been hacked (past tense). As soon as you open IE, though, you could get a new exploit. That exploit disappears when you shut the machine down, though.
No, it was a Kim Dotcom reference. He got the GUILTY license plate. That and similar "rub their nose it" actions didn't help his relationship with law enforcement and the courts.
I WAS not saying that using Tor indicates that one might be doing something shady, but I'll say it now. People using the internet in the clear, not using Tor , are doing something shady maybe 1% of the time. On Tor, maybe 80% of the traffic is shady. So arithmetic tells us that Tor traffic is 80 times more likely to be shady than non-Tor traffic.
Which is why if I were the NSA, FBI, or ONI, I'd run most of the Tor nodes or otherwise ensure that I could map all Tor traffic. That's the fundamental weakness of Tor - it protects against ONE node spying on you, by assuming that MOST nodes are friendly.
If I were a bad guy, I'd stay far away from Tor and instead send coded messages via Facebook, Youtube, or some other channel in which 99.99% of the bytes are completely uninteresting, cat videos and such. It's easy to hide 128 bytes of coded message when it's buried within 1,000,000,000,000,000,000,000,000 bytes of inanity. "Hiding " your shady dealings in a pile of shady, illegal stuff that the feds want to look at seems like a less optimal strategy.
> Most of the times your read about the feds jumping up and down on someone, it's when they decided to be "clever" or belligerent, or similar. Nothing is more likely to get a good response than a calm, respectful response.
So true. Most of the time. Of course there are exceptions. Also, getting a custom license plate that says GUILTY probably doesn't help.
If you DON'T send any header specifying your preference regarding convenience versus privacy, you get the default behavior. That's the DEFINITION of default, what happens when it's unspecified. Think about that for second and you'll realize that's true (assuming you're not stupid, of course).
Since sending no extra header at all gets you the default behavior (by definition) , any extra header is useful only if it indicates something other than the default.
Therefore, for a browser to send extra headers specifying by default is useless, no matter what the context, by the very definition of the word "default".
You claimed a user has to be technically advanced in order to choose. The browser could have just as easily given the user a dialog with these two checkboxes:
Do you prefer web sites to provide you more convenience, or more privacy? O More convenience and features O More privacy
Had they done that, the header would have had meaning - it would have indicated something about the user's preference.
On the other hand, since the browser sent DNT by default, that means only that the user might prefer the default balance between convenience and privacy- exactly the same thing as not sending any header at all.
One I'll always remember was some Actionscript or Javascript which would never happen with the debugging console open, but would always halt the program if the debugging console was closed.
It turned out to be a call to console.log, which is a fatal error in IE if the debug console isn't visible at the moment.
Major advertisers starting following the DNT standard. Then browser vendors broke the protocol, in such a way that it became useless.
The protocol was a way to say "this user chosen has opted out of any customizations, saved favorites, or other features that rely on cookies or similar technologies. This user wants more than the default level of privacy, and is willing to give up features which depend on cookie or other tracking."
When browsers started lying and sending a DNT headers for people who had NOT made that choice, the protocol became useless.
At least some of these symbols ARE in common use already, often printed so small that you don't notice them if you're not looking for them. For example, I never knew that the gluten-free symbol existed until my wife was diagnosed with celiac disease (gluten intolerance) . Now that I know what to look for, I see the symbol quite often; sometimes on packaged foods and sometimes on menus.
Checking a few of the products in my pantry right now, I see that it's about evenly split between the symbol and the words "gluten free". Fritos for example, use the words. Chex cereal has the words and a _different_ symbol. Standardization would make shopping easier, faster and safer.
That said, standardizing WHERE on the package this information is found would be the most useful. It's most often listed immediately after the standard ingredient listing, but there is a lot of variation so we have to carefully examine all around the whole package looking for one of the two pictorial symbols, or the words "gluten free", or the circled GF symbol, or the words "gluten free". The most common is the most useful - an icon of a wheat stalk with the crossed out circle (similar to the "no smoking" symbol).
An ip kvm will do exactly what you want. They are used in data centers to control machines throughout the building. You can get a used Raritan on ebay for about $200-$250.
As others have pointed out, hdmi video is multiple gigabits, so you're not going to have Bluray quality video, or gaming FPS, without a dedicated tables. If you want that kind of video, the standard is called hdbase-t. You can run it over cat5e or cat6.
You do NOT need to drill new holes and go through the same trouble you did when you installed the first cable. Simply tie a string to the existing cable, then pull it out, leaving the string in it's place. Tie on another cable and another string and pull it back the other way. Now you have two cables where you used to have one, AND you have a string ready to go for adding another cable. Next time, pull a string along with any cable you pull. If the holes are too small for two cables, just enlarge the existing holes a bit. Don't try to force too many cables into too small of a hole. Just take three minutes to drill it out a bit larger.
Ps - for any new holes s, don't drill through brick, drill through the mortar.
Those issues will be resolved by a side effect of this being a government order. According to the GAO, on average it takes 4 1/2 years from the time the government orders a computer until it's installed. Right now, multiple government agencies have been told to start thinking about a plan. In two years (2017), each agency will have their plan and they'll start working to to resolve the differences between agencies. In another year (2018), they'll put out some RFPs. Those will go through the federal procurement process and the order will be placed about two years later (2020). That's when the 4 1/2 year average clock starts, so expect installation around first quarter 2025.
The goal is that it should be 30 times faster than TODAY'S computers. And be operational in ten years. They can pretty much just order a Nexus 47, or an HP Proliant gen 12.
I figure Slashdot can't be worth more than about $100,000 USD. Valuing SourceForge is a bit more complicated. A lot of traffic, but major damage to the brand lately.
Something like. Kickstarter, or a purchase by a successful community member or three, isn't out of the question.
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.
Slashdot Mirror
You rather missed the entire point. The system disk, and EFI, are read-only, controlled from OUTSIDE of the operating system. You use the SAN or hypervisor to set it read-only. Sure Windows knows how to write FAT32, but that doesn't make it able to write to media which doesn't accept writes.
In his first two years, when the dems had full control,of the houee and senate, he made the economy significantly WORSE. When unemployment is high is not the time to focus on adding historical new burdens to hiring, such as Obamacare. You may remember his campaign commercials on radio when he planned to "go after companies". That's not how you stimulate business.
You can't blame that on republicans obstructing his agenda when his party had full control of the house, senate, and white house.
Things started to get closer to normal only AFTER the republicans started checking his war on business.
BIOS is dead. With EFI, most of the boot code is in the efi partition, on the "disk" which is read-only courtesy of your san, hypervisor, or the fact that it's a cd-rom.
There is a limited firmware on the motherboard which loads the initial efi file. That could, in theory, be compromised, except that if you virtualize, you could also set that read-only in the hypervisor. So your virtual machine pretty darn safe. The host machine needs to be secured , but it doesn't need an operating system, just a hypervisor. That's quite a bit safer than running a full desktop OS.
The headline is crap, of course.
That said, it's not too hard to have a version such that you know it's unaltered when you boot each morning. You do basically a live CD, booting from a read-only lun.
Just as you separate a normal user USING the machine from an administrator account UPDATING the OS, you can have the OS basically read-only during use and set it to writeable only when you need to update the software. That change is done outside of the OS, either via the NAS or the hypervisor.
In that way, you can come in eqch morning knowing your Windows system hasn't been hacked (past tense). As soon as you open IE, though, you could get a new exploit. That exploit disappears when you shut the machine down, though.
No, it was a Kim Dotcom reference. He got the GUILTY license plate. That and similar "rub their nose it" actions didn't help his relationship with law enforcement and the courts.
I WAS not saying that using Tor indicates that one might be doing something shady, but I'll say it now. People using the internet in the clear, not using Tor , are doing something shady maybe 1% of the time. On Tor, maybe 80% of the traffic is shady. So arithmetic tells us that Tor traffic is 80 times more likely to be shady than non-Tor traffic.
Which is why if I were the NSA, FBI, or ONI, I'd run most of the Tor nodes or otherwise ensure that I could map all Tor traffic. That's the fundamental weakness of Tor - it protects against ONE node spying on you, by assuming that MOST nodes are friendly.
If I were a bad guy, I'd stay far away from Tor and instead send coded messages via Facebook, Youtube, or some other channel in which 99.99% of the bytes are completely uninteresting, cat videos and such. It's easy to hide 128 bytes of coded message when it's buried within 1,000,000,000,000,000,000,000,000 bytes of inanity. "Hiding " your shady dealings in a pile of shady, illegal stuff that the feds want to look at seems like a less optimal strategy.
> Most of the times your read about the feds jumping up and down on someone, it's when they decided to be "clever" or belligerent, or similar. Nothing is more likely to get a good response than a calm, respectful response.
So true. Most of the time. Of course there are exceptions.
Also, getting a custom license plate that says GUILTY probably doesn't help.
If you DON'T send any header specifying your preference regarding convenience versus privacy, you get the default behavior. That's the DEFINITION of default, what happens when it's unspecified. Think about that for second and you'll realize that's true (assuming you're not stupid, of course).
Since sending no extra header at all gets you the default behavior (by definition) , any extra header is useful only if it indicates something other than the default.
Therefore, for a browser to send extra headers specifying by default is useless, no matter what the context, by the very definition of the word "default".
You claimed a user has to be technically advanced in order to choose. The browser could have just as easily given the user a dialog with these two checkboxes:
Do you prefer web sites to provide you more convenience, or more privacy?
O More convenience and features
O More privacy
Had they done that, the header would have had meaning - it would have indicated something about the user's preference.
On the other hand, since the browser sent DNT by default, that means only that the user might prefer the default balance between convenience and privacy- exactly the same thing as not sending any header at all.
One I'll always remember was some Actionscript or Javascript which would never happen with the debugging console open, but would always halt the program if the debugging console was closed.
It turned out to be a call to console.log, which is a fatal error in IE if the debug console isn't visible at the moment.
Major advertisers starting following the DNT standard.
Then browser vendors broke the protocol, in such a way that it became useless.
The protocol was a way to say "this user chosen has opted out of any customizations, saved favorites, or other features that rely on cookies or similar technologies. This user wants more than the default level of privacy, and is willing to give up features which depend on cookie or other tracking."
When browsers started lying and sending a DNT headers for people who had NOT made that choice, the protocol became useless.
At least some of these symbols ARE in common use already, often printed so small that you don't notice them if you're not looking for them. For example, I never knew that the gluten-free symbol existed until my wife was diagnosed with celiac disease (gluten intolerance) . Now that I know what to look for, I see the symbol quite often; sometimes on packaged foods and sometimes on menus.
Checking a few of the products in my pantry right now, I see that it's about evenly split between the symbol and the words "gluten free". Fritos for example, use the words. Chex cereal has the words and a _different_ symbol. Standardization would make shopping easier, faster and safer.
That said, standardizing WHERE on the package this information is found would be the most useful. It's most often listed immediately after the standard ingredient listing, but there is a lot of variation so we have to carefully examine all around the whole package looking for one of the two pictorial symbols, or the words "gluten free", or the circled GF symbol, or the words "gluten free". The most common is the most useful - an icon of a wheat stalk with the crossed out circle (similar to the "no smoking" symbol).
An ip kvm will do exactly what you want. They are used in data centers to control machines throughout the building. You can get a used Raritan on ebay for about $200-$250.
As others have pointed out, hdmi video is multiple gigabits, so you're not going to have Bluray quality video, or gaming FPS, without a dedicated tables. If you want that kind of video, the standard is called hdbase-t. You can run it over cat5e or cat6.
You do NOT need to drill new holes and go through the same trouble you did when you installed the first cable. Simply tie a string to the existing cable, then pull it out, leaving the string in it's place. Tie on another cable and another string and pull it back the other way. Now you have two cables where you used to have one, AND you have a string ready to go for adding another cable. Next time, pull a string along with any cable you pull. If the holes are too small for two cables, just enlarge the existing holes a bit. Don't try to force too many cables into too small of a hole. Just take three minutes to drill it out a bit larger.
Ps - for any new holes s, don't drill through brick, drill through the mortar.
Those issues will be resolved by a side effect of this being a government order. According to the GAO, on average it takes 4 1/2 years from the time the government orders a computer until it's installed. Right now, multiple government agencies have been told to start thinking about a plan. In two years (2017), each agency will have their plan and they'll start working to to resolve the differences between agencies. In another year (2018), they'll put out some RFPs. Those will go through the federal procurement process and the order will be placed about two years later (2020). That's when the 4 1/2 year average clock starts, so expect installation around first quarter 2025.
The goal is that it should be 30 times faster than TODAY'S computers.
And be operational in ten years. They can pretty much just order a Nexus 47, or an HP Proliant gen 12.
I figure Slashdot can't be worth more than about $100,000 USD. Valuing SourceForge is a bit more complicated. A lot of traffic, but major damage to the brand lately.
Something like. Kickstarter, or a purchase by a successful community member or three, isn't out of the question.
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. :)