Re: Windows 10 newsgroup ?

[ps56k[_2_]]

"Big_Al" > wrote in message
...
> ps56k wrote on 2/12/2015 3:57 PM:
>> just wondering if a Windows 10 newsgroup
>> has been created on Usenet ?
>>
>>
> If you are using a reader, you can search in the box where you list and
> subscribe to groups, just put 10 or ten in and
> search for one of those.
>
> But to simplify things, the current one I see traffic in is:
> alt.comp.os.windows-10
>
tnx - got it -
wondering why the WIN7 group didn't do a "group create" in the same
structure ?

[Cecil Propes]

ps56k brought next idea :
> "Big_Al" > wrote in message
> ...
>> ps56k wrote on 2/12/2015 3:57 PM:
>>> just wondering if a Windows 10 newsgroup
>>> has been created on Usenet ?
>>>
>>>
>> If you are using a reader, you can search in the box where you list and
>> subscribe to groups, just put 10 or ten in and
>> search for one of those.
>>
>> But to simplify things, the current one I see traffic in is:
>> alt.comp.os.windows-10
>>
> tnx - got it -
> wondering why the WIN7 group didn't do a "group create" in the same structure
> ?

Why would they?

[Cecil Propes]

ps56k brought next idea :
> "Big_Al" > wrote in message
> ...
>> ps56k wrote on 2/12/2015 3:57 PM:
>>> just wondering if a Windows 10 newsgroup
>>> has been created on Usenet ?
>>>
>>>
>> If you are using a reader, you can search in the box where you list and
>> subscribe to groups, just put 10 or ten in and
>> search for one of those.
>>
>> But to simplify things, the current one I see traffic in is:
>> alt.comp.os.windows-10
>>
> tnx - got it -
> wondering why the WIN7 group didn't do a "group create" in the same structure
> ?

Why would they?

[VanguardLH[_2_]]

NOTE: ps56k changed the list of newsgroups *WITHOUT NOTICE*. Changing
newsgroups without notice is troll or rude behavior. He decided to
include the Windows 10 newsgroup on a completely separate issue that
should have been submitted ONLY to the Windows 10 newsgroup.

ps56k's original newsgroup list to ask where is Win10 newsgroup:
alt.comp.os.windows-8
alt.windows7.general
ps56k's newsgroup change only to address Win10 newgroup naming:
alt.comp.os.windows-8
alt.windows7.general
alt.comp.os.windows-10
My reply is only to on-topic newsgroup of:
alt.comp.os.windows-10

A problem with ps56k's change of newsgroups is that the Win10 newsgroup
may not and is likely not carried by a respondent's NNTP server. For
now, Eternal-September is the only one carrying that newsgroup. When a
respondent using a different NNTP server attempts to reply to ps56k's
changed newsgroups list, the respondent will get an error that no such
newsgroup existing on that respondent's injection server. Posts
specifying multiple newsgroups are submitted to only one NNTP server.
ps56k is using the ES server so his changed newsgroups list would
function okay, but not for non-ES respondents.


ps56k wrote:
<snipped the inquiry of where is Win10 newsgroup in other newsgroups>
> wondering why the WIN7 group didn't do a "group create" in the same
> structure ?

The Windows 7 newsgroup was created under the wrong hierachy; however,
the "alt" hierarchy is a mess as it is not regulated as under the Big-8
hierarchy; see http://en.wikipedia.org/wiki/Big_8_(Usenet). Not even
the microsoft.* newsgroups were part of the Big-8 hierarchy. For
consistency with prior use, the Windows 7 newsgroup should've been
placed under the alt.os or alt.comp.os hierarchies.

Just because a Usenet provider adds their own newsgroup does not mean it
will get peered to other Usenet providers. Some Usenet providers will
not carry a new newsgroup until it gets on ICS's approved list. This is
to eliminate the spurious and uncoordinated addition of newsgroups or
those with extremely narrow focus that duplicate the purpose of existing
newsgroups. At Giganews, their policy is:

http://www.giganews.com/support/usenet/
"How do I request that a newsgroup be added to Giganews?"

ISC's list is just for the Big-8 hierarchies. Giganews doesn't mention
what, if any, regulation they employ regarding what they carry in the
"alt" hierarchy.

Maybe one day this will get cleaned up to put the Windows newsgroups
under the Big-8 comp.os.ms-windows.* hierarchy but I suspect each
version of Windows will have long expired before any such correction is
made by Usenet providers. So we're stuck with the hodgepodge collection
of newsgroups scattered under the alt hierarchy. The "freedom" of the
alt hierarchy (see http://en.wikipedia.org/wiki/Alt.*_hierarchy) also
means it is a mess, and not all NNTP servers will carry them all. I did
not closely monitor the alt.config newsgroup to see if there really was
a discussion of where to add the Windows newsgroups under the alt
hierarchy but only recall a couple posts asking for their creation.
Most of the requests (not discussions) in alt.config seem to be
generated by just a couple trolls or often duplicate the purpose of
existing newsgroups because the requestors want a very narrowly defined
purpose for their "personal" newsgroup (i.e., only they or a couple
others would use such a narrow newsgroup).

Because Eternal-September added the Windows 10 newsgroup does not mean
that new-group request gets proliferated to other NNTP servers. If you
use or switch to another NNTP server, that newsgoup may not be there.

[VanguardLH[_2_]]

NOTE: ps56k changed the list of newsgroups *WITHOUT NOTICE*. Changing
newsgroups without notice is troll or rude behavior. He decided to
include the Windows 10 newsgroup on a completely separate issue that
should have been submitted ONLY to the Windows 10 newsgroup.

ps56k's original newsgroup list to ask where is Win10 newsgroup:
alt.comp.os.windows-8
alt.windows7.general
ps56k's newsgroup change only to address Win10 newgroup naming:
alt.comp.os.windows-8
alt.windows7.general
alt.comp.os.windows-10
My reply is only to on-topic newsgroup of:
alt.comp.os.windows-10

A problem with ps56k's change of newsgroups is that the Win10 newsgroup
may not and is likely not carried by a respondent's NNTP server. For
now, Eternal-September is the only one carrying that newsgroup. When a
respondent using a different NNTP server attempts to reply to ps56k's
changed newsgroups list, the respondent will get an error that no such
newsgroup existing on that respondent's injection server. Posts
specifying multiple newsgroups are submitted to only one NNTP server.
ps56k is using the ES server so his changed newsgroups list would
function okay, but not for non-ES respondents.


ps56k wrote:
<snipped the inquiry of where is Win10 newsgroup in other newsgroups>
> wondering why the WIN7 group didn't do a "group create" in the same
> structure ?

The Windows 7 newsgroup was created under the wrong hierachy; however,
the "alt" hierarchy is a mess as it is not regulated as under the Big-8
hierarchy; see http://en.wikipedia.org/wiki/Big_8_(Usenet). Not even
the microsoft.* newsgroups were part of the Big-8 hierarchy. For
consistency with prior use, the Windows 7 newsgroup should've been
placed under the alt.os or alt.comp.os hierarchies.

Just because a Usenet provider adds their own newsgroup does not mean it
will get peered to other Usenet providers. Some Usenet providers will
not carry a new newsgroup until it gets on ICS's approved list. This is
to eliminate the spurious and uncoordinated addition of newsgroups or
those with extremely narrow focus that duplicate the purpose of existing
newsgroups. At Giganews, their policy is:

http://www.giganews.com/support/usenet/
"How do I request that a newsgroup be added to Giganews?"

ISC's list is just for the Big-8 hierarchies. Giganews doesn't mention
what, if any, regulation they employ regarding what they carry in the
"alt" hierarchy.

Maybe one day this will get cleaned up to put the Windows newsgroups
under the Big-8 comp.os.ms-windows.* hierarchy but I suspect each
version of Windows will have long expired before any such correction is
made by Usenet providers. So we're stuck with the hodgepodge collection
of newsgroups scattered under the alt hierarchy. The "freedom" of the
alt hierarchy (see http://en.wikipedia.org/wiki/Alt.*_hierarchy) also
means it is a mess, and not all NNTP servers will carry them all. I did
not closely monitor the alt.config newsgroup to see if there really was
a discussion of where to add the Windows newsgroups under the alt
hierarchy but only recall a couple posts asking for their creation.
Most of the requests (not discussions) in alt.config seem to be
generated by just a couple trolls or often duplicate the purpose of
existing newsgroups because the requestors want a very narrowly defined
purpose for their "personal" newsgroup (i.e., only they or a couple
others would use such a narrow newsgroup).

Because Eternal-September added the Windows 10 newsgroup does not mean
that new-group request gets proliferated to other NNTP servers. If you
use or switch to another NNTP server, that newsgoup may not be there.

[Big_Al[_4_]]

ps56k wrote on 2/12/2015 4:24 PM:
> "Big_Al" > wrote in message
> ...
>> ps56k wrote on 2/12/2015 3:57 PM:
>>> just wondering if a Windows 10 newsgroup
>>> has been created on Usenet ?
>>>
>>>
>> If you are using a reader, you can search in the box where you list and
>> subscribe to groups, just put 10 or ten in and
>> search for one of those.
>>
>> But to simplify things, the current one I see traffic in is:
>> alt.comp.os.windows-10
>>
> tnx - got it -
> wondering why the WIN7 group didn't do a "group create" in the same
> structure ?
>
>
>
If you look at the groups for 7 8 and 10 7 is really the one out of sync.
alt.windows7.general
alt.comp.os.windows-8
alt.comp.os.windows-10

[Big_Al[_4_]]

ps56k wrote on 2/12/2015 4:24 PM:
> "Big_Al" > wrote in message
> ...
>> ps56k wrote on 2/12/2015 3:57 PM:
>>> just wondering if a Windows 10 newsgroup
>>> has been created on Usenet ?
>>>
>>>
>> If you are using a reader, you can search in the box where you list and
>> subscribe to groups, just put 10 or ten in and
>> search for one of those.
>>
>> But to simplify things, the current one I see traffic in is:
>> alt.comp.os.windows-10
>>
> tnx - got it -
> wondering why the WIN7 group didn't do a "group create" in the same
> structure ?
>
>
>
If you look at the groups for 7 8 and 10 7 is really the one out of sync.
alt.windows7.general
alt.comp.os.windows-8
alt.comp.os.windows-10

[Gene E. Bloch[_2_]]

On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:

> A problem with ps56k's change of newsgroups is that the Win10 newsgroup
> may not and is likely not carried by a respondent's NNTP server. For
> now, Eternal-September is the only one carrying that newsgroup.

I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
news.individual.net.

This doesn't quite invalidate your comment, it just corrects it.

I don't intend to look into any other servers to see if the NG is
present; maybe others who use them will pipe up.

--
Gene E. Bloch (Stumbling Bloch)

[Gene E. Bloch[_2_]]

On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:

> A problem with ps56k's change of newsgroups is that the Win10 newsgroup
> may not and is likely not carried by a respondent's NNTP server. For
> now, Eternal-September is the only one carrying that newsgroup.

I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
news.individual.net.

This doesn't quite invalidate your comment, it just corrects it.

I don't intend to look into any other servers to see if the NG is
present; maybe others who use them will pipe up.

--
Gene E. Bloch (Stumbling Bloch)

[Johnny]

On Fri, 13 Feb 2015 11:18:16 -0800
"Gene E. Bloch" > wrote:

> On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:
>
> > A problem with ps56k's change of newsgroups is that the Win10
> > newsgroup may not and is likely not carried by a respondent's NNTP
> > server. For now, Eternal-September is the only one carrying that
> > newsgroup.
>
> I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
> news.individual.net.
>
> This doesn't quite invalidate your comment, it just corrects it.
>
> I don't intend to look into any other servers to see if the NG is
> present; maybe others who use them will pipe up.
>

Albasani.net has the group.

[Johnny]

On Fri, 13 Feb 2015 11:18:16 -0800
"Gene E. Bloch" > wrote:

> On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:
>
> > A problem with ps56k's change of newsgroups is that the Win10
> > newsgroup may not and is likely not carried by a respondent's NNTP
> > server. For now, Eternal-September is the only one carrying that
> > newsgroup.
>
> I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
> news.individual.net.
>
> This doesn't quite invalidate your comment, it just corrects it.
>
> I don't intend to look into any other servers to see if the NG is
> present; maybe others who use them will pipe up.
>

Albasani.net has the group.

[Brian Gregory]

On 13/02/2015 05:36, VanguardLH wrote:
> NOTE: ps56k changed the list of newsgroups *WITHOUT NOTICE*. Changing
> newsgroups without notice is troll or rude behavior. He decided to
> include the Windows 10 newsgroup on a completely separate issue that
> should have been submitted ONLY to the Windows 10 newsgroup.
>
> ps56k's original newsgroup list to ask where is Win10 newsgroup:
> alt.comp.os.windows-8
> alt.windows7.general
> ps56k's newsgroup change only to address Win10 newgroup naming:
> alt.comp.os.windows-8
> alt.windows7.general
> alt.comp.os.windows-10
> My reply is only to on-topic newsgroup of:
> alt.comp.os.windows-10
>
> A problem with ps56k's change of newsgroups is that the Win10 newsgroup
> may not and is likely not carried by a respondent's NNTP server. For
> now, Eternal-September is the only one carrying that newsgroup. When a
> respondent using a different NNTP server attempts to reply to ps56k's
> changed newsgroups list, the respondent will get an error that no such
> newsgroup existing on that respondent's injection server. Posts
> specifying multiple newsgroups are submitted to only one NNTP server.
> ps56k is using the ES server so his changed newsgroups list would
> function okay, but not for non-ES respondents.
>
>
> ps56k wrote:
> <snipped the inquiry of where is Win10 newsgroup in other newsgroups>
>> wondering why the WIN7 group didn't do a "group create" in the same
>> structure ?
>
> The Windows 7 newsgroup was created under the wrong hierachy; however,
> the "alt" hierarchy is a mess as it is not regulated as under the Big-8
> hierarchy; see http://en.wikipedia.org/wiki/Big_8_(Usenet). Not even
> the microsoft.* newsgroups were part of the Big-8 hierarchy. For
> consistency with prior use, the Windows 7 newsgroup should've been
> placed under the alt.os or alt.comp.os hierarchies.
>
> Just because a Usenet provider adds their own newsgroup does not mean it
> will get peered to other Usenet providers. Some Usenet providers will
> not carry a new newsgroup until it gets on ICS's approved list. This is
> to eliminate the spurious and uncoordinated addition of newsgroups or
> those with extremely narrow focus that duplicate the purpose of existing
> newsgroups. At Giganews, their policy is:
>
> http://www.giganews.com/support/usenet/
> "How do I request that a newsgroup be added to Giganews?"
>
> ISC's list is just for the Big-8 hierarchies. Giganews doesn't mention
> what, if any, regulation they employ regarding what they carry in the
> "alt" hierarchy.
>
> Maybe one day this will get cleaned up to put the Windows newsgroups
> under the Big-8 comp.os.ms-windows.* hierarchy but I suspect each
> version of Windows will have long expired before any such correction is
> made by Usenet providers. So we're stuck with the hodgepodge collection
> of newsgroups scattered under the alt hierarchy. The "freedom" of the
> alt hierarchy (see http://en.wikipedia.org/wiki/Alt.*_hierarchy) also
> means it is a mess, and not all NNTP servers will carry them all. I did
> not closely monitor the alt.config newsgroup to see if there really was
> a discussion of where to add the Windows newsgroups under the alt
> hierarchy but only recall a couple posts asking for their creation.
> Most of the requests (not discussions) in alt.config seem to be
> generated by just a couple trolls or often duplicate the purpose of
> existing newsgroups because the requestors want a very narrowly defined
> purpose for their "personal" newsgroup (i.e., only they or a couple
> others would use such a narrow newsgroup).
>
> Because Eternal-September added the Windows 10 newsgroup does not mean
> that new-group request gets proliferated to other NNTP servers. If you
> use or switch to another NNTP server, that newsgoup may not be there.
>

alt.comp.os.windows-10 is on Giganews.

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

[Brian Gregory]

On 13/02/2015 05:36, VanguardLH wrote:
> NOTE: ps56k changed the list of newsgroups *WITHOUT NOTICE*. Changing
> newsgroups without notice is troll or rude behavior. He decided to
> include the Windows 10 newsgroup on a completely separate issue that
> should have been submitted ONLY to the Windows 10 newsgroup.
>
> ps56k's original newsgroup list to ask where is Win10 newsgroup:
> alt.comp.os.windows-8
> alt.windows7.general
> ps56k's newsgroup change only to address Win10 newgroup naming:
> alt.comp.os.windows-8
> alt.windows7.general
> alt.comp.os.windows-10
> My reply is only to on-topic newsgroup of:
> alt.comp.os.windows-10
>
> A problem with ps56k's change of newsgroups is that the Win10 newsgroup
> may not and is likely not carried by a respondent's NNTP server. For
> now, Eternal-September is the only one carrying that newsgroup. When a
> respondent using a different NNTP server attempts to reply to ps56k's
> changed newsgroups list, the respondent will get an error that no such
> newsgroup existing on that respondent's injection server. Posts
> specifying multiple newsgroups are submitted to only one NNTP server.
> ps56k is using the ES server so his changed newsgroups list would
> function okay, but not for non-ES respondents.
>
>
> ps56k wrote:
> <snipped the inquiry of where is Win10 newsgroup in other newsgroups>
>> wondering why the WIN7 group didn't do a "group create" in the same
>> structure ?
>
> The Windows 7 newsgroup was created under the wrong hierachy; however,
> the "alt" hierarchy is a mess as it is not regulated as under the Big-8
> hierarchy; see http://en.wikipedia.org/wiki/Big_8_(Usenet). Not even
> the microsoft.* newsgroups were part of the Big-8 hierarchy. For
> consistency with prior use, the Windows 7 newsgroup should've been
> placed under the alt.os or alt.comp.os hierarchies.
>
> Just because a Usenet provider adds their own newsgroup does not mean it
> will get peered to other Usenet providers. Some Usenet providers will
> not carry a new newsgroup until it gets on ICS's approved list. This is
> to eliminate the spurious and uncoordinated addition of newsgroups or
> those with extremely narrow focus that duplicate the purpose of existing
> newsgroups. At Giganews, their policy is:
>
> http://www.giganews.com/support/usenet/
> "How do I request that a newsgroup be added to Giganews?"
>
> ISC's list is just for the Big-8 hierarchies. Giganews doesn't mention
> what, if any, regulation they employ regarding what they carry in the
> "alt" hierarchy.
>
> Maybe one day this will get cleaned up to put the Windows newsgroups
> under the Big-8 comp.os.ms-windows.* hierarchy but I suspect each
> version of Windows will have long expired before any such correction is
> made by Usenet providers. So we're stuck with the hodgepodge collection
> of newsgroups scattered under the alt hierarchy. The "freedom" of the
> alt hierarchy (see http://en.wikipedia.org/wiki/Alt.*_hierarchy) also
> means it is a mess, and not all NNTP servers will carry them all. I did
> not closely monitor the alt.config newsgroup to see if there really was
> a discussion of where to add the Windows newsgroups under the alt
> hierarchy but only recall a couple posts asking for their creation.
> Most of the requests (not discussions) in alt.config seem to be
> generated by just a couple trolls or often duplicate the purpose of
> existing newsgroups because the requestors want a very narrowly defined
> purpose for their "personal" newsgroup (i.e., only they or a couple
> others would use such a narrow newsgroup).
>
> Because Eternal-September added the Windows 10 newsgroup does not mean
> that new-group request gets proliferated to other NNTP servers. If you
> use or switch to another NNTP server, that newsgoup may not be there.
>

alt.comp.os.windows-10 is on Giganews.

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

[Justin Tyme[_2_]]

On Fri, 13 Feb 2015 11:18:16 -0800, "Gene E. Bloch"
> wrote:

>On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:
>
>> A problem with ps56k's change of newsgroups is that the Win10 newsgroup
>> may not and is likely not carried by a respondent's NNTP server. For
>> now, Eternal-September is the only one carrying that newsgroup.
>
>I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
>news.individual.net.
>
>This doesn't quite invalidate your comment, it just corrects it.
>
>I don't intend to look into any other servers to see if the NG is
>present; maybe others who use them will pipe up.

Astraweb has recently added this group to their list.
--
JT

[Justin Tyme[_2_]]

On Fri, 13 Feb 2015 11:18:16 -0800, "Gene E. Bloch"
> wrote:

>On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:
>
>> A problem with ps56k's change of newsgroups is that the Win10 newsgroup
>> may not and is likely not carried by a respondent's NNTP server. For
>> now, Eternal-September is the only one carrying that newsgroup.
>
>I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
>news.individual.net.
>
>This doesn't quite invalidate your comment, it just corrects it.
>
>I don't intend to look into any other servers to see if the NG is
>present; maybe others who use them will pipe up.

Astraweb has recently added this group to their list.
--
JT

[gram pappy]

"Gene E. Bloch" > wrote in message
...
> On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:
>
>> A problem with ps56k's change of newsgroups is that the Win10
>> newsgroup
>> may not and is likely not carried by a respondent's NNTP server. For
>> now, Eternal-September is the only one carrying that newsgroup.
>
> I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
> news.individual.net.
>
> This doesn't quite invalidate your comment, it just corrects it.
>
> I don't intend to look into any other servers to see if the NG is
> present; maybe others who use them will pipe up.
>
> --
> Gene E. Bloch (Stumbling Bloch)

alt.comp.os.windows-10 also on Aioe.org

gram pappy

[gram pappy]

"Gene E. Bloch" > wrote in message
...
> On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:
>
>> A problem with ps56k's change of newsgroups is that the Win10
>> newsgroup
>> may not and is likely not carried by a respondent's NNTP server. For
>> now, Eternal-September is the only one carrying that newsgroup.
>
> I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
> news.individual.net.
>
> This doesn't quite invalidate your comment, it just corrects it.
>
> I don't intend to look into any other servers to see if the NG is
> present; maybe others who use them will pipe up.
>
> --
> Gene E. Bloch (Stumbling Bloch)

alt.comp.os.windows-10 also on Aioe.org

gram pappy

[VanguardLH[_2_]]

Johnny wrote:

> "Gene E. Bloch" wrote:
>
>> VanguardLH wrote:
>>
>>> A problem with ps56k's change of newsgroups is that the Win10
>>> newsgroup may not and is likely not carried by a respondent's NNTP
>>> server. For now, Eternal-September is the only one carrying that
>>> newsgroup.
>>
>> I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
>> news.individual.net.
>>
>> This doesn't quite invalidate your comment, it just corrects it.
>
> Albasani.net has the group.

After ES added the Win10 newsgroup, yes, eventually it showed up at
Albasani but it took a LONG time for that to happen. Despite that I
normally use Albasani, I had to subscribed to the Win10 newsgroup using
my ES account because it wasn't at Albasani (how long it took to show up
I wouldn't know). For quite awhile, the only place to find the Win10
newsgroup was on the ES server. After Ray added it to ES, it sure took
a lot longer for the newsgroup to propagate to other NNTP servers than
could be accounted by normal new group requests.

Now that the Win10 newsgroup showed up on Albasani, I can choose to
visit that newsgroup using Albasani. Thanks for the update.

[VanguardLH[_2_]]

Brian Gregory wrote:

> VanguardLH wrote:
>
>> Because Eternal-September added the Windows 10 newsgroup does not mean
>> that new-group request gets proliferated to other NNTP servers. If you
>> use or switch to another NNTP server, that newsgoup may not be there.
>
> alt.comp.os.windows-10 is on Giganews.

Ah, it finally made it there. Know when Giganews finally decided to get
around to adding it?

[John Szalay]

VanguardLH > wrote in :

> Brian Gregory wrote:
>
>> VanguardLH wrote:
>>
>>> Because Eternal-September added the Windows 10 newsgroup does not mean
>>> that new-group request gets proliferated to other NNTP servers. If you
>>> use or switch to another NNTP server, that newsgoup may not be there.
>>
>> alt.comp.os.windows-10 is on Giganews.
>
> Ah, it finally made it there. Know when Giganews finally decided to get
> around to adding it?
>

I show Nov 3rd as when it first appeared on giganews

[R. C. White]

Hi, Vanguard.

My ISP (Grande Communications, Inc., here in San Marcos, TX) bundles its NSP
(news.grandecom.net) using Giganews. It has been carrying
alt.comp.os.windows-10 for several months, since November 2014, at least.

Of course, that doesn't do you or Brian any good, but others here might live
within reach of Grande.

RC
--
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP (2002-2010)
Windows Live Mail 2012 (Build 16.4.3528.0331) in Win8.1 Pro w/Media Center


"VanguardLH" wrote in message ...

Brian Gregory wrote:

> VanguardLH wrote:
>
>> Because Eternal-September added the Windows 10 newsgroup does not mean
>> that new-group request gets proliferated to other NNTP servers. If you
>> use or switch to another NNTP server, that newsgoup may not be there.
>
> alt.comp.os.windows-10 is on Giganews.

Ah, it finally made it there. Know when Giganews finally decided to get
around to adding it?

[Brian Gregory]

On 14/02/2015 18:17, VanguardLH wrote:
> Brian Gregory wrote:
>
>> VanguardLH wrote:
>>
>>> Because Eternal-September added the Windows 10 newsgroup does not mean
>>> that new-group request gets proliferated to other NNTP servers. If you
>>> use or switch to another NNTP server, that newsgoup may not be there.
>>
>> alt.comp.os.windows-10 is on Giganews.
>
> Ah, it finally made it there. Know when Giganews finally decided to get
> around to adding it?
>

Around the middle of November I think.

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

[Brian Gregory]

On 15/02/2015 09:42, Brian Gregory wrote:
> On 14/02/2015 18:17, VanguardLH wrote:
>> Brian Gregory wrote:
>>
>>> VanguardLH wrote:
>>>
>>>> Because Eternal-September added the Windows 10 newsgroup does not mean
>>>> that new-group request gets proliferated to other NNTP servers. If you
>>>> use or switch to another NNTP server, that newsgoup may not be there.
>>>
>>> alt.comp.os.windows-10 is on Giganews.
>>
>> Ah, it finally made it there. Know when Giganews finally decided to get
>> around to adding it?
>>
>
> Around the middle of November I think.
>

FWIW I asked them to add it on November 2nd (in giganews.newsgroups).

--

Brian Gregory (in the UK).
To email me please remove all the letter vee from my email address.

[Char Jackson]

On Fri, 13 Feb 2015 11:18:16 -0800, "Gene E. Bloch" >
wrote:

>On Thu, 12 Feb 2015 23:36:09 -0600, VanguardLH wrote:
>
>> A problem with ps56k's change of newsgroups is that the Win10 newsgroup
>> may not and is likely not carried by a respondent's NNTP server. For
>> now, Eternal-September is the only one carrying that newsgroup.
>
>I don't use E-S; I'm reading your post in alt.comp.os.windows-10 on
>news.individual.net.
>
>This doesn't quite invalidate your comment, it just corrects it.
>
>I don't intend to look into any other servers to see if the NG is
>present; maybe others who use them will pipe up.

I see it on AstraWeb (as someone else already mentioned) as well as the
Highwinds Group of NSPs: Easynews, Usenetserver, Newshosting, and possibly
others in the HWG family.