Slashdot Mirror
Google Open Sources Etherpad, Piratepad Launches
Thomas Nybergh writes "The Etherpad code was released by Google under the Apache license a few hours ago. Google's initial plan, after acquiring the service, was to use Etherpad's tech with its new Wave collaboration platform and to shut down the original service entirely. Soon after the Etherpad code was released, the Swedish Pirate Party launched their instance of the service at piratepad.net. An announcement, which also mentions a new Tor node, is published on the party website (Google translation). The original Etherpad service had in a short time become a killer application for collaborative work within at least the Swedish, and according to my personal experience, in the Finnish Pirate Party as well. The Etherpad open source project is available at Google Code."
Small wonder they wanted to acquire AppJet to send its programmers to the Google Wave slave mines to make Wave work more like EtherPad. I'm tickled pink they went through with their pledge to open-source it, and did it so quickly.
Isn't it amazing? This is the code that was AppJet's entire revenue stream...and after Google bought them for ten million dollars, they're giving all that work away to the community, free.
You can argue all you want about whether Google is really evil or not, but either way it certainly has its non-evil moments.
Editor Emeritus and Senior Writer, TeleRead.org
If Canonical is serious about promoting their cloud platform this should be relatively easy for them to host and roll client access into their next desktop release. They could also host the server component in their repo to make it cake to install on internal servers as well. Wave without the "Google" would be awesome.
I was just thinking about how this is Google's answer to "acquire and assimilate" business practices. When Oracle or Microsoft do it it's murder, but when Google do it they Open Source the product then abandon the original.
Is this better?
ilovegeorgebush
I would see Gmail's live chat feature being quite close in concept.
I don't. Being able to go back and edit what someone else has written previously is a fundamentally different concept IMO.
What about using EtherPad for Wikis? Seems the perfect match: The learning curve is lower than for current Wiki markup (and ease of editing was one point of Wikis, after all), the history function is already included, and since it's now Open Source, the missing functionality (especially Wiki links) could easily be added.
The Tao of math: The numbers you can count are not the real numbers.
I just have one tiny question after reading it: What the fuck is Etherpad?
sic transit gloria mundi
Seems far superior to this Etherpad in every sense of the word.
Technically speaking, Wave is superior (I've used both). However, what makes Etherpad so popular is that it is easier to use. As of this time, Wave is still in Alpha mode, and while I get it, many tech friends who have tried to use it really don't understand the applicability of the software. They don't see it as a much better way to collaborate. They still want to stick to traditional e-mail for organization (which I hate, particularly when conversation threading and search is not available in e-mail).
So, Wave = Technically Stronger; Etherpad = Usability is Stronger. Add the good parts of the two together, and you get a much better project overall.
Could this be good legislation to implement and curb or eliminate the Embrace=>Extend=>Extinguish business practices?
When you buy out a company that makes software, you must open source the current code. This would make companies more valuable standalone and increase competition, and also allow those that should die off to die off. If another company does wish to invest, competition is still there since the code is now open source.
Like a city whose walls are broken down is a man who lacks self-control.
I this the parent's point was that a company acquiring another would have to either keep developping or support the target company's assets, or Open Source them instead of burying them in a shallow grave, never to be heard of again. Which would be a Good Thing (tm).
It doesn't have to mean "lose all the software to the public".
More like "create a public open branch of whatever was created to this day".
Also, "open source" doesn't have to mean "free as a beer". You can grab the code, tamper with it, compile it, but to use it for anything meaningful you have to purchase a license, and to redistribute your modified code you must purchase a redistribution license, sending a part of your profit upstream.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
There is also uxoo.com. Free software at its best - other websites will certainly follow.
Hopefully all these competing services will do to good old plain text edition something just as great as youtube did to videos.
Start the competition!