candycanearter07 <no@thanks.net> wrote:
> On 10/19/23 10:15, Frank Slootweg wrote:
> > Yes, he should have asked. He's new to Usenet, which allows him some
> > leeway, but (IMO) he's using way too much of it and doesn't seem (want?)
> > to learn. So I've filtered him here and some other groups (but not
> > news.software.readers).
>
> I am trying to learn!

When you're ignoring comments/advice, like not snipping too much
context (which you are doing *again* in this response of yours), you're
not really "trying to learn", are you!?

I.e. you should have kept most - if not all - of AJL's post. Now it's
unclear *what* (I said) you should have asked and *who* you should have
asked (me, but that's not clear without the missing context).

So if you get some advice on how to (not) use Usenet, take note or
discuss it, but don't just ignore it.

On 2023-10-19 17:19, Ken Blake wrote:
> On 19 Oct 2023 15:03:17 GMT, Frank Slootweg <this@ddress.is.invalid>
> wrote:
>
>> AJL <noemail@none.com> wrote:
>>> Frank Slootweg wrote:
>>>> AJL wrote:
>>>
>>>>> Moving to a new ISP is like moving to a new house if you use their
>>>>> email system. Everybody has to be advised of the new address.
>>>>> PITA. That's why I started using Gmail addresses years ago...
>>>
>>>> Yes, I also have several Gmail addresses, but as I said, our main/old
>>>> addresses predate the web/Internet and hence Gmail. An even earlier
>>>> address is in printed books. A tad hard to change those! :-)
>>>
>>> IIRC my first email address was with AOL. Probably mid 90s...
>>
>> My first email address was an inter-company address, (very) early 70s.
>> At the time it wasn't called 'email' (the term probably didn't even
>> exist yet (at least not generally)), but it was mail via electronic
>> means.
>
>
> My first e-mail address came for free with the BBS (Bulletin Board
> System) I used around 1990. It was only good to contact other users
> of that BBS.
>
> I never used it. I couldn't understand what value an e-mail address
> had.

Very few people could. I did not imagine.

Yes, I also had an email with my Fidonet point.

--
Cheers,
Carlos E.R.

On 2023-10-19 17:58, AJL wrote:
> On 10/19/2023 7:49 AM, Frank Slootweg wrote:
>> AJL <noemail@none.com> wrote:
>>> On 10/18/2023 2:06 PM, Oscar Mayer wrote:
....
> Also I was surprised to find that even though you completely changed the
> subject line to "[OT] Be careful updating Thunderbird!" both Google
> Groups and my PhoNews newsreader kept putting new posts under the old
> thread. But this TB newsreader made a new thread. ???.

Not mine.

--
Cheers,
Carlos E.R.

On 10/19/23 14:33, Frank Slootweg wrote:
> candycanearter07 <no@thanks.net> wrote:
>> On 10/19/23 10:15, Frank Slootweg wrote:
>>> Yes, he should have asked. He's new to Usenet, which allows him some
>>> leeway, but (IMO) he's using way too much of it and doesn't seem (want?)
>>> to learn. So I've filtered him here and some other groups (but not
>>> news.software.readers).
>>
>> I am trying to learn!
>
> When you're ignoring comments/advice, like not snipping too much
> context (which you are doing *again* in this response of yours), you're
> not really "trying to learn", are you!?
>
> I.e. you should have kept most - if not all - of AJL's post. Now it's
> unclear *what* (I said) you should have asked and *who* you should have
> asked (me, but that's not clear without the missing context).
>
> So if you get some advice on how to (not) use Usenet, take note or
> discuss it, but don't just ignore it.

OK
--
user <candycane> is generated from /dev/urandom

On 10/19/2023 10:52 AM, Frank Slootweg wrote:
> AJL <noemail@none.com> wrote:

>> I was surprised to find that even though you completely changed
>> the subject line, both Google Groups and my PhoNews newsreader kept
>> putting new posts under the old thread. But this TB newsreader
>> showed a new thread.

> Because it is a normal response, i.e. it has a 'References:' header
> with the message-id of the parent (your) post, it should be threaded
> as a new *sub*thread, under/in the old thread. Also note that a
> proper newsreader should strip off the '(was: ...)' part of the
> 'Subject:', which your Thunderbird correctly did.

Let me try again. Perhaps I said it wrong. If I check Google or Pho for
all threads this sub-thread is nowhere to be found unless I open the
original thread. With TB under View>Threads>All this sub-thread is easy
to spot even though it is under the original thread.

I prefer TB in this situation because I often FORGET the main thread
subject title and the sub-thread still sticks out. With Google and Pho I
have to hunt through a bunch of threads to find it. A personal problem,
I know...

> If I can be bothered, I might check in Thunderbird later.

Don't bother. I think I've definitely worn this sub-sub-thread out...

On 10/19/2023 10:33 AM, Frank Slootweg wrote:
> AJL <noemail@none.com> wrote:

>> I remember when traveling across country the first thing I would do
>> after checking in for the night was to check for local AOL phone
>> numbers. Then hook up my handset to the motel's handset and beep
>> away. Those were the days...

> Yes, fond memories. Our sales (and service) engineers even used
> 'acoustic couplers', a modem in the form of a large handset which
> you could put over the handset in a public telephone booth, i.e. no
> physical connection needed. Worked at a whopping 300 baud (IIRC).

That's the device I was trying to describe (above) that I was using on
the motel's room phone. I just didn't remember that it was called an
acoustic coupler....

BTW my version of TB says we're both spelling 'coupler' wrong. But
Google says it's Ok. Whom to believe...

On 10/19/23 16:57, AJL wrote:
> On 10/19/2023 10:33 AM, Frank Slootweg wrote:
>> AJL <noemail@none.com> wrote:
>
>>> I remember when traveling across country the first thing I would do
>>> after checking in for the night was to check for local AOL phone
>>> numbers. Then hook up my handset to the motel's handset and beep
>>> away. Those were the days...
>
>> Yes, fond memories. Our sales (and service) engineers even used
>> 'acoustic couplers', a modem in the form of a large handset which
>> you could put over the handset in a public telephone booth, i.e. no
>> physical connection needed. Worked at a whopping 300 baud (IIRC).
>
> That's the device I was trying to describe (above) that I was using on
> the motel's room phone. I just didn't remember that it was called an
> acoustic coupler....
>
> BTW my version of TB says we're both spelling 'coupler' wrong. But
> Google says it's Ok. Whom to believe...
>

TB's spellcheck isn't the best. I've had to add a bunch of words to
dictionary.
--
user <candycane> is generated from /dev/urandom

On 10/19/2023 3:02 PM, candycanearter07 wrote:
> On 10/19/23 16:57, AJL wrote:

>> BTW my version of TB says we're [me 'n Frank] both spelling 'coupler' wrong. But
>> Google says it's Ok. Whom to believe...

> TB's spellcheck isn't the best. I've had to add a bunch of words to
> dictionary.

Your headers still say you're using Betterbird not TB. You have TB too?

AJL <noemail@none.com> wrote:
[...]

> BTW my version of TB says we're both spelling 'coupler' wrong. But
> Google says it's Ok. Whom to believe...

Huh!? Does it (TB) say what it thinks is the 'correct' spelling?

I mostly use Google Translate to check spelling if I'm unsure, so
that's of no help in this case.

AJL <noemail@none.com> wrote:
[...]

> Let me try again. Perhaps I said it wrong. If I check Google or Pho for
> all threads this sub-thread is nowhere to be found unless I open the
> original thread. With TB under View>Threads>All this sub-thread is easy
> to spot even though it is under the original thread.
>
> I prefer TB in this situation because I often FORGET the main thread
> subject title and the sub-thread still sticks out. With Google and Pho I
> have to hunt through a bunch of threads to find it. A personal problem,
> I know...

Yes that's the right way. Good on TB! :-)

[...]

On 10/19/23 17:15, AJL wrote:
> On 10/19/2023 3:02 PM, candycanearter07 wrote:
>> On 10/19/23 16:57, AJL wrote:
>
>>> BTW my version of TB says we're [me 'n Frank] both spelling 'coupler'
>>> wrong. But
>>> Google says it's Ok. Whom to believe...
>
>> TB's spellcheck isn't the best. I've had to add a bunch of words to
>> dictionary.
>
> Your headers still say you're using Betterbird not TB. You have TB too?

When I used TB.
And BB has the same dictionary, I'm pretty sure.
--
user <candycane> is generated from /dev/urandom

On 10/20/2023 3:44 AM, Frank Slootweg wrote:
> AJL <noemail@none.com> wrote:

>> BTW my version of TB says we're both spelling 'coupler' wrong. But
>> Google says it's Ok. Whom to believe...

> Huh!? Does it (TB) say what it thinks is the 'correct' spelling?

Right clicking coupler (which has/had the red wavy line underneath
indicating a misspell (in this post too)) the suggestions are: couplet,
couple, couples, coupled, couple r.

That last one with the space is probably it and the space is likely a
bug but would you trust it? Me neither. Google to the rescue...

If you have too much time on your hands like I do, give it a try on your
version...

> I mostly use Google Translate to check spelling if I'm unsure, so
> that's of no help in this case.

My problem is I don't realize I misspelled a word. (like my first try at
'misspelled' above had only one 's' until the red wavy line whacked me).
So when I use a no-spell-check newsreader like PhoNews or Groundhog my
poor spelling often hangs out.

Candy claimed to be able to modify the spelling function in TB. I looked
and don't see that capability in mine. I think he perhaps just made
another mistake at what newsreader he was using.

Eternal-September has been taking 20 or more seconds to accept my posts
lately. Hope that's not a bad sign...

On 10/20/2023 7:55 AM, candycanearter07 wrote:
> On 10/19/23 17:15, AJL wrote:
>> On 10/19/2023 3:02 PM, candycanearter07 wrote:

>>> TB's spellcheck isn't the best. I've had to add a bunch of words
>>> to dictionary.
>>
>> Your headers still say you're using Betterbird not TB. You have TB
>> too?
>
> When I used TB. And BB has the same dictionary, I'm pretty sure.

Pretty sure? Ah. Well I looked in my version of TB and couldn't find how
to add words to the dictionary but that doesn't mean the capability's
not hiding in there somewhere...

Frank Slootweg wrote:

> Currently there are lots of reports (in the Windows groups), that the
> latest major update, v115, is severely broken, probably mostly for news,
> but maybe also for e-mail. (FWIW, I use 60.9.0).

Enough with the FUD, plenty of us are happy with TB v115

AJL <noemail@none.com> wrote:
> On 10/20/2023 3:44 AM, Frank Slootweg wrote:
> > AJL <noemail@none.com> wrote:
>
> >> BTW my version of TB says we're both spelling 'coupler' wrong. But
> >> Google says it's Ok. Whom to believe...
>
> > Huh!? Does it (TB) say what it thinks is the 'correct' spelling?
>
> Right clicking coupler (which has/had the red wavy line underneath
> indicating a misspell (in this post too)) the suggestions are: couplet,
> couple, couples, coupled, couple r.
>
> That last one with the space is probably it and the space is likely a
> bug but would you trust it? Me neither. Google to the rescue...
>
> If you have too much time on your hands like I do, give it a try on your
> version...

My version (60.9.0) gives the same suggestions, so it's a bug.

> > I mostly use Google Translate to check spelling if I'm unsure, so
> > that's of no help in this case.
>
> My problem is I don't realize I misspelled a word. (like my first try at
> 'misspelled' above had only one 's' until the red wavy line whacked me).
> So when I use a no-spell-check newsreader like PhoNews or Groundhog my
> poor spelling often hangs out.

I only check spelling for English words, if I'm unsure. If I'm not
unsure, I don't check and I just post the article. If that means there
are spelling errors in my text, tough! I'm Dutch, so sue me!

> Candy claimed to be able to modify the spelling function in TB. I looked
> and don't see that capability in mine. I think he perhaps just made
> another mistake at what newsreader he was using.

In the right-clicked menu, there's an 'Add to Dictionary' choice.
There I added 'coupler' (without space) and now when I type 'coupler'
it's accepted as correct.

So I think Candy means you can *add* the correct spelling, not
*modify* the existing lists.

> Eternal-September has been taking 20 or more seconds to accept my posts
> lately. Hope that's not a bad sign...

As I suggested in another group (Candy might recognize it):

"Get a proper NSP!" :-)

Andy Burns <usenet@andyburns.uk> wrote:
> Frank Slootweg wrote:
>
> > Currently there are lots of reports (in the Windows groups), that the
> > latest major update, v115, is severely broken, probably mostly for news,
> > but maybe also for e-mail. (FWIW, I use 60.9.0).
>
> Enough with the FUD, plenty of us are happy with TB v115

Of course. That's the case with most software and with most updates.

But there haven't been that many problem reports (problem, not bug)
for a long time, so it's not all plain sailing. And then there's the
issue of the changed profile format.

You call it FUD, I call it a warning/heads-up (note "be careful").

Frank Slootweg wrote:
> AJL wrote:
>> Frank Slootweg wrote:
>>> AJL wrote:

>>>> my version of TB says we're both spelling 'coupler' wrong.

>>> Huh!? Does it (TB) say what it thinks is the 'correct' spelling?

>> Right clicking coupler the suggestions are: couplet, couple,
>> couples, coupled, couple r. That last one with the space is
>> probably it and the space is likely a bug.

> My version (60.9.0) gives the same suggestions, so it's a bug.

>> Candy claimed to be able to modify the spelling function in TB.

> In the right-clicked menu, there's an 'Add to Dictionary' choice.

There it is in plain sight just like Candy said. No excuses...

> There I added 'coupler' (without space) and now when I type
> 'coupler' it's accepted as correct.

Worked with mine too.

> So I think Candy means you can *add* the correct spelling, not
> *modify* the existing lists.

My apology to the new guy who knew more than the old (in more ways than
one) guy...

>> Eternal-September has been taking 20 or more seconds to accept my
>> posts lately. Hope that's not a bad sign...

> As I suggested in another group (Candy might recognize it): "Get a
> proper NSP!" :-)

As long as you can see my post it's proper. But the day may come.
Remember aioe...

BTW my newsreader says you misspelled NSP! So I fixed it for you... ;)

On Fri, 20 Oct 2023 18:43:15 +0100, Andy Burns <usenet@andyburns.uk>
wrote:

>Frank Slootweg wrote:
>
>> Currently there are lots of reports (in the Windows groups), that the
>> latest major update, v115, is severely broken, probably mostly for news,
>> but maybe also for e-mail. (FWIW, I use 60.9.0).
>
>Enough with the FUD, plenty of us are happy with TB v115

I'm not sure it's FUD, since we all use different feature of TB, and
set its options differently.

But my experience is like yours. No problems with 115.

On 10/20/23 10:44, AJL wrote:
> On 10/20/2023 7:55 AM, candycanearter07 wrote:
>> On 10/19/23 17:15, AJL wrote:
>>> On 10/19/2023 3:02 PM, candycanearter07 wrote:
>
>>>> TB's spellcheck isn't the best. I've had to add a bunch of words
>>>>  to dictionary.
>>>
>>> Your headers still say you're using Betterbird not TB. You have TB
>>>  too?
>>
>> When I used TB. And BB has the same dictionary, I'm pretty sure.
>
> Pretty sure? Ah. Well I looked in my version of TB and couldn't find how
> to add words to the dictionary but that doesn't mean the capability's
> not hiding in there somewhere...

Just right click a highlighted word, then click Add to Dictionary.
--
user <candycane> is generated from /dev/urandom

On 10/20/23 14:19, AJL wrote:
> Frank Slootweg wrote:
>> AJL wrote:
>>> Candy claimed to be able to modify the spelling function in TB.
>
>> In the right-clicked menu, there's an 'Add to Dictionary' choice.
>
> There it is in plain sight just like Candy said. No excuses...
>
>> There I added 'coupler' (without space) and now when I type
>> 'coupler' it's accepted as correct.
>
> Worked with mine too.
>
>> So I think Candy means you can *add* the correct spelling, not
>> *modify* the existing lists.
>
> My apology to the new guy who knew more than the old (in more ways than
> one) guy...

I'm pretty sure almost every spell check system has a function to add
custom words..

>>> Eternal-September has been taking 20 or more seconds to accept my
>>> posts lately. Hope that's not a bad sign...
>
>> As I suggested in another group (Candy might recognize it): "Get a
>> proper NSP!" :-)
>
> As long as you can see my post it's proper. But the day may come.
> Remember aioe...
>
> BTW my newsreader says you misspelled NSP! So I fixed it for you...  ;)
>

Yea, I recognized it.
--
user <candycane> is generated from /dev/urandom