<html><head></head><body>Would there be any negative impact from setting up a 301 back to https://www.noisebridge.net, you know, other then you having to do more work which requires finding coffee?<br>
<br>
<br>
--<br>
Rubin Abdi<br>
rubin@starset.net<br><br><div class="gmail_quote">Andy Isaacson <adi@hexapodia.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; ">On Sat, Feb 26, 2011 at 10:21:20PM -0800, Andy Isaacson wrote:
> On Sat, Feb 26, 2011 at 06:59:10PM -0800, Rubin Abdi wrote:
> > 20110226-185703 rubin110@corrode:~$ curl -v <a href="http://noisebridge.com">noisebridge.com</a>
> > * getaddrinfo(3) failed for <a href="noisebridge.com:80">noisebridge.com:80</a>
>
> I don't think <a href="http://noisebridge.com">noisebridge.com</a> or <a href="http://noisebridge.org">noisebridge.org</a> have ever resolved.
> Should they?
... which is to say, I was around when we registered .com and .org, and
AFAIK it was just to prevent domain squatters from grabbing them; and I help run the DNS servers, and I don't see any signs of any configuration having ever been done.
I suppose we could make them mirrors of .net, or use them for whatever else. We did specifically consider which TLD to use and decided to use
<a href="http://noisebridge.net">noisebridge.net</a> as our primary domain.
-andy
</pre></blockquote></div></body></html>