A cautionary tale for sure, we do the same, but luckily via remote satellite hubs on a queuing system so ours has not broken.
I think if anyone ever uses another persons data or API they should build in a remote location and caching function from the ground up to avoid these issues. Either when they break by design or accident.
I don’t think they were harsh at all, McGovern tried to contact them before blocking them, which is the polite professional thing to do.
Not having a pop at ManagedQ as I don’t know them but, there are too many new companies out there ripping off other peoples content without permission. I know that I’m seeing more of it in the U.K.
Doesn’t hurt to actually ask for permission does it?
It wasn’t harsh at all. In other industries (travel) you still have to pay to get data every time a user requests it, very un-”2.0″ but that’s life, no such thing as a free lunch.
Marzipan from Toledo
“which is run by a few programmers out of a basement in Palo Alto”
….yeah, a few programmers in a garage never threatened anybody … ha
Was he justified? Is that an honest question?
It fits right in with my Scrabulous arguments… these companies are protecting their brands.
What if I had made a site that scraped the managedQ offering via server requests and duplicated their site 100%, making their servers do all the work of building the result set while I yanked the HTML and replaced their logo with my own? Would that be acceptable? If they got pissed about that would it be an overreaction?
Imagine if they had credited Snap with the images… had they given attribution and graciously and profusely thanked Snap for such a bomb ass service then things might have gone differently for them.. but they knowingly deceived both Snap and their users in what can only be described as cowardly and despicable… and they know it.

techcrunch.com