And that's what they would have to do..."copy it to China"
Which is basically all the clone is at this point.
I still think your focusing too much on "language" rather than "community".
I'm focused on language because that's the justification being given for cloning web apps. No matter what language you want to deal with, claiming that you can't build a community without entirely cloning another team's web app is asinine.
As I stated elsewhere, the internal software architecture (or licensing) is not the issue here, the cloned result presented to users/customers is.
Your argument was that someone can't take a web app and "copy it to China," yet this is exactly what it is at this point from the perspective of someone using the application. So, according to you now, apparently it can be done as long as the person who "cop[ies] it to China" happens to be on Chinese soil at the time and, unbeknownst to a regular user, builds it using a different web framework and open sources it.
No, in fact your origin implication was the right one: the hard part is building a community and delivering a service customized for market beyond simply changing the language, something that so far has not been done here with this application yet.
My argument is that there is more to a "product" than the attributes that make it the clone you see now. Will this new author develop this into something more or will someone else take his open source and develop more with it but for India or Korea? Time will tell. I reserve judgment.