Re: Upcoming Changes to News Server ... - Mailing list pgsql-general
From | Gary L. Burnore |
---|---|
Subject | Re: Upcoming Changes to News Server ... |
Date | |
Msg-id | 6.1.1.1.2.20041123205737.03a94420@popd.databasix.com Whole thread Raw |
In response to | Re: Upcoming Changes to News Server ... (Stephan Szabo <sszabo@megazone.bigpanda.com>) |
Responses |
Re: Upcoming Changes to News Server ...
|
List | pgsql-general |
At 11:56 PM 11/23/2004, Stephan Szabo wrote: >On Tue, 23 Nov 2004, Gary L. Burnore wrote: > > > At 07:47 PM 11/23/2004, terry@ashtonwoodshomes.com wrote: > > > > -----Original Message----- > > > > From: pgsql-general-owner@postgresql.org > > > > [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Jim Seymour > > > > Sent: Tuesday, November 23, 2004 5:18 PM > > > > To: pgsql-general@postgresql.org > > > > Subject: Re: [GENERAL] Upcoming Changes to News Server ... > > > > > > > > > > > > > > > > "Gary L. Burnore" <gburnore@databasix.com> wrote: > > > > > > > > > [snip] > > > > > > > > > > It's ok. Mysql's better anyway. > > > > > > > > Was that absolutely necessary? > > > > > >Was what necessary? (The cheap shot or the fact that he is ill > informed? :) > > > > > >For the record, I have both mysql and postgresql installations, and > > >postgresql, even without pgadmin > > >iii, is far superior in MANY ways to mysql. > > > > > > Many, maybe. Not all and certainly not more. Of course, ihat's my OPINION > > and I am quite well informed about databases, thankyouverymuch. > > > > I'm also well informed about running an NSP and what kind of mess Marc is > > now making and that's still the subject of the thread. > >I really wish you would give those of us that don't run an NSP more >information on this, because mostly you've said it's a mess or broken or >wrong without any additional information. Maybe this seems obvious to >you, but it isn't to most of the rest of us. > >I'm also trying to figure out which portions of what Marc is doing are at >what level of badness in your opinion. I think they're broken into the >following, but I may be misreading his message. > > Not sending mailing list posts to comp.databases.postgresql.*. > Leaving the groups on his server for incoming messages only. > Doing another hierarchy in order to provide groups on his own > server. > Asking if others wish to get that hierarchy. > Possibly confusing the issue if some (but not all) of the groups were > to be voted on and accepted. It appears that his aliiasing hasn't actually taken effect yet. Once it does, apparently things will be slightly better because he's then sending posts to pgsql.* not comp.databases.postgres.* . As of a short while ago, we were still receiving articles from the list. Now they show up in our unwanted.log file as groups we refuse to carry. (The same thing google did). We've removed all of the comp.databases.postgres.* groups from our server and our feeds anyway. Do did google. So will anyone else who's still holding the bogus groups. Basically, the thing that Marc is doing that's 'bad', is unilaterally making changes that effect your list without any discussion with those who it effects either ON the list or in USENet. USENet people tried to help and got a "we don't see it as broken from our side so who cares?" attitude. So now you'll have less places passing your posts along to the next NSP. Less propigation. I know of at least two, DataBasix and Google. I'm sure there are more. Marc's choice. Maybe not yours. But as he's already shown me, who cares?
pgsql-general by date: