![]()
When I read yesterday that Retweet.com was about to launch a competitor to Nick Halstead’s Tweetmeme, I dropped Nick an email to ask if he had anything to say about it. He didn’t reply to my email, and now I think I know why. Look what Nick just posted on the Tweetmeme blog:
What caught my attention was that some industrious individual (@travisketchum) had left a comment on the TechCrunch article that he had been doing some digging around on the website and had found a link to their development environment. What we found ourselves was that our retweet button Javascript and the Wordpress plugin code seemed to have been directly copied from ours.
We are happy for others to learn from our endeavors and flattered by the copying but some of our more complex JavaScript was obfuscated to deter others from attempting to re-use our code. We take a dim view of trying to pass off our code especially when it is attempting to create a competitor.
We our seeking further legal advice and will be pursuing every avenue to protect the hard work of our team.
Can this be true? I’ve emailed Nick for more information, and I’ll be trying to get hold of Retweet.com’s COO, Tyson Quick, as well.
Update: I’ve been alerted to the following similarities in code between the Retweet.com and Tweetmeme.
(1) Take a look at the code for Retweet.com’s Retweet button (retrieved from http://174.129.199.128/meme/static/retweets.js at 17:43 today):
(function()
{
var _url=window.location.href;
var _url=_url.replace(/((?:?|&)?fbc_receiver=.+)?(?:#.*)?$/,"");
var url=((typeof retweet_url=="string")?retweet_url:((typeof retweet_URL=="string")?retweet_URL:_url)).replace(/+/g,"%2b");
var source=(typeof retweet_source=="string")?escape(retweet_source):((typeof retweet_SOURCE=="string")?escape(retweet_SOURCE):false);
var style=(typeof retweet_style=="string")?escape(retweet_style):((typeof retweet_STYLE=="string")?escape(retweet_STYLE):"normal");
var src="http://174.129.199.128/meme/widget/tweets/";
switch(style){
case"compact":
var h=20;var w=90;break;
case"rednose":var h=71;var w=60;break;default:var h=71;var w=60;break
}
src+=url;
if(source!=false)
{
src+="&source="+source
}
document.write('<iframe src="'+src+'" height="'+h+'" width="'+w+'" frameborder="0" scrolling="no"></iframe>');
retweet_url=null;
retweet_URL=null;
retweet_source=null;
retweet_SOURCE=null;
retweet_style=null;
retweet_STYLE=null})();
This is an almost exact copy of Tweetmeme’s retweet button code. The word “tweetmeme” has been replaced with “retweet”. Note also the “rednose” reference: it refers to a now-defunct feature of Tweetmeme’s button.
(2) Here’s some code from Retweet.com’s Wordpress plugin (retrieved from http://174.129.199.128/meme/static/retweets.zip today at 17:49):
function tm_options() { add_options_page(‘Retweets Settings’, ‘Retweets’, 8, __FILE__, ‘tm_options_page’);
}
function tm_update($content) {
See those "tm_" functions? "tm" stands for Tweetmeme.
Want more? Try looking at the two websites side by side.
Update 2 (@17:58): It appears Retweet.com has begun to delete offending code from its servers. Check out this 404 error for a page that previously contained widget code.

I’m glad that they are taking down that code. It’s not like the code was “inspired” or anything it was a simply copy&paste with a find and replace to change “tweetmeme” to “retweet”.
I hope Nick stands up for Tweetmeme and the awesome service they provide.
Ollie
Surely these things happen all the time?, in some ways that has made the web what it is today by being able to view source, adapt etc.
Code is copied and ideas are developed and not attributed (where did the original idea for tweetmeme come from? http://cleverclogs.org/2009/07/the-original-idea-behind-tweetmeme.html) all the time.
If there are parts of tweetmeme are protected by patent(s) then that is a different issue and worth seeking legal advice.
In the meantime this is just a good PR opportunity to build the tweetmeme brand (especially as one “wronged”) against any new “upstarts”…
Oh yeah, the cooked up the WHOLE thing. And hey, it’s OK, theft has made the world what it is today!
I hope both companies get some PR value out of this exposure, because there certainly isn’t any news value.
All that JS snippet does is write out an iframe, hardly worth obfuscating or stealing.
Anyone interesting in implementing a ready-made retweet button without infringing copyright can look to @jeresig’s open source solution which he posted here: http://ejohn.org/blog/retweet/
Update from the trenches
– Mesiab Labs responds to Tweetmeme.com and Techcrunch post:
http://rt.nu/-m95
“one of our developers had based a prototype button and widget on tweetmeme.com’s publicly viewable scripts “. So you admit you copied their code?
Good luck trademarking retweet (per your blog post). You may own the domain, but never the word.
the best retweet.com can do now is just own up, apologize for being daft and try to release a great product.
this is rapidly becoming a trainwreck, everyone knows they fucked up, they’ve been caught out – just fess up, offer a public apology to tweetmeme and get on with the product.
Um, Im pretty sure that is exaclty what Kevin’s post was above ^ http://rt.nu/-m95
I have no idea why I wrote essentially the same thing twice in two seperate paragraphs.
really wish techcrunch would overhaul their comment system (hint: disqus)
And TechCrunch steals Tweetmeme or Retweet.com’s code by posting it here?
Anyone can paste code. Only some people paste it into their systems to actually use it (or abuse it).
This is quite an interesting case – in essence its no different in law to copying and minor alteration of someone’s else’s music, video or other prior art to create a new piece.
Also, arguably it is just taking a small sample of someone else’s total code base to reproduce, much like taking bits from reports etc to make one’s own, with minor alterations.
And besides, as we all apparently support piracy in music and video, why not for code?
(Not supporting Retweet here, just pointing out the plusses and minusses of the impact of perfect digital reproduction)
I think when it comes to the social world you need to be a lot more careful than perhaps others have been in the last 15 years of copying and pasting web code.
This new visibility will sure bring some questions about openness… imagine what will happen in the coming years when it is not “open” code that is copied but open data.
Decided to write a blog post about it.
“the confusion of copying code on the web”
http://bit.ly/12O3LG
Is this so different from stealing photos? Like you did last week Milo?
Users would not care who is the original…
How did I miss this news and not hear about it?
This is a hilarious story – some company copying another’s code and passing it off as theirs.
Thanks guys for this post, I have added retweet.com to my black list. I won’t be using their service as it turns out that they are stealing code.
diaclasis http://wiki.answers.com/Q/User:Wellbutrin wellbutrin Courvoisier wellbutrin
angor http://wiki.answers.com/Q/User:Wellbutrin – generic wellbutrin