csh
/
y.st.
forked from y.st./y.st.


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138
							<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2015 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2015/10-October/17.xhtml" />
		<title>...
	are some gTLDs actually within my reach? &lt;https://y.st./en/weblog/2015/10-October/17.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2015/10-October/17.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2015/10-October/16.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2015/10-October/18.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1>...
	are some <abbr title="generic top-level domain">gTLD</abbr>s actually within my reach?</h1>
			<p>Day 00224: Saturday, 2015 October 17</p>
		</header>
<p>
	Going back through the six domain registries that I thought did not ask for a telephone number, I found that not only did one of them ask for a telephone number, it <strong>*required*</strong> one.
	The issue was that I didn&apos;t notice that before registering the domain, you must register the domain contacts separately.
	Sadly, I&apos;ve had to downgrade the <a href="/en/URI_research/ccTLDs.xhtml#hm"><code>//hm.</code> registry</a> from being one of my most recommended six to being completely unusable.
	The other five do not appear to have this same issue, thankfully.
</p>
<p>
	I found at least three potentially-usable registries today, though due to a bit of excitement, I may have found others and forgotten them.
	None of the usable <abbr title="country code top-level domain">ccTLD</abbr>s were particularly noteworthy though.
	The <a href="/en/URI_research/usable_ccTLDs.xhtml#tg">Togolese Republic</a>, <a href="/en/URI_research/usable_ccTLDs.xhtml#vi">Virgin Islands of the United States</a>, and <a href="/en/URI_research/usable_ccTLDs.xhtml#co.ve">Bolivarian Republic of Venezuela</a> all ask for a telephone number and refuse to allow you to leave that field blank, but they allow you to enter strings saying that you do not have telephone service.
</p>
<p>
	The really interesting thing I found today was a registrar that also allows one to specify that he/she does not have a telephone number by setting the telephone number field to a non-telephone-number string.
	This registrar sells <code>//com.</code>, <code>//info.</code>, <code>//net.</code>, and <code>//org.</code> domains.
	This registrar&apos;s prices are comparatively high, and I don&apos;t know if they include <abbr title="Domain Name System">DNS</abbr> servers, but if I absolutely need to get a domain under a <abbr title="generic top-level domain">gTLD</abbr>, they could help me out.
	Unless I were to attempt to place an order, I can&apos;t be sure that the actual registries would accept the registration with a non-numeric telephone number value, but I really want to think that I&apos;ve found a place that allows such registration.
	More importantly, should I tell people about this discovery? If I don&apos;t tell anyone, than this discovery is of no value.
	I would be happier using a domain that allowed me to outright leave the telephone number field blank, or even better, did not ask me for a telephone number at all.
	On the other hand, if I tell people, than this potential loophole could get closed.
	Not only would <abbr title="Internet Assigned Numbers Authority">IANA</abbr> be upset that there is a way to register a name under a <abbr title="generic top-level domain">gTLD</abbr> and want to fix it, but there are also those that would directly oppose me and my goals.
	Some people feel I&apos;m childish for trying to escape the telephone number system and might want to through whatever obstetrical they can into my path.
	Other people are outright trolls and would see this as an opportunity to mess with me not because they even know who I am, but just because they <strong>*can*</strong> mess with me.
	I will keep the exact details of my discovery to myself for now while I think on this, only writing here that the discovery was made at all.
</p>
<p>
	I&apos;ve finished compiling my <abbr title="country code top-level domain">ccTLD</abbr> research, and will start the next phase tomorrow.
	I&apos;ve sorted out the usable <abbr title="country code top-level domain">ccTLD</abbr>s from the unusable, but continuing on, I only want to focus on the cream of the crop, the five most forward-thinking <abbr title="country code top-level domain">ccTLD</abbr> registries available.
	There&apos;s no point in further research on the unusable ones, and research is exhausting, so I&apos;d rather not pour a whole lot of energy into the lesser-but-still-usable registries either, especially right after having looked into every <abbr title="country code top-level domain">ccTLD</abbr> in existence.
</p>
<p>
	My Oregon tax return check arrived today, though not the tax return check from the <abbr title="Internal Revenue Service">IRS</abbr>.
	I had actually forgotten all about the tax return checks because I&apos;ve been busy, but maybe also because this is the wrong time of year to receive them.
</p>
<p>
	Malaria researchers may have discovered <a href="http://www.medicaldaily.com/malaria-parasite-cancer-cure-weve-been-looking-accidental-discovery-displays-357302">the beginnings of a new treatment for cancer</a>.
	I won&apos;t jump to conclusions and call it a cure just yet, but it&apos;s something to look forward to.
	My biggest fear though is that it will be pattented and horded instead of actually being used to help people.
</p>
<p>
	It seems that because <a href="http://wowana.me/">wowaname</a>&apos;s website is not accessible over <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> and mine is, attempting to connect to her website over <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> results in reaching my website on her domain.
	I hadn&apos;t really thought about the effects of her setting up <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> on her server for me, but I suppose that result makes sense.
	It would either be that or reaching her website on her domain using my certificate, assuming she didn&apos;t explicitly set up <abbr title="Hypertext Transfer Protocol Secure">HTTPS</abbr> service on her website to correct the anomaly.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
		<hr/>
		<p>
			Copyright © 2015 Alex Yst;
			You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F10-October%2F17.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F10-October%2F17.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>