Maybe, maybe not. They hinted at it, but at the same time, they also suggested that licensing terms could override that right. So the question is whether the whole "software is licensed, not sold" thing passes the courts' duck test.
For security and/or police to be able to prevent such assaults, a law explicitly banning men in women's bathrooms may be necessary â" without it, such people can not be removed from there preemptively.
Heaven forbid they should arrest people under any of the hundreds of other laws that such behavior would violate (assault, indecent exposure, loitering in a restroom with intent to commit lewd acts, peeping tom laws, etc.).
... you aren't free to properly flush afterwards.
1.6 gallons is actually plenty of water for flushing a toilet if the toilet is designed correctly and the drain pipes actually slope downwards at a sufficient angle to carry sewage away. Clogging is almost invariably caused by toilets that are designed badly. And trust me when I say that there were plenty of badly designed toilets before 1992 as well.
...watching MSNBC & Al Jazeera and splitting the difference.
That's half facetious, but the reality is that if you get all your news from a single source, you're guaranteed to get a biased view of reality, no matter what the source. The best thing you can do is to get information from as many different sources as possible, and when there are differences, do a little digging through meta-analysis sites to try to figure out where the truth lies.
If you don't have time to do that, your only choice is to accept that you will always be at least to some degree uninformed, hope that it doesn't matter, and don't worry about it.
The Central District of California is part of the 9th circuit. The Vernor decision was made by the 9th Circuit Court of Appeals, so Vernor effectively (and, IMO, incorrectly) overrode the precedent in Softman.
Now the next logical step, if you're a sociopathic corporation, would be to sue the companies that provided the cartridges to the recyclers, alleging tortious interference with the contract between users and Lexmark. However, this won't yield significant financial wins, so the next step after that is to use the lawsuit to demand their customer list and start suing individual users. And the next step after that is Chapter 11, followed by Chapter 7.
It doesn't matter if they know who qualifies. People take low-wage jobs in part because of tax credits make it possible for them to eke out a living. If those credits weren't available, low-wage earners would be more likely to hunt for jobs that pay an extra buck an hour, and employers would eventually be forced to pay more if they wanted to actually have workers. So in a very real sense, the EITC effectively subsidizes those employers by making it possible for them to pay below-market wages. Of course, the same could probably be said about a basic income.
In the real world, those of us who work for a living use hundreds of nails every single day
I didn't say hundreds of nails. I said hundreds of dollars' worth of nails. That's many, many thousands of nails—enough to build a stud wall several hundred feet long. Besides, in the real world, you aren't on a watch list, and you should be paying for building supplies on a company card so that expenses can be easily tracked, rather than doing it under the table in cash, which is much more likely to result in theft. But don't let facts get in the way of your perfectly good rant.
Physical surveillance would be a hopelessly inefficient approach. Building bombs requires supplies, and purchases of such supplies can and should be tracked. I mean, I'm not advocating that buying nails should require a photo ID, but if somebody goes into a hardware store and buys hundreds of dollars' worth of nails using cash, that should raise red flags, and should get reported along with surveillance camera photos.
Similarly, if somebody buys any quantity of nails on a credit card belonging to someone who is on a terrorist watchlist, that should raise red flags, and that person's future and recent past purchases should undergo more intensive scrutiny.
And if a credit card gets flagged as stolen, all recent purchases should be similarly carefully scrutinized under the assumption that the person using it may have been doing something nefarious.
The design of a machine learning system capable of doing this sort of analysis autonomously is left as an exercise for the reader.
My long-standing comment on the subject is, "The good thing about making it easier to write software is that more people can write software. The bad thing about making it easier to write software is that more people can write software."
The thing is, having 10x as many people who can "code" isn't a virtue. It's a nuisance. It just means that there will be 10x as much bad software, making it even harder to find good software written by people who actually know what they're doing, because it gets lost in the noise.
How do we know there isn't in-person fraud in the states that don't require picture ID?
Fraud in vote-by-mail is lower risk and easier. Why would anybody even attempt in-person voter fraud? It would be like stealing guns from a military armory when you could steal them from a random person's house while he or she is gone for the weekend.
This is exactly the opposite of what we should be doing. There are very good reasons that Appalachia has never been successful at anything other than resource extraction.
Besides the contour of the land, those reasons would be....
Most medical mistakes that result in death are not caused by misdiagnosis, though that does occur. Most of them are from a combination of surgical mistakes and human error while dispensing/choosing medication. There are a lot of much easier ways to reduce medical mistakes without going so far as to replace doctors with a computer.
Even if the only thing we did was require that every packet of medication was tagged with a barcode and require that appropriate people scan the patient's chart and the barcode prior to dispensing it to verify that it is the medicine prescribed, we'd save a decent number of lives.
And if computers also did checks for contraindications (giving aspirin to someone with a history of bleeding ulcers, giving antibiotics in conjunction with Lipitor, giving any number of drugs with MAOIs, etc.), it would save even more lives.
Notice that neither of these even requires AI. They just require proper electronic medical records and some pretty basic coding skills.
There are remarkably few bacteria that can survive in such a basic environment (8.3 pH), and I don't think they would survive in the much less basic environment inside the human body. Contamination with heavy metals (e.g. aluminum oxide) would be a more plausible concern.
They just have to stop doing this, then. I mean, it's tragic when any business is harmed in any way - but this is just too far. The banana eatery business is what this country was built on, and I can't imagine the hardships faced by grocers selling less bananas than normal.
I can't wait to see your face when you find out about Google's free lunches.:-D
Drywall isn't very hard. Car windows aren't, either. And survivability for a cell phone in a 16-foot drop onto concrete depends entirely on how it hits, which is random luck. Besides, you said that most of those events were well over a decade ago, and AFAIK no cell phone prior to the iPhone (2007) had a glass screen. Plastic screens didn't have those problems.
My phones get dropped. Sometimes when I'm walking, in which case it's prone to "landing" on my foot during a froward step and being sent across the floor. I've had phones fall out of my pocket atop 16ft ladders on to concrete floors. Hell, I had one fall out of my pocket getting into the car and get driven over twice, once when I backed out, and again when I pulled back into the parking spot when I realized it wasn't in my pocket and thought I had left it inside. It was in a puddle when this happened.
The reason your phone didn't break in all those instances is that breakage risk is proportional to the delta-v on impact. When it hit your foot, that cushioned the fall, and the delta-v hitting from three inches up is essentially zero, and sliding causes nothing but scuff marks. And the car incident... well, that's in part because compression was applied to the face of the device. Phones are designed to stand normal amounts of flexing, and your tire presents a fairly even amount of force. What they don't deal with very well are impacts on the corners, or impacts with sharp things like rocks that cause highly uneven stress on a single part of the screen.
It is relatively easy to break a phone. Just drop it three or four feet on its corner onto concrete. You'll have a shattered screen with high probability. Or drop it onto a gravel-covered yard from three or four feet. Or put it into your back pocket and sit on it the wrong way in a hard chair. Or....
It's why you fund academia to do the research and why government agencies do have a place in medicine. That model fits this problem much better than simple commerce.
Agreed. Of course, the real question we should be asking is this: If government agencies and government-funded academia can (and, indeed, must) do the research, why do we need drug companies? Shouldn't we just cut out the middlemen and have the academic institutions and government agencies contract out the manufacturing directly?
The thing is, when you do that (remove deprecated API's), people will default to a worse scenario: not updating PHP at all.
That's actually not what happens in practice. Statistically, it isn't the one-off apps that get hacked. Instead, hackers tend to mostly go after mass-deployment apps (phpBB, WordPress, etc., because they yield the most bang for the buck. After all, why steal passwords on one site when you can steal passwords on 100,000 sites just as easily?
The problem with mass-deployment apps is that developers are wary of making potentially dangerous changes like switching MySQL APIs. Instead, they do the minimum maintenance required to fix known holes. Unfortunately, because these apps are the ones that get the most eyes looking for holes, they tend to be compromised frequently under that model. Thus it is of paramount importance to force those developers to upgrade their API usage when serious problems make the use of the older APIs unsafe.
Fortunately, this generally "just works" because those same apps also have a steady flow of new users. When a backwards-incompatible API update happens, those new users want to run [insert random bulletin board/CMS software here] on their servers, and if their shared hosting providers no longer provide old versions of PHP that support those APIs, they can't run the software. Thus, this puts pressure on the developers of that software to take the risk and update their software so that they won't stop getting new users. Once the developers have updated the software, all users of that software package are free to upgrade their versions of PHP to a newer version.
For one-offs, yes, in theory, you might cause somebody to decide not to upgrade. But even there, often their ISP will eventually say, "We notice you're running an outdated version of PHP" and force the issue. Either way, if you break a known-unsafe API and people choose to not upgrade their entire server stack rather than update the software on the server, that's an obvious choice to neglect security that the site owner made, knowing full well that not staying up-to-date is a bad idea. If you continue to allow use of the old API, there's a decent chance that the people who developed software for those one-off sites won't even know that something is wrong and needs to be fixed, because their software is still working. So even in those situations, removing the API provides a benefit.
And if you really want to make it less painful for the one-offs, you can do that by continuing to maintain the legacy code as an optional install. The shared server admins will refuse to install it, forcing folks to upgrade their software, and the random one-off software authors will either fix their code (if they're forced to by their ISP) or will continue manually installing the package on their servers until the extra hassle makes it worth their time to fix their code.
This is just another example of why you should deprecate APIs with known security design flaws quickly and remove them just as quickly. PHP's MySQL API should have been deprecated when mysqli and PDO came onto the scene in PHP 5.0 (2004) and removed entirely within a couple of years after that. Instead, they didn't deprecate it until PHP 5.5 (2013) and didn't remove it until PHP 7 (2015). IMO, that was about a decade too late, and by the time they finally got around to it, thousands of websites developed using the old, vulnerable-by-design API have been compromised.
I think I was wrong about that number. After a little digging, I've concluded that the correct number for Nougat is probably closer to 4.5 GB. For comparison, the base installation size for iOS is about 4.3 GB, which is to say that the size difference is statistical noise. But the difference still doesn't change the fact that a user with a 16 GB device is in a world of hurt on either platform, nor the fact that a 2 GB device would be completely infeasible on either platform.
Either way, even if I had been correct about that number, Sierra would still only be smaller because of a technicality. The Sierra installer is almost 5GB, and historically, the installed size of OS X was at least 2x the installer size, because the installer package is highly compressed. However, newer versions of OS X bend the rules through the use of transparent file compression on disk, making the OS installation take less space. Unfortunately, that sort of trickery is probably not practical on a cell phone with its severely limited CPU and even more severely limited battery capacity, which is why Sierra appears to take only slightly more disk space than iOS or Android when in actuality it is closer to 3x as big.
"on its face" is the English translation of "prima facie", which is a legal term that means "at first glance". So the judge dismissed the case as being invalid because a bucket can't be copyrighted because physical objects don't fall within the scope of copyright. And a docket is a list/calendar of cases that are scheduled to be heard.
It's funny because Nantucket limericks almost invariably end with "f**k it", but I used a slightly less precise (but contextually appropriate) rhyme to avoid doing what was expected. In other words, it's funny in a situational irony sort of way.
Slashdot Mirror
Maybe, maybe not. They hinted at it, but at the same time, they also suggested that licensing terms could override that right. So the question is whether the whole "software is licensed, not sold" thing passes the courts' duck test.
Heaven forbid they should arrest people under any of the hundreds of other laws that such behavior would violate (assault, indecent exposure, loitering in a restroom with intent to commit lewd acts, peeping tom laws, etc.).
1.6 gallons is actually plenty of water for flushing a toilet if the toilet is designed correctly and the drain pipes actually slope downwards at a sufficient angle to carry sewage away. Clogging is almost invariably caused by toilets that are designed badly. And trust me when I say that there were plenty of badly designed toilets before 1992 as well.
To expand on West Wing's comment on the subject, they want government just small enough to fit into your bedroom and bathroom.
...watching MSNBC & Al Jazeera and splitting the difference.
That's half facetious, but the reality is that if you get all your news from a single source, you're guaranteed to get a biased view of reality, no matter what the source. The best thing you can do is to get information from as many different sources as possible, and when there are differences, do a little digging through meta-analysis sites to try to figure out where the truth lies.
If you don't have time to do that, your only choice is to accept that you will always be at least to some degree uninformed, hope that it doesn't matter, and don't worry about it.
The Central District of California is part of the 9th circuit. The Vernor decision was made by the 9th Circuit Court of Appeals, so Vernor effectively (and, IMO, incorrectly) overrode the precedent in Softman.
Now the next logical step, if you're a sociopathic corporation, would be to sue the companies that provided the cartridges to the recyclers, alleging tortious interference with the contract between users and Lexmark. However, this won't yield significant financial wins, so the next step after that is to use the lawsuit to demand their customer list and start suing individual users. And the next step after that is Chapter 11, followed by Chapter 7.
It doesn't matter if they know who qualifies. People take low-wage jobs in part because of tax credits make it possible for them to eke out a living. If those credits weren't available, low-wage earners would be more likely to hunt for jobs that pay an extra buck an hour, and employers would eventually be forced to pay more if they wanted to actually have workers. So in a very real sense, the EITC effectively subsidizes those employers by making it possible for them to pay below-market wages. Of course, the same could probably be said about a basic income.
Perhaps by sneaking into their houses and stealing their shoes—workers of the world untie, and all that.
Heads on pikes, historically speaking.
I didn't say hundreds of nails. I said hundreds of dollars' worth of nails. That's many, many thousands of nails—enough to build a stud wall several hundred feet long. Besides, in the real world, you aren't on a watch list, and you should be paying for building supplies on a company card so that expenses can be easily tracked, rather than doing it under the table in cash, which is much more likely to result in theft. But don't let facts get in the way of your perfectly good rant.
Physical surveillance would be a hopelessly inefficient approach. Building bombs requires supplies, and purchases of such supplies can and should be tracked. I mean, I'm not advocating that buying nails should require a photo ID, but if somebody goes into a hardware store and buys hundreds of dollars' worth of nails using cash, that should raise red flags, and should get reported along with surveillance camera photos.
Similarly, if somebody buys any quantity of nails on a credit card belonging to someone who is on a terrorist watchlist, that should raise red flags, and that person's future and recent past purchases should undergo more intensive scrutiny.
And if a credit card gets flagged as stolen, all recent purchases should be similarly carefully scrutinized under the assumption that the person using it may have been doing something nefarious.
The design of a machine learning system capable of doing this sort of analysis autonomously is left as an exercise for the reader.
My long-standing comment on the subject is, "The good thing about making it easier to write software is that more people can write software. The bad thing about making it easier to write software is that more people can write software."
The thing is, having 10x as many people who can "code" isn't a virtue. It's a nuisance. It just means that there will be 10x as much bad software, making it even harder to find good software written by people who actually know what they're doing, because it gets lost in the noise.
Fraud in vote-by-mail is lower risk and easier. Why would anybody even attempt in-person voter fraud? It would be like stealing guns from a military armory when you could steal them from a random person's house while he or she is gone for the weekend.
Besides the contour of the land, those reasons would be....
Most medical mistakes that result in death are not caused by misdiagnosis, though that does occur. Most of them are from a combination of surgical mistakes and human error while dispensing/choosing medication. There are a lot of much easier ways to reduce medical mistakes without going so far as to replace doctors with a computer.
Even if the only thing we did was require that every packet of medication was tagged with a barcode and require that appropriate people scan the patient's chart and the barcode prior to dispensing it to verify that it is the medicine prescribed, we'd save a decent number of lives.
And if computers also did checks for contraindications (giving aspirin to someone with a history of bleeding ulcers, giving antibiotics in conjunction with Lipitor, giving any number of drugs with MAOIs, etc.), it would save even more lives.
Notice that neither of these even requires AI. They just require proper electronic medical records and some pretty basic coding skills.
There are remarkably few bacteria that can survive in such a basic environment (8.3 pH), and I don't think they would survive in the much less basic environment inside the human body. Contamination with heavy metals (e.g. aluminum oxide) would be a more plausible concern.
I can't wait to see your face when you find out about Google's free lunches. :-D
Drywall isn't very hard. Car windows aren't, either. And survivability for a cell phone in a 16-foot drop onto concrete depends entirely on how it hits, which is random luck. Besides, you said that most of those events were well over a decade ago, and AFAIK no cell phone prior to the iPhone (2007) had a glass screen. Plastic screens didn't have those problems.
The reason your phone didn't break in all those instances is that breakage risk is proportional to the delta-v on impact. When it hit your foot, that cushioned the fall, and the delta-v hitting from three inches up is essentially zero, and sliding causes nothing but scuff marks. And the car incident... well, that's in part because compression was applied to the face of the device. Phones are designed to stand normal amounts of flexing, and your tire presents a fairly even amount of force. What they don't deal with very well are impacts on the corners, or impacts with sharp things like rocks that cause highly uneven stress on a single part of the screen.
It is relatively easy to break a phone. Just drop it three or four feet on its corner onto concrete. You'll have a shattered screen with high probability. Or drop it onto a gravel-covered yard from three or four feet. Or put it into your back pocket and sit on it the wrong way in a hard chair. Or....
Agreed. Of course, the real question we should be asking is this: If government agencies and government-funded academia can (and, indeed, must) do the research, why do we need drug companies? Shouldn't we just cut out the middlemen and have the academic institutions and government agencies contract out the manufacturing directly?
Indeed. Too bad Google doesn't provide a dup search engine. Oh, wait....
That's actually not what happens in practice. Statistically, it isn't the one-off apps that get hacked. Instead, hackers tend to mostly go after mass-deployment apps (phpBB, WordPress, etc., because they yield the most bang for the buck. After all, why steal passwords on one site when you can steal passwords on 100,000 sites just as easily?
The problem with mass-deployment apps is that developers are wary of making potentially dangerous changes like switching MySQL APIs. Instead, they do the minimum maintenance required to fix known holes. Unfortunately, because these apps are the ones that get the most eyes looking for holes, they tend to be compromised frequently under that model. Thus it is of paramount importance to force those developers to upgrade their API usage when serious problems make the use of the older APIs unsafe.
Fortunately, this generally "just works" because those same apps also have a steady flow of new users. When a backwards-incompatible API update happens, those new users want to run [insert random bulletin board/CMS software here] on their servers, and if their shared hosting providers no longer provide old versions of PHP that support those APIs, they can't run the software. Thus, this puts pressure on the developers of that software to take the risk and update their software so that they won't stop getting new users. Once the developers have updated the software, all users of that software package are free to upgrade their versions of PHP to a newer version.
For one-offs, yes, in theory, you might cause somebody to decide not to upgrade. But even there, often their ISP will eventually say, "We notice you're running an outdated version of PHP" and force the issue. Either way, if you break a known-unsafe API and people choose to not upgrade their entire server stack rather than update the software on the server, that's an obvious choice to neglect security that the site owner made, knowing full well that not staying up-to-date is a bad idea. If you continue to allow use of the old API, there's a decent chance that the people who developed software for those one-off sites won't even know that something is wrong and needs to be fixed, because their software is still working. So even in those situations, removing the API provides a benefit.
And if you really want to make it less painful for the one-offs, you can do that by continuing to maintain the legacy code as an optional install. The shared server admins will refuse to install it, forcing folks to upgrade their software, and the random one-off software authors will either fix their code (if they're forced to by their ISP) or will continue manually installing the package on their servers until the extra hassle makes it worth their time to fix their code.
This is just another example of why you should deprecate APIs with known security design flaws quickly and remove them just as quickly. PHP's MySQL API should have been deprecated when mysqli and PDO came onto the scene in PHP 5.0 (2004) and removed entirely within a couple of years after that. Instead, they didn't deprecate it until PHP 5.5 (2013) and didn't remove it until PHP 7 (2015). IMO, that was about a decade too late, and by the time they finally got around to it, thousands of websites developed using the old, vulnerable-by-design API have been compromised.
I think I was wrong about that number. After a little digging, I've concluded that the correct number for Nougat is probably closer to 4.5 GB. For comparison, the base installation size for iOS is about 4.3 GB, which is to say that the size difference is statistical noise. But the difference still doesn't change the fact that a user with a 16 GB device is in a world of hurt on either platform, nor the fact that a 2 GB device would be completely infeasible on either platform.
Either way, even if I had been correct about that number, Sierra would still only be smaller because of a technicality. The Sierra installer is almost 5GB, and historically, the installed size of OS X was at least 2x the installer size, because the installer package is highly compressed. However, newer versions of OS X bend the rules through the use of transparent file compression on disk, making the OS installation take less space. Unfortunately, that sort of trickery is probably not practical on a cell phone with its severely limited CPU and even more severely limited battery capacity, which is why Sierra appears to take only slightly more disk space than iOS or Android when in actuality it is closer to 3x as big.
"on its face" is the English translation of "prima facie", which is a legal term that means "at first glance". So the judge dismissed the case as being invalid because a bucket can't be copyrighted because physical objects don't fall within the scope of copyright. And a docket is a list/calendar of cases that are scheduled to be heard.
It's funny because Nantucket limericks almost invariably end with "f**k it", but I used a slightly less precise (but contextually appropriate) rhyme to avoid doing what was expected. In other words, it's funny in a situational irony sort of way.