Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] .on TLD Proposal

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] .on TLD Proposal


Chronological Thread 
  • From: Maiyannah Bishop <maiyannah.bishop AT postactiv.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] .on TLD Proposal
  • Date: Fri, 18 Nov 2016 15:52:06 -0500
  • Archived-at: <https://lists.opennicproject.org/sympa/arcsearch_id/discuss/2016-11/582F69F6.4020503%40postactiv.com>
  • List-archive: <https://lists.opennicproject.org/sympa/arc/discuss>
  • List-id: <discuss.lists.opennicproject.org>
  • Organization: postActiv

A thought: as a canadian, this would probably be confusing for people use to Ontario's subdomain off the .ca TLD operated by CIRA  (.on.ca), if we went with .on  Personally, I wouldn't use it.

-mb

On 2016-11-18 15:04, Daniel Quintiliani wrote:
You raise an interesting point about a general-purpose TLD for things that don't qualify as "geek". When I set up a game server (a VPS), I proposed a TLD here, but ICANN already had reserved it. 

This game (Minetest) isn't really "geek", it is an "oss" game but that has nothing to do with a server running it, and my server did not "encourage" anything, which disqualifies it from "free". I wound up going with "dyn", but I use a VPS, and can create a cron job. Normal Web sites don't have that ability.

As for ".on" vs ".onic", since people are likely not to hear about OpenNIC unless they set it up, I think ".onic" is better for promotional purposes, and so my vote is for ".onic"

--

-Dan Q


On Fri, 18 Nov 2016 07:18:27 -0600, Jonah Aragon <jonaharagon AT gmail.com> wrote:

Draago, you make some valid points I'm going to take time to consider. I'd
just like to reply to two of them right now.

1. I don't necessarily want to become as big as .com, rather I wanted to
make a TLD within the OpenNIC community that could be a go-to choice when
none of the other TLDs pertain to the topic. It may not seem like a large
issue now for the reasons you mention, most of the internet can't access
the OpenNIC network, but I want to work towards getting ISPs and other
large organizations to support the network in the future, and I see this as
a good step in that direction. While it works fine for the community right
now (highly tech oriented), not everybody may want .geek domains to
represent them :)

2. I want to be heavily aligned with OpenNIC, it's part of this mission to
get many users on the network, and all our resources will reflect that.
That being said, I don't think .onic being the TLD makes much sense from a
practical view, users won't want to type .onic every time they visit a
domain, as a reminder they're already on the network anyways. And I can't
picture many people saying "w w w dot my domain dot o-nick" to people (in
10-20 years, when OpenNIC becomes more ubiquitous).
Additionally, companies and other entities may be dissuaded by having
OpenNIC branding in their domains (this is looking into the future), it
would be similar to if ICANN created .icann and expected most companies to
use it; it seems to imply a relationship with ICANN that doesn't
necessarily exist.

That being said, I'll keep thinking about the points you made, and
alternate choices in case .on becomes a sticking point with people, but for
now .on is still my primary choice of TLD.

Hope all that (mostly rambling) made sense.

Jonah


--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

      

--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org


Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.19.

Top of Page