-
Website
http://mashable.com/ -
Original page
http://mashable.com/2007/04/19/petition-against-alexas-statsaholic-lawsuit/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Robert Basil
142 comments · 9 points
-
Jennifer Van Grove
152 comments · 23 points
-
r0cketman22
322 comments · 52 points
-
rajagiri4
160 comments · 2 points
-
barringtonarch
155 comments · 4 points
-
-
Popular Threads
-
AT&T CEO Wants iPhone Users to Limit Usage
1 day ago · 172 comments
-
Facebook’s New Privacy Push Concerns Experts
13 hours ago · 50 comments
-
Facebook Is Down
7 hours ago · 21 comments
-
What Do Seniors Do Online? Visit Facebook and YouTube, of Course [STATS]
5 hours ago · 13 comments
-
Burger King Beguiles Hungry Men With Shower Babe [VIDEO]
7 hours ago · 17 comments
-
AT&T CEO Wants iPhone Users to Limit Usage
How about agreeing on a self imposed ban to not report any news pertaining to Amazon or ones in which Amazon is a party.
It wont hurt us, we would still have plenty of stuff to report, but it will surely make higher ups at Amazon shiver.
Think about it and let me know.
Fair enough. Not covering Alexa is easy...I don't trust their stats too much anyway (and I hope that statsaholic will add other stat providers for comparison).
Not sure what we'll do re:Amazon coverage.
I am fairly confident, we could get through with this.
Statsaholic you got my support.
This statsaholic product was not using the known Alexa API to there web services. Instead he was avoiding the cost of using them by some sort of scraping.
I have always paid for the use of Alexa's web services. Read google's terms of service (google maps), you are not supposed to make ANY money off your mashups. Alexa and Amazon WANT you to make money, but they also need you to support their costs hence the exorbitant (read sarcasm) $0.15 for 1,000 requests. I mean this is like using Amazons S3 service to store data, and not paying for it, how could we expect them to support that (without putting up ads or something)?
If this guy wanted to build the site, he could have, but he also could have paid for the use of the data. He bit the hand that feeds him and is getting what he deserves.
At least read Alexa's side of the story before you jump to conclusions.
http://awis.blogspot.com/2007/03/alexaholicstat...
I agree with you.
"The Alexa Web Search Platform provides public access to the vast web crawl collected by Alexa Internet. Users can search and process billions of documents -- even create their own search engines -- using Alexa's search and publication tools. Alexa provides compute and storage resources that allow users to quickly process and store large amounts of web data. Users can view the results of their processes interactively, transfer the results to their home machine, or publish them as a new web service." - https://websearch.alexa.com
And what took a billion dollar corp a whole year to sue a little guy ?
Are you donating the disk space and cpu power to Alexa to have them hand out the information to Statsaholic?
If the answer is no, then Alexa has to pay for storage, bandwidth and cpu power. How would you suggest they do that?
All statsaholic had to do was do what everyone else who uses the Alexa API does, and pay the modest amount for the service (I do it, why should anyone else be exempt?)
Bilal: Alexa/Amazon is not a charity. They used their skills to collect user data. That data is an aggregate and does not belong to you, or to any other group of users. If they want to charge for it, that's their decision. It's not a tax if you have the choice not to pay it.
I can't speak for the developer, because he's currently embroiled in this lawsuit. But offers were supposedly made to pay for access at a higher price than the API fees and rejected.
This should have been settled by both parties just agreeing to a price for the data - claiming hundreds of thousands of dollars in damages is overkill. I was largely on Amazon's side until they went with the heavy handed approach.
Alexa should not decide to allow some applications that use there api and disallow others.
If that is true, I might change my opinion. Right now it is He said She said stuff....
Note also that timing of this offer to pay more for the service would matter too, Statsaholic may have burned bridges...
Anyway I think it is useful to at least see the other side of the story.
Thanks for the info Pete!
James
Back in early 2006 I had to use Geocoding for European Countries in a project I was doing. From all the search companies with a local search property only Microsoft was providing Geocoding via its API for a subscription fees. Guess what, I didnt used it because at that time I didnt have had credit card. In about a month Google offered Geocoding Data for Europe for free. Although it was getting that data from companies like Mapquest and others for a fee.
You know whats the difference between MS and Google. MS makes a product and then thinks about how to get its users blood dry, by imposing all sorts of subscriptions and fees. Google makes a product and offers it for free and tries to be of value to users, and once it is of value it tries to monetize not by sucking its users dry but rather by serving ads.
So dear get over the MS mentality, it wont get you anywhere...
Yeah, I agree with the He said She said analysis. I don't put statsaholic totally outside of blame's way (in fact I think Ron may have fired them up a little bit by ducking the filters - even ZDnet says it was cat and mouse). But I do think a lawsuit is a step too far.
It's a bit like Photobucket vs MySpace - MySpace actually has a case, but they receive bad PR nonetheless. I don't think Alexa's lawsuit is totally meritless, but it is terrible PR for a company that's trying to promote itself as developer friendly, and pursuing this any further would be disastrous. Legitimate users of the API may be left with the impression that Amazon will resort to legal action if any dispute arises.
Note that you also cannot use most Google services to make money, legally that is. So if you were charging for (or making money from) your geoencoding service you were probably violating googles terms and conditions.
Maybe you're right and Alexa should have a business model where they advertise to make there money back. I have no idea if that would work.
But dear, not everything in life is free, especially if the service is designed to build a company around. Frankly if Statsaholic didn't like Alexa's business model they should have gone to someone else, not violated the terms and conditions of Alexa.
James
Legal stuff should always be a last resort I agree.
Well we shall see, there is always the possibility of a settlement and something that could make everyone happy...
Anyhow sometimes a dissenting view is useful I think, sorry if I annoyed everyone.
Statsaholic is hotlinking images from Alexa. Isn't this a bad thing to do?
Amazon provides an API to get this data. Statsaholic could be using this service, but it is not.
The API costs money to use, similar to most of the other Amazon APIs. This is probably why Statsaholic is not using the API.
But since Amazon is using their resources to get the data in the first place, they should be free to charge whatever they want. Again this is similar to their other services.
Why is hotlinking images ok for Statsaholic to do?
Web 2.0 is supposed to be about collaboration and connectedness, where is the example from Alexa here?
https://www.amazon.com/gp/help/contact-us/gener...
Viva la Boycot!
I'm going to have to look into using something else other than S3 which I have been happily using for a while now.
Some people just don't get what it means to release an API. It's not so that you can wait until someone else develops an application using your API, then you steal the idea from them by crying trademark violation or some such. Very disappointing.
Hell, we can't even agree on a bad guy when we are apparently see one in action.
Google is wonderful and perfect, Digg is the place for news (whoooaaahahahaha!), MySpace is a community like a quaint little village in the Swiss Alps, and YouTube is the Web 2.0 equivalent of "I Love Freaking Lucy."
"Ricky, Ricky Fred has got his hand up my dress! Don't worry Luceeee, Fred is our neighbor!"
It is true, the relative allegations should be examined. Perhaps a boycott of Amazon until they either produce incontrovertible evidence that mean old Statsaholic harmed them?
The blososphere can be the jury. Give them 1 week to present the evidence, let Pete be the judge and we come back here and decide.
Now that would be Web 2.0!
http://techfold.com/2007/04/20/what-is-the-real...
The meat of it is:
It emerged in comments however (see comments by James), that statsaholic was not using the Alexa API (which charges fees), but was instead scraping, or otherwise circumventing the API. James points readers to the Alexa Blog post on the topic in which Alexa takes issue with:
1. Trademark infringement via the “Alexaâ€holic name. Though Alexaholic has changed its name, Alexa points out that Statsaholic still redirects the Alexaholic domain to the new site - a remedy that is not satisfactory to Alexa. Personally, I think Alexa forfeited their rights to demand restitution from Statsaholic by allowing the use of the Alexaholic domain for years, and explicitly stating that they were aware of the Alexaholic, and supportive of it. Alexa should be content with the Statsaholic switch and call it a lesson learned on trademark protection.
2. Alexa also takes issue with Statsaholic’s use of graphs. The Alexa fee-based API (AWIS)does not include graphs - so statsaholic apparently (more-or-less) hotlinks them. This issue has the ring of legitimacy to it. The charts and the system to produce them consume resources, and the IP behind the charting system has value. If Statsaholic used paid AWIS data and their own charting engine, their wouldn’t be a problem. But it seems that Statsaholic is doing neither.
IN summary: (a) Statsaholic is entited to the Statsaholic name, and traffic from Alexaholic. (b) If Statsaholic is a viable business, it can afford to put out for its own chart rendering engine, and pay for use of AWIS data. To be honest, that sound preferable anyway - there’s a lot more opportunity to add value to data when you’re completely in control of presentation; and, that would give Statsaholic the opportunity to blend with data from other sources, creating a superior metric.
In any event, Alexa I don’t think Alexa needed to resort to litigation to get this ball rolling, but I don’t know both sides of the story. Pete C. suggests in response to James in comments that Alexa tried to up-charge Statsaholic, asking for more than the standard AWIS fees - is this substantiated?
Since this is not the service they provide via the API, it makes sense they would charge more for it for this one-off case.
Of course, if he uses the API, Amazon will not have a problem with that.
:( :( :(
I wouldnt want to have to do anything with Amazon.com, if this is how it chooses to be.
James and techfold said it best. If someone is not willing to sell you something (access to their proprietary graphs), then you can't steal it by claiming you offered to pay.
Statsaholic should give up the alexaholic domain, and generate its own stats based on the Alexa API. If they survive this lawsuit that is.
'Nuff said.
Is this another nail in the coffin of cooperative net building?
User-agent: ia_archiver
Disallow: /
Lending your tools to the neighbor and getting mad when he uses them better than you did is pretty childish.
The problem is that Statsaholic isn't actually USING the alexa API, though they could be. Statsaholic is deliberately avoiding using the alexa API to avoid paying the fees associated with its use, hence the lawsuit.