News for hackers. Stuff that matters.
Re:How I attacked myself using Google and I ramped up a $100... by hm8 on Wednesday April 25, 2012 @05:14PM (#3891134)
Like the author notes, I don't think the problem was with Google. It was no fault of theirs. The reason: It's a fine line between maintaining privacy policies and managing such events. If google were storing/caching these links, there would have been an outcry from those worried about user privacy and stuff.

About the by-the-hour downloads, well there again is a trade-off between providing data quickly and doing a lazy evaluation.

I think, as the author notes, it was just an unfortunate event that was a consequence of good design decisions gone bad circumstantially and wreaking havoc for the author.

It was certainly nice of Amazon to have made that refund. The resources (read bandwidth) were used after all.

Re:How I attacked myself using Google and I ramped up a $100... by mooism2 on Thursday April 26, 2012 @03:05AM (#3892823)
Google are presumably storing/caching these photos for an hour before expiring and redownloading them.

I don't see why Google don't redownload them using If-Modified-Since, and reusing the original downloaded photos in the case that the origin server says they've not changed.

Re:How I attacked myself using Google and I ramped up a $100... by ricardobeat on Wednesday April 25, 2012 @08:26PM (#3891782)
I don't understand the privacy concern - a publicly accessible URL doesn't offer any privacy. It's the same as a transparent proxy.
Re:How I attacked myself using Google and I ramped up a $100... by andrewreds on Wednesday April 25, 2012 @11:49PM (#3892298)
A password works by there is a piece of text that only you know, and thus, when you give that password to a server, that server knows who you are.

can't you also view a url as a password? (If only I know the url, then only I can download the file).

I am able to give out a url to someone else, so they can access the file, likewise, I can give out my file server's username and password, and whoever has it can also access my files.

Re:How I attacked myself using Google and I ramped up a $100... by gizzlon on Thursday April 26, 2012 @03:36AM (#3892884)
You have a point, but the difference is that url's are not usually considered secret and are therefore not treated the same way a password would be. For example in the browser..
Re:How I attacked myself using Google and I ramped up a $100... by piaskal on Friday April 27, 2012 @07:30AM (#3898567)
Google is already storing urls to those files.
Re:How I attacked myself using Google and I ramped up a $100... by yew on Wednesday April 25, 2012 @09:55PM (#3892003)
I think it is primarily a legal concern. Legally, caching public content is not always an acceptable (or at least clear-cut) practice. I concur in thinking that's a little silly, but enough people disagree for it to be an issue that Google has to take into account.

There have been similar complaints about attempts to aggregate the contents of Hacker News posts, for example.

Re:How I attacked myself using Google and I ramped up a $100... by tripzilch on Thursday April 26, 2012 @08:11AM (#3893469)
> If google were storing/caching these links, there would have been an outcry from those worried about user privacy and stuff.

Where would we be without Google taking such a noble and strongly principled stance on user privacy, applied equally and consistently, striving to avoid legal responsibility, even when it costs unrelated parties thousands of dollars.