There’s a new domain topping the charts as the most-visited new gTLD site.
A few days ago, namu.wiki replaced searchengines.guru in the top spot, the first time the leading position has changed hands since DI PRO first started tracking daily Alexa scores in July 2014.
namu.wiki appears to be a
Japanese Korean wiki site dedicated to some kind of manga/anime thing. It was registered in April.
searchengines.guru is a Russian forum devoted to discussions of search engine optimization.
Japanese Korean site has an Alexa rank of 1,875 today, compared to 1,994 for the SEO site. The highest score we’ve ever recorded for a new gTLD domain was 717.
Interestingly, only two of the site in the top 10 are in English. Two appear to be associated with spam.
The usual caveats about the reliability of Alexa data applies.
DotMusic Limited, the .music applicant founded by Constantine Roussos, is using a highly suspicious Wikipedia page in its attempt to win the .music contention set.
The applicant and many supporters have been citing the Wikipedia “music community” page in support of DotMusic’s ongoing Community Priority Evaluation, despite the fact that the page draws text, without citation, from DotMusic’s own application.
The Wikipedia page was created October 21, 2014, just two weeks after rival .music applicant Far Further spectacularly failed in its own Community Priority Evaluation bid.
Three of its supporters (Jeunesses Musicales International, International Society of Music Education, and International Federation of Musicians) have cited the Wikipedia article in DotMusic-drafted letters sent to ICANN.
An early version of the sign-and-submit form letter DotMusic is encouraging supporters to send to ICANN included the Wikipedia reference (this one, for example) but it appears to have been removed from form comments sent after the end of July.
Its web site currently says that its definition of “music community” is “confirmed by Wikipedia”.
In fact, the Wikipedia page pulls lots of its language from DotMusic’s 2012 new gTLD application, as represented in the table below.
|Music community is defined as a logical alliance of interdependent communities that are related to music,||The Community is a strictly delineated and organized community of individuals, organizations and business, a logical alliance of communities of a similar nature (COMMUNITY)|
|The music community shares a cohesive and interconnected structure of artistic expression, with diverse subcultures and socio-economic interactions between music creators, their value chain, distribution channel and fans subscribing to common ideals.||The Community and the .MUSIC string share a core value system of artistic expression with diverse, niche subcultures and socio-economic interactions between music creators, their value chain, distribution channel, and ultimately engaging fans as well as other music constituents subscribing to common ideals.|
|Under such structured context music consumption becomes possible regardless whether the transaction is commercial and non-commercial||Under such structured context music consumption becomes possible regardless whether the transaction is commercial and non-commercial|
The phrase “logical alliance” originates in the ICANN Applicant Guidebook, as part of the CPE rules.
But that still leaves two sentences that appear to have been only lightly edited after being taken wholesale from the DotMusic application.
The Wikipedia page does not refer to domain names or ICANN, nor does it cite DotMusic as a source, despite the fact (per a Google search) that phrases such as “socio-economic interactions between music creators” have only ever appeared in .music’s application.
That’s unusual, because the citations in the article, many of which are to weighty, barely comprehensible scholarly works, give the impression of a well-researched and well-sourced piece.
Only one Wikipedia editor, known by the handle Dr. Blofeld, has contributed anything of substance to the page. Three others have provided cosmetic edits.
While a prolific editor since 2006, the closest he had previously come to writing an article about music were his contributions to a page about a green Versace dress once worn by singer Jennifer Lopez, according to Blofeld’s user page.
He seems to be much more interested in nature, architecture and film (including James Bond films, naturally).
On wonders why he had the sudden urge to scratch-build a 375-word article about the “music community”, having evidently read a dozen academic works on the topic, that fails to cite DotMusic’s application as the source of some of the text.
In summary, the evidence points towards the article being created solely for the purpose of assisting DotMusic towards a CPE victory that would save it the seven-figure sum .music is likely to fetch if it goes to auction.
There are eight applicants for .music in total.
Dot-brand gTLD applicants that were playing wait-and-see with ICANN’s contracting process signed Registry Agreements in droves last week.
At least 67 new RAs were signed in the last three days of July, on or around the ICANN’s July 29 deadline, ICANN’s web site shows.
This means that there are still about 50 applicants that have not pulled the trigger and may have to apply for an 60-day last-chance extension.
A week before the deadline, roughly 170 brands had still not signed contracts.
The July 29 deadline was put in place for dot-brands last year due to delays creating Specification 13 of the RA, which gives brands special opt-out clauses dealing with things like sunrise periods.
Those that have still not obtained RAs are expected to be flagged as “Will Not Proceed” and will have to apply to ICANN for the extension under its Application Eligibility Reinstatement process.
The African Union Commission has criticized ICANN’s “dysfunctional accountability process” that has kept the proposed .africa gTLD in limbo for the last few years.
In a communique yesterday (pdf), the AUC also reiterated that .africa applicant ZA Central Registry has the support of both the AUC and its member states, and that governments used almost every avenue available to them to object to the rival DotConnectAfrica bid.
The letter reads:
The Africa region, African Internet stakeholders, the ZACR and AUC are the unfortunate victims of a dysfunctional accountability process and an independent review panel that did not delve more deeply to understand the new gTLD process, the role of governments in that process, and how the ICANN multistakeholder model functions in general.
A few weeks ago, an Independent Review Process panel controversially ruled that ICANN had treated DCA’s application unfairly, in violation of its bylaws, when it accepted Governmental Advisory Committee advice to reject it.
The panel said that ICANN should have at least asked the GAC for the rationale behind its advice, something that the new gTLD program’s rules did not require it to do.
One of the issues at the heart of the subsequent debate is whether ICANN inappropriately helped out ZACR’s bid by drafting an AUC letter of support and then tried to cover its actions up by inappropriately redacting information from the IRP ruling before publication.
On Friday, ICANN published a new version of the ruling that had these references restored, while retaining redactions related to the actions of Kenyan government officials.
We know what the still-redacted text says because Kieren McCarthy, writing for The Register, obtained a clean copy and published it a couple of weeks ago.
ICANN also promised to publish its reasoning if it makes redactions to any documents in future.
In a blog post on Friday, general counsel John Jeffrey said that ICANN helping the AUC draft its letter of support was not a unique case, nor was it inappropriate:
ICANN staff has helped many applicants and their supporters understand how to properly document support. Not only did we make a template support letter publicly available to all as part of the New gTLD Program Applicant Guidebook (see Appendix to Module 2), we have answered questions, received through our customer service channel, as to how interested parties can document support for a given gTLD application. In the case of ZA Central Registry, ICANN appropriately assisted the applicant in documenting support from the AUC.
Our actions surrounding the .AFRICA applications were not unique, since we assist any applicant who requests assistance, or who needs clarification in learning how best to document support or other matters. We have provided assistance to all applicants regarding their applications to the maximum extent possible.
On the claims that ICANN tried to “cover up” this assistance by redacting the IRP’s ruling and previous IRP filings, Jeffrey said that the information was covered by a confidentiality agreement agreed to by itself and DCA and endorsed by the IRP panel.
He said that ICANN was “motivated by our obligation to the community to post the document quickly and the competing, yet mandatory obligation, to respect confidential information while being as transparent as possible.”
He said ICANN attempted to reach out to those affected by the “confidential” parts of the ruling to seek permission to remove the redactions.
But McCarthy also seems to have seen emails exchanged between DCA and ICANN, and he says that ICANN redacted it over DCA’s objections.
McCarthy further says that ICANN only became interested in removing the redactions after he had already published the clean version of the ruling at The Reg — five days after the initial publication by ICANN.
Jeffrey’s post, which refers to “erroneous reporting” in an apparent allusion to McCarthy’s articles, nevertheless fails to address this claim, lending credibility to the cover-up allegations.
The .africa gTLD has been contracted to ZACR, but DCA’s rejected application has been returned to evaluation per the IRP’s ruling, where it is broadly expected to fail for want of governmental support.
Disclosure #1: I recently filed a Documentary Information Disclosure Policy request seeking the release of all the unredacted exhibits in DCA v ICANN. Given ICANN’s wont to usually respond to such requests only at the end of the full 30 days permitted by the policy, I should not expect to see an answer one way or the other until the last week of August.
Disclosure #2: As regular readers may already be aware, due to my long-held and never-disguised view that DCA was mad to apply for .africa without government support, I was once accused of being a part of a “racial conspiracy” against DCA on a blog I believe to be controlled by DCA. Naturally, after I stopped laughing, this libelous allegation pissed me off no end and enhanced my belief that DCA is nuts. Around the same time DCA also, under its own name, filed an “official complaint” (pdf) with ICANN, omitting the race card, alleging that I was part of a conspiracy against it.
ICANN has beaten off a lawsuit from alternate root provider name.space for a second time, with a US appeals court ruling that the new gTLD program was not an illegal conspiracy.
name.space sued ICANN in 2012, claiming that the program broke competition laws and that “conflicted” ICANN directors conspired with the industry in an “attack” on its business model.
The company runs an alternate DNS root containing hundreds of TLDs that hardly anyone knows about, cares about, or has access to.
Almost 200 of the strings in its system had matching applications in the 2012 new gTLD round; many have since been delegated.
The company’s complaint asked for an injunction against all 189 matching TLDs.
But a court ruled against it in 2013, saying that name.space had failed to make a case for breaches of antitrust law.
Last week, an appeals court upheld that ruling, saying that the company had basically failed to cross the legal threshold from simply making wild allegations to showing evidence of an illegal conspiracy.
“We cannot… infer an anticompetitive agreement when factual allegations ‘just as easily suggest rational, legal business behavior.’,” the court ruled, citing precedent.
“Here, ICANN’s decision-making was fully consistent with its agreement with the DOC [US Department of Commerce] to operate the DNS and the Root,” it wrote. “In transferring control to ICANN, the DOC specifically required it to coordinate the introduction of new TLDs onto the Root. This is exactly what ICANN did in the 2012 Application Round”.
“The 2012 rules and procedures were facially neutral, and there are no allegations that the selection process was rigged,” the panel ruled.
The court further ruled that ICANN is not a competitor in the markets for domain names as registry, registrar or defensive registration services, therefore it could not be subject to antitrust claims for those markets.
A few other claims against ICANN were also dismissed.
In short, it’s a pretty decisive victory for ICANN. General counsel John Jeffrey said in a statement that ICANN is “pleased” to have won.
All the major documents in the case, including the latest opinion, can be downloaded here.
While the lawsuit has been making its way through the courts, the .space gTLD has actually been delegated and the domain name.space is owned by its new registry, Radix.
There’s some salt in the wounds.