Groups | Search | Server Info | Login | Register

Groups > alt.comp.hardware > #16768

Re: Android for my Acer Aspire One

Cross-posted to 2 groups.

Show all headers | View raw

Richard Kettlewell <rjk@greenend.org.uk> wrote:
> Frank Slootweg <this@ddress.is.invalid> writes:
> > Richard Kettlewell <rjk@greenend.org.uk> wrote:
> >> Frank Slootweg <this@ddress.is.invalid> writes:
> >>> Richard Kettlewell <rjk@greenend.org.uk> wrote:
> >>>> "s|b" <me@privacy.invalid> writes:
> >>>>> On Sat, 4 Jul 2015 20:53:05 -0700, Norm X wrote:
> >>>>>> This message is X-posted to alt.comp.hardware & comp.mobile.android.
> >>>>>
> >>>>> Not sure, but I don't think it made it to comp.mobile.android. There's a
> >>>>> space in your Newsreader header.
> >>>> 
> >>>> Looks fine to from here.  (The syntax is quite liberal about
> >>>> whitespace)
> >>>
> >>>   No the syntax is *not* quite liberal. It's only that many News servers
> >>> or/and newsreaders are 'liberal' about accepting/processing crap from
> >>> non-compliant newsreaders. But to be fair, we can't expect them to
> >>> already get it after only three-plus decades, can we!? :-(
> >> 
> >> What did you have in mind?
> >
> >   In the older standards/RFCs a space *between newsgropups* in the
> > Newsgroups: header was not allowed. So the OP's header
> >
> >> Newsgroups: alt.comp.hardware, comp.mobile.android
> >
> > was not allowed.
> 
> 850 and 1036 are rather vague but they do incorporate 822 by reference,
> and 822 allows arbitrary whitespace between tokens.  So whitespace
> allowed in Newsgroups: is at least a plausible interpretation, though in
> the absence of a proper grammar you can?t say anything for sure.

  I understand what you're saying, but 1036 referencing 822 does not
mean that everything in 822 applies back to 1036.

  1036 is only 'vague' in the sense that it does not specifically say
that a space isn't allowed. But argueing that something is allowed if
it's not specifically forbidden, is a logical fallacy.

> You can look at the early implementations though, and it seems B News
> accepted spaces in the Newsgroups: header.  So in your view of the world
> I guess the rot had already set in by the mid 1980s.  Personally I?m
> skeptical about this idea that everyone including early server
> implementors has been getting it wrong for 30 years.

  AFAIK, INN has been warning for this. Don't know what it does in it's
current release nor if the behaviour is configurable.

  My newsreader - tin - warns and refuses to post:
  
Error: The "Newsgroups:" line has spaces  in it that MUST be removed.
       The only allowable  space is the one  separating the colon (:)
       from  the  contents.  Use a  comma  (,)  to separate  multiple
       newsgroup names.

  While my version is rather old, I don't think the current version is
different (I don't think Urs would allow that! :-)).

> >   The newer/current standards/RFCs are more lenient, because they allow
> > for FWS (Folding White Space), but as the name implies, that's intended
> > for *folding* (too) long lines, not for use within a short line.
> >
> >   Because there is always a lot of old(er) software around, the mantra
> > is "Be strict in what you send and lenient in what you accept.". So the
> > OP's newsreader SHOULD NOT have put the space in the list of newsgroups,
> > but other software - News servers and newsreaders alike - SHOULD accept
> > the 'broken' Newsgroups: header, and the latter is exactly what
> > happened.
> 
> Well, the statement was about what the syntax is, not about what it may
> or may not have been in 1981, and 5536 is the current spec, so I?m
> content that it stands.

  Yes, your statement was and is correct. I'm just pointing out whether
or not that statement is really relevant and whether the accepted
practice is recommended practice. The motto is still "Don't break
something if you don't have to!".

  Well, wasn't that a nice topic change from that boring Android/Linux
stuff!? :-)

  AFAIC, EOD, but feel free to continue if you want.

Back to alt.comp.hardware | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Android for my Acer Aspire One Norm X <nobody@nowhere.com> - 2015-07-04 20:53 -0700
  Re: Android for my Acer Aspire One Big_Al <Big_al@invalid.com> - 2015-07-05 07:40 -0400
  Re: Android for my Acer Aspire One Theo Markettos <theom+news@chiark.greenend.org.uk> - 2015-07-05 20:47 +0100
    Re: Android for my Acer Aspire One Frank Slootweg <this@ddress.is.invalid> - 2015-07-05 20:18 +0000
      Re: Android for my Acer Aspire One Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-07-05 21:39 +0100
      Re: Android for my Acer Aspire One Norm X <nobody@nowhere.com> - 2015-07-07 15:17 -0700
  Re: Android for my Acer Aspire One "s|b" <me@privacy.invalid> - 2015-07-05 21:58 +0200
    Re: Android for my Acer Aspire One Richard Kettlewell <rjk@greenend.org.uk> - 2015-07-05 21:10 +0100
      Re: Android for my Acer Aspire One Frank Slootweg <this@ddress.is.invalid> - 2015-07-05 20:25 +0000
        Re: Android for my Acer Aspire One Richard Kettlewell <rjk@greenend.org.uk> - 2015-07-05 22:02 +0100
          Re: Android for my Acer Aspire One Frank Slootweg <this@ddress.is.invalid> - 2015-07-06 18:37 +0000
            Re: Android for my Acer Aspire One Richard Kettlewell <rjk@greenend.org.uk> - 2015-07-06 20:24 +0100
              Re: Android for my Acer Aspire One Frank Slootweg <this@ddress.is.invalid> - 2015-07-06 21:42 +0000
      Re: Android for my Acer Aspire One "s|b" <me@privacy.invalid> - 2015-07-05 22:27 +0200
        Re: Android for my Acer Aspire One Richard Kettlewell <rjk@greenend.org.uk> - 2015-07-05 22:02 +0100
          Re: Android for my Acer Aspire One "s|b" <me@privacy.invalid> - 2015-07-06 19:43 +0200
  Re: Android for my Acer Aspire One Ammammata <ammammata@tiscalinet.it> - 2015-07-07 07:03 +0000
  Re: Android for my Acer Aspire One Norm X <nobody@nowhere.com> - 2015-09-06 17:08 -0700

csiph-web