Drew from zillow. I've been in contact with Mr Bunson about this issue. I don’t think that it’s appropriate to discuss our conversation in public, however, I will say that what is described here is not a complete representation of the conversation. He’s welcome to continue to use the API as long as he doesn’t infringe upon our trademark and use our brand name "Zillow" on his website.
I believe you have to be able to show that you tried to stop others from infringing on your brand to protect your trademark at some future point in court.
Google sent letters to many people when 'google' was becoming a verb most likely for this reason.
Is that a bad thing? It's their data, and it's helping them. I think the damage to their brand among developers is happening right here (I'm sure as hell staying away from Zillow in the future). Compare that with the 'damage' it would cause some random consumers who may or may not have a problem with izillow. Not worth it.
There are people out there who will read "unofficial version" and still not know that it's not official. Those people will not be any more clued in just because it has a different name - if it looks/works like zillow, it is zillow. Targetting this level of understanding is futile.
Honestly I can understand zillow's side here but I'm just curious. Shouldn't the original use of izillow.com been grounds for trademark enforcement? The only thing I think is less than savory is that now, when you have your own iPhone application, you're going after this person and making sure people don't mistake it for an official version.
But like you say, there are details here that have not been disclosed, so I am by no means passing any kind of judgement.
Have you folks learned nothing from previous examples?
Just a few weeks ago, the 'hacker community' was raising torches and pitchforks to defend a logo creator accused of "stealing his own work". We later learned he was likely guilty as charged: http://news.ycombinator.com/item?id=552160
Have any of you spoken with Zillow? Before picking up your e-torches and e-pitchforks and twittering yourselves into apoplexy again, you might want to pause and ask "why would a company who depends upon developers do something so obviously hostile to third-party developers?"
Something doesn't smell right here, and public airing blind conclusions in a "too smart to be wrong yet again" echo chamber doesn't help matters for either party.
Ok sorry about the douchebag part but come on, what part of YOUR API don't you understand? You need to grow a pair and tell your lawyers they work for you, not the other way around.
If he's using your API, and publicizing your service, what is he supposed to call his app/website?
His new about page would read: "We use an API from a company in which we cannot name, trust us it's really good and you know them, but for legal reasons we can't say who it is."