Gnus development mailing list
 help / color / mirror / Atom feed
From: "Robin S. Socha" <robin@socha.net>
Subject: Re: Domain name for that Gnus stuff on socha,net
Date: 06 Apr 2001 08:14:27 +0200	[thread overview]
Message-ID: <deathsquad.m3k84yv9ks.fsf@socha.net> (raw)
In-Reply-To: <87n19uj0bs.fsf@inanna.rimspace.net> (Daniel Pittman's message of "06 Apr 2001 11:15:03 +1000")

* Daniel Pittman <daniel@rimspace.net> writes:
> On 05 Apr 2001, Lars Magne Ingebrigtsen wrote:

>> We need a domain name for the tutorials-and-stuff thing.
>> news.gnus.org is taken, so...  er... resources.gnus.org?
>>
>> Anybody?

> Isn't, er, `www.gnus.org' or `gnus.org' the place most people are
> going to look for this?

Well, there's somethings to consider.

* gnus.org is functional and looks quite nice for the most part.
* gnus.org is perfectly well browsable with lynx. socha.net is definitly
  not (it works OK with w3m and w3, though ;-)).
* gnus.org loads fast. Although socha.net's connectivity is probably as
  good as it gets, the PHP news engine behind it is (for the time being)
  rather slow.
* quimby at least is in a company DMZ. socha.net is not. If socha.net is
  broken into, that's bad luck (and taking into consideration PHP's
  history, it's not all that unlikely, OpenBSD or not...).

Therefore I fully agree with Lars that what's there should stay there.

> I know I would and I grok this new-fangled "there is more than one
> server in a domain" idea that causes so much trouble for many Internet
> users with their shiny new AOL account...

I don't see the problem, really. If you want gnus, you'll get it at
gnus.org. If you wanted resources, you had to go the gnus.org/resouces/
(IIRC), anyway. No difference.

> Anyway, if it /must/ be a distinct machine, I don't know that many
> people care (and `resources' is probably a good bet) 

I think it's ok, too. "community" might also work.

> - because you will have a link of `gnus.org', wont you?

<Directory /var/www/htdocs/gnus/>
Redirect /resources/ http://resources.gnus.org/
</Directory>

Insert mod_rewrite at will. Any further questions? ;-)
-- 
Robin S. Socha, Bastard Consultant From Hell <http://socha.net/>
Note to experienced users: Please don't encourage anti-support behavior.
Don't try to answer questions from users who don't provide the necessary
information. Guessing what they did is an incredible waste of time. (DJB)


  reply	other threads:[~2001-04-06  6:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-05 20:27 Lars Magne Ingebrigtsen
2001-04-06  1:15 ` Daniel Pittman
2001-04-06  6:14   ` Robin S. Socha [this message]
2001-04-06 17:17     ` Amos Gouaux
2001-04-06 21:17       ` Kai Großjohann
2001-04-10 16:18     ` Jason R. Mastaler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=deathsquad.m3k84yv9ks.fsf@socha.net \
    --to=robin@socha.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).