It should also be considered it might nudge them away from the act.
Artistic expression in both production and consumption of media has definite positive values.
If you wish me to explain this in terms of a low-brow analogy...... horny catholic school girls unable to express themselves sexually.
Sure -- there's also the same correlation between people who express themselves sexually too much... and for the wrong reasons...... but like everything... it all depends why... which is why laws like this don't work -- it doesn't think of the why... it doesn't even think of the problem... it doesn't even go to the length to think how the subject relates to the problem. It's just a law designed to look good -- ramifications be damned.
There are no laws restricting the sale of R rated movies to minors in the US or Canada -- attempts were deemed unconstitutional. It's an industry regulation.
To be fair -- in your comment between eggs and embryonic stem cell research...... we don't eat human eggs.
That said, I very much agree that our problems with bestiality stems from our problems with sex... especially since it occurs to various degrees in just about every instance of sex... from masturbation through to furries... homosexuality to pornography. (IMO -- all four listed subjects are perfectly healthy for those who genuinely enjoy it... among many other taboo topics)
And the worst part is -- it's entirely counter-productive. Promoting self-expression in the long run and on average promotes the best citizens. Obviously I'm not saying that everything should be legal or sponsored by the Government...... nooo...... but (creating or studying) artistic expressions of said acts should not only be legal... but should be promoted.
It's like how the crime rate typically drops when the death penalty is revoked in a given jurisdiction...... threat of legal recourse regardless of how severe is still a form of advertising. Almost no publicity is bad publicity.
Then of course you have the problem of public companies being legally required to ONLY consider the best interest of their shareholders and related business partners -- especially those which may have a massive (at least perceived) financial interest in crippling the company's infrastructure... ahh conundrums. Good luck sorting this one out folks.
The extra jobs are for the future products from the same development team...... which likely would have made it regardless.
Piracy can be damaging to a company -- but almost always the company sunk itself -- either by fighting piracy rather than monetizing their audience... or by being confused to what their audience even is.
Adobe knows that residential piracy of Creative Suite applications is beneficial for them in the long run... they try to get the professional user to push their company for a license of Creative Suite (or purchase it themselves if they go commercial freelance)... and they try to get the casual user on the Elements line. They're better off just letting the middle (aspiring professional) that can't due with Elements pirate Creative Suite so they become legal users when they become commercial... rather than commercial GIMP/etc. artists.
If your company spends its time and capital developing all their new features open... it doesn't need to spend its time and capital defeating other standards.
Betamax was technically superior to VHS.
Yeah, common law has often shown that Non-Compete doesn't actually work... judges often overturn.
Beyond that though, keep in mind... *they* fired *him*... the contract was already breached... and severance was paid.
Seemingly ironic, yes -- but this isn't releasing information of an ongoing legal process, it's releasing opinion-based statements against the Defense's legal statement publicly.
If this trial somehow attempts to deport Assange to the States (where he faces charges from his work at Wikileaks) -- it's total BS.
They break programs that were poorly written, simply put.
Some people execute off the data memory space... some people point to specific points in memory assuming that what they think they put there will be there.
Either they draw a line in the sand and break those programs (some of which are internally-developed corporate programs where the programmer quit and/or died years or even decades ago...) or they let those programs ride in the exception category.
It has nothing to do with ASLR or DEP... it has everything to do with programs written by people who didn't know and/or care that ASLR and DEP exist... and would crash if ASLR or DEP were running on them.
If everyone practiced great and secure programming practices... DEP and ASLR would be next-to perfect solutions to prevent the "whoopsies" from overwriting execute addresses. Unfortunately... that assumes that the only time you're executing from data is by accident.
The user and the programs they run have limited permissions -- they do not have the permissions to install Rootkits... but they can call APIs with root permissions.
If those libraries (such as, for instance, networking APIs) accept data... it will place the data in the memory space of the API's code. If there's a flaw in the way data is written to the memory... the API might accidentally overwrite some executable code in its memory space.
What happens the next time the executable code is called? It's not there anymore... the data is there because the API accidentally overwrote itself with the data
What if the person who sent the data KNEW that API had a problem with specific sized data under specific conditions? What if they ALSO knew exactly how far from the start of the data the start of the executable code was in the program's memory space?
Get them to open that data under those conditions... and blam... a limited user passes data to a limited program which passes data to a high-privileged API which runs the malware blindly.
What permissions level will it have? The API's... because that's where the overwritten executable code is... the processor and OS simply sees executable code from a high-privileged API and runs it (Unless it has DEP properly configured -- in which case it says "Huh... this code is tagged as data HOLY CRAP ABORT!" and your program or whole damn computer crashes gloriously to prevent the data from executing.)
This is an inherent problem with computers. Somewhere... someone... needs to be root privileged. If that root privileged code accepts data... you can have a security flaw. And errors like that are something that you could review dozens of times and never see anything wrong with it.
Really it's not the patent or copyright system that people are against -- it's people being dicks.
You can have proprietary dicks sending DMCA notices or filing patent/trademark infringement cases for -- for example -- having the letters "sky" in the product name "skype" (oddly enough without going after Microsoft for SkyDrive or Google for Sky... you know -- the companies who can fight back).
You can have proprietary people doing *great* things... giving APIs, providing community support, multi-licensing for educational or whatever.
You can obviously have open people doing great things for the community -- just look at slashdot for that example. They can also be dicks... shunning everything that's not GPL complaint... etc. Basically being almost identically behaved as the proprietary dicks... just using the copyright law to say "You must -----" rather than "You can't -----".
Obviously dependencies gets complicated especially for software patents and copyrights -- so libraries and OSes are best in the more LGPL-side of things (so that the programs, some of which are artistically and culturally relevant, are on a platform that's legally enforced to be open forever) but yeah. Tangent in a tangent in a tangent.
Slashdot Mirror
It should also be considered it might nudge them away from the act.
... horny catholic school girls unable to express themselves sexually.
... but like everything... it all depends why... which is why laws like this don't work -- it doesn't think of the why... it doesn't even think of the problem... it doesn't even go to the length to think how the subject relates to the problem. It's just a law designed to look good -- ramifications be damned.
Artistic expression in both production and consumption of media has definite positive values.
If you wish me to explain this in terms of a low-brow analogy...
Sure -- there's also the same correlation between people who express themselves sexually too much... and for the wrong reasons...
There are no laws restricting the sale of R rated movies to minors in the US or Canada -- attempts were deemed unconstitutional. It's an industry regulation.
There was no next ... ffffff.
Unfortunately it was before Google so you didn't find it.
AOL Keywords, Navigating through a Yahoo directory tree, and Webcrawler :(
Actually from where I heard this story originally, it SHOULD include Youtube, etc.
And yet so many people think that Google *is* the internet these days.
There's something deliciously ironic about math helping people get to 3rd base quicker.
Because Android uses Java for its applications... and Jobs is a very very spiteful man.
To be fair -- in your comment between eggs and embryonic stem cell research... ... we don't eat human eggs.
... nooo... ... but (creating or studying) artistic expressions of said acts should not only be legal... but should be promoted.
... threat of legal recourse regardless of how severe is still a form of advertising. Almost no publicity is bad publicity.
That said, I very much agree that our problems with bestiality stems from our problems with sex... especially since it occurs to various degrees in just about every instance of sex... from masturbation through to furries... homosexuality to pornography. (IMO -- all four listed subjects are perfectly healthy for those who genuinely enjoy it... among many other taboo topics)
And the worst part is -- it's entirely counter-productive. Promoting self-expression in the long run and on average promotes the best citizens. Obviously I'm not saying that everything should be legal or sponsored by the Government...
It's like how the crime rate typically drops when the death penalty is revoked in a given jurisdiction...
What would such a mission entail? Actually seeing the asteroid before it hits us... ... we have serious problems with that as it is.
Then of course you have the problem of public companies being legally required to ONLY consider the best interest of their shareholders and related business partners -- especially those which may have a massive (at least perceived) financial interest in crippling the company's infrastructure... ahh conundrums. Good luck sorting this one out folks.
I believe I saw a 3-country license of Cyber Shield in a Best Buy or something...
The extra jobs are for the future products from the same development team... ... which likely would have made it regardless.
Piracy can be damaging to a company -- but almost always the company sunk itself -- either by fighting piracy rather than monetizing their audience... or by being confused to what their audience even is.
Adobe knows that residential piracy of Creative Suite applications is beneficial for them in the long run... they try to get the professional user to push their company for a license of Creative Suite (or purchase it themselves if they go commercial freelance)... and they try to get the casual user on the Elements line. They're better off just letting the middle (aspiring professional) that can't due with Elements pirate Creative Suite so they become legal users when they become commercial... rather than commercial GIMP/etc. artists.
Agreed. You could burn a flag -- it's just cloth... but it will be taken as an assault against something other than polyester.
If your company spends its time and capital developing all their new features open... it doesn't need to spend its time and capital defeating other standards. Betamax was technically superior to VHS.
Yeah, common law has often shown that Non-Compete doesn't actually work... judges often overturn. Beyond that though, keep in mind... *they* fired *him*... the contract was already breached... and severance was paid.
... I'm not sure if loading many elements in a single Powerpoint slide is achievement worthy...
Acheivement Unlocked: Used Times New Roman font... again!
Seemingly ironic, yes -- but this isn't releasing information of an ongoing legal process, it's releasing opinion-based statements against the Defense's legal statement publicly. If this trial somehow attempts to deport Assange to the States (where he faces charges from his work at Wikileaks) -- it's total BS.
Simply put, you can view Wikipedia faster on the cheaper ISPs.
They break programs that were poorly written, simply put.
Some people execute off the data memory space... some people point to specific points in memory assuming that what they think they put there will be there.
Either they draw a line in the sand and break those programs (some of which are internally-developed corporate programs where the programmer quit and/or died years or even decades ago...) or they let those programs ride in the exception category.
It has nothing to do with ASLR or DEP... it has everything to do with programs written by people who didn't know and/or care that ASLR and DEP exist... and would crash if ASLR or DEP were running on them.
If everyone practiced great and secure programming practices... DEP and ASLR would be next-to perfect solutions to prevent the "whoopsies" from overwriting execute addresses. Unfortunately... that assumes that the only time you're executing from data is by accident.
Yes they can install a rootkit.
The user and the programs they run have limited permissions -- they do not have the permissions to install Rootkits... but they can call APIs with root permissions.
If those libraries (such as, for instance, networking APIs) accept data... it will place the data in the memory space of the API's code. If there's a flaw in the way data is written to the memory... the API might accidentally overwrite some executable code in its memory space.
What happens the next time the executable code is called? It's not there anymore... the data is there because the API accidentally overwrote itself with the data
What if the person who sent the data KNEW that API had a problem with specific sized data under specific conditions? What if they ALSO knew exactly how far from the start of the data the start of the executable code was in the program's memory space?
Get them to open that data under those conditions... and blam... a limited user passes data to a limited program which passes data to a high-privileged API which runs the malware blindly.
What permissions level will it have? The API's... because that's where the overwritten executable code is... the processor and OS simply sees executable code from a high-privileged API and runs it (Unless it has DEP properly configured -- in which case it says "Huh... this code is tagged as data HOLY CRAP ABORT!" and your program or whole damn computer crashes gloriously to prevent the data from executing.)
This is an inherent problem with computers. Somewhere... someone... needs to be root privileged. If that root privileged code accepts data... you can have a security flaw. And errors like that are something that you could review dozens of times and never see anything wrong with it.
XKCD explains it well -- http://xkcd.com/327/
They used Scaleform -- which uses Flash tools -- but uses its own Flash-clone for the player.
Really it's not the patent or copyright system that people are against -- it's people being dicks.
You can have proprietary dicks sending DMCA notices or filing patent/trademark infringement cases for -- for example -- having the letters "sky" in the product name "skype" (oddly enough without going after Microsoft for SkyDrive or Google for Sky... you know -- the companies who can fight back).
You can have proprietary people doing *great* things... giving APIs, providing community support, multi-licensing for educational or whatever.
You can obviously have open people doing great things for the community -- just look at slashdot for that example. They can also be dicks... shunning everything that's not GPL complaint... etc. Basically being almost identically behaved as the proprietary dicks... just using the copyright law to say "You must -----" rather than "You can't -----".
Obviously dependencies gets complicated especially for software patents and copyrights -- so libraries and OSes are best in the more LGPL-side of things (so that the programs, some of which are artistically and culturally relevant, are on a platform that's legally enforced to be open forever) but yeah. Tangent in a tangent in a tangent.