Two Seamless members say hackathon misattribution was unintentional

HackMIT organizers refer to incident as ‘plagiarism’ but maintain team members were not found ‘guilty’

PUBLISHED ONLINE: November 12, 2014

Since the publication of an article in The Tech about allegations of plagiarism against HackMIT contestants on the Seamless team, HackMIT organizers and two members of Seamless have stated that the videos they presented as output of their own code in the hackathon’s final presentation were actually published by Microsoft Research. Both these two contestants and the organizers said that the misattribution was unintentional, while a third member of the Seamless team has sought to publicly distance himself from the project.

HackMIT organizers have since stated that they do not stand by a HackMIT blog post’s initial characterization of the incident as a “disqualification” of Seamless, who they said stepped down voluntarily.

Seamless, which had originally won second place at the hackathon, did not receive the $3,000 prize last month after HackMIT investigated accusations that the videos the members showed in their final presentation were not their own results. Another top eight finalist, AgileAssault, was also “disqualified” for submitting a similar hack the week before to HackUMBC, according to the blog post.

Seamless was composed of three MIT sophomores: Kevin Kwok ’17, Nikhil Buduma ’17, and Guillermo Webster ’17.

The team was seen referring to the looping videos in question as their own results during their final pitch. Webster introduced some of the videos, saying, “It’s a very difficult algorithm, and it was a big pain to implement… but here are some products of that.” Buduma refers to the process by which the videos were produced as “our algorithm” several times during the presentation.

In a written statement to The Tech, Webster said that in their final presentation, “failing to attribute the videos to Microsoft qualifies as plagiarism.” However, he said that the lack of proper attribution was unintentional.

Webster said that the team was trying to present their implementation of a Javascript-based viewing utility for looping videos, which could take videos processed with Microsoft Research’s algorithm and selectively render certain parts of them. He said an iOS gallery of Microsoft Research’s videos was also part of the presentation.

Though Webster said they also tried to make an end-to-end implementation of the Microsoft Research algorithm capable of making short videos into seamless loops, both he and Kwok indicated to The Tech that they did not successfully generate such loops using their own code during the hackathon.

“Backstage, I voiced concern about correctly attributing everything, and we decided as a team that we would do so, but in this regard the presentation went very poorly,” Webster wrote.

“When we presented, we were just going to be like, ‘And this is what it might look like if your photos were moving,’ but I guess it morphed from an explanation into graph cuts to an explanation of the algorithm,” Webster said. “And then on stage, [it turned into] ‘this was our algorithm…’”

Webster said, “If we had really wanted to be cheaters, we could have just produced our own videos with the implementation that is freely downloadable from the website. Again, we weren’t trying to say that we made those.”

“I guess it’s probably a bad assumption for us to have made — an assumption that we made is that ‘isn’t it obvious that we didn’t make that?’” Webster added, referring to the looping videos.

There are two rounds of judging at HackMIT before the final round. Webster said that the pitches he made in the initial rounds of judging were very different from the final presentation and said he had made clear at that time that the videos were not produced by Seamless.

TechX associate director Ankush M. Gupta ’16 said he was among the judges who judged Seamless in one of the two rounds before final judging. “Their presentation from the initial round of judging and the final round of judging was actually quite different. In the initial round of judging, Kevin and Guillermo were the two people presenting it. They presented… here is a sample input, here is what the output would be. They cited the Microsoft paper,” and then demonstrated the web-based component of the project, he said.

During the final presentation, Buduma spoke the most, while Webster and Kwok contributed only minor explanations about their project.

“During our actual presentation, I was mostly oblivious,” Kwok wrote in a statement to The Tech. “We had mentioned the [Microsoft Research] paper, but failed to clearly articulate that their example data was simply used to showcase the video loop viewers.”

According to Kwok, during the final presentation, “There were phrases which seemed to be liable to misinterpretation, but I felt they were all within the bounds of true. It wasn’t until afterward, talking to Guillermo, that I began to realize the misleadingness of the sum of it all, and I began to feel uncomfortable with what we had done.”

Webster said that he realized that the audience overestimated the extent of Seamless’ contribution immediately after the presentation, when a judge implied that she thought the team had implemented a system to add motion to still images. “The first question we were asked by the judges made it clear that we were not being judged for what we accomplished,” he said. “[The first judge] clearly thought that not only were the videos ours, but that the algorithm was ours, and that it could work magic.”

However, in response to the first judge’s question, Buduma said, “Let’s say you were at Disneyland taking a picture with your family and people are moving past you or behind you. This algorithm would actually operate on that and remove the person in the first place. So here’s an example… if you look at the result of our algorithm, [the dancing person] gets removed,” while referring to a looping video displayed on-screen.

According to Gupta, the members of Seamless “did not explicitly come forward to HackMIT as an organization” after their presentation. “Personally, I felt bad enough that I had planned on donating the money to charity when I got it,” Webster said.

Kwok wrote, “To be honest, it felt like good closure when we agreed to step down from second place. Even though it was all an honest misunderstanding, the fact that our descriptions were ambiguous enough to leave that up to interpretation was unacceptable, and for that I am personally sorry.”

None of the members of Seamless commented for the initial article in The Tech about the matter. Webster said the team members initially decided to ignore interview requests in the hopes that “maybe if we ignore it, it’ll go away.” Many comments were left on the original Tech article, some proclaiming the presentation to be completely faultless while others accusing the members of intentional deception.

Seamless Member Roles

After the first Tech article was published, Buduma sent in a statement distancing himself from his teammates, saying that he had no involvement in the team’s attempt to implement Microsoft Research’s algorithm. He also posted similar statements on a public Facebook page and in a named comment on the original Tech article, adding that he felt the original article “framed [him] as complicit” and that he experienced “harassment” and “blackmail” when asked for comment by a reporter for The Tech.

In his statement, he wrote, “I had zero involvement in building the ‘magical’ back-end of project (which could be easily confirmed by the HackMIT team by taking a look at the Git repository and revision history) and… I was not involved in any misconduct that might have occurred.”

The team’s Git repository indicates that Buduma did commit back-end code as part of the team’s attempt to implement Microsoft’s algorithm, which seemed at odds with his statement that he only worked on a front-end interface for the videos.

“As can be verified in the Git logs, Nikhil did commit at least once to the MATLAB code, of which the C++ code is a direct port,” said Webster. “He wrote the function spatula, which is the spatial energy function,” he said, referring to an aspect of the video processing algorithm the team attempted to implement.

Kwok said, “For the first few hours of the hackathon, Guillermo and Nikhil worked on porting the energy functions specified in the paper into MATLAB, as we had found bindings for a graph cut optimization library.”

Buduma also stated, “[Webster and Kwok] just needed me to do a bit of front-end work and help them pitch.” In an interview with The Tech, however, Webster expressed some concerns with Buduma’s account.

“I personally didn’t ask for help with pitching the project at the beginning of HackMIT, and it was my impression that we had recruited Nikhil to help with the project in general, especially given that we had started working on the algorithm together,” said Webster. “I’m not sure what interactions Kevin and Nikhil had without my knowledge.” Kwok had pitched a HackMIT project himself the previous year with Webster, now called Project Naptha, and won second.

Buduma wrote, “If I had known that there was something fishy about their work, I would have never agreed to be a part of it.”

Webster said all of the team members knew that the videos were taken from Microsoft’s page. In the video of their final presentation, Buduma refers to the Microsoft videos as the results of “our algorithm” multiple times.

The HackMIT organizers said they did not know what information Buduma had or did not have about the team’s project during the competition and therefore couldn’t confirm or deny his claim that he knew less about the internal workings of the project than his teammates.

HackMIT responds

The Tech had previously reported that HackMIT organizers had conducted a hearing with members of Seamless. Siegel had previously stated that they had decided to step down without being “incriminated or found guilty of anything.”

When asked why Seamless didn’t demonstrate the functionality of their implementation in the hearing, Gupta said, “It is a multiple-hour-long process to generate the videos, which is part of the reason they explained for why they had to use Microsoft’s videos instead of their own.”

HackMIT co-director Katie Siegel ’16 said that during the hearing with herself and Gupta, Seamless team members demonstrated the functionality of parts of their code. “They did implement, and we saw that they implemented… all the parts of the algorithm that were necessary to generate the output,” she said.

But Siegel also said that she had not seen an end-to-end run of Seamless’s code, i.e. a non-looping video processed and turned into a looping video.

Webster said that he had never successfully run the code end-to-end until he modified the code from the hackathon recently. He said that this past weekend, “I changed some stuff, fixed some errors,” adding that with the modifications “it worked and it took 8 hours.”

Kwok told The Tech, “Toward the end of the hackathon, we managed to get C++ code to a state where a subset of the optimization could be run. We noticed that it was extremely slow, taking about a minute to run on a single candidate period, a task that needs to be run several hundred times before a single video loop can be generated.” He added, “On top of that, we weren’t even sure the data was formatted correctly.”

According to Gupta, the investigation concluded before the full functionality of that implementation could be determined. “Essentially our investigation concluded once we reached our mutual conclusion that the prize would not be awarded to them,” he said.

“We did not find them guilty through… verifying or not verifying that the code [worked],” Siegel said.

It was unclear from the organizers’ statements in the interview how the outcome of the hearing would have changed if Seamless had produced a fully functional implementation during the meeting. After their interview, the organizers emailed The Tech asserting that the state of the code’s functionality did not affect their decision to make Seamless ineligible for prizes.

Fellow HackMIT organizer Richard Z. Ni ’15, Gupta, and Siegel sought to draw a distinction between declaring the team “guilty” of “plagiarism” and allowing them to “step down” as a result of a “misrepresentation.” They further distanced themselves from a HackMIT blog post that said that they “disqualified” the hacks of two teams at the competition.

Ni said that Seamless not receiving the second place prize was part of a “mutual decision.” Siegel said that based on the hearing, “We decided that there was not enough evidence to find them guilty, and we talked about it a little bit more and they decided that instead of going on and digging further into the code… they were just going to step down because of the misrepresentation we discussed during the meeting that we had.”

While Ni said, “We technically didn’t disqualify them because they agreed to step down,” there is no such distinction in the HackMIT rules, nor any set procedure for dealing with alleged rule violations.

Of the blog post, Siegel said, “I don’t think at the time we thought too closely about the exact word ‘disqualification,’” adding that it was written by a member of the development operations team rather than those involved in the hearing.

Siegel suggested that “disqualification” was referenced in the blog post because Seamless was “lumped in” with AgileAssault, another project that was made ineligible for prizes by the organizers and which she did say was “disqualified” by HackMIT. But from Siegel’s description of the process used to remove AgileAssault from competition, the difference between disqualification and stepping down remained unclear.

“We did not investigate thoroughly,” she said, in reference to AgileAssault. She said she approached the project’s creator with the information that organizers of another hackathon said that he had recently presented a very similar project at a previous hackathon, while HackMIT only allows projects created entirely during the competition. Though the creator agreed, he defended himself by saying that it was a re-implementation of a previous concept with new code. According to Siegel, she said, “‘I still think that the two projects were too similar and that we can’t give you the prize,’ and he said, ‘Ok, I accept that.’”

The organizers also asserted that they did not find the Seamless team members “guilty” of any specific charge, citing a lack of evidence of malicious intent, although the HackMIT rules also do not reflect such a distinction.

Ni said that HackMIT had never described the incident as plagiarism, but after being read the MIT Academic Integrity Handbook definition of plagiarism, he said “I would think that it is plagiarism [by MIT’s] definition… If we didn’t think there was any plagiarism we wouldn’t even have talked to them [about stepping down].”

Siegel said, “The reason why we decided that what they showed us was not conclusive enough to find them guilty was because they didn’t [finish] the end-to-end [implementation]… to the point that they were able to present the change in the Microsoft videos.”

According to Ni, “‘Guilt’ implies a lot. It implies some sort of moral failure. And for us, we didn’t want to assign any sort of moral failure to their actions.” Gupta also said, “While we agree that they plagiarized, we have no evidence to attribute that to some sort of malicious intent or moral failure on their part. And that is why we… didn’t make a statement that would imply as such.”

Siegel said that only she and Gupta were involved in the investigation and that neither was friends with the members of Seamless. “In fact, all of the HackMIT team members who did know them took a big step away… when it came to reviewing this,” she said.

She also said that investigation was conducted internally because the HackMIT leadership was better positioned to make the decision than those outside the organization, who she said might be less familiar with the structure of the hackathon.

They said they had not made any decisions about whether members of Seamless would be allowed to enter HackMIT in future years.

Anonymous over 9 years ago

So it sounds like Nikhil, who has been very vocal about saying it was all the fault of the other two, was actually the one who did the most damage. What a surprise!

Nice reporting. I think The Tech handled the situation well.

Anonymous over 9 years ago

Sounds like a super cool project!

To the seamless members, from an outsider:

Don't let the tabloid haters affect you. They will go away eventually, once they have found another fake controversy to cover. Unfortunately, reporting like this is par for the course for student newspaper tabloids.

People need to understand that presentations are hard. Some people have bugs in their code and other people have bugs in their presentations.

People involved in the hackathon community know that mistakes like this happen literally all the time. That is ok though because hackathons are a place to learn and make mistakes, and these mistakes are easy to fix. You guys were just an unfortunate target of overzealous reporters looking for a story.

And please please don't let this incident discourage you from going to future hackathons. No one in the hackathon community thinks you guys were being malicious, and we all understand that people misspeak in their presentations sometimes. And hopefully the hackathon community will get it shit together on policies to deal with outside harassers. Even if it means having to bar press from an event (I know I am going to do this at the student hackathons that I run). It is important that students feel safe at an event.

And unrelated to this newspaper incident, I hope that you release the tool that you worked on. Not to "prove anyone wrong" or anything, but because it sounded like a really awesome project that people would want to see. And you should be proud of the work that you did!

Anonymous over 9 years ago


Was there anything that was not malicious here?

They sold their video player (a couple lines of Javascript) as a magical algorithm ("our algorithm") that can automagically loop videos using sophisticated techniques to produce beautiful, seamless results.

This is like taking one of Albert Einstein's research papers, handing it in as a term paper, and claiming that it was an accidental misrepresentation because they meant to communicate that they printed the paper, not authored it.

This isn't a mistake, and it's no little misunderstanding. The whole presentation is a pack of lies. They very clearly and purposefully lied to the audience of a thousand people at the hackathon. Anyone can go and look at the original video, and you will see that this isn't a little miscommunication or little embellishment -- they are not pitching a video player, they are pitching a magical algorithm as their own:

It's quite interesting to watch this video in the context of this article and the previous one, .

The Seamless team did put on a great show! It was quite enjoyable to see such a nice presentation of Microsoft's work. It seemed even more zealous than the original Microsoft presentation itself. If this was a presentation competition, I'm sure they would have done really well, because they did a superb job with the pitch. The whole thing was a lie, though, so that's a bit of an issue when pitching something as your own invention.

I'm disappointed in all three of these MIT students. I thought they were better than this.

And I'm especially disappointed in Nikhil, putting together this huge sob story, lying to everyone and throwing his teammates under the bus, when he was complicit in the whole thing: [mirror:]

Anonymous over 9 years ago

As someone who has seen the git repo previously (as someone interested in the project after hackmit) and looking at the git log now again, this article disgusts me. First of all, any person who can read a git log can see that only a tiny fragment of code was pushed at the very beginning of the hackathon does not constitute working on the backend. There are tens of other files, adding up to at least a thousand or couple thousand lines of code there. Moreover, you don't see another commit until late in the night/early morning of October 5th from the accused, now all in a completely separate folder called iOS.

Can't even get the few facts straight in a relatively straightforward case. Probably twisted the words from Guillermo as well. Poor guy.

The Tech should not be able to play God with no checks and balances. I agree with previous comments on the situation that the Tech shouldn't be invited to MIT events any longer.

Anonymous over 9 years ago

Someone really needs to clarify to me what banning the Tech from such events will do. All the information that the Tech gathered in this article and the previous could have been gathered by anyone and did not require them to actually be present for any part of HackMIT.

The presentation was (and still is) on Youtube, the blog post, git repository, and Microsoft information are all online, and the interviews were conducted afterwards over the phone.

Anonymous over 9 years ago

4: perhaps you should actually read the article. If you had, you'd know that the part regarding the git log is merely summarizing the statements of one of the team members, specifically Webster, and is not a separate claim that the Tech is making. So what you really mean is "Webster's statements disgust you", not "this article disgusts you".

Your second statement is entirely unfounded. Probably you just made random stuff up because you have nothing better to do.

2: "No one in the hackathon community thinks you guys were being malicious" yeah that's obviously false. Try again.

Anonymous over 9 years ago

Did they misrepresent? Yes, they were being judged by hackathon standards, which is to produce glamorous results. They did not produce the glamorous results (even if given the time they could) but led others to believe they did.

The problem however is with the hackathon format itself. Experienced people will tell you that complex algorithms take time to develop, implement and sometimes run, which was exactly the problem here. Does anyone believe most serious ideas can be translated into something truly mesmerizing in the space of two days, even by a team of very smart people? There are those who delude themselves so, like VC's seeing a startup pitches full of lies all the time. It's pretty clear that Team Seamless has learned well from the very culture that spawned hackathons. I don't blame them.

Anonymous over 9 years ago


The article is reporting the facts from what various parties said, not voicing an opinion like "tabloid haters". Honestly, it seems like the only ones being harassed here are the authors, by people like you. Similarly, the only controversy is the one you manufactured when you passive aggressively suggested that the authors published the article with malicious intentions, when in reality the article objectively expresses a diverse set of viewpoints.

Also, it's confusing why you encourage Seamless to release their work when it's already available. The article clearly indicates the location of the semi-public git repository at

Anonymous over 9 years ago

Newspapers think that if you just publish a bunch of quotes, and "objectively expresses a diverse set of viewpoints" it absolves them of all responsibility.

The malicious intent is obvious. "Cheaters need to be punished" right? That is a quote from Nikhil's conversation with the reporter.

That fact of the matter is that accusations like this should not be on the front page of a newspaper. There was never any controversy, it was just some crusade by some overzealous reporters.

There is no other way to explain the reporter's behavior in the phone conversation with Nikhil.

And the github isn't available. The hackathon community is larger than just MIT.

Scully over 9 years ago

#5 When writing a news article it is important to get quotes from people. It is also important to get pictures of the event. Also, they often need to get special access to performers, for interviews, ect

Banning The Tech from an event will make their job significantly harder. I run a couple major events on campus and this is what I plan on doing.

Just never ever talk to them, ignore their emails, and don't given them access and then they won't be able to write about your event. And even if they do, their article will be of much lower quality and information. And then you win and they lose!

Anonymous over 9 years ago

I guess I shouldn't be surprised that people are taking more offense at The Tech's reporting than at the original problem they reported. I'm not comfortable with the details about the interview that Nikhil reported -- frankly, if it's true, it's distasteful. But seeing how people are so vindictive to The Tech here highlights how much these people hate an expose of lies. It seems like it's an open secret that this happens at hackathons. But to report it is, apparently, in poor form.

It's like amateur hour here with people talking about banning a newspaper from their events. Let's see you hackers hack journalism (lol) and start a better newspaper at MIT. God knows we could use one.

Anonymous over 9 years ago

I don't buy any of this "misunderstanding" crap. It's one thing if you have a whole ton of material to show and forget to mention that one small part of it isn't yours, but this is blatant misrepresentation of an entire body of work. They just straight-up used Microsoft's work and called it their own.

Anonymous over 9 years ago

Once again, no matter the situation, cheating/plagiarizing/misrepresenting other people's work is wrong. It doesn't matter if they were "in the moment", or only had 5 minutes to present, or that hackathons are a stressful event.

#2: "That is ok though because hackathons are a place to learn and make mistakes, and these mistakes are easy to fix."

This is an event with very real-world consequences: money, the potential for more funding, company growth opportunities, fame, a line on a resume, etc. This is NOT an opportunity for students to cheat, especially when there's company sponsors looking for potential startups to fund and partner with.

Being from MIT doesn't exclude students from the negative consequences of cheating. I can't believe #2 would even say otherwise.

Seamless's punishment by the media is minimal compared to the potential multi-million-dollar lawsuit they would've faced had they not been caught, received their prize package, and received angel/VC funding.

Anonymous over 9 years ago

#13, again, are you certain there would be lawsuits rather than the VC's going along, in turn lying to their own investors? Cheaters (or what would be considered such by academia) rule this world. The sleazy world out there and the ivory tower do not naturally mix, and that's why there has been such an effort to bridge the divide with these events, and look what students are being taught -- show glamour at all costs, for $$$. It's the risk of taking on such partnership.

Anonymous over 9 years ago

#14: Seems like you're one of the Seamless cheaters, or someone close to them in terms of values.

Even if cheaters did rule the world, that doesn't mean it's right. You gave pathetic excuses for Seamless's behavior, implying (since they might not get caught) that it's somehow okay.

These are the same types of people that embezzle money from organizations and steal from their family and friends - anything to get ahead right? I'm so thankful the guys at Dropbox caught them before they were given the resources to actually make money off of it.

Anonymous over 9 years ago

#15, what do you mean by "the guys at Dropbox caught them"? I don't recall reading that in either of the news articles or outside accounts.