<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">sword.pw = 8 characters<br>
sword.Bible = 11 characters<br>
crosswire.org = 13 characters<br>
crosswire.Bible = 15 characters<br>
<br>
See
<a class="moz-txt-link-freetext" href="http://www.nic.bible/blog/post/when-can-.bible-domain-names-be-registered#.VruHEnUrKho">http://www.nic.bible/blog/post/when-can-.bible-domain-names-be-registered#.VruHEnUrKho</a>
for registration opening information. You can preregister, now,
but actual registration for the general public starts at 10:00 AM
EST on March 8, 2016.<br>
<br>
I'm not too worried about blocks based on the TLD, although that
will probably happen in some places, because it is already
exceedingly easy to compile lists of Bible sites from search
engines, keyword scans, etc. Even Kalaam Media's coy names on
minority language Bible sites are but a very thin veil, easily
seen through. Some national-level censors are very sophisticated.
So, yes, this is an issue, but not a good reason to avoid .Bible
domain names, any more than I would avoid domain names like
eBible.org or Biblias.me. I just wouldn't go to .Bible names
exclusively. Besides, they are kind of pricey. Still, the fees
help support the American Bible Society, so I don't feel too bad
about that. National firewalls tend to be a bit porous, especially
when any sort of serious corporate use is allowed. Small leaks in
firewalls become torrents, so to speak, when data that is easy to
share comes through, even if it is hand carried.<br>
<br>
When I registered eBible.org, I could have had eBible.com and
eBible.net, too. They were all available.<br>
<br>
If you preregister sword.Bible and Crosswire.Bible at Epik.com,
chances are very good that you will get them on March 8, 2016.<br>
I just registered Sword.pw and set it to redirect to
crosswire.org. Feel free to use that URL where brevity is at a
premium, like on Twitter or in text messages. I think Sword.Bible
would be more memorable than Sword.pw, though.<br>
<br>
On 02/10/2016 01:05 AM, David Haslam wrote:<br>
</div>
<blockquote cite="mid:1455102348899-4656073.post@n4.nabble.com"
type="cite">
<pre wrap="">Thanks for the heads-up.
Were we to register and use, we'd end up having to use 6 more keys to type
the URL.
One thing for sure, the new TLD will be blocked by regimes hostile to the
Gospel of Christ.
Having such a TLD makes it easier to block than by examining content.
That could be a huge disadvantage should too many organisations jump on this
particular bandwagon.
Even so, it will have its uses.
David
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
<p><font color="#000000">Aloha,<br>
<i>Kahunapule Michael Johnson</i></font></p>
<table cellpadding="7" cellspacing="0">
<tbody>
<tr>
<td style="background: rgb(255, 255, 0)"><font
color="#000000"><b>MICHAEL JOHNSON<br>
PO BOX 881143<br>
PUKALANI HI 96788-1143</b><br>
USA</font></td>
<td style="background: rgb(0, 255, 255)"><font
color="#000000">
<a href="http://eBible.org">eBible.org</a><br>
<a href="http://MLJohnson.org">MLJohnson.org</a><br>
Mobile: +1 <b>808-333-6921</b><br>
Skype: kahunapule</font></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>