Spurned applicant crowd-funding to fight ICANN for .gay gTLD
The community-driven applicant for .gay is attempting to raise hundreds of thousands of dollars via crowd-funding to challenge a series of adverse decisions that look set to lock it out of running the gTLD.
Alongside the fundraising, dotgay LLC has launched an extraordinary broadside at its frustrators, accusing ICANN of “discrimination” and rival applicants of trying to “exploit” the gay community.
The company wants to raise $360,000 via this Generosity.com page, “to challenge decisions that have stalled community efforts for .GAY.”
Although the campaign has been running for 23 days, so far only three people (including a former employee) have donated a total of $110.
Given the vast number of LGBTQIA organizations that have lent their support to dotgay, I can only assume a lack of publicity is to blame for the $359,890 shortfall.
A five-minute video announcing the campaign has been on YouTube since August 3, but at time of writing has only been viewed 100 times.
In the video, embedded below, dotgay says that only it can properly represent the LGBTQIA (Lesbian, Gay, Bisexual, Transgender, Queer, Intersex and Ally) community.
ICANN is dividing the community by accepting the Economist Intelligence Unit’s decision that the company should fail its Community Priority Evaluation (largely because the TQIA are not necessarily “gay”), the video voiceover suggests.
This is an old game that highlights how LGBTQIA continue to be disadvantaged and discriminated against. If .gay is not recognized as a community domain, ICANN will simply auction the namespace to the highest bidder and pocket the proceeds. If ICANN assigns to the right to operate the registry for .gay to a company seeking to exploit it for profit — very possibly without community participation in policy development for the domain, or taking into consideration LGBTQIA interests and concerns — the community will have no assurances .gay will be s safe space on the internet… In the end, ICANN and the three other applicants for the .gay domain have shown no respect for the global gay community’s wishes.
Neither the video not the crowdfunding page specify exactly what the $360,000 would be used for.
However, in order to challenge the CPE decision(s) against it, a lawsuit or an Independent Review Process — either of which could wind up costing over a million dollars — would be the most usual avenues of attack.
Perhaps eager to avoid the possibility of a legal challenge, the three other applicants — Minds + Machines, Rightside and Top Level Design — this week wrote to ICANN to demand a hasty resolution of the long-running saga.
Writing on behalf of all three, Rightside VP Statton Hammock wrote (pdf):
It has been more than FOUR years since the Applicants filed their applications for .GAY. Since this time long ago, dotGay has filed THREE community objections, one against each of the Applicants; TWO community priority applications, ONE Independent Review Panel request (later withdrawn) and ONE motion for reconsideration with the BGC which has been carefully considered by the members of that Committee and found insufficient to be granted. In total dotGay has had SIX “bites of the apple” and has been unsuccessful each time… It is simply time for the Board to affirm these decisions and allow the .GAY applications to proceed to contention set resolution.
The ICANN board had been due to consider dotgay’s latest Request for Reconsideration at at a meeting August 9, but the agenda item was removed, the letter notes. The applicants called on the board to meet again soon to make a decision.
After the board processes the RfR, .gay would presumably go to auction. Whether the auction resulted in ICANN pocketing the cash (as dotgay claims) or being distributed between the three losing applicants remains to be seen.
Whether the auction is public or private, the crowdfunding campaign strongly suggests that dotgay does not currently have the resources to win.
Ombudsman trashes ICANN’s rejection of .gay “community”
ICANN’s outgoing Ombudsman fired a parting shot at his former employer last week with a scathing analysis of its rejection of .gay as a community gTLD.
ICANN should reject the decisions of two independent Economist Intelligence Unit panels, which found that Dotgay LLC’s application for .gay did not meet the strict definition of “community” under ICANN rules, LaHatte wrote.
“This is the time to recognise that even if the EIU evaluation did not achieve the appropriate number of points, that the community is real, does need protection and should be supported,” he wrote.
His recommendation appears on his personal blog, dated July 27, the same day his contract with ICANN expired. It has not appeared on the official ICANN Ombudsman blog.
The EIU is responsible for conducting Community Priority Evaluations for applicants who claim to be representing communities.
Its decisions have been unpredictable and to a degree inconsistent, but both times its panels looked at Dotgay’s .gay, they scored the application lower than the 14 out of 16 points required to pass the CPE.
Winning a CPE generally means you get the gTLD in question. Losing means you have to go to auction against competing applicants.
In the case of .gay, the other applicants are Top Level Design, Minds + Machines and Rightside.
Dotgay failed both times because its stated community — which includes straight people — does not match the string “gay”.
Nobody’s ever said that there’s no such thing as a gay community, they’ve just said there’s no such thing as a gay Community (big C) as defined by Dotgay LLC.
LaHatte’s recommendation does not delve into the nitty-gritty of the scoring process, but seems to criticize the system — and the flawed Request for Reconsideration system Dotgay has thrice unsuccessfully invoked — as “inadequate”. He wrote:
The role of the ombudsman is to deal with issues of fairness, and this encompasses issues such as respect for diversity and support for all parts of our community. Sometimes the mechanisms which we have put together to resolve challenges are simply inadequate…
But the issue that I want to emphasise in this recommendation is that it has always been open to ICANN to reject an EIU recommendation, especially when public interest considerations are involved. What is needed is to take a bold approach and demonstrate to the ICANN community, but also much more widely, to the world of Internet users, that ICANN has a commitment to principles of international law (see Article IV of the Bylaws), including human rights, fairness, and transparency.
The board will be very aware of the human rights initiatives undertaken in the light of the IANA transition and the careful evaluation of the accountability processes. But sometimes it is necessary to take a view which evaluates whether the decision taken corresponds with the bylaws and articles of incorporation. That view should be that ICANN supports the gay community and recognises that there is a community which requires protection and recognition, which has been marginalized, threatened and attacked, and which should be considered a genuine community notwithstanding the EIU recommendation.
He’s basically calling on ICANN’s board to cast aside the rules and previous practice in this particular instance and instead make a political statement, in my reading of the recommendation.
I don’t think ICANN will do that.
On a couple of occasions when Dotgay has suffered an ICANN-induced setback in the past, ICANN has put out statements reminding everyone that there will be a .gay, they only question is who runs it.
Because Dotgay filed a community application, it would be obliged to make .gay a restricted space. Its application talks about registrants having to be approved as eligible before they register.
But it also would have the strictest measures in place to address homophobia and harassment — something the other applicants may, but have not formally committed, to implement.
dotgay loses third .gay appeal
Death warrant or portent of impending legal action?
dotgay LLC has lost its third attempt to get ICANN to reconsider tossing its application for community priority status in the fight for the .gay gTLD.
According to ICANN, on Sunday its Board Governance Committee threw out dotgay’s third Request for Reconsideration, an attempt to give the company an unprecedented third go at the Community Priority Evaluation process.
CPEs allow community gTLD applicants to avoid expensive auctions, but dotgay has lost two primarily on the grounds that its definition of community includes people who are not gay.
Its latest RfR was pretty weak, based on a technicality about which staffers at the Economist Intelligence Unit (which carries out the CPEs) were in charge of verifying its letters of community support.
The rationale for the BGC’s determination, which still needs to be rubber-stamped by the full ICANN board, has not been published yet.
But it seems from a blog post that ICANN now expects .gay to go to auction, where there are four competing applicants in total.
ICANN does not usually publish blog posts on RfR decisions, but in the .gay case it has been keen to avoid being accused of any motivation beyond a dogged pursuit of correct procedure.
So will dotgay go quietly? It remains to be seen.
While all new gTLD applicants had to sign a release promising not to sue ICANN, .africa applicant DotConnectAfrica sued earlier this year and managed to get a sympathetic judge who seems bent on allowing the case to go to trial.
dotgay has a third crack at .gay appeal
dotgay LLC has filed another appeal with ICANN, hoping to get its community-based .gay application back in the race.
It submitted a third Request for Reconsideration (pdf) this week, arguing on a technicality that its bid should have another Community Priority Evaluation.
The company has already lost two CPEs based on the Economist Intelligence Unit CPE panel’s belief that its definition of “gay” is too broad because it includes straight people.
It’s also lost two RfRs, which are adjudicated by ICANN’s Board Governance Committee.
The newest RfR addresses not the core “not gay enough” issue, but a procedural error at the EIU it believes it has identified.
According to the filing, dotgay is in possession of emails from an EIU employee who was responsible for verifying some of the dozens of support letters it had received from dotgay’s backers (generally equal rights campaign groups).
The company argues, citing the BGC’s own words, that this employee was not one of the official CPE “evaluators”, which means the EIU broke its own rules of procedure:
considering the fact that the CPE Process Document – which is considered by the BGC to be “consistent with” and “strictly adheres to the Guidebook’s criteria and requirements”, it is clear that the verification of the letters should have been performed by an independent evaluator… and not by someone “responsible for communicating with the authors of support and opposition letters regarding verification in the ordinary course of his work for the EIU”.
It wants the CPE to be conducted again, saying “it is obvious that the outcome of a process is often, if not always, determined by the fact whether the correct process has been followed”.
It’s difficult to see how the outcome of a third CPE, should one be undertaken, could be any different to the first two. Who verifies the support letters doesn’t seem to speak to the reason dotgay hasn’t scored enough points on its other two attempts.
But the alternative for the company is an expensive auction with the other .gay applicants.
Another CPE would at least buy it time to pile more political pressure on ICANN and the EIU.
“We’re not homophobic!” ICANN pleads as it throws out .gay appeal
ICANN has refused dotgay LLC’s latest appeal against adverse .gay decisions, and has taken the unusual step of preemptively defending itself against probably inevitable accusations from gay rights groups.
On Monday, the Board Governance Committee threw out dotgay’s Request for Reconsideration, in which the company had asked for a third crack at the Community Priority Evaluation process that could have seen it win .gay without paying at auction.
Today, BGC chair Chris Disspain published a blog post that’s basically a defense against accusations that ICANN is somehow intolerant or ignorant of gay issues.
The post explains the RfR process, explains that the latest decision doesn’t mean there won’t be a .gay or that dotgay won’t win the contention set, winding up:
I want to make clear that the denial of the Request for Reconsideration is not a statement about the validity of dotgay LLC’s application or dotgay LLC’s supporters. The decision means that the BGC did not find that the CPE process for dotgay, LLC’s .GAY application violated any ICANN policies or procedures.
It is ICANN’s responsibility to support the community-developed process and provide equitable treatment to all impacted parties. We understand that this outcome will be disappointing to supporters of the dotgay LLC application. We appreciate the amount of interest that this topic has generated within the ICANN community, and we encourage all interested parties to participate in the multistakeholder process to help shape how future application rounds are defined.
dotgay’s two CPEs, which were evaluated by the Economist Intelligence Unit, failed because the company defined its “community” too broadly, to include people who aren’t gay.
The company says that it’s “common sense” that “gay” is an umbrella term not only for lesbian and bisexual people, but also for people with non-standard gender identities and straight people who support equal rights.
(As an aside, I recently learned that former boxing promoter Kellie Maloney, the UK’s poster girl for transgender issues, disagrees with same-sex couples raising kids and once called for gay pride marches to be banned. I wonder how she fits under this umbrella.)
But the second EIU panel “determined that the applied-for string does not sufficiently identify some members of the applicant’s defined community, in particular transgender, intersex, and ally individuals”.
The CPE application fell apart on that basis. It scored 10 of the available 16 points, four points shy of a winner.
Due to the sensitive nature of this kind of thing, and the fact that dotgay does have a truckload of genuine support from prominent campaigning members of its community, ICANN and the EIU have come in for criticism.
Some of that criticism has implied that ICANN, the EIU, the process or all three are in some way homophobic or at least ignorant.
An article on gay news website The Gayly this week said: “The EIU’s actions contradict all common sense and are being interpreted as the outcome of a hostile environment.”
dotgay encouraged supporters to tweet: “Say NO to unfair & unequal treatment of the gay community at the hands of @TheEIU #Yes2dotgay”.
I’ve seen some tweets from supporters that use stronger language, which I’m guessing is what the BGC is trying to preempt today.
Now that it has exhausted the RfR process without success, expect dotgay to file an Independent Review Process appeal with ICANN, delaying the .gay contention set resolution for a year or more.
UN group supports community .gay bid
An organization representing staff members of the United Nations has come out in support of dotgay LLC’s struggling community application for the .gay gTLD.
UN-GLOBE comprises UN employees who identify as “lesbian, gay, bisexual, transgender, and inter-sex”. Its primary goals are pushing for equal rights for these groups within the UN system.
In a letter to ICANN (pdf) earlier this month, the organization said it supports dotgay’s application, despite its Community Priority Evaluation being rejected twice.
The Economist Intelligence Unit’s judging panel has kicked out both of dotgay’s CPEs on the grounds that the applicant’s definition of “gay” includes straight people, and straight people aren’t gay.
But UN-GLOBE, echoing dotgay’s own view, wrote:
We also express our disagreement over the results of the Community Priority Evaluation of October 8, 2015 that rejected dotgay LCC’s community application based on its narrow analysis of the term gay. The term gay should be understood globally instead, as it is generally understood by the internationally diverse lesbian, gay, bisexual, transgender, queer, intersex, and ally (LGBTQIA) community represented in dotgay LLC’s application.
It might be worth noting that UN-GLOBE makes no mention of its own membership including “allies” — that is, people who are not LGBTQI but nevertheless support equal rights — in its letter or on its web site.
dotgay currently has an outstanding Request for Reconsideration against its latest CPE loss, which is expected to be decided by ICANN’s Board Governance Committee on Monday.
If ICANN closes the door on more appeals, the .gay contention set will go to auction where its rivals are Rightside, Top Level Design and Minds + Machines.
One way or another, there will be a .gay gTLD, the only question is whether it will be restricted to approved “gay community” members or open to all.
.gay applicant appeals community loss, again
dotgay LLC has appealed its Community Priority Evaluation defeat again, filing a new Request for Reconsideration with ICANN this week.
It’s an unprecedented second use of the RfR process to appeal its CPE loss, in which the Economist Intelligence Unit panel decided the applicant’s definition of “gay” was far too broad to award dotgay enough points to pass the evaluation.
But dotgay wants ICANN to initiate a third CPE, to be carried out by anyone other than the EIU.
The EIU panel said earlier this month that it had “determined that the applied-for string does not sufficiently identify some members of the applicant’s defined community, in particular transgender, intersex, and ally individuals”.
Basically, EIU was pointing out, for the second time, that transgender people and straight “allies” aren’t “gay”.
It awarded dotgay 0 out of the possible 4 points available on “Nexus” criteria, meaning the applicant failed to hit the 14 points required to win.
While the RfR dodges the transgender issue altogether, dotgay has some interesting arguments in response to the “ally” question.
It’s now claiming that “ally” refers to companies and organizations that support the equal rights cause (because non-human legal entities don’t have a gender identity or sexual preference) and to proxy registrars:
Now, since an organization or company in itself can impossibly be “lesbian” or “gay”, Requester has been seeking for a way to also position these companies and organizations in this community definition. For this reason, Requester has referred to these organizations as “allies” in the context of the LGBTQIA definition.
Furthermore, as stated in the Application, LGBTQIAs are a vulnerable group in many countries and societies, and too often still the subject of prosecution for who they are. In order to put in place safeguards for those gay community members who do not wish to be directly associated with a domain name registration, organizations and companies who in essence cannot be “non-heterosexual” should have the possibility to act as a proxy service, which is common practice in the domain name industry.
In any case, any such “ally” must be approved by an Authentication Partner in order to be able to register a domain name in its own name or in the name or on behalf of a third party who meets the LGBTQI requirements.
It’s an interesting argument, but I can’t see anything in its original application that would support such a position.
dotgay may be on stronger ground with its claim that it unfairly lost one point on the “Opposition” criteria of the CPE.
Two points were available there. Applicants could lose one point immediately if there was a single letter of opposition from a relevant, non-negligible organization.
The EIU seems to have been in possession of such a letter, though its CPE ruling does not name the opponent.
dotgay thinks the opponent was the Q Center, a community center in Portland, Oregon, which opposed dotgay in writing in 2014 but, following a change in its board of directors, retracted that opposition (pdf).
So it may be the case that dotgay unfairly lost a point.
Regaining that point would not be enough to give the company a winning CPE score, but if the EIU screwed up that may be grounds for ICANN to initiate another rerun of the CPE.
However, it’s quite rare for ICANN’s board of directors to approve an RfR.
If dotgay loses, it will either have to go to auction against its rival applicants or file an Independent Review Process complaint, its final avenue of appeal.
Read its RfR here.
.gay flunks community review for second time
dotgay LLC has failed in its bid to eliminate its competitors for the new gTLD .gay for the second time.
After an unprecedented re-run of its Community Priority Evaluation, the applicant scored just 10 out of the 16 available points.
That’s exactly the same as it scored the first time around, exactly one year ago, still four points short of success.
For the second time, dotgay scored zero from a possible four points on the “Nexus” criteria — the link between the string “gay” and the community dotgay wants to serve.
The CPE panel decision reads:
The Panel has determined that more than a small part of the applicant’s defined community is not identified by the applied-for string, as described below, and that it therefore does not meet the requirements for Nexus.
…
The Panel has determined that the applied-for string does not sufficiently identify some members of the applicant’s defined community, in particular transgender, intersex, and ally individuals
As I explained a year ago, when the first CPE panel flunked the applicant for exactly the same reason, dotgay’s proposed community included lots of people who would not necessarily describe themselves as “gay”.
You, possibly, for example.
If you’re an “ally” of gay people, by for example supporting equal rights, then you would qualify as “gay” under dotgay’s definition.
If you’re transgender or intersex, you would similarly captured by this definition. The panel said:
Despite the applicant’s assertions to the contrary, its own evidence here shows that “gay” is most commonly used to refer to both men and women who identify as homosexual, and not necessarily to others. The applicant’s “umbrella term” argument does not accurately describe, for example, the many similar transgender stories in the mass media where “gay” is not used to identify the subject. In these cases, “transgender” is used because “gay” does not identify those individuals.
The panel concluded that .gay “does not identify or match” the target community, and scored it zero.
dotgay had a second roll of the dice because the first CPE panel was found to have committed a process error by not sufficiently verifying the company’s many dozens of letters of support from gay advocacy organizations.
However, this error did not relate to the Nexus criteria, so a victory was always going to be a long shot.
The .gay gTLD is now heading to auction, where Minds + Machines, Rightside and Top Level Design are the other bidders.
You can read the new decision in PDF format here.
.gay is gay enough after all? ICANN overturns community panel decision
One of the applicants for .gay has won a significant battle in the fight for the controversial new gTLD.
In a shock move, a committee of ICANN’s board of directors has overturned the rejection of dotgay LLC’s Community Priority Evaluation, ordering that the case should be re-examined by a new panel of experts.
As you may recall, dotgay’s CPE was kicked out in October after the Economist Intelligence Unit panel decided that the company’s defined community was too broad to be described by “gay” as it included a lot of people who aren’t gay, such as straight people.
The decision — which I thought was probably correct — caused an uproar from dotgay’s myriad supporters, which include dozens of international equal rights and gay community organizations.
dotgay filed a Request for Reconsideration, ICANN’s cheapest but least reliable form of appeal, and today found out it actually won.
ICANN’s Board Governance Committee, which handles the RfR process, this week ruled (pdf):
The BGC concludes that, upon investigation of Requester’s claims, the CPE Panel inadvertently failed to verify 54 letters of support for the Application and that this failure contradicts an established procedure. The BGC further concludes that the CPE Panel’s failure to comply with this established CPE procedure warrants reconsideration. Accordingly, the BGC determines that the CPE Panel Report shall be set aside, and that the EIU shall identify two different evaluators to perform a new CPE for the Application
The successful RfR appears to be based on a technicality, and may have no lasting impact on the .gay contention set.
Under the EIU’s process rules: “With few exceptions, verification emails are sent to every entity that has sent a letter(s) of support or opposition to validate their identity and authority”.
It seems that the EIU was sent a bundle of 54 letters of support for dotgay, but did not email the senders to verify they were legit. The BCG wrote:
Over the course of investigating the claims made in Request 14-44, ICANN learned that the CPE Panel inadvertently did not verify 54 of the letters of support it reviewed. All 54 letters were sent by the Requester in one correspondence bundle, and they are publicly posted on ICANN’s correspondence page.36 The 54 letters were deemed to be relevant by the EIU, but the EIU inadvertently failed to verify them.
If an applicant wins a CPE it means all the other applicants are automatically excluded, and the door is now open for the EIU to rethink its earlier decision.
So do competing applicants Rightside, Minds + Machines and Top Level Design now have genuine cause for concern? Not necessarily.
CPE applicants need to score at least 14 out of 16 available points in order to win, and dotgay only scored 10 points in its original evaluation.
Crucially, the EIU panel said that because the “community” as defined by dotgay included transgender, intersex, asexual and straight “allies” of equal rights, it was too broad to score any of the available four points on the “Nexus” criteria.
The BCG could find no fault with the EIU’s determination on Nexus, so even if dotgay’s letters of support are verified according to procedure, it would not necessarily lead to dotgay picking up any more Nexus points.
The BCG wrote on Nexus: “Requester’s substantive disagreement with the CPE Panel’s conclusion does not support reconsideration”.
However, given that the EIU is going to do the entire CPE all over again with new panelists, it seems entirely possible that dotgay could win this time.
Why kicking out the .gay “community” was right
Since Dotgay’s application for a Community Priority Evaluation on .gay failed last week, there’s been some unrest among its supporters and in the media.
An effort to get #ICANNisBroken trending hasn’t exactly set the Twittersphere alight, but there have been a handful of news stories that attack the CPE decision for failing to represent the gay community.
I think the criticisms are misplaced.
The Economist Intelligence Unit, which conducts the CPEs for ICANN, got it right in this case, in my view.
Dotgay scored 10 points out of 16 on the CPE. It needed 14 to pass. A pass would have given it exclusive rights to .gay, forcing the three other applicants to withdraw.
It could have scored 14 had it managed to get 4 points out of the available 4 on the “Nexus” criteria — the strength of the relationship between the string “gay” and the community Dotgay said it wanted to represent.
The EIU scored Dotgay zero.
The reason was that Dotgay, in its application, defined its community like this:
The Gay Community includes individuals who identify themselves as male or female homosexuals, bisexual, transgender, queer, intersex, ally and many other terminology – in a variety of languages – that has been used at various points to refer most simply to those individuals who do not participate in mainstream cultural practices pertaining to gender identity, expression and adult consensual sexual relationships. The Gay Community has also been referred to using the acronym LGBT, and sometimes the more inclusive LGBTQIA. The most common and globally understood term – used both by members of the Gay Community and in the world at large – is however “Gay”.
Dotgay lost the 4 points it needed to pass the CPE almost entirely because of this paragraph.
It overstretched, and it doing so it failed to play by the ICANN rules.
Remember, the EIU was asked to determine the “nexus”, or correlation, between the gTLD string — the word “gay” — and the people Dotgay said it was trying to represent.
By trying to be as inclusive as possible to as many different sexuality/gender identities as it could, Dotgay lost sight of the fact that the gTLD string it wants only describes a subsection of those people.
LGBTQIA isn’t even a particularly well-understood acronym. The “A” could mean “Ally”, as Dotgay said in its application, or “Asexual”, as it is often (but not in Dotgay’s application) interpreted.
Dotgay tried to define “intersex” people — humans whose genitalia or other sexual characteristics do not conform to the standard male/female norms — as “gay”. Are they “gay”?
It tried to define “allies” of gay rights as “gay”. Are we?
The majority of the straight people reading this post, myself included, would characterize themselves as an “ally” of the gay community — we’re supporters of equal rights — but we would not call ourselves “gay”.
The fact that we wouldn’t is an important part of the EIU’s logic, the reason it found Dotgay had overstretched in its community definition, and as hard as I try I can’t figure out why that logic is faulty.
“Membership in the Gay Community is not restricted by any geographical boundaries and is united by a common interest in human rights,” the Dotgay application reads.
Is that not an implicit admission that the “gay community” defined in the application actually includes the majority of the populations of most right-thinking democracies?
Regardless of the EIU’s logic, there has been a moderate amount of outrage online about its decision.
The article getting the most link love appears to be this one at Slate, written by “LGBTQ activist” Marc Naimark.
First, note the acronym Naimark uses in his bio at the bottom of the piece. There are two letters missing when compared to the Dotgay application — “I” and “A”, for “Intersex” and “Ally” or “Asexual”.
Would Dotgay have won its CPE if it had limited itself to the same five letters? Maybe, maybe not. GLAAD defines “gay” as only those people attracted to the same gender. Transsexuals may not count. I and A almost certainly don’t.
Is this just nit-picking?
Not really. The point of the CPE, taken as a whole, was to allow genuine communities to avoid expensive auctions whilst preventing gaming by unscrupulous registries that would seek to claim a valuable string without a genuine community behind them.
In a previous new gTLD round, ICM Registry defined its .xxx “community” as essentially ‘anyone who wants to be a member of the community’. The .mobi registry defined its community as basically ‘anyone with a mobile phone’.
These were both attempts, in my view, to game the rules ICANN had put in place for that particularly new gTLD application round. They were both successful.
What Dotgay tried to do with its .gay application was to define its community as basically everyone. I don’t think I would call it gaming, but I might call it a failure to follow the community rules closely enough.
So is it a bad thing that Dotgay’s CPE got rejected?
I don’t think so.
Remember, Dotgay has not been ruled out of the process. It can still compete at auction with the other applicants.
If that’s too rich for it, there may even be an opportunity for the company to combine in another way with a rival applicant, rather like DotGreen did with Afilias for .green.
In Salon, Naimark wrote that a non-Community .gay — one manged by Top Level Design, Minds + Machines or Rightside, the other three applicants — will likely be awash with pornography or homophobia:
Now, instead, .gay is up for auction, with dotgay LLC facing off against three much larger rivals whose sole aim is to make as much money as possible from .gay names. That means no oversight over who gets a name or what it’s used for. Gay bashers will be able to buy .gay domains. More significantly, the largest market is likely to be among porn sites. Any legitimate use of the name by individuals, businesses, and organizations associated with the LGBTQ community will likely be drowned in a sea of sex: On the Internet, everyone will be .gay for pay.
On the face of it, that seems like a compelling argument. Wouldn’t it be nicer if .gay was devoted to worthy causes rather than gay porn? I would probably agree with that argument.
But none of the four applicants for .gay — not even Dotgay — have any prohibitions or restrictions on porn in their applications.
There’s no reason on the new gTLD program record to believe Dotgay won’t sell .gay domains to porn sites too.
Where Dotgay does have a moral advantage against its competitors is in its explicit prohibitions against homophobic speech in the domain names it sells.
One of the policies it proposes in its application is that domain names should not be “words or phrases that incite or promote discrimination or violent behavior, including anti-gay hate speech.”
The other three applicants don’t have anything nearly as specific in their applications.
But by applying as a formal, big-C “Community” applicant, Dotgay also had to promise to restrict its gTLD to a limited number of people who were members of its self-defined “community”.
This is where I struggle.
Dotgay proposes to restrict .gay to people who obtain a special code via a number of as-yet unspecified, approved “Authentication Providers” — organizations that represent sections of the LGBTQIA community.
This process has clearly been created by the applicant, in my opinion, in order to get the required number of points in the CPE’s “Registration Policies” criteria, where you have to be restrictive to win.
What Dotgay is proposing is a system whereby in order to express your homosexuality (or membership of another LGBTQIA community, including “ally”) you need to apply to an approved gay-related organization for a special code.
That just seems wrong to me.
Whatever happened to the “self-identified” gay person? I thought that “self-identification”, in the sexual and gender identity world, was a bit of a big deal.
You need a password to “come out” online? Really?
I don’t want to be accused of “straightsplaining”, so it’s a genuine question: is it okay for a registry to need to authenticate your sexual/gender identity before you can register a .gay domain?
Recent Comments