Google Takes Down HuddleChat After Complaints [Warning]

desmondhaynes writes "There were striking similarities between one of Google's App Engine demos, HuddleChat (a real-time chat application) and the Campfire app from 37Signals. Google has taken HuddleChat down from the App Engine app gallery." Google explains: 'The App Engine team was looking for some sample apps to help kick the tires on their new system, so we invited Googlers to build some as side projects. A couple of our colleagues here built HuddleChat in their spare time because they wanted to share work within their team more easily and thought persistent web chat would do the trick. We've heard some complaints from the developer community, though, so rather than divert attention from Google App Engine itself, we thought it better to just take HuddleChat down.'" We noted the launch of Google's App Engine yesterday.

Update: 04/10 14:51 GMT by KD : A reader wrote in to warn that the link in this article is infected. Windows users beware, and have your AV up-to-date.

Whiners

[Anonymous Coward]

If your business model is based on such a trivial application, why should anyone care if you fail?

Re:

[Thought1]

Exactly. Get a clue, people. Stop trying to patent the frikkin' XOR cursor loop.

Re:

[easyTree]

Exactly. Get a clue, people. Stop trying to patent the frikkin' XOR cursor loop.

That sentence is MINE, BITCH! (Patent #9023092384092384.)

Early settlements will be accepted etc..

Re:Whiners

[NoTheory]

No, if 37signals business model is that trivial.

The complaints are ironic if what Zed Shaw says [zedshaw.com] is true:

Well, silly boys and girls, rails-core ripped off the idea and probably most of the workings for Campfire from NextApp Echo2 ChatClient Demo. [searchenginewatch.com] I know this because I was in the rails-core IRC channel and I showed them how cool this Echo2 framework was, including that chat demo. A few weeks later they had Campfire and since they say it took them two weeks to write it, Iâ(TM)m guessing they got lots of inspiration.

Re:

[easyTree]

* Warning: similarity detected between two things contained within the universe. Lawyers are being dispatched to your location. do - not - move! *

*Sigh* - 'Tired of the "this idea is mine and noone else's" now. Please stop.
 

Re:

[easyTree]

I'm mean really, how far would football as 'sport' have gotten if every team was required to have their own shape of ball? Yes, I realise the USAnians have already made a start on this :D but at least they share the ball between two parties; both of whom have several indirect common goals.

Whatever happened to:
a) 'hey, look what I can do'
b) 'cool; if I take what you did and add *this*..'
c) 'omg yeah, waaay cool'
d) goto b

now it's:
a) 'hey, look what I can do'
b) 'cool; if I take

37Signals should learn to innovate, not whine

[Anonymous Coward]

If you want it make it big by offering minimalism don't be surprised when someone does exactly the same thing. The 37 Signals developers and DHH should be ashamed of themselves for claiming huddlechat is a rip off, it is an obvious idea and plenty of other websites had implemented similar chat system BEFORE campfire ever came around.

It is funny how a company who sells a book on design philsophy complains when someone else uses that philosophy.

If you deliberately make featureless software don't be surprised when people "copy" it, even as a tech demo.

Compete and Innovate.

Re:37Signals should learn to innovate, not whine

[Anonymous Coward]

I agree, I followed this controversy and frankly the issue is that both huddlechat and campfire look exactly like many of the AIM clients out there. They have the same layout and very similar features. They even look like toned down MSN chat applications. If you design to the style du-jour it is totally likely that you will look similar especially in a similar arena, chat clients. I think the issue here is that the domain is so minimal that any client who tries the bare minimum of ajax web chat with file uploads will end up being the same. So I guess 37signals is claiming they somehow own the minimal implementation. Well they don't, it is an obvious idea and they should buck up.

Re:37Signals should learn to innovate, not whine

[ShieldW0lf]

I wrote something like this 5 years ago, so we could have a chat meeting with some clients who were behind a corporate firewall. It wasn't that pretty, but it did pretty much the same thing, and it only took a couple of hours to write.

I would be ashamed to put something so trivial out into the community and charge people money for it.

Wish my girlfriend bent over as quickly and easily as Google.

So, when will Google be taking down every other service offering they have besides search? Everything they offer outside of Search and Google Earth are "me-too" products when you get right down to it.

Re:

[Anonymous Coward]

Wish my girlfriend bent over as quickly and easily as Google.

She does.

Re:

[billcopc]

Why is there no "+4 Saved this boring thread with a laugh" moderation ?

Yeah, that perked me up a tad on this gray depressing day.

Re:

[darkpixel2k]

I wrote the whole thing in mod_perl inside of 8 hours.

Oh yeah--well I wrote mine in mod_python inside of 4 hours...

Re:37Signals should learn to innovate, not whine

[StallmanHearties]

This is also ignoring the issue that this company is selling the software as a service. Which means you are paying for timesharing. If it were free software you could install it on your machine and provide a service to people you care about. You could also ensure your privacy by installing it on your own machine. Timesharing is generally bad because it means you have no freedom to change and 37signals has long had a history of ignoring customer feature requests.

IAWTP. Innovation that Campfire should offer:

[Enlarged to Show Tex]

Computerized smoke signals

Re:IAWTP. Innovation that Campfire should offer:

[calebt3]

I know! Let's call it UDP!

Re:IAWTP. Innovation that Campfire should offer:

[Enoxice]

I just thought you should know that I've tried explaining this to everyone around me that heard me laughing, and I think I failed at it.

Re:

[geminidomino]

You bastard... do you have any idea what green tea in the sinuses FEELS like?!

Re:

[encoderer]

Warm Snot?

Re:

[geminidomino]

No...

Tanic Acid + Mucus Membranes != a fun time

Re:

[geminidomino]

That is, of course, supposed to be "tannic" acid

Re:

[binaryspiral]

Computerized smoke signals

No, no, no... Sony's batteries already have this feature.

Re:

[Seumas]

I'm not familiar with either app, so perhaps I'm missing something. However, how can they get all stirred up over it? Can ONLY "Remember The Milk" do to-do lists on line? Can ONLY Amazon do sales online? Can ONLY Google do spreadsheets on line?

Seriously, unless the Google version clearly took a trademark or other creative content from them *or* literally took actual CODE from them, then who the hell cares?

Whiney Ruby bastards.

Re:

[cmacb]

"Seriously, unless the Google version clearly took a trademark or other creative content from them *or* literally took actual CODE from them, then who the hell cares?"

Apparently people who work for 37signals, and all their family and friends, and friends of friends. The Google group on this seemed to have about 3 to 1 diatribes about how evil it was to steal this pathetic concept. If I were Google I would have just told them to screw themselves... but the bad PR 37signals will get for being wuss programme

Re:

[Joe U]

Campfire is about as complex as KeepTalking was in 1999. It's not original, it's just flashier.

Re:

[NigelBeamenIII]

According to the blog Read Write Web [readwriteweb.com], they received an e-mail from Jason Fried, the 37Signals founder, claiming that it was basically a "feature for feature, layout for layout" copy. That's the closest I've found to them officially whining so far.

IRC rip-off?

[Anonymous Coward]

"Persistent web chat," eh -- the idea sounds so novel, I'm sure they must have pirated source code straight from "campfire" -- unless this is just a web frontend to IRC, like yahoo! chat or something like that.

What's the big friggin' deal? Not that I've ever even heard of Campfire anyway, but it doesn't sound unique in any meaningful way.

and first post.

Re:

[TheBracket]

Even if its not an IRC front-end, "persistent" web-chat is hardly a novel concept. Heck, I had it running (in ASP, blech) on a site I created back in 1999 - complete with "rooms" that retained their state/history, searchable logs, etc. It's not exactly rocket science.

Re:

[Hatta]

If you just need a persistent IRC session, use irssi & screen. It can't be beat.

Please help me out here

[Fuzuli]

I'm not sure I am getting the reason for taking this app down. Really. If I were to clone an app to demonstrate a new platform, would that be a problem? So, what is the possibility of Google taking down google docs, in response to complaints from MS, or some other online office software provider?
No bad intentions here, I just don't get it. Care to enlighten me?

Re:Please help me out here

[MozeeToby]

I think they pulled the app mostly for PR reasons; not that the app generated tons of bad PR but that it was distracting people from what google wanted them talking about. Rather than argue about their right to have the app, they simply pulled it so people wouldn't be able to argue about it on the blogosphere.

Re:Please help me out here

[kingcool1432]

they simply pulled it so people wouldn't be able to argue about it on the blogosphere.

Front page on Slashdot. Wow, they sure dodged that bullet.

Re:

[mweather]

That's not funny, that's insightful.

Re:

[PitaBred]

Yup. But their statement made the front page too. Which is the important bit... WHY they took it down.

Re:

[DragonWriter]

Front page on Slashdot. Wow, they sure dodged that bullet.

You miss the point. Sure, people were already talking about the app and its similarity to Campfire, and they'll now (briefly) talk about Google taking it down. But with it down, there is nothing to keep that conversation alive more than a couple days, whereas as long as the app was up it would be a continued source of discussion distracting from the aspects of Google AppEngine that Google wants people to talk about, which aren't really the sample ap

Re:

[klenwell]

Rather than argue about their right to have the app, they simply pulled it so people wouldn't be able to argue about it on the blogosphere.

That to me would be the bigger story. Some (including myself) were quick to note this very issue in yesterday's thread announcing the new app engine service:

Build you new killer app, have it grow to the point where it takes advantage of the trumpeted scaling features of the service, then helplessly watch it disappear when Google PR feels it's "distracting people from wh

Re:

[raga]

... Rather than argue about their right to have the app, they simply pulled it so people wouldn't be able to argue about it on the blogosphere.

And that's why we are arguing about it here.

Re:Please help me out here

[Otter]

So, what is the possibility of Google taking down google docs, in response to complaints from MS, or some other online office software provider?

As best I understand, the Ruby on Rails cultists are one of the main developer groups they're counting on as App Engine customers, so they don't want to offend its leader. Annoying Microsoft doesn't cost them anyone they want to work with, and might help.

Re:Please help me out here

[syphax]

This is ./, we don't understand pragmatism. Unless we're coding.

Re:

[encoderer]

"Unless we're coding." ... And in such a case the attending physician should just let most of you die.

Re:

[Alsee]

we don't understand pragmatism. Unless we're coding.

Programmer One: What's this code here?

Programmer Two explains five pages of adaptive enhanced Quicksort code.

Programmer One: Wow, those are some pretty impressive techniques to speed up quicksort, and it cleverly solves the Quicksort worst-case running time problem to boot. But we're only sorting a list of five items, wouldn't it be more pragmatic to just use Bubblesort?

Programmer Two reaches under his desk and literally pulls out home built working replic

Re:

[bheekling]

Actually, in that case I would go for Comb Sort [wikipedia.org].
As simple as Bubble Sort, and pretty much as fast as Quick Sort.

Re:

[Shados]

Personaly, for 5 elements, I'd just use the sort extension method. You know, like myData.Sort();

Oh wait, you guys still coding in C++ or something like that?

(Thisisajokedontkillme)

Sour grapes.

[Anonymous Coward]

37Signals is the marketing force behind Ruby on Rails, and Google's AppEngine is heavily geared toward Django, which the RoR world seems to consider a big threat due to Django's allegedly superior robustness and speed. I wouldn't be surprised if they'd spent their time since the announcement of AppEngine looking for something to act martyred about and hopefully redirect some buzz toward their own offering.

In which case Google probably did the right thing disabling the trivial app before the buzz hijack could succeed.

Or maybe I've been in this industry too long and I'm just way bitter, I don't know.

Re:

[August Lilleaas]

..and Google's AppEngine is heavily geared toward Django, which the RoR world seems to consider a big threat due to Django's allegedly superior robustness and speed.

The RoR world, at least it's big names, doesn't feel threatened by Django, as they don't care about critics that compares them to other frameworks. The fuck you picture from a talk by DHH [gilesbowkett.com] - enuff said.

Re:Sour grapes.

[Achromatic1978]

Right. And the email from a founder of 37S complaining "is not official"... here's a hint: If something motivates you enough to put a slide in a presentation saying "Fuck You", someone's gotten under your skin.

Could you be the prototypical RoR apologist?

Re:

[OutOnARock]

Maybe the RoR gang, with their "The Rails Way" or the highway, are really worried about:

1. Google using Python instead of Ruby.
2. Google not drinking the DHH RoR koolaid.
3. DHH et. al. quaking in their tiny little boots that "Google+Guido+Python3000+the webframework that BLOWS AWAY Rails" will finally put the buggy Rails framework in a coffin.

Python blows Ruby away. Ruby survives commercially because it has Rails for simple web apps. Not scaling yet to play in the tall grass with the big dog

Re:

[shutdown -p now]

Python blows Ruby away.

As a language, hardly. But considering the speed of existing implementations, and availability of libraries for both, you are right.

And I guess Sun commmitting to make the JVM into a VM and guess what the next language will be....Ruby...WRONG.....Python

And here you're wrong. Jython has been effectively dead for ages, still stuck at Python 2.2 stage (and even that is a rather recent development - it has been at 2.1 for a loong time before that). Yes, Sun has finally hired Jython guys

Re:

[mounthood]

No bad intentions here, I just don't get it. Care to enlighten me?

I think it goes like this:

• * Doing great UI design is important.
• * We spend lots of time and effort on the UI. ex. http://www.37signals.com/svn/posts/887-design-decisions-calendar-picker-for-backpack-reminders [37signals.com]
• * They *exactly* copied our hard work.

Think in terms of Apple complaining that someone copied the iPod UI. It doesn't seem fair that someone can trivially copy something that takes so much time and effort. Good design should be rewarded and encouraged. Of course I don't know how that should work

Re:

[randyest]

Judging by the side-by-side shot in the article, I'd say your use of the word "exactly" is unwarranted. Moreover, I'd challenge you to show or describe a UI for such a simple chat tool that looks less like yours than the one google made.

Re:

[Breakfast Pants]

Your link was to some article about the minute details they go to in their design; if you looked at huddle chat you would see that no such thing was copied.

Re:

[SpinyNorman]

Call me cynical, but my take on it was a Google self-advertisement :-

"We built a fully functioning space shuttle over the weekend as a demo of our coolness, but NASA objected so we dismantled it. No biggie."

I don't see the problem.

[maciarc]

They both look like chat apps. How many different ways is there to show a chat window, a text entry box and a list of people in the room?

more importantly..

[thermian]

How is their product even saleable?

I mean, how much can they seriously expect to make from a cut down chat client when there are a gazzillion billion and two chat clients already out there?

Re:

[randyest]

I'd guess it isn't. If it is, I'd love their sucker^Wcustomer list.

Re:

[Xsydon]

How many different ways is there to show a chat window, a text entry box and a list of people in the room?

42.

Re:

[cparker15]

I think you meant 37.

Re:

[Alsee]

How many different ways is there to show a chat window, a text entry box and a list of people in the room?

Too many. Unfortunately some people insist on re-demonstrating that fact in near endless ways.

Just for starters, you could place the constantly updating (i.e. distracting) people list as a horizontal rectangle *between* the text entry line and text view window.

Or, for SUPER MEGA bonus points, you can leave the people list on the side and just put the text entry box *above* the chat window.
(For a fun Fun

Re:

[mgblst]

This is a bad joke. So the guy is saying that there are lots of ways to show your content on a website, and compares it to watch faces? Let me guess, he approves of watch manufacturers sueing each other over watch face similarities?? Personally, I only like watches with one type of watch face, an analog clock and the date, most of these designs happen to look pretty damn similar.

Campfire is hardly innovative

[tolan-b]

It's just a nice web interface to a chat room, hardly revolutionary. Anyone getting hot under the collar about someone copying it has a great future ahead of them in the patent troll business.

Sure if they copied it exactly feature for feature and took the interface then it's understandable but otherwise...

Re:

[tolan-b]

Right, well that's why I added the qualifier :)

The article is light and obviously the app isn't up for comparison any more. But as another poster said, there's only so many ways you can order a chat window, a text entry box, and a current users list..

Campfire is hardly feature rich.

Real-time chat applications are overrated

[Tibor the Hun]

When I need to reach my contacts on the blogosphere 2.0, to let them know, for example when I'm doing lunch, or taking a vac-a, I just que up my batch chat application, que up the chats in that, (including my questions and a list of possible answers) and presto.. 45 minutes later the batch is done, and all of my contacts are notified, and we had a meaningful (though somewhat predictable) conversation.

I don't know who really needs real-time chat, except maybe pilots, or UAV operators.

Re:Real-time chat applications are overrated

[Ctrl-Z]

I just call my secretary.

Re:

[stephanruby]

your mom?

Re:

[fuzzlost]

Just because your mom answers the phone before you do doesn't mean she is your secretary.

Re:

[Tibor the Hun]

Thank you!
I will try to remember that.
I'll blame it on my ESL nature.
(For years I used to pronounce "Kludge" as "fudge" with a K. No one knew what I was saying.)

Also, I see my original post is up to +3 insightful... Come on mods. Batch-chat?

How are either of these anything new?

[phpmysqldev]

Based on this article I think I will make a low feature program that allows people to look at remote "pages" and view them in a standardized format. Yes, yes similar things have been done before, but my product will be sub par and do nothing revolutionary.

And if anyone else tries to "copy" that Ill go after them with a vengeance.

Re:How are either of these anything new?

[atlastiamborn]

Are you saying you're going to develop a web-based web browser?

That would be like totally awesome, imagine being able to browse the web from any web-capable device!

Re:

[Phroggy]

He never said it would be web-based. Although, I think you can run this [www.iol.ie] in Internet Explorer...

Re:

[earthbound kid]

Well, for people using Internet Explorer, access to a real web browser via the web would be a big step up!

Real-time chat patent pending?

[Anonymous Coward]

So now businesses trying to claim inventions even if they didn't register patents?

Re:

[evanbd]

Actually, "Hey, we thought of that first. Don't steal our ideas, please." seems like a much better way of doing things than patents and lawsuits. It seems to me that Google is just being polite, here. 37Signals is being a bit asinine, but if it matters to them and not to Google, why shouldn't they honor the request?

Re:

[geminidomino]

Actually, "Hey, we thought of that first. Don't steal our ideas, please." seems like a much better way of doing things than patents and lawsuits.

No, it's only a precursor to lawsuits, if they do not comply. Jason said so himself [37signals.com].

"And 1% of the time it requires legal intervention..."

It's just that it's such incredible crap that, like this, no one thinks its worth the bother.

huh?

[apodyopsis]

I applaud them for their principled stand, but I ridicule them for this decision. It was surely taken in the interests of staving off a good 'ole web flaming then any sensible grounds. There are so many of these applications of this style and format around that I find it hard buy their argument.

And I, for one, would find this kind of demo application extremely interesting. It always interesting to see how these things are done.

Bottom line - I think there is nothing intrinsically special with this kind of application, any of us with a modest amount of programming experience could of knocked it up. It is always interested to see a standard basic application in a new system as a common ground to allow ease of adoption. For that reason there is a bunch of "hello worlds", "simple graphs" and so forth. On a web development system you would expect by the same argument to see "tables", "blogs", "portals" and the "simple chat" as their demos. This is like MS trying to stop the notepad demo that comes with some windows compilers, or LiveJournal trying to stop the blog demo that came with GWT. Totally Daft.

Go on, reinstate it!

Re:huh?

[ezzzD55J]

any of us with a modest amount of programming experience could of knocked it up

AAAAAAAAAARGH

Re:

[Anonymous Coward]

AAAAAAAAAARGH

What? "Could of" is actually the technically correct way to write it, as a matter have fact.

The REAL Reason

[garett_spencley]

Google had spent a couple weeks developing HuddleChat but then they read this [slashdot.org] Slashdot story on Monday and realized that they are all/mostly introverts and really don't like Chat and IM programs after all.

The 37Signals story is just a cover-up so they don't look silly.

Re:

[Alsee]

Jokes aside, it sounds like HuddleChat is exactly the sort of thing to SOLVE the issues raised by the prior story. I have never used HuddleChat and have a limited understanding of how it works, but it sound like exactly the sort of non-interrupting messaging system he would like.

-

They should have made the code available

[jocknerd]

It would have been nice to see the code for a "real" working app on App Engine.

Translation

[JamesRose]

We Stole their idea, and we did it so unsubtly that we can't even slightly pretend we didn't. It was this or get into a storm of lawsuits and bad PR.

Re:

[cHiphead]

Wait so are you pretending to speak from the mouth of Google for stealing 37sigs 'idea' or from the mouth of 37sig for stealing the most generic chat interface 'idea' reworked into another language from everyone else?

I'd really like to know, b/c a developer at Google probably looked at various web chat, IM chat, and IRC interfaces going back to 1997 for inspiration for huddlechat. The idea that anyone can steal that shoddy, generic interface from 37sigs two bit chat app is fucking ridiculous. Or maybe its

Meh

[Vexorian]

This almost looks like google saying "won't feed the trolls"

If it was MS instead of Google...

[qaam]

I'm surprised most slashdotters seem to think that Google was in the right here. Let's leave out Google's name and see how the story sounds:

A company with over 10,000 employees duplicates a 10 person company's product feature for feature, even down to the animation effects, and gives it away for free.

Substitute MS for Google in this story and slashdotters would be flaming mad. It's not that Google just created a similar chat app to Campfire, it's that they created a carbon clone of Campfire, which is de

Re:If it was MS instead of Google...

[Chyeld]

Substitute Microsoft for Google and yes, people would be far more up in arms about it.

"Why?" you ask? Do you really need that spelt out for you?

Microsoft has based its entire business history on unethical actions and slippery business tactics. They did not get ahead in the world by being the best at their products; they got ahead by screwing over anyone they could get away with screwing.

Google on the other hand has based its rep and business practices on delivering the 'best' product. They haven't gotten ahead by double dealing, underhanded tactics, or screwing over people.

Yes, Google HAS done things that people don't agree with. But none of the things that people point out are deliberate attempts to screw with people.

Microsoft got in bed with companies telling them that they were specifically planning on doing X, while secretly planning on doing Y. They did this, as has been documented, to give Microsoft an edge in its own competing product.

Google has had van drivers accidentally drive up someone's driveway while taking low resolution pictures. One had malice in their intent; one simply made a mistake.

Microsoft stole, actually STOLE, someone's code and distributed it as part of Win9x. They didn't even bother to remove the copyright strings in the binary and only stopped distributing it when they were found guilty by a jury (see Stac Electronics).

Google had two engineers in their off time who copied an extremely generic idea and placed it in their gallery of "look what you can do with this new toy we have!" and took it down when it became apparent that there would be hard feelings over it.

There is a reason why Microsoft gets the shit treatment and Google doesn't. And it's not because everyone here has "Google fever". It's because so far Google acts responsibly and ethically while so far Microsoft acts predatory and unethically.

Re:

[qaam]

Good points. I applaud Google for acting responsibly here by taking down HuddleChat quickly. In general Google is a "good" company; they certainly don't deserve the "shit" treatment in the way that MS does.

Google had two engineers in their off time who copied an extremely generic idea and placed it in their gallery of "look what you can do with this new toy we have!" and took it down when it became apparent that there would be hard feelings over it.

I agree that Campfire is a totally generic idea; however, its execution is not. Of course it only took Google employees two weeks to copy Campfire... after all, the Google guys didn't have to do any thought, they just had to bang out code to do mimic Campfire's ideas. How long would it take for two Goo

Re:

[Chyeld]

Compare the side by sides presented in the article and try to claim again that the two engineers copied anything.

There is a reason why you can't copyright an UI or an idea but can copyright source code.

Google's people did nothing wrong.

37Signals hasn't said a thing.

[shinma]

Everyone keeps jumping on 37Signals for being whiners, but they haven't said anything about this in their blog. This is a case of the "blogosphere" getting up in arms about something on behalf of the "victim" without the victim ever lifting a finger.

Re:

[Chyeld]

Really? [searchenginewatch.com]

"We're flattered Google thinks Campfire is a great product," said Jason Fried, 37signals CEO and co-founder. "We're just disappointed that they stooped so low to basically copy it feature for feature, layout for layout. We thought that would be beneath Google, but maybe its time to reevaluate what they stand for."

Re:

[shinma]

I hadn't seen that article, but that would also be a comment solicited by a journalist. 37Signals hasn't posted anything about it on their site, or the Signal Vs. Noise blog.

here is what started it all

[hashmap]

"We're flattered Google thinks Campfire is a great product," said Jason Fried, 37signals CEO and co-founder. "We're just disappointed that they stooped so low to basically copy it feature for feature, layout for layout. We thought that would be beneath Google, but maybe its time to reevaluate what they stand for." From http://blog.searchenginewatch.com/blog/080408-123318 [searchenginewatch.com]

Re:

[mosch]

Christ.

This makes me regret that I give 37signals money every month for a bunch of basecamp accounts. But it makes me *extremely glad* that Highrise has some idiotic limitations on the total number of contacts that kept me from integrating it as the CRM solution for one of my new ventures.

If you want to have more than 50k contacts on Highrise, you're out of luck. You can't even give them more money every month to solve the problem (I e-mailed and asked. They confirmed this, then ignored my follow-up aski

Phew, we had that in 2001

[Enleth]

Campfire was released on 16 February 2006 [37signals.com], while we had this on a website I'm an admin at since mid-2001. PHP and some JS. It works to this day and looks the same, although it was rewritten several times throughout the years to use AJAX instead of a reloaded frame.

No, I'm not giving you an URL - I wish I could, to prove my words, but the server load is high enough without the /. crowd trying the thing out...

Re:

[Enleth]

Oh, I forgot to mention that it even IS called "campfire" - the whole website is themed as a medieval village, with the campfire outside the gates as a place to chat even for unregistered newcomers.

Re:

[Breakfast Pants]

*please* link. The slashdot effect from a comment this far down (and this late) won't be a big deal.

Re:

[Enleth]

http://osada.heroes.net.pl/ognisko/ [heroes.net.pl] - here you go.

rock and a hard place

[nguy]

Google doesn't want to get a reputation for ripping people off, so baseless as these accusations are, they had to pull it.

Still, anybody who complained to Google about similarities to 37Signals should get a life. 37Signals didn't invent simplicity and they didn't invent any of the application categories they are making money with. Nor is there anything illegal, unethical, or even bad about re-implementing someone else's application.

(I also find the 37Signals applications overpriced and underperforming, b

Lawsuits on Rails?

[MadMidnightBomber]

I don't remember the "moan about other people's demo apps" bit from "Getting Real".

Quick semi-related shameful plug

[sydneyfong]

http://www.iwannachat.net/ [iwannachat.net]. It's basically a rather modern AJAX persistent web chat. I don't know how it compares with Huddlechat since I didn't follow the news yesterday and now its down :-/

Please pardon the testing crap in the demo room :)

Re:

[geminidomino]

Pfft. I just did it in 30 minutes, perl, and javascript.

Re:

[Fastolfe]

The app that was taken down was a demo application written by Google engineers. It was intended to simply be a sample application. Google's reasons for taking it down were right there in the article's summary. This wasn't an involuntary "take-down" of some Joe's app, it was effectively a Google application. I really don't think it's appropriate to infer anything from this about Google's willingness to take down future applications based on 3rd-party complaints.

Where is it? Umm. Here....

[Chyeld]

From your friendly "site:google.com evil" Google query....

Here? [google.com]

Google Code of Conduct Preface

"Don't be evil." Googlers generally apply those words to how we serve our users. But "Don't be evil" is much more than that. Yes, it's about providing our users unbiased access to information, focusing on their needs and giving them the best products and services that we can. But it's also about doing the right thing more generally - following the law, acting honorably and treating each other with respect.