I missed the boat... posted the comment to the wrong story AND made it too late http://yro.slashdot.org/commen...

But I'm having trouble finding who DID make it.

real protests have 50000000 members

50000000 ftw?

http://www.threefeloniesaday.c...

If you're going to include an obscure technology like Java in the article. Could you please explain what it is?

Calling... https://www.youtube.com/watch?...

I'm going to call Godwin on that string theory remark

TFA quotes this estimate to Information Technology and Innovation Foundation (ITIF). This is not a source that I would trust to give estimates on the amount of US business lost due to public knowledge of NSA industrial espionage.

Another publicly available and reliable source of attributing business losses to external factors already exists: public company 10-K reports, including the Risk Factors section and the MD&A section.

Although there may be a bandwagon effect, or a "bath" effect which may cause overstatement, this will provide a great upper bound for the actual business lost due to these reasons. Companies CYA by disclosing all kinds of risks, including even some of these obvious items:

> ENTRANCE INTO NEW OR DEVELOPING MARKETS EXPOSES US TO ADDITIONAL COMPETITION
> Difficulties in staffing and managing international operations

So, when we start seeing real companies blaming their missed results on this reason, then I will see the reason as credible.

The only rapper that is worth listening to who talks on science topics is MC Hawking.

Yes, and if you gave someone who never read or wrote code before and gave them a printed sheet of Perl... they might wonder if the sheet is upright or upside down.

The correct cause of action is:

Common carriers should not be modifying the content of their service.

Good point. If someone places 200+ calls to 911 and they are not stopped, this is a failure of E911, not the NSI policies.

To add to the discussion regarding 18 U.S.C. 1030, I will note that this website does not affirmatively note anywhere that these photos are to be considered private.

Thank you, this is the discussion I hoped would come out of this article. Fact is, people on Slashdot are definitely going to stumble onto this type of stuff over and over. I'm glad to run into other people to compare scruples with.

Hackers (good word) have an instinct. If they run into an awesome API, the first thought is: how do I maximize this across all the limits and make something amazing? But with vulnerabilities, and unintended code paths, you need to step back and understand the consequences of what you are doing as well as the appearance of what you are doing. A comment from Greyfox below illustrates perfectly, "so why don't we take the dick-detection algorithm from Chat Roulette and then plug that into a batch Curl against this Artisan State, and then...". Obviously that was facetious, but you need to avoid certain lines of thinking... "well I know this thing, and I could tell everyone, but they wouldn't want that, and then they have lots of money...".

At the end of the day, you need to have clear intentions and don't inflate your ego by thinking they are more interested in fixing the problem than you are.

Obviously the photos aren't that private (the Asian girl), since I put them on Slashdot's front page. But the others ones (now seeing the lax security) it will be worth for me to invest in a good printer and print on my own.