Discuss mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

Correct, nor should there be on the website.  The last thing we need is someone trolling for our email addresses so they can spam us.

However... at some point we may set up a method where admin info can be read from the ldap server.  More than likely the IRC names will correspond with the usernames selected in ldap, so the info could be grabbed as needed.

Generally, however, if you need to know who admins a server, ask in IRC.  Julian, brianko, or myself are usually around to look it up.

On 02/06/2013 09:15 PM, Jamyn Shanley wrote:

It's good information to have, but there are no email contacts listed in any of the results.

[...]

bbs: IRC=texnofobix

dyn: IRC=texnofobix

free: IRC=julian

fur: IRC=ph3-der-loewe

geek: IRC=julian

gopher: IRC=brianko

indy: IRC=julian

ing: IRC=timgws

micro: IRC=timgws

neo: IRC=neo

null: IRC=julian

oss: IRC=shdwdrgn

oz: ADMIN=Martin_C

parody: IRC=shdwdrgn

On Wed, Feb 6, 2013 at 9:08 PM, Jeff Taylor <shdwdrgn AT sourpuss.net> wrote:

If you're comfortable with the command line, you can also use this...

# dig +short TXT ns2.opennic.glue

It also works for TLDs...

# dig +short TXT free.opennic.glue

On 02/06/2013 05:18 PM, Jamyn Shanley wrote:

> Speaking of contact, may I suggest that all TLD operators get an alias or forwarder for their space as part of the process? Ex:
>

> oz AT tld.opennicproject.org <mailto:oz AT tld.opennicproject.org>
>
> ... and then the tld.opennicproject.org <http://tld.opennicproject.org> can list all available TLDs with contact information as well. Or whatever works for the group... but this way, there's a quick, easy, consistent, and memorable way to contact any operator, even if their infrastructure is down or you can't remember their gmail address off the top of your head..