Cross-posting etiquette

[Dan]

Hello,

One more x-post and then I promise I’ll stop …

Can someone set the record straight what is the right etiquette in regards
to inn.qnx.com newsgroups.

First, though, what is wrong with x-posting? For example I’m porting an
existing app and have a problem with gcc and tempates on QNX6, why shouldn’t
I be allowed to post it across a number of ngs, eg

qdn.public.porting (I’m porting existing code)
qdn.public.qnxrtp.devtools (gcc)
comp.lang.c++ (templates & c++)

and a couple more general ones (still relevant though) to get more hits.
Provided I’m not x-posting from alt.binaries what is the issue?

I have no idea how ng server is organised. Is the problem a technical one or
ergonomic one - having to strain your eyes ove the same thread in another
group…?

Or lets try a democratic process. Who wants to retain x-posting? (I won’t
sue anyone even if I lose by 200 votes, no, even 1 vote).

Dan

[dzm]

I vote for “retain x-posting”.

Dzulbokhari

Dan wrote:

Hello,

One more x-post and then I promise I’ll stop …

Can someone set the record straight what is the right etiquette in regards
to inn.qnx.com newsgroups.

First, though, what is wrong with x-posting? For example I’m porting an
existing app and have a problem with gcc and tempates on QNX6, why shouldn’t
I be allowed to post it across a number of ngs, eg

qdn.public.porting (I’m porting existing code)
qdn.public.qnxrtp.devtools (gcc)
comp.lang.c++ (templates & c++)

and a couple more general ones (still relevant though) to get more hits.
Provided I’m not x-posting from alt.binaries what is the issue?

I have no idea how ng server is organised. Is the problem a technical one or
ergonomic one - having to strain your eyes ove the same thread in another
group…?

Or lets try a democratic process. Who wants to retain x-posting? (I won’t
sue anyone even if I lose by 200 votes, no, even 1 vote).

Dan

[Warren_Peece1]

Well, my opinion would be that I find it annoying to read the same post in two
or three different newsgroups “ON INN.QNX.COM”. I can see where you may want
to post something on QDN, and on qnxstart.com, and comp.lang.c++ or whatnot,
and I think that’s fine. But asking in qdn.public.{news,porting,os,devtools}
sucks. QNX has people that follow these newsgroups pretty closely, and
although they may occasionally overlook a post by accident, they’re pretty good
about helping people out and there’s really no need to ask the same question 4
times because it just makes it difficult to tell who has been helped and who
hasn’t. I vote nuke the cross-posting on inn.qnx.com, and vive` le x-post
(pardon my pseudo-French) everywhere else. I see cross-posting on QDN to be a
form of SPAM… Mass-advertising to “get more hits” as it were.

Now let’s demand a re-count until I get what I want. But can we only count the
votes I want to count?

-Warren


“Dan” <none@no.spam> wrote in message news:8v1qdo$1tt$1@inn.qnx.com…
| Hello,
|
| One more x-post and then I promise I’ll stop …
|
| Can someone set the record straight what is the right etiquette in regards
| to inn.qnx.com newsgroups.
|
| First, though, what is wrong with x-posting? For example I’m porting an
| existing app and have a problem with gcc and tempates on QNX6, why shouldn’t
| I be allowed to post it across a number of ngs, eg
|
| qdn.public.porting (I’m porting existing code)
| qdn.public.qnxrtp.devtools (gcc)
| comp.lang.c++ (templates & c++)
|
| and a couple more general ones (still relevant though) to get more hits.
| Provided I’m not x-posting from alt.binaries what is the issue?
|
| I have no idea how ng server is organised. Is the problem a technical one or
| ergonomic one - having to strain your eyes ove the same thread in another
| group…?
|
| Or lets try a democratic process. Who wants to retain x-posting? (I won’t
| sue anyone even if I lose by 200 votes, no, even 1 vote).
|
| Dan
|
|
|
|

[Thomas_Hentschel]

Not that I’m advertising x-posting, but it should be allowed reasonably.
Maybe a decent news client, which filters x-posts for you could help?

In case of a recount, lets also include comp.lang.* and comp.os.*

-Th

Warren Peece wrote:

Well, my opinion would be that I find it annoying to read the same post in two
or three different newsgroups “ON INN.QNX.COM”. I can see where you may want
to post something on QDN, and on qnxstart.com, and comp.lang.c++ or whatnot,
and I think that’s fine. But asking in qdn.public.{news,porting,os,devtools}
sucks. QNX has people that follow these newsgroups pretty closely, and
although they may occasionally overlook a post by accident, they’re pretty good
about helping people out and there’s really no need to ask the same question 4
times because it just makes it difficult to tell who has been helped and who
hasn’t. I vote nuke the cross-posting on inn.qnx.com, and vive` le x-post
(pardon my pseudo-French) everywhere else. I see cross-posting on QDN to be a
form of SPAM… Mass-advertising to “get more hits” as it were.

Now let’s demand a re-count until I get what I want. But can we only count the
votes I want to count? >

-Warren

“Dan” <> none@no.spam> > wrote in message news:8v1qdo$1tt$> 1@inn.qnx.com> …
| Hello,
|
| One more x-post and then I promise I’ll stop …
|
| Can someone set the record straight what is the right etiquette in regards
| to inn.qnx.com newsgroups.
|
| First, though, what is wrong with x-posting? For example I’m porting an
| existing app and have a problem with gcc and tempates on QNX6, why shouldn’t
| I be allowed to post it across a number of ngs, eg
|
| qdn.public.porting (I’m porting existing code)
| qdn.public.qnxrtp.devtools (gcc)
| comp.lang.c++ (templates & c++)
|
| and a couple more general ones (still relevant though) to get more hits.
| Provided I’m not x-posting from alt.binaries what is the issue?
|
| I have no idea how ng server is organised. Is the problem a technical one or
| ergonomic one - having to strain your eyes ove the same thread in another
| group…?
|
| Or lets try a democratic process. Who wants to retain x-posting? (I won’t
| sue anyone even if I lose by 200 votes, no, even 1 vote).
|
| Dan
|
|
|
|

[Armin_Steinhoff1]

Warren Peece wrote:

Well, my opinion would be that I find it annoying to read the same post in two
or three different newsgroups “ON INN.QNX.COM”.

A good news reader marks the cross posted message
in all targeted groups after reading one of it …
that happens at least if you are using the news
reader of Netscape.

Armin

[Armin_Steinhoff1]

Dan wrote:

Hello,

One more x-post and then I promise I’ll stop …

Can someone set the record straight what is the right etiquette in regards
to inn.qnx.com newsgroups.

First, though, what is wrong with x-posting? For example I’m porting an
existing app and have a problem with gcc and tempates on QNX6, why shouldn’t
I be allowed to post it across a number of ngs, eg

qdn.public.porting (I’m porting existing code)
qdn.public.qnxrtp.devtools (gcc)
comp.lang.c++ (templates & c++)

You can minimize the ‘noise’ produced by replys if
you choose one of these groups
as the Reply-To group.

Armin

[Armin_Steinhoff1]

Armin Steinhoff wrote:

Dan wrote:

Hello,

One more x-post and then I promise I’ll stop …

Can someone set the record straight what is the right etiquette in regards
to inn.qnx.com newsgroups.

First, though, what is wrong with x-posting? For example I’m porting an
existing app and have a problem with gcc and tempates on QNX6, why shouldn’t
I be allowed to post it across a number of ngs, eg

qdn.public.porting (I’m porting existing code)
qdn.public.qnxrtp.devtools (gcc)
comp.lang.c++ (templates & c++)

You can minimize the ‘noise’ produced by replys if
you choose one of these groups
as the Reply-To group.

Sorry … that’s wrong. It must be the Followup-To
group …

Armin

Armin

[system]

In qdn.public.porting Armin Steinhoff <A-Steinhoff@web_.de> wrote:

We have always had a policy of asking our senior developers to monitor
the newsgroups and answer questions. This was generally a matter of each
of them spending half an hour a day going through the groups and looking for
issues that fall into their area of responsibility.

Cross posting increases the number of messages, and requires a bit more
thought on the part of the senior developers to mentally filter out cross
posts, and if they need to go back and provide further feedback in finding
which of the cross posted posts was turned into an actual thread. The amount
of time it takes to go through the newsgroups has increased lately, partly
due to the newness of RTP and a high number of new users, but also partly due
to more cross posting.

Our policy is now that monitoring the newsgroups is optional for senior
developers and that issues that need to be addressed by them will be bought
to their attention by tech support people.

Most of the senior developers are still monitoring the newsgroups, but if
the signal to noise ratio becomes too low (due to cross posting or too much
`advocacy’ type non-technical content), the quality of responses you get
here will become diluted over time as the senior people simply tune out.

I think that if you are tempted to cross post because it’s too difficult to
categorize your issue into one of the existing groups, suggest a new group
on the advocacy channel.

If you are tempted to cross post because you think it will get you more
attention, make sure that the issue is really worth cross posting.

And people who cross post at the drop of a hat will quickly become the boy
who cried wolf in the minds of most of the developers here.

[Paul_Russell]

I hate cross posting within qdn.** and comp.os.qnx
as I can’t properly follow the answer threads…

If separate streams of answers start up in each group,
how can you follow it to a clean conclusion?

I vote to block cross-posting.

I’d also like to see comp.os.qnx split into comp.os.qnx.qnx4 comp.os.qnx.qnxrtp
and the old comp.os.qnx blocked from new messages, but reatined for searches (via dejanews)
-Paul


Armin Steinhoff <A-Steinhoff@web_.de> wrote in message news:3A152166.A7513A45@web_.de…

Warren Peece wrote:

Well, my opinion would be that I find it annoying to read the same post in two
or three different newsgroups “ON INN.QNX.COM”.

A good news reader marks the cross posted message
in all targeted groups after reading one of it …
that happens at least if you are using the news
reader of Netscape.

Armin

[system]

In qdn.public.porting Paul Russell <paul@jenosys.com> wrote:

I’d also like to see comp.os.qnx split into comp.os.qnx.qnx4 comp.os.qnx.qnxrtp
and the old comp.os.qnx blocked from new messages, but reatined for searches (via dejanews)
-Paul

All of the comp.os.??? newsgroups are true USENET newsgroups. They are
not created or administered by us, but by interested users.

I’m not sure either if policy has changed, but it’s generally frowned
upon for those newsgroups to be used as advertising or tech support
channels by commercial entities.

Many of the developers here do not even monitor comp.os.qnx for that
last reason.

If you have an important issue that you would like to get an official
response from us on, post it to one of the qdn newsgroups.

[Warren_Peece1]

<pete@qnx.com> wrote in message news:8v49st$fsc$1@nntp.qnx.com…

| If you have an important issue that you would like to get an official
| response from us on, post it to one of the qdn newsgroups.

See!? He said ONE of the newsgroups! Nuke cross-posting!

-Warren

[kiwiunixman]

If it is band (I will be very happy if it is) then a new news group will
have to be opened, qdn.public.support.xpa (x-posting anonymous) to help
x posting addicts get over their addiction.

kiwiunixman

Dan wrote:

Hello,

One more x-post and then I promise I’ll stop …

Can someone set the record straight what is the right etiquette in regards
to inn.qnx.com newsgroups.

First, though, what is wrong with x-posting? For example I’m porting an
existing app and have a problem with gcc and tempates on QNX6, why shouldn’t
I be allowed to post it across a number of ngs, eg

qdn.public.porting (I’m porting existing code)
qdn.public.qnxrtp.devtools (gcc)
comp.lang.c++ (templates & c++)

and a couple more general ones (still relevant though) to get more hits.
Provided I’m not x-posting from alt.binaries what is the issue?

I have no idea how ng server is organised. Is the problem a technical one or
ergonomic one - having to strain your eyes ove the same thread in another
group…?

Or lets try a democratic process. Who wants to retain x-posting? (I won’t
sue anyone even if I lose by 200 votes, no, even 1 vote).

Dan

[system]

In comp.os.qnx Paul Russell <paul@jenosys.com> wrote:

I hate cross posting within qdn.** and comp.os.qnx
as I can’t properly follow the answer threads…

If separate streams of answers start up in each group,
how can you follow it to a clean conclusion?

I vote to block cross-posting.

How about I just remove access to comp.os.qnx on the inn.qnx.com server? That
should clear up the muddy waters. Then everything is qdn.public.* As pete
stated, we do not control comp.os.qnx – as it is part of the USENET “Big 8”

I’d also like to see comp.os.qnx split into comp.os.qnx.qnx4 comp.os.qnx.qnxrtp
and the old comp.os.qnx blocked from new messages, but reatined for searches (via dejanews)
-Paul

–
Joe Bishop (joe@qnx.com)

[Carlos_Clarke1]

On 27 Nov 2000 16:00:10 GMT, joe@qnx.com wrote:

In comp.os.qnx Paul Russell <> paul@jenosys.com> > wrote:
I hate cross posting within qdn.** and comp.os.qnx
as I can’t properly follow the answer threads…

If separate streams of answers start up in each group,
how can you follow it to a clean conclusion?

I vote to block cross-posting.

How about I just remove access to comp.os.qnx on the inn.qnx.com server? That
should clear up the muddy waters. Then everything is qdn.public.* As pete
stated, we do not control comp.os.qnx – as it is part of the USENET “Big 8”

Please don’t do that. It is much easier to keep track of all my QNX
newsgroups by going to one place.

I’d also like to see comp.os.qnx split into comp.os.qnx.qnx4 comp.os.qnx.qnxrtp
and the old comp.os.qnx blocked from new messages, but reatined for searches (via dejanews)
-Paul