Litigation is somewhat of an issue when dealing with Apple's hardware/software and reverse engineering.
Reverse engineering is legal in the US. Any information gleaned from such activities that doesn't violate a patent, an NDA, or copyright / DMCA can be publicly disclosed with impunity. Reverse engineering for the purposes of interoperability is also well supported by prior case law.
My understanding is that cochineal is more commonly used in countries where certain synthetic reds are banned due to concerns about toxicity, allergies, or carcinogenic properties. Fortunately, profit is more important than public safety in the US so we get to eat the cheapest option.
It doesn't matter how extensively Google uses user data internally. Almost none of their users are paying for the services they use. Bloomberg subscribers, on the other hand, are paying a pretty penny for each terminal. A degree of privacy is a reasonable expectation.
Reminds me about a short story I once read about a future in which fast food workers are micromanaged by a computer giving them constant instruction on their minute to minute tasks through a headset.
So big media copyright holders want to have it both ways then. They get to apply federal law to extend the copyright term beyond 56 (28+28) years and then they get to claim that those same grandfathered pre-1976 works are not subject to federal DMCA provisions.
If federal law shouldn't apply then we should strip all post-1976 federal provisions from the copyright of older works. From Wikipedia here are the federal laws that would be nullified:
Copyright Act of 1976 - extended term to either 75 years or life of author plus 50 years; extended federal copyright to unpublished works; preempted state copyright laws; codified much copyright doctrine that had originated in case law Berne Convention Implementation Act of 1988 - established copyrights of U.S. works in Berne Convention countries Copyright Renewal Act of 1992 - removed the requirement for renewal Uruguay Round Agreements Act (URAA) of 1994 - restored U.S. copyright for certain foreign works Copyright Term Extension Act of 1998 - extended terms to 95/120 years or life plus 70 years Digital Millennium Copyright Act of 1998 - criminalized some cases of copyright infringement
After stripping away these provisions a work created before 1976 with one renewal would have a copyright term of 28+28 years rather than the silly 95 years we have today.
Unfortunately, my bank's, broker's, credit union's etc... websites are unusable without it
Then use NoScript and temporarily allow those sites when you need to use them. Or just permanently whitelist them since your are screwed anyway if your banking sites have been compromised with malware.
No what Agile means is "we're too lazy to develop specifications before development and we're too lazy to document the behavior when we make a release because we're already working on the next sprint".
The "robot" part is pretty redundant. Its behavior could be easily matched with a non-anthropomorphic machine. It could be made even simpler, faster, and more reliable by replacing the reciprocating elbow with a rotary disc sporting multiple peeling tools.
The number of devices from which a user accesses the service.
So does Twitter just publicly disclose a simple device count or the detailed information on all devices? If the latter, isn't that a whopping security hole to be exploited by people looking for targets with known vulnerable devices.
You can't get the full current out of the power supply without going through a negotiation phase. If that doesn't happen the interface defaults to normal current limit of 0.5A. The same thing happens today with the USB 2.0 charging ports capable of delivering up to 2.1A.
An ad blocker won't help you if malware code is served from a site the blocker doesn't know about or from something completely unrelated to ads at all. Aggressive use of noscript with very few whitelisted sites is the only way to clamp down on malicious javascript running on your computer.
You didn't have to install Cygwin for that. You could have just installed the MinGW GCC. You can even set up VS to use the GCC tool suite if you don't want to leave the IDE.
Today there is probably no new PC out there that has less than 4 GB of RAM, and 64-bit OS is a necessity.
That's not exactly true. 32-bit x86 has supported a 36-bit memory space (with 4GB per process) since PAE was introduced on the PentiumPro. The sticky wicket has been that MS only allowed use of PAE on 32-bit sever editions of Windows but there are plenty of other operating systems that offer unlimited use of this feature.
Most users would not need more than 4GB per process. An additional benefit would be memory savings and better cache utilization by not paying the 64-bit tax on applications that don't need it. The argument that you need 64-bits "for speed" is a false creation of an advertising industry that was stuck without any significant advances anywhere else (MHz, cores) to market the new thing as better that your old thing.
Unless "everything you have" is so illegally outrageous that the story needs to be told.
It wasn't. Manning just copied everything indiscriminately. There's no way he was even capable of sifting through what he had taken to know what the juicy bits were. There's no way to justify what he did as being "for the greater good".
There is an often ignored matter of why Army security procedures were so lax that it was possible to use writable media on what should have been a locked down network. If this has happened at a DOD contractor site there would be massive fines handed down and the possibility of prosecution for those who left the holes in place but somehow when these lapses happen in the military itself they can just be swept away lest anyone's career path be jeopardized. The lapdog press has conveniently ignored bringing that to public light.
It could also be argued that a takedown notice does not constitute a creative work deserving of copyright protection and as such the DMCA would not apply.
A clean, modern systems language would be nice to have. Too bad Rust looks like the bastard offspring of of a C++, VB, and Perl threeway. I see gobs of punctuation peppered everywhere where a much simpler syntax could be employed. Do you really need to have namespaces separated by "::" instead of "."?
The Chinese were creating backdoored bootleg Cisco gear. I would surmise that violates a few international treaties and is justification for taking protective measures.
Slashdot Mirror
FWIW Viagra was an accident. It was originally developed as a treatment for hypertension.
Litigation is somewhat of an issue when dealing with Apple's hardware/software and reverse engineering.
Reverse engineering is legal in the US. Any information gleaned from such activities that doesn't violate a patent, an NDA, or copyright / DMCA can be publicly disclosed with impunity. Reverse engineering for the purposes of interoperability is also well supported by prior case law.
You don't have to imagine. Take a look at his hosting on Nova Science Now. That's essentially what the new program will be like.
My understanding is that cochineal is more commonly used in countries where certain synthetic reds are banned due to concerns about toxicity, allergies, or carcinogenic properties. Fortunately, profit is more important than public safety in the US so we get to eat the cheapest option.
It doesn't matter how extensively Google uses user data internally. Almost none of their users are paying for the services they use. Bloomberg subscribers, on the other hand, are paying a pretty penny for each terminal. A degree of privacy is a reasonable expectation.
You forgot the all important email contacts scraper and spam generator.
Reminds me about a short story I once read about a future in which fast food workers are micromanaged by a computer giving them constant instruction on their minute to minute tasks through a headset.
So big media copyright holders want to have it both ways then. They get to apply federal law to extend the copyright term beyond 56 (28+28) years and then they get to claim that those same grandfathered pre-1976 works are not subject to federal DMCA provisions.
If federal law shouldn't apply then we should strip all post-1976 federal provisions from the copyright of older works. From Wikipedia here are the federal laws that would be nullified:
Copyright Act of 1976 - extended term to either 75 years or life of author plus 50 years; extended federal copyright to unpublished works; preempted state copyright laws; codified much copyright doctrine that had originated in case law
Berne Convention Implementation Act of 1988 - established copyrights of U.S. works in Berne Convention countries
Copyright Renewal Act of 1992 - removed the requirement for renewal
Uruguay Round Agreements Act (URAA) of 1994 - restored U.S. copyright for certain foreign works
Copyright Term Extension Act of 1998 - extended terms to 95/120 years or life plus 70 years
Digital Millennium Copyright Act of 1998 - criminalized some cases of copyright infringement
After stripping away these provisions a work created before 1976 with one renewal would have a copyright term of 28+28 years rather than the silly 95 years we have today.
Unfortunately, my bank's, broker's, credit union's etc ... websites are unusable without it
Then use NoScript and temporarily allow those sites when you need to use them. Or just permanently whitelist them since your are screwed anyway if your banking sites have been compromised with malware.
No what Agile means is "we're too lazy to develop specifications before development and we're too lazy to document the behavior when we make a release because we're already working on the next sprint".
The "robot" part is pretty redundant. Its behavior could be easily matched with a non-anthropomorphic machine. It could be made even simpler, faster, and more reliable by replacing the reciprocating elbow with a rotary disc sporting multiple peeling tools.
The number of devices from which a user accesses the service.
So does Twitter just publicly disclose a simple device count or the detailed information on all devices? If the latter, isn't that a whopping security hole to be exploited by people looking for targets with known vulnerable devices.
You can't get the full current out of the power supply without going through a negotiation phase. If that doesn't happen the interface defaults to normal current limit of 0.5A. The same thing happens today with the USB 2.0 charging ports capable of delivering up to 2.1A.
You can telnet into a JetDirect card to control it without the fancy web interface. Bonus if you make an application to simplify the process.
Or just install whatever dev header packages you need and compile it yourself against your current libraries.
An ad blocker won't help you if malware code is served from a site the blocker doesn't know about or from something completely unrelated to ads at all. Aggressive use of noscript with very few whitelisted sites is the only way to clamp down on malicious javascript running on your computer.
I don't think they're a significant eyesore during the day but the huge mass of blinking red lights at night is not such a great thing.
You didn't have to install Cygwin for that. You could have just installed the MinGW GCC. You can even set up VS to use the GCC tool suite if you don't want to leave the IDE.
Today there is probably no new PC out there that has less than 4 GB of RAM, and 64-bit OS is a necessity.
That's not exactly true. 32-bit x86 has supported a 36-bit memory space (with 4GB per process) since PAE was introduced on the PentiumPro. The sticky wicket has been that MS only allowed use of PAE on 32-bit sever editions of Windows but there are plenty of other operating systems that offer unlimited use of this feature.
Most users would not need more than 4GB per process. An additional benefit would be memory savings and better cache utilization by not paying the 64-bit tax on applications that don't need it. The argument that you need 64-bits "for speed" is a false creation of an advertising industry that was stuck without any significant advances anywhere else (MHz, cores) to market the new thing as better that your old thing.
Unless "everything you have" is so illegally outrageous that the story needs to be told.
It wasn't. Manning just copied everything indiscriminately. There's no way he was even capable of sifting through what he had taken to know what the juicy bits were. There's no way to justify what he did as being "for the greater good".
There is an often ignored matter of why Army security procedures were so lax that it was possible to use writable media on what should have been a locked down network. If this has happened at a DOD contractor site there would be massive fines handed down and the possibility of prosecution for those who left the holes in place but somehow when these lapses happen in the military itself they can just be swept away lest anyone's career path be jeopardized. The lapdog press has conveniently ignored bringing that to public light.
It was already posted above. A direct link to a Google provided CSV. Can't get any easier than that.
It could also be argued that a takedown notice does not constitute a creative work deserving of copyright protection and as such the DMCA would not apply.
C++ was never designed so much as hacked together. It's the CVS of languages.
A clean, modern systems language would be nice to have. Too bad Rust looks like the bastard offspring of of a C++, VB, and Perl threeway. I see gobs of punctuation peppered everywhere where a much simpler syntax could be employed. Do you really need to have namespaces separated by "::" instead of "."?
The Chinese were creating backdoored bootleg Cisco gear. I would surmise that violates a few international treaties and is justification for taking protective measures.