Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
cmsg newgroup free.snipe
2 views
Skip to first unread message
Sn!pe
Apr 21, 2021, 7:49:26 PM4/21/21
to
For your newsgroups file:
free.snipe Release the wading bird.
--
^Ï^ <https://youtu.be/_kqytf31a8E>
My pet rock Gordon just is.
free.snipe Release the wading bird.
--
^Ï^ <https://youtu.be/_kqytf31a8E>
My pet rock Gordon just is.
Adam H. Kerman
Apr 21, 2021, 8:07:24 PM4/21/21
to
You know I'm contractually obligated to make fun of you for this, right?
No tab, no Control header, no charter
Luck with the vanity froup. No one posts to any of my froups o' haet.
No tab, no Control header, no charter
Luck with the vanity froup. No one posts to any of my froups o' haet.
Sn!pe
Apr 21, 2021, 8:58:05 PM4/21/21
to
Thanks for the pointers, Adam. My previous effort succeeded,
I must take a closer look to see what I did last time.
Adam H. Kerman
Apr 21, 2021, 10:51:55 PM4/21/21
to
Sn!pe <snip...@gmail.com> wrote:
>Adam H. Kerman <a...@chinet.com> wrote:
>>Sn!pe <snip...@gmail.com> wrote:
>>>For your newsgroups file:
>>>free.snipe Release the wading bird.
>>You know I'm contractually obligated to make fun of you for this, right?
>>No tab, no Control header, no charter
>>Luck with the vanity froup. No one posts to any of my froups o' haet.
>Bah! Colour me embarrassed.
>Thanks for the pointers, Adam. My previous effort succeeded,
>I must take a closer look to see what I did last time.
Newsgroups: free.snipe (send it only to the group being newgrouped)
>Adam H. Kerman <a...@chinet.com> wrote:
>>Sn!pe <snip...@gmail.com> wrote:
>>>For your newsgroups file:
>>>free.snipe Release the wading bird.
>>You know I'm contractually obligated to make fun of you for this, right?
>>No tab, no Control header, no charter
>>Luck with the vanity froup. No one posts to any of my froups o' haet.
>Bah! Colour me embarrassed.
>Thanks for the pointers, Adam. My previous effort succeeded,
>I must take a closer look to see what I did last time.
Control: newgroup free.snipe
Approved: your email address
Subject: cmsg newgroup free.snipe (no longer a command but tradition)
For your newsgroups file:
free.snipe<tab character>Release the wading bird.
Charter:
whatever your suggestions are for on topic discussion
Sn!pe
Apr 22, 2021, 8:53:36 AM4/22/21
to
Adam H. Kerman
Apr 22, 2021, 12:24:54 PM4/22/21
to
^
Not a tab character; your composer isn't entering one
Can you enter it directly with the character code?
It's probably not going to prevent it from being appended to the
newsgroups file on most servers that create it.
>Charter:
>Dedicated to all who probe the boggy, marshy places of Usenet in search
>of things to eat.
>--
>^Ï^ <https://youtu.be/_kqytf31a8E>
^
You've got a UTF-8 character in your sigfile but your MIME header says
ISO-8859-1. I didn't notice that earlier.
Not a tab character; your composer isn't entering one
Can you enter it directly with the character code?
It's probably not going to prevent it from being appended to the
newsgroups file on most servers that create it.
>Charter:
>Dedicated to all who probe the boggy, marshy places of Usenet in search
>of things to eat.
>--
>^Ï^ <https://youtu.be/_kqytf31a8E>
^
You've got a UTF-8 character in your sigfile but your MIME header says
ISO-8859-1. I didn't notice that earlier.
Sn!pe
Apr 22, 2021, 1:47:28 PM4/22/21
to
> Sn!pe <snip...@gmail.com> wrote:
> >For your newsgroups file:
> >free.snipe Release the wading bird.
> ^
> Not a tab character; your composer isn't entering one
>
> Can you enter it directly with the character code?
>
> It's probably not going to prevent it from being appended to the
> newsgroups file on most servers that create it.
>
Hmm, I don't understand that, I definitely used the tab key.
> >For your newsgroups file:
> >free.snipe Release the wading bird.
> ^
> Not a tab character; your composer isn't entering one
>
> Can you enter it directly with the character code?
>
> It's probably not going to prevent it from being appended to the
> newsgroups file on most servers that create it.
>
Whatever, E-S has created it, as have aioe and Viper (which
I think is a Highwinds reseller).
> >Charter:
> >Dedicated to all who probe the boggy, marshy places of Usenet in search
> >of things to eat.
>
> >--
> >^Ï^ <https://youtu.be/_kqytf31a8E>
> ^
> You've got a UTF-8 character in your sigfile but your MIME header says
> ISO-8859-1. I didn't notice that earlier.
>
encodings if it doesn't need the full UTF-8 charset. I think "Latin
capital I with diaeresis" is an ISO-8859-1 character but I'm out of
my comfort zone here.
<https://www.fileformat.info/info/charset/ISO-8859-1/list.htm>
--
^Ï^ <https://youtu.be/_kqytf31a8E>
Adam H. Kerman
Apr 22, 2021, 2:50:00 PM4/22/21
to
Sn!pe <snip...@gmail.com> wrote:
>Adam H. Kerman <a...@chinet.com> wrote:
>>Sn!pe <snip...@gmail.com> wrote:
>>>For your newsgroups file:
>>>free.snipe Release the wading bird.
>> ^
>>Not a tab character; your composer isn't entering one
>>Can you enter it directly with the character code?
>>It's probably not going to prevent it from being appended to the
>>newsgroups file on most servers that create it.
>Hmm, I don't understand that, I definitely used the tab key.
This is a long-standing problem. Certain composers in newsreaders and
>Adam H. Kerman <a...@chinet.com> wrote:
>>Sn!pe <snip...@gmail.com> wrote:
>>>For your newsgroups file:
>>>free.snipe Release the wading bird.
>> ^
>>Not a tab character; your composer isn't entering one
>>Can you enter it directly with the character code?
>>It's probably not going to prevent it from being appended to the
>>newsgroups file on most servers that create it.
>Hmm, I don't understand that, I definitely used the tab key.
certain text editors are loathe to allow the use of a tab character, even
though it's ASCII, substituting a string of spaces. It's a feature but I
call it broken behavior. Well, that screws up the newsgroups file line
in a newgroup message. The problem is well known and News servers are
programmed to substitute the required tab upon processing the newgroup
message or creating the group.
>Whatever, E-S has created it, as have aioe and Viper (which
>I think is a Highwinds reseller).
itself.
You can see what INN does upon processing the newsgroups file line by
downloading the sample active and newsgroups files at
ftp://ftp.isc.org/pub/usenet/CONFIG
as those files aren't updated unless the newsgroups file line is in good
syntax but the tab substitution should be made.
>>You've got a UTF-8 character in your sigfile but your MIME header says
>>ISO-8859-1. I didn't notice that earlier.
>MacSOUP does use UTF-8 when it has to, but falls back to lesser
>encodings if it doesn't need the full UTF-8 charset. I think "Latin
>capital I with diaeresis" is an ISO-8859-1 character but I'm out of
>my comfort zone here.
UTF-8 multibyte character instead. It doesn't display correctly for me unless
I set the terminal emulation to display UTF-8.
><https://www.fileformat.info/info/charset/ISO-8859-1/list.htm>
Sn!pe
Apr 22, 2021, 3:25:30 PM4/22/21
to
Adam H. Kerman <a...@chinet.com> wrote:
> Sn!pe <snip...@gmail.com> wrote:
> >Adam H. Kerman <a...@chinet.com> wrote:
> >>Sn!pe <snip...@gmail.com> wrote:
>
> >>>For your newsgroups file:
> >>>free.snipe Release the wading bird.
> >> ^
> >>Not a tab character; your composer isn't entering one
>
> >>Can you enter it directly with the character code?
>
> >>It's probably not going to prevent it from being appended to the
> >>newsgroups file on most servers that create it.
>
> >Hmm, I don't understand that, I definitely used the tab key.
>
> This is a long-standing problem. Certain composers in newsreaders and
> certain text editors are loathe to allow the use of a tab character, even
> though it's ASCII, substituting a string of spaces. It's a feature but I
> call it broken behavior. Well, that screws up the newsgroups file line
> in a newgroup message. The problem is well known and News servers are
> programmed to substitute the required tab upon processing the newgroup
> message or creating the group.
>
> >Whatever, E-S has created it, as have aioe and Viper [edit].
> Sn!pe <snip...@gmail.com> wrote:
> >Adam H. Kerman <a...@chinet.com> wrote:
> >>Sn!pe <snip...@gmail.com> wrote:
>
> >>>For your newsgroups file:
> >>>free.snipe Release the wading bird.
> >> ^
> >>Not a tab character; your composer isn't entering one
>
> >>Can you enter it directly with the character code?
>
> >>It's probably not going to prevent it from being appended to the
> >>newsgroups file on most servers that create it.
>
> >Hmm, I don't understand that, I definitely used the tab key.
>
> This is a long-standing problem. Certain composers in newsreaders and
> certain text editors are loathe to allow the use of a tab character, even
> though it's ASCII, substituting a string of spaces. It's a feature but I
> call it broken behavior. Well, that screws up the newsgroups file line
> in a newgroup message. The problem is well known and News servers are
> programmed to substitute the required tab upon processing the newgroup
> message or creating the group.
>
>
> Right, but the issue is whether the tab appears in the newsgroup file
> itself.
>
> You can see what INN does upon processing the newsgroups file line by
> downloading the sample active and newsgroups files at
>
> ftp://ftp.isc.org/pub/usenet/CONFIG
>
> as those files aren't updated unless the newsgroups file line is in good
> syntax but the tab substitution should be made. [snip to end]
> Right, but the issue is whether the tab appears in the newsgroup file
> itself.
>
> You can see what INN does upon processing the newsgroups file line by
> downloading the sample active and newsgroups files at
>
> ftp://ftp.isc.org/pub/usenet/CONFIG
>
> as those files aren't updated unless the newsgroups file line is in good
>
Interesting. I see two free.* groups I've newgrouped in the past
but not my two latest ones. I assume that it takes time for 'active'
and 'newsgroups' to be updated? I'll keep an eye on this.
Adam H. Kerman
Apr 22, 2021, 6:56:05 PM4/22/21
to
Sn!pe
Apr 23, 2021, 8:10:51 AM4/23/21
to
Adam H. Kerman <a...@chinet.com> wrote:
[..]
> >> You can see what INN does upon processing the newsgroups file line
> >> by downloading the sample active and newsgroups files at
> >>
> >> ftp://ftp.isc.org/pub/usenet/CONFIG
> >>
> >> as those files aren't updated unless the newsgroups file line is in
> >> good syntax but the tab substitution should be made. [snip to end]
> >>
> >
> >Interesting. I see two free.* groups I've newgrouped in the past
> >but not my two latest ones. I assume that it takes time for 'active'
> >and 'newsgroups' to be updated? I'll keep an eye on this.
> >
>
> Russ doesn't run the update all that often anymore; maybe overnight.
>
I see both free.rocks and free.snipe are there now. I do find
> >> by downloading the sample active and newsgroups files at
> >>
> >> ftp://ftp.isc.org/pub/usenet/CONFIG
> >>
> >> as those files aren't updated unless the newsgroups file line is in
> >> good syntax but the tab substitution should be made. [snip to end]
> >>
> >
> >Interesting. I see two free.* groups I've newgrouped in the past
> >but not my two latest ones. I assume that it takes time for 'active'
> >and 'newsgroups' to be updated? I'll keep an eye on this.
> >
>
> Russ doesn't run the update all that often anymore; maybe overnight.
>
this process fascinating, even if it is reducing Usenet to being
my train-set. Whatever, it's only free.* and I guess it does no
harm to play with the machinery like this.
0 new messages