Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Future of .bit though OpenNIC

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Future of .bit though OpenNIC


Chronological Thread 
  • From: "Daniel Quintiliani" <danq AT runbox.com>
  • To: "discuss" <discuss AT lists.opennicproject.org>
  • Subject: Re: [opennic-discuss] Future of .bit though OpenNIC
  • Date: Mon, 18 Dec 2017 15:29:21 -0500 (EST)

Namecoin isn't subject to a "registrar," you purchase .bit domains yourself
using NMC through the Namecoin Core software. When it comes to cryptocurrency
such as Bitcoin and Namecoin, there are many people who have the
infrastructure and resources to store the blockchain privately and not rely
on a third party wallet service to hold the funds for them (until they go out
of business or get arrested for something).

Are you suggesting OpenNIC only cover .bit domains which are whitelisted by
the owner accepting an OpenNIC-specific charter, or to only cover .bit
domains which are registered through an OpenNIC-provided/approved third party
wallet service?

--

-Dan Q

On Mon, 18 Dec 2017 13:11:37 -0600, Administrador <admin AT bambusoft.com> wrote:

> Sorry, let me explain my self
>
> .bit is under namecoin blockchain system and you need to use namecoins
> to buy .bit domains
> we (as opennic) just serve as a slave entry point for .bit domains. No
> need for charter here
>
> But, if I wish to allow users to register .bit using a namecoin wallet
> ... I will allow them "similar not equal" to .null charter
> I will use my infrastructure as a registrar for .bit
> sorry if I didnt explain correctly
>
> Jonah, Emercoin is not Namecoin
>
> Regards
>
> Mario Rdz
>
>
> El 18/12/2017 a las 12:54 p. m., vv AT cgs.pw escribió:
> > Can I assume that you mean that you would like
> > to use the .null charter for .bit? I was unable
> > to parse your sentence.
> >
> > ~ Ole
> >
> >
> > On Mon, 18 Dec 2017 12:30:46 -0600
> > Administrador <admin AT bambusoft.com> wrote:
> >
> >> Hi Calum:
> >>
> >> I am Mario Rodriguez, .oz and .null TLDs operator at
> >> opennic
> >>
> >> I am interested in take .bit administration, but I will
> >> change the charter to use .bit similar to .null.
> >>
> >> If this is OK by the community let me know
> >>
> >> Regards
> >>
> >>
> >> El 18/12/2017 a las 12:10 p. m., Calum McAlinden escribió:
> >>> Dear All,
> >>>
> >>> I'm considering not continuing to operate the .bit zone
> >>> for OpenNIC due to not being involved in the project
> >>> anymore and also the ongoing spam use of .bit.
> >>>
> >>> I'm aware that there are ways around the spam issue,
> >>> for example applying the blacklist when the zone is
> >>> generated on my server rather than individual T2s.
> >>>
> >>> However, I wanted to ask whether anyone would be
> >>> interested in taking the running of this on? There is a
> >>> Python script in my repository at
> >>> https://github.com/CalumMc/nmczone which generates a
> >>> zonefile from the blockchain.
> >>>
> >>> If you are interest in taking this over, please let me
> >>> know and we can proceed with the agreement of the
> >>> community.
> >>>
> >>> Kind regards,
> >>> Calum
> >>>
> >>>
> >>>
> >>> --------
> >>> 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
>
> --
>
>
> <http://www.bambusoft.com>
>
> Administración / Soporte técnico
> admin AT bambusoft.com <mailto:admin AT bambusoft.com> / +52 (33) 1815-6186
>
> Bambusoft http://www.bambusoft.com
>
> Facebook Icon <https://www.facebook.com/bambusoft>
>
> Este mensaje de correo puede contener información privilegiada o
> confidencial para uso exclusivo de su(s) respectivo(s) receptor(es).
> Cualquier distribución diseminación, copia o la toma de cualquier acción
> en relación con la información aqui contenida esta prohibida. El correo
> electrónico no es seguro y no puede garantizarse que sea libre de
> errores ya que puede ser fácilmente interceptado, modificado o contener
> virus. Cualquiera que se comunique con nostros por correo electrónico se
> entiende que acepta estos riesgos. La empresa no se hace responsable de
> errores u omisiones en este mensaje y niega cualquier responsabilidad
> por cualquier daño como resultado del uso de este correo. Cualquier
> opinión o afirmación contenida en este mensaje y sus archivos adjuntos
> son responsabilidad única de su autor y no necesariamente representan
> los de la empresa.
>
> This e-mail message may contain confidential or legally privileged
> information and is intended only for the use of the intended
> recipient(s). Any unauthorized disclosure, dissemination, distribution,
> copying or the taking of any action in reliance on the information
> herein is prohibited. E-mails are not secure and cannot be guaranteed to
> be error free as they can be intercepted, amended, or contain viruses.
> Anyone who communicates with us by e-mail is deemed to have accepted
> these risks. Company Name is not responsible for errors or omissions in
> this message and denies any responsibility for any damage arising from
> the use of e-mail. Any opinion and other statement contained in this
> message and any attachment are solely those of the author and do not
> necessarily represent those of the company.
>
> Aviso de privacidad
> <https://www.bambusoft.com/site/company/privacypolicy.php>
>
>
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org





Archive powered by MHonArc 2.6.19.

Top of Page