Re: setting up lax security on one ethernet interface while leaving the other strict
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Mon, 29 Sep 2008 15:02:24 -0500
On Sun, 28 Sep 2008, in the Usenet newsgroup comp.os.linux.networking, in
article <785221b8-0e46-4b7b-896a-1d71a1dc97b3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
David Schwartz wrote:
NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.
Where have you been looking? <A0>On google? <A0>Wow, google doesn't filter
posts from google - there's a surprise. <A0>I'd bet if you looked harder,
you would find specific *public* news servers that block posts from
groups.google.com, never mind non-public servers (like those run
by my or my wife's employers).
Ah, so in your world, a post that doesn't go to every news server is
"not seen".
Twisting the meaning rather hard, aren't you? The note I include says
that it REDUCES THE CHANCE of a post being seen. Do you feel that if
a news server doesn't carry any posts from group.google.com, or the
fairly well documented (posted in newsgroups - such as
news.software.readers) evidence that some people really do block,
delete, or filter posts simply can't be true? And therefore filters
must not exist. How do you know this is or is not the case?
In that case, every post is "not seen" and *nothing* increases the
changes that a post will be "not seen" since there is no way to raise
the probability beyond a certainty.
Ah, nothing anyone can say can change your mind. And anything that is
posted that you disagree with...
News is a service, not a protocol.
like the RFCs you decided are not relevant... why, they simply must not
exist. I'll bet the posts to news.admin.net-abuse.usenet and/or
news.admin.net-abuse.policy discussing the banning of Google (which
strangely, groups.google.com doesn't seem to have available on their
search engine) don't exist in your view either.
Web servers that serve news are "real news server"s.
Are they serving news on port 119 or 563?
Ah, so the *port* a news server serves news on is what makes a news
server "real". You know that's nonsense.
Do they follow RFC0977,
RFC1036, or RFC3977? <A0> Or do they alter news posts - as google does.
As I said, news is a service not a protocol. Are you going to ignore
that argument or address it?
Are you going to ignore RFC0977? RFC3977? Are you going to ignore
any post that disagrees with you?
The real question is how may people just IGNORE <A0>google crap
Given the fact that many news readers can filter on the Message-ID:
header, and everyone and their goat has published simple instructions
on how to do so, it's rather difficult to guess how many ignore google
_crap_ <A0>verses how many ignore all posts from google (whether in one
or all newsgroups they may read).
So, in other words, you have no idea.
And you know it's not significant, or doesn't happen at all?
No - it's simply that nothing anyone can say or write will change your
mind. You feel that groups.google.com is a news server and EVERYONE must
see every post that originates there. Others disagree, but that's not
significant to you. I suppose you think that because you see ads from
google, everyone else should and can't imagine why people might take
steps to avoid seeing them. That those steps might reduce the chance
of a post from groups.google.com - whether spam or not - from being
seen by everyone who views these groups obviously can't be important.
Old guy
.
- Follow-Ups:
- Re: setting up lax security on one ethernet interface while leaving the other strict
- From: David Schwartz
- Re: setting up lax security on one ethernet interface while leaving the other strict
- References:
- setting up lax security on one ethernet interface while leaving the other strict
- From: dan
- Re: setting up lax security on one ethernet interface while leaving the other strict
- From: Moe Trin
- Re: setting up lax security on one ethernet interface while leaving the other strict
- From: David Schwartz
- Re: setting up lax security on one ethernet interface while leaving the other strict
- From: Send
- Re: setting up lax security on one ethernet interface while leaving the other strict
- From: Moe Trin
- Re: setting up lax security on one ethernet interface while leaving the other strict
- From: David Schwartz
- setting up lax security on one ethernet interface while leaving the other strict
- Prev by Date: Re: OpenSSH Assistance - New Admin
- Next by Date: Re: Weird problem, only one port, 80, is blocked.
- Previous by thread: Re: setting up lax security on one ethernet interface while leaving the other strict
- Next by thread: Re: setting up lax security on one ethernet interface while leaving the other strict
- Index(es):
Relevant Pages
|