Jennifer Lawrence consented to the distribution of the photo on the magazine cover. The personal photos were just that - personal.
The existence of a photograph or video of your naked body in the public sphere does not grant the public ownership over all images of your body, similarly to the way that giving a person permission to have sex with you N times does not automatically give them rights to N+1.
What makes DRM different from SSH/SSL/PGP is that after SSH does its part in delivering data to you securely, it releases the data to you to do with as thou wilt. DRM systems are designed to ONLY release the data to your eyes and ears so that the analog hole notwithstanding, you can't make a copy.
Having an open source DRM client would allow you to modify the client to put decrypted data anywhere. In a file, for instance, thus cleaning DRM from the content.
This has nothing to do with secure key exchanges and everything to do with what happens to the data between decryption and playback.
Tell me how a air traffic controller or a teacher, to use two examples a "parasite appendage to the real economy"? All are not strictly needed, but the economy would be much smaller if planes would crash into each other, or if people didn't learn to read and write so they could contribute more to the economy.
Technically, services such as air traffic control, education and the transportation infrastructure don't have to depend on the government. Private entities could be established to maintain and develop these systems on a for-profit basis. Users of these services would be billed directly at the time they use the services. The public at large would not be directly financially responsible.
Whether subjecting things like education and traffic control to the whims of private interest is a good thing is another question.
> Gimme a program that I can take a picture of the nutritional label that comes on EVERYTHING, > and log that I ate it. That's OCR. It's kinda hard. I'll wait.
This onion has no nutritional label, so you can't use OCR./Maybe/ the app can recognize the object as an onion, estimate the mass of the onion based on known geometric parameters, and log the nutritional content based on mean-onionness adjusted by inferred z-score?!! Ok, that's legit. But.. how does it know how much of the onion I ate? Self reporting is not accurate, so... what, assume I ate the whole thing? Aaagh, this is killing me!
On behalf of all bitter, sad people drinking alone at the bar I would like to protest. Many sad, bitter people drinking alone at the bar are also perceptive, intelligent people and as such would never express their sadness and bitterness by either posting empty inflammatory statements on Slashdot, nor expressing their biased blanket judgements against sad, intelligent drinkers by callously lumping the aforementioned drinkers into the same derogatory category as the author of the aforementioned inflammatory statement as a form of retort.
http, html, javascript, etc... are just for the view. For the heavy server-side lifting you can use whatever proven reliable technologies you feel like entrusting your project to.
Tried a browser-based UI and come to the conclusion that it just won't do?/If/ you structured your app properly, you can swap your browser-based front-end for something else without completely uprooting your back-end. It's not going to be effortless, but then again you shouldn't need to get too deep into your project before you realize the UI's no good.
This mainly applies to business apps that can deal with a bit of UI latency and don't need to pump huge amounts of data to the user (i.e.: not a professional graphics app).
MS Office is faster than OO. Faster to start, faster to use, faster to sort spreadsheets. That's the #1 problem my users have with OO. The company I work for is pretty cash-strapped, so we use old machines / FLOSS wherever we can, and while OO does not cut it on a 1.4 GHz PowerPC with a gig of ram it is absolutely dysfunctional on a 700MHz machine. NeoOffice too.
Slashdot Mirror
Could have been an ok reply, if not for that homophobic slur at the end...
Consent matters.
Jennifer Lawrence consented to the distribution of the photo on the magazine cover. The personal photos were just that - personal.
The existence of a photograph or video of your naked body in the public sphere does not grant the public ownership over all images of your body, similarly to the way that giving a person permission to have sex with you N times does not automatically give them rights to N+1.
why?
What makes DRM different from SSH/SSL/PGP is that after SSH does its part in delivering data to you securely, it releases the data to you to do with as thou wilt. DRM systems are designed to ONLY release the data to your eyes and ears so that the analog hole notwithstanding, you can't make a copy.
Having an open source DRM client would allow you to modify the client to put decrypted data anywhere. In a file, for instance, thus cleaning DRM from the content.
This has nothing to do with secure key exchanges and everything to do with what happens to the data between decryption and playback.
Tell me how a air traffic controller or a teacher, to use two examples a "parasite appendage to the real economy"? All are not strictly needed, but the economy would be much smaller if planes would crash into each other, or if people didn't learn to read and write so they could contribute more to the economy.
Technically, services such as air traffic control, education and the transportation infrastructure don't have to depend on the government. Private entities could be established to maintain and develop these systems on a for-profit basis. Users of these services would be billed directly at the time they use the services. The public at large would not be directly financially responsible.
Whether subjecting things like education and traffic control to the whims of private interest is a good thing is another question.
EXACTLY like murder.
why would they?
> Gimme a program that I can take a picture of the nutritional label that comes on EVERYTHING,
> and log that I ate it. That's OCR. It's kinda hard. I'll wait.
This onion has no nutritional label, so you can't use OCR. /Maybe/ the app can recognize the object as an onion, estimate the mass of the onion based on known geometric parameters, and log the nutritional content based on mean-onionness adjusted by inferred z-score?!! Ok, that's legit. But.. how does it know how much of the onion I ate? Self reporting is not accurate, so... what, assume I ate the whole thing? Aaagh, this is killing me!
On behalf of all bitter, sad people drinking alone at the bar I would like to protest. Many sad, bitter people drinking alone at the bar are also perceptive, intelligent people and as such would never express their sadness and bitterness by either posting empty inflammatory statements on Slashdot, nor expressing their biased blanket judgements against sad, intelligent drinkers by callously lumping the aforementioned drinkers into the same derogatory category as the author of the aforementioned inflammatory statement as a form of retort.
Does the leader of a country need to know how all the mechanisms that run the country operate?
No. Leaders hire experts.
wait... so you mean the odds are just like in the real world?
By "looking over both shoulders", do you mean "behind you"?
> you have no guarantee
What guarantee is there that the driver will be monitoring the camera display?
You've never seen an unregulated rail crossing, then?
Yeah! And American Idol has some genuinely talented singers!
http, html, javascript, etc... are just for the view. For the heavy server-side lifting you can use whatever proven reliable technologies you feel like entrusting your project to.
Tried a browser-based UI and come to the conclusion that it just won't do? /If/ you structured your app properly, you can swap your browser-based front-end for something else without completely uprooting your back-end. It's not going to be effortless, but then again you shouldn't need to get too deep into your project before you realize the UI's no good.
This mainly applies to business apps that can deal with a bit of UI latency and don't need to pump huge amounts of data to the user (i.e.: not a professional graphics app).
yeah, but then it's just a matter of time until someone cracks the currency and learns to activate the evil bit.
what happens when the trolls extort actual money from them?
Nothing. They pay and move on. Losing the occasional trollsuit is the cost of making a killing.
are you challenging the internet to produce an scp client with porn popups?
Dude.. sorry.
MS Office is faster than OO. Faster to start, faster to use, faster to sort spreadsheets. That's the #1 problem my users have with OO. The company I work for is pretty cash-strapped, so we use old machines / FLOSS wherever we can, and while OO does not cut it on a 1.4 GHz PowerPC with a gig of ram it is absolutely dysfunctional on a 700MHz machine. NeoOffice too.