Read 'em and weep, Win 10 sheeple.

Windows XP Vulnerabilities: 741
https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=739&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=741&sha=96656e0273b52e8473fbf8b6371fe2ed4a0f8ae8

Windows 10 vulnerabilities: 2,261
https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=32238&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=2261&sha=41e451b72c2e412c0a1cb8cb1dcfee3d16d51c44

On Thu, 15 Jul 2021 20:27:11 -0500, Merle@invalid.com wrote:

>Read 'em and weep, Win 10 sheeple.
>
>Windows XP Vulnerabilities: 741
>https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=739&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=741&sha=96656e0273b52e8473fbf8b6371fe2ed4a0f8ae8
>
>Windows 10 vulnerabilities: 2,261
>https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=32238&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=2261&sha=41e451b72c2e412c0a1cb8cb1dcfee3d16d51c44
>

Subject need to be spell checked. :o)

Eye surgery has the eyes blurred for a few more days.

On Thu, 15 Jul 2021 20:27:11 -0500, Merle@invalid.com wrote:
> Read 'em and weep, Win 10 sheeple.
>
> Windows XP Vulnerabilities: 741
> https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=739&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=741&sha=96656e0273b52e8473fbf8b6371fe2ed4a0f8ae8
>
> Windows 10 vulnerabilities: 2,261
> https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=32238&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=2261&sha=41e451b72c2e412c0a1cb8cb1dcfee3d16d51c44

That just shows how Windows 10 is prematurely released, including the
updates. They say "rapid development". But it also mean not well tested. In
fact, testing is not the proority of "rapid development". The priority is
only for fast paced development.

But one of the good things about newer Windows versions is that, they lure
hackers and malware authors away from from older Windows versions. Leaving
older Windows version systems in peace.

On Sat, 17 Jul 2021 00:06:53 +0700, JJ <jj4public@gmail.com> wrote:

>On Thu, 15 Jul 2021 20:27:11 -0500, Merle@invalid.com wrote:
>> Read 'em and weep, Win 10 sheeple.
>>
>> Windows XP Vulnerabilities: 741
>> https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=739&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=741&sha=96656e0273b52e8473fbf8b6371fe2ed4a0f8ae8
>>
>> Windows 10 vulnerabilities: 2,261
>> https://www.cvedetails.com/vulnerability-list.php?vendor_id=26&product_id=32238&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&cweid=0&order=1&trc=2261&sha=41e451b72c2e412c0a1cb8cb1dcfee3d16d51c44
>
>That just shows how Windows 10 is prematurely released, including the
>updates. They say "rapid development". But it also mean not well tested. In
>fact, testing is not the proority of "rapid development". The priority is
>only for fast paced development.
>
>But one of the good things about newer Windows versions is that, they lure
>hackers and malware authors away from from older Windows versions. Leaving
>older Windows version systems in peace.

10-4, old buddy! :o)

Same to you, you brainwashed officious twit !

😉 Good Guy 😉 wrote:
> On 16/07/2021 02:27, Merle@invalid.com wrote:
>> Read
>>
> CAN YOU JUST FUCK OFF.
> CAN YOU JUST FUCK OFF.
> CAN YOU JUST FUCK OFF.
> CAN YOU JUST FUCK OFF.
> CAN YOU JUST FUCK OFF.
>
> STOP VANDALISING THIS NEWSGROUP WITH YOUR CRAP LINKS.
>
> You don't have the necessary intelligence to know what is secure and
> what is not and in what context is security best discussed. Windows XP
> is no longer supported so idiots like you can keep singing about it for
> years to come.
>
> YOU ARE A BLIND FOOL! GO FUCK YOURSELF.
>
> --
>
> With over 1.3 billion devices now running Windows 10, customer
> satisfaction is higher than any previous version of windows.
>

On Sat, 17 Jul 2021 00:06:53 +0700, JJ <jj4public@gmail.com> wrote:

>But one of the good things about newer Windows versions is that, they lure
>hackers and malware authors away from from older Windows versions. Leaving
>older Windows version systems in peace.

I wonder when the last hack was aimed at a W98 machine.

Jolly,

> Same to you, you brainwashed officious twit !

Just put him into your killfile.

You know, its rather amusing to see the hypocrisy with which GG complains
about "crap links". Absolutitly *none* of the subjects he has posted has
anything to do with XP [1], and his links are therefore absolutily worthless
to anyone here.

[1] from 45 he started last six months most are about Win 10 or related,
quiete a number about non-computer stuff (ufos, argentinians, gaza city,
biden, cancel culture, amazon, twitter, etc) and /not a single one/ about
XP.

Also, most of all of those subjects he posted were pretty-much copy-pasted
from news sites.

His demands that we all read his posts as HTML but first have to ask his
permission to do so is just the cherry on top.

Regards,
Rudy Wieser

On Sat, 17 Jul 2021 10:37:13 +0200, R.Wieser wrote:
> Jolly,
>
>> Same to you, you brainwashed officious twit !
>
> Just put him into your killfile.

For me, I already did. Quite early, that is.

Somehow, my news client know something's wrong with all of his posts. Each
time I try to retrieve any of his posts' message body, the news client gives
me a silent treatment and stops responding - refusing to load any of his
messages. So, I just killfile him.

I don't know what happended to him. He used to be a good usenet citizen.
Rarely trolls and posts off topics. But now, all of his posts are crap.

On Fri, 16 Jul 2021 19:40:06 -0400, gfretwell@aol.com wrote:
> On Sat, 17 Jul 2021 00:06:53 +0700, JJ <jj4public@gmail.com> wrote:
>
>>But one of the good things about newer Windows versions is that, they lure
>>hackers and malware authors away from from older Windows versions. Leaving
>>older Windows version systems in peace.
>
> I wonder when the last hack was aimed at a W98 machine.

And I wonder when was the last virus made for OS/2 or even DOS & CP/M. :)

Cause I think most, if not, all of the people who still use old OSes are
loyal and honest fans.

JJ,

>> Just put him into your killfile.
>
> For me, I already did. Quite early, that is.

I've been giving him the benefit of the doubt for a while, but after seeing
he just kept posting stuff with no relation to this newsgroup I also did.

> Somehow, my news client know something's wrong with all of his
> posts. Each time I try to retrieve any of his posts' message body,
> the news client gives me a silent treatment and stops responding

Hmmm.. strange (but befitting him :-) ). IE6 doesn't have a problem with
it, and a peek just now at the raw message (headers & body) doesn't show
anything outof the ordinary that I can see.

> I don't know what happended to him. He used to be a good usenet
> citizen. Rarely trolls and posts off topics. But now, all of his posts
> are crap.

I noticed the same and sometimes wonder what might have caused it ...

Regards,
Rudy Wieser

"R.Wieser" wrote:
> Jolly,
>
>> Same to you, you brainwashed officious twit !
>
> Just put him into your killfile.

No need here. Thankfully, Eternal September rejects HTML posts so I
never see his crap unless someone responds to it.

Apd,

> Thankfully, Eternal September rejects HTML posts so I
> never see his crap unless someone responds to it.

Thats *the* major downside of actually removing someones posts (either by
the server or by the reader) : as no parent to a reply can be found that
parents "killfile" status cannot be determined either.

My OE6 has that "lets just delete the message and forget all about it"
problem too. Either stooopid or an attempt to get people to pay to drop
that "E" in the middle. :-\

Regards,
Rudy Wieser

On Sun, 18 Jul 2021 15:07:00 +0100, "Apd" <not@all.invalid> wrote:

>"R.Wieser" wrote:
>> Jolly,
>>
>>> Same to you, you brainwashed officious twit !
>>
>> Just put him into your killfile.
>
>No need here. Thankfully, Eternal September rejects HTML posts so I
>never see his crap unless someone responds to it.
>

You people just keep making trolls like him satisfied with your
constant mention of them. They're attention seekers. Kill file them
and that's it. Don't sit around discussing the moron. You're just
feeding him when you do.

You people make filtering sound like as perplexing a problem as
Differential Calculus.

And don't give me this crap "You're feeding him, too, with your post."

No, I ain't complaining about him. I'm complaining about you people
whining about how the simplicity of Kill Filtering seems to escape
you.

"Apd" <not@all.invalid> wrote

| No need here. Thankfully, Eternal September rejects HTML posts so I
| never see his crap unless someone responds to it.
|

I didn't know that. I use ES, but I've been blocking Good Guy
for years, anyway. Funny thing... For many years I never blocked
anyone. It seemed rude and there weren't really problems. But
these days I block lots of people. Some are anti-social. Others
are oddballs. Some are just lonely people who like to post things
like, "I just spilled coffee on my keyboard. What do you think is
the best cleaner?"

I suppose the landscape has changed a lot. 20 years ago the
groups were alive with questions, tweaking, programming discussions...
and lots of MVPs. These days we're all old, most of the MVPs are
gone, few people are programming shareware, and most of the
on-topic questions are not so much tweaking as surviving Win10.
Or people reporting, with surprise, that they just got the latest Win10
remake and their computer is still booting.

Maybe we'll need to start a microsoft.public.prostate.tips and
then we can just use that group for all Windows issues. :)

Merle,

>>"R.Wieser" wrote:
>>> Jolly,
>>>
>>>> Same to you, you brainwashed officious twit !
>>>
>>> Just put him into your killfile.
>>
>> No need here. Thankfully, Eternal September rejects HTML posts
>> so I never see his crap unless someone responds to it.

Two things:

One: Learn to quote. That last "No need here" part of the quote there is
not mine.

Two: Learn to discern between talking about someone and how to get rid of
his crap.

> No, I ain't complaining about him. I'm complaining about you
> people whining

And you do not realize that you are now whining about, and (possibly) just
feeding *us* ? :-)

> the simplicity of Kill Filtering seems to escape you.

Lol.

You know what seems to have fully escaped you ? That not all newsgroup
readers handle "killfiling" in the same way, and some approaches do not give
the desired result. Also, that the "Ethernal september" usenet server, by
its deletion of certain posts, makes itself part of that problem. Are you
telling us that we are not allowed to discuss that ? Really ?

Suggestion: if you cannot grasp, or simply do not care about what others are
talking about you can always use the button which will hide that message
subtree (your reader program /does/ have such a button, no ?). Better for
you and us.

On the other hand, you could just be trolling ...

Regards,
Rudy Wieser

"R.Wieser" wrote:
> Apd,
>> Thankfully, Eternal September rejects HTML posts so I
>> never see his crap unless someone responds to it.
>
> Thats *the* major downside of actually removing someones posts (either by
> the server or by the reader) : as no parent to a reply can be found that
> parents "killfile" status cannot be determined either.

The "References" header will have what you need. If you can't find the
message in OE look it up on Howard Knight:
<http://al.howardknight.net/>

> My OE6 has that "lets just delete the message and forget all about it"
> problem too.

Mark as read?

> Either stooopid or an attempt to get people to pay to drop
> that "E" in the middle. :-\

?

"Mayayana" wrote:
> "Apd" wrote
>| No need here. Thankfully, Eternal September rejects HTML posts so I
>| never see his crap unless someone responds to it.
>
> I didn't know that.

Nor did I until GG's posts became noticeable by their absence. Then
I heard about the HTML block in one of the support groups (aioe or
ES). It's fairly recent, probably less than a year.

> I use ES, but I've been blocking Good Guy for years, anyway.

I just used to skip his posts - land on one then "next unread".

> Funny thing... For many years I never blocked
> anyone. It seemed rude and there weren't really problems. But
> these days I block lots of people. Some are anti-social. Others
> are oddballs. Some are just lonely people who like to post things
> like, "I just spilled coffee on my keyboard. What do you think is
> the best cleaner?"

I never found the need to filter until a couple of years back when a
bot started posting in a group I follow (it posts in a few). I delete
those outright. Then another poster appeared from one of the troll
groups with content-free one-liners in fully-quoted replies. That was
another delete. Finally, there's one who compulsively replies with
insults to every post made by certain people he doesn't like. He's
never contributed anything. That's another for immediate deletion.

> I suppose the landscape has changed a lot. 20 years ago the
> groups were alive with questions, tweaking, programming discussions...
> and lots of MVPs. These days we're all old, most of the MVPs are
> gone, few people are programming shareware, and most of the
> on-topic questions are not so much tweaking as surviving Win10.
> Or people reporting, with surprise, that they just got the latest Win10
> remake and their computer is still booting.

So true. This guy wants to revive Usenet and has a PDF presentation
about it:
<https://www.big-8.org/wiki/User:Jason_Evans>

I wish him luck.

> Maybe we'll need to start a microsoft.public.prostate.tips and
> then we can just use that group for all Windows issues. :)

I actually LOL'd at that (a rare thing).

Apd,

> The "References" header will have what you need.

How ? Yes, the last entry in there tells you who the current posts parent
is, but if the parent was deleted (on the server or client), than all data
about that parent is gone. There simply is nothing to look at.

> If you can't find the message in OE look it up on Howard Knight:

:-) Yes you can. But you will than have to do that for /every reply/ to
that killfiled person. IOW, you will need to notice that a reply is
possibly to someone you have killfiled, verify it and than remove the reply.
Thats a /lot/ of work. :-\

>> My OE6 has that "lets just delete the message and forget all
>> about it" problem too.
>
> Mark as read?

OE6 has a "view" and "ignore" modi (which needs a manual addition of a
"display rule" to actually /do/ anything - something I only "recently" was
made aware of), both of which are inherited.

Though that still causes the message to be displayed and needs manual manual
labour on every reply to a non-existing (killfiled and thus deleted) parent.
IOW, a game of whack-a-mole ...

But as I am a bit of a tinkerer and hobby programmer I found a way to
disable the "delete" part of the build-in killfile. After that I wrote some
stuff to use the names in that killfile list (stored in the registry) to do
some filtering of my own, marking the caught messages as "ignore". Presto,
I do not see killfiled messages or the replies to them anymore (but can
still access them if the need is there). :-)

>> Either stooopid or an attempt to get people to pay to
>> drop that "E" in the middle. :-\
>
> ?

MS sells Outlook. Outlook Express is just the dumbed down, "try it for
free" version that gets installed with Windows (at least upto XP).

Regards,
Rudy Wieser

On Mon, 19 Jul 2021 03:25:36 +0100, Apd wrote:
>
> So true. This guy wants to revive Usenet and has a PDF presentation
> about it:
[snip: URL censored]

LOL. Might as well use PowerPoint, and to recommend that Usenet content
should be JavaScript... heck, WebAssembly enabled.

"R.Wieser" wrote:
> Apd,
[...]
>> Mark as read?
>
> OE6 has a "view" and "ignore" modi (which needs a manual addition of a
> "display rule" to actually /do/ anything - something I only "recently" was
> made aware of), both of which are inherited.
>
> Though that still causes the message to be displayed and needs manual manual
> labour on every reply to a non-existing (killfiled and thus deleted) parent.
> IOW, a game of whack-a-mole ...
>
> But as I am a bit of a tinkerer and hobby programmer I found a way to
> disable the "delete" part of the build-in killfile. After that I wrote some
> stuff to use the names in that killfile list (stored in the registry) to do
> some filtering of my own, marking the caught messages as "ignore". Presto,
> I do not see killfiled messages or the replies to them anymore (but can
> still access them if the need is there). :-)

I gather from all that you want to kill the subthreads arising from
killfiled messages. I didn't know it was even possible in OE.

>>> Either stooopid or an attempt to get people to pay to
>>> drop that "E" in the middle. :-\
>>
>> ?
>
> MS sells Outlook. Outlook Express is just the dumbed down, "try it for
> free" version that gets installed with Windows (at least upto XP).

I wasn't aware Outlook could do NNTP. An org I worked for used Outlook
for mail and OE for the internal newsgroups. I never liked Outlook,
always preferring OE which is a different product and not one I
consider to be "dumbed down".

"JJ" wrote:
> On Mon, 19 Jul 2021 03:25:36 +0100, Apd wrote:
>> So true. This guy wants to revive Usenet and has a PDF presentation
>> about it:
> [snip: URL censored]
>
> LOL. Might as well use PowerPoint, and to recommend that Usenet content
> should be JavaScript... heck, WebAssembly enabled.

WTF are you on about? I must admit I don't know how he thinks he's
going to revive it.

Apd,

> I gather from all that you want to kill the subthreads arising
> from killfiled messages.

Yup.

> I didn't know it was even possible in OE.

It isn't. Due to that stooopid decision they made to actually /delete/ a
killfiled posters message - all of it.

> I wasn't aware Outlook could do NNTP.

Ehhhrmmm ... To be honest, I took it for granted it would due to what I
always understood as the "full product" vs "free-to-try" version relation.
I just did a search for it, and saw that Outlook doesn't actually support
NNTP. I stand corrected. Thanks for bringing it up.

> always preferring OE which is a different product

I've got nothing to compare, as I've never used Outlook. Glanced at it,
but nothing more.

Regards,
Rudy Wieser

On Mon, 19 Jul 2021 at 11:33:01, R.Wieser <address@not.available> wrote
(my responses usually follow points raised):
>Apd,
>
>> The "References" header will have what you need.
>
>How ? Yes, the last entry in there tells you who the current posts parent
>is, but if the parent was deleted (on the server or client), than all data
>about that parent is gone. There simply is nothing to look at.

I'm sure I've seen (I think "References") headers that contain
references to the entire thread (or at least as much of it as the
previous post retained). (After all, if the header is called
"References", with an s, ...)
[]
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The average age at which a woman has her first child has passed 30.
Jason Cowley, RT 2016/6/11-17

On Mon, 19 Jul 2021 at 19:46:19, Apd <not@all.invalid> wrote (my
responses usually follow points raised):
>"R.Wieser" wrote:
[]
>> MS sells Outlook. Outlook Express is just the dumbed down, "try it for
>> free" version that gets installed with Windows (at least upto XP).
>
>I wasn't aware Outlook could do NNTP. An org I worked for used Outlook
>for mail and OE for the internal newsgroups. I never liked Outlook,
>always preferring OE which is a different product and not one I
>consider to be "dumbed down".
>
>
O can't do news, but pretends it can, by calling OE (msimn); at least,
that was the case up to about 20 years ago when my employer ditched news
altogether (internal and external). Since MS don't like news, I can't
see them ever adding it to O; they've probably removed the pretence from
later versions (if only because OE wasn't supplied with later Windows
[though may still _work_ under some of them if the .exe is copied]).
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The average age at which a woman has her first child has passed 30.
Jason Cowley, RT 2016/6/11-17

John,

> I'm sure I've seen (I think "References") headers that contain references
> to the entire thread (or at least as much of it as the previous post
> retained)

Yes, it does (which is why I said "the *last entry* in there tells you who
the current posts parent is" - emphasis mine). But how does that help ?

Mind you, none of the other stored posts can have been killfiled - they
would not have been stored if they where . :-) IOW, that means that you
could go thru all the actually stored messages, but /not one of them/ would
have a "killfile" indicator that could get inherited.

Also, the grandparent of the current post could be A-OK (read: the killfiled
parent message could be a reply into a thread started by someone else).

Regards,
Rudy Wieser