Skip to content

Registrars page for namecoin.info#51

Open
sdalemans wants to merge 4 commits intonamecoin:masterfrom
sdalemans:49-registration-page
Open

Registrars page for namecoin.info#51
sdalemans wants to merge 4 commits intonamecoin:masterfrom
sdalemans:49-registration-page

Conversation

@sdalemans
Copy link

As discussed in issue #49, I created a simple registrars page for namecoin.info. At least to start with something and needs to be reviewed.

@indolering
Copy link

@phelixbtc can you vet this? Any objections to throwing it into production?

@phelixbtc
Copy link

http://namecoin.info/beta/?p=registrars
Looks good to me. ACK
There is a typo: corpoTation

@indolering
Copy link

Well, I didn't get the kind of bump I was hoping for, sorry for the drama : (

@JeremyRand
Copy link
Member

There are a few things I would suggest rewording.

"No need to extend the domain yourself" -- change "extend" to "renew"

Under disadvantages, I would replace the first one with the following list:

"The registrar could steal your domains if its operators are evil."
"The registrar may be a larger target for cyberattacks, and a successful attacker could steal your domains."
"The registrar could be pressured by a legal or extralegal attacker to hand over your domains."

Also add the following disadvantage to the end of the list:

"Registrars can charge substantially higher fees than you would pay by registering domains yourself."

@JeremyRand
Copy link
Member

Also, I would strongly suggest having this on bit.namecoin.info rather than www.namecoin.info since it's .bit-specific rather than general Namecoin use.

@phelixbtc
Copy link

I'm with Jeremy and Indolering in that this should go to the .bit site. Close?

@JeremyRand
Copy link
Member

@phelixbtc Can we keep this open until a PR is opened in the bit.namecoin.info repo? That way it's less likely that we (read: I) will forget about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants