Discuss mailing list

[Verax <verax AT 8chan.co>]

Unfortunately this is really the only way forward.  Breaking
compatibility with ICANN is a surefire way to die off at this point (in
the future it may be different, but who knows.

I see 2 ways forward in this issue.

1)  Move .free to .liber (latin for free, similar to french 'libre') and
move on since that should be safe fore a while

2) use .e and move existing domains to .fre.e.  1 letter domains should
be safe for now due to existing ICANN policies, though that may change
in the near future as they run out of domains to whore out for a quick buck.

On a related note, I'd appreciate it if no one tried to register .n, so
that if someone thinks they can make money off of .chan (fat chance) we
have a fallback.

Regards,
Verax

Jonah Aragon wrote:
> My personal opinion is we need to drop .free to look out for new users,
> as disappointing as that is.
> 
> The best option is #2 in my eyes, is support .libre as a great
> alternative TLD. Amazon hasn't started using the TLD (except for
> nic.free) or allowing registrations so I'd say we have at least a few
> months to make the transition as smooth as possible. A lot of links will
> need to be updated everywhere because your registry is at reg.for.free...
> 
> I think we should try to get .libre passed as soon as possible, the
> charter shouldn't be that different from .free. That way during the
> transition period we can have both resolving to the same records for a
> while, while people make the switch.
> 
> Jonah
> 
> 
> On Dec 3, 2016 2:13 AM, "Jeff Taylor" <shdwdrgn AT sourpuss.net
> <mailto:shdwdrgn AT sourpuss.net>> wrote:
> 
>     Well damn...  The threat of .free being used by ICANN has been out
>     there for a few years, almost since they opened up their gTLDs, but
>     the application has always fallen through or been dropped.
>     Unfortunately I see that as of November 7th Amazon successfully
>     registered the TLD, and it is in fact resolving from ICANN now.
> 
>     So we need to discuss the matter, and determine how Opennic wants to
>     proceed.  For reference there are 157 active domains registered
>     under .free (around 8 of those are system domains like www.free).
> 
>     -- We can choose to ignore ICANN and continue using .free as an
>     opennic TLD
>     -- We can move the existing opennic domains to a new TLD and support
>     ICANN's .free
>     -- We can drop all opennic domains and support ICANN's .free
> 
>     Although it is possible to merge the records from both sources, it
>     is a labor-intensive pain in the butt and we would have to consider
>     every domain name that conflicts now and in the future... This is
>     not an option I feel is worthwhile.  Thus, the three options above
>     are really the only choices we have.  There has been some discussion
>     about migrating .free to a new .libre TLD under opennic, and if
>     enough people are interested in migrating then I would take
>     suggestions and a vote for the new TLD name.  If we want to choose
>     option 1 above, then we do nothing and continue to ignore ICANN's
>     TLD.  If we want option 3, then I simply remove .free from opennic,
>     and the ICANN domains will start resolving.
> 
> 
> 
> 
>     --------
>     You are a member of the OpenNIC Discuss list.
>     You may unsubscribe by emailing
>     discuss-unsubscribe AT lists.opennicproject.org
>     <mailto: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