On 09/05/2023 03:06, J. P. Gilliver (John) wrote:
> On Tue, 9 May 2023 at 00:12:49, Phil <philusenet1458@gmx.com> wrote: (my
> responses usually follow points raised):
>>> What did they think new would come out of asking the same question
>>> that has
>>> been asked essentially once a month already by the same person asking
>>> it?
>>
>> Think you must have me confused with someone else. The first time I've
>> been on this newsgroup is today.
>
> I wrote this earlier.
>
> "Every post from Phil, AJL, T, Layman, Theo, micky and others is a repeat
> post already made hundreds of times already, that they copy & paste anew."
>
> You're all one and the same to me since you all repeat the same thing.
> Even if you're new, this is the most often asked question on this group.
>
> You should have searched first instead of rehashing it over & over again.

I think you should go back to bed, and then get out on the *proper* side.
--
Cheers,
Roger

On 5/8/2023 11:42 PM, Phil wrote:

> PhoNews seems to work pretty
> well on my Pixel 6a running Android 13. At least on the reading side.
> I'll give it a bit longer of a test before upgrading to the paid
> version, which allows posting.

You can go directly to all UNREAD posts in PhoNews:

tap comp.mobile.android > tap top right ground looking icon (second one
in) > tap 'unread'.

The newest unread posts are from the bottom up. It took me awhile to
find this. Saves time and clicks. If you already have, disregard.

My password bug is odd. Occasionally the app would complain that it
couldn't make contact with the server (eternal-september). I discovered
that the password had been scrambled and lengthened from 8 characters to
the whole line. Rebooting the app solved it and my old correct password
returned without having to reenter it. I haven't had the problem in
awhile now so maybe an update cured it. It happened on several of my
devices ranging from Android 9 to 12 and Chromebooks.

Compared to Thunderbird, PhoNews is a PITA to use (IMO). But at least it
works for me on my Android devices (most of the time). I'd be curious
how you find it after using it awhile...

> It's nice to be back on Usenet after all these years. It has reminded
> about every newsgroup having their resident 'Character' though :-)

I've quit Usenet more than once but always came back. Maybe the word
addicted applies. If you take your 'resident characters' as
entertainment, things look better... ;)

On Tue, 9 May 2023 03:06:20 +0100, "J. P. Gilliver (John)"
<G6JPG@255soft.uk> wrote:

>On Tue, 9 May 2023 at 00:12:49, Phil <philusenet1458@gmx.com> wrote: (my
>responses usually follow points raised):
>>> What did they think new would come out of asking the same question that has
>>> been asked essentially once a month already by the same person asking it?
>>
>> Think you must have me confused with someone else. The first time I've
>> been on this newsgroup is today.
>
>I wrote this earlier.
>
>"Every post from Phil, AJL, T, Layman, Theo, micky and others is a repeat
>post already made hundreds of times already, that they copy & paste anew."
>
>You're all one and the same to me since you all repeat the same thing.
>Even if you're new, this is the most often asked question on this group.
>
>You should have searched first instead of rehashing it over & over again.

Although I agree with that last statement, let me point out that not
everyone who comes to a newsgroup knows how to do a search on it or
even that searching is possible. So I really never blame anyone for
not first searching.

AJL <noemail@none.com> wrote:
> On 5/8/2023 10:53 AM, J. P. Gilliver (John) wrote:
> > AJL <noemail@none.com> wrote: (my responses
>
> >>> Every post from Phil, AJL, T, Layman, Theo, micky and others is a
> >>> repeat post already made hundreds of times already, that they copy &
> >>> paste anew.
>
> >> There might be somebody NEW that finds the info interesting and helpful.
>
> > None of those are new people but even if they were, a search is expected.
> > There can't be a more often asked question than this one asked again today.
>
> Plus extra space in this group is so very limited, huh.
>
> BTW nice beard.
> Saw your photo on this thread over in (gasp) Google Groups... :-O
>
> <https://groups.google.com/g/comp.mobile.android/c/p4eO5il5yyE>

I take it that you did not see/read/understand my responses (in this
thread) about this character?

Ken Blake <Ken@invalid.news.com> wrote:
> On Tue, 9 May 2023 03:06:20 +0100, "J. P. Gilliver (John)"
> <G6JPG@255soft.uk> wrote:
>
> >On Tue, 9 May 2023 at 00:12:49, Phil <philusenet1458@gmx.com> wrote: (my
> >responses usually follow points raised):
> >>> What did they think new would come out of asking the same question that has
> >>> been asked essentially once a month already by the same person asking it?
> >>
> >> Think you must have me confused with someone else. The first time I've
> >> been on this newsgroup is today.
> >
> >I wrote this earlier.
> >
> >"Every post from Phil, AJL, T, Layman, Theo, micky and others is a repeat
> >post already made hundreds of times already, that they copy & paste anew."
> >
> >You're all one and the same to me since you all repeat the same thing.
> >Even if you're new, this is the most often asked question on this group.
> >
> >You should have searched first instead of rehashing it over & over again.
>
>
> Although I agree with that last statement, let me point out that not
> everyone who comes to a newsgroup knows how to do a search on it or
> even that searching is possible. So I really never blame anyone for
> not first searching.

Please read - carefully - what (and to whom) you're responding. I
thought you knew the real JPG. I repeat: Let's be careful out there.

On 9 May 2023 17:45:41 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:

>Ken Blake <Ken@invalid.news.com> wrote:
>> On Tue, 9 May 2023 03:06:20 +0100, "J. P. Gilliver (John)"
>> <G6JPG@255soft.uk> wrote:
>>
>> >On Tue, 9 May 2023 at 00:12:49, Phil <philusenet1458@gmx.com> wrote: (my
>> >responses usually follow points raised):
>> >>> What did they think new would come out of asking the same question that has
>> >>> been asked essentially once a month already by the same person asking it?
>> >>
>> >> Think you must have me confused with someone else. The first time I've
>> >> been on this newsgroup is today.
>> >
>> >I wrote this earlier.
>> >
>> >"Every post from Phil, AJL, T, Layman, Theo, micky and others is a repeat
>> >post already made hundreds of times already, that they copy & paste anew."
>> >
>> >You're all one and the same to me since you all repeat the same thing.
>> >Even if you're new, this is the most often asked question on this group.
>> >
>> >You should have searched first instead of rehashing it over & over again.
>>
>>
>> Although I agree with that last statement, let me point out that not
>> everyone who comes to a newsgroup knows how to do a search on it or
>> even that searching is possible. So I really never blame anyone for
>> not first searching.
>
> Please read - carefully - what (and to whom) you're responding. I
>thought you knew the real JPG. I repeat: Let's be careful out there.

Thanks. I saw your post only after I sent this.

On 5/9/2023 10:40 AM, Frank Slootweg wrote:
> AJL <noemail@none.com> wrote:
>> On 5/8/2023 10:53 AM, J. P. Gilliver (John) wrote:

>>> None of those are new people but even if they were, a search is
>>> expected. There can't be a more often asked question than this
>>> one asked again today.

>> Plus extra space in this group is so very limited, huh.

>> BTW nice beard. Saw your photo on this thread over in (gasp) Google
>> Groups... :-O

> I take it that you did not see/read/understand my responses (in this
> thread) about this character?

You're saying that's really a picture of AH?? Not a bad looking dude.
But bottom line I really don't care much about nym shifting. Truth be
known I've shifted a few times myself in the last few decades. I also
don't filter anyone. As previously said I look on it as interesting
often helpful entertainment but take nothing seriously. But thanks
anyway for the warning...

On 09/05/2023 16:39, AJL wrote:
> On 5/8/2023 11:42 PM, Phil wrote:
>
>> PhoNews seems to work pretty
>> well on my Pixel 6a running Android 13. At least on the reading side.
>> I'll give it a bit longer of a test before upgrading to the paid
>> version, which allows posting.
>
> You can go directly to all UNREAD posts in PhoNews:
>
> tap comp.mobile.android > tap top right ground looking icon (second one
> in) > tap 'unread'.
>
> The newest unread posts are from the bottom up. It took me awhile to
> find this. Saves time and clicks. If you already have, disregard.
>
> My password bug is odd. Occasionally the app would complain that it
> couldn't make contact with the server (eternal-september). I discovered
> that the password had been scrambled and lengthened from 8 characters to
> the whole line. Rebooting the app solved it and my old correct password
> returned without having to reenter it. I haven't had the problem in
> awhile now so maybe an update cured it. It happened on several of my
> devices ranging from Android 9 to 12 and Chromebooks.
>
> Compared to Thunderbird, PhoNews is a PITA to use (IMO). But at least it
> works for me on my Android devices (most of the time). I'd be curious
> how you find it after using it awhile...
>
>> It's nice to be back on Usenet after all these years. It has reminded
>> about every newsgroup having their resident 'Character' though :-)
>
> I've quit Usenet more than once but always came back. Maybe the word
> addicted applies. If you take your 'resident characters' as
> entertainment, things look better...  ;)
>
>
Thanks for the tips AJL. Really useful.

AJL <noemail@none.com> wrote:
> On 5/9/2023 10:40 AM, Frank Slootweg wrote:
> > AJL <noemail@none.com> wrote:
> >> On 5/8/2023 10:53 AM, J. P. Gilliver (John) wrote:
>
> >>> None of those are new people but even if they were, a search is
> >>> expected. There can't be a more often asked question than this
> >>> one asked again today.
>
> >> Plus extra space in this group is so very limited, huh.
>
> >> BTW nice beard. Saw your photo on this thread over in (gasp) Google
> >> Groups... :-O
>
> > I take it that you did not see/read/understand my responses (in this
> > thread) about this character?
>
> You're saying that's really a picture of AH?? Not a bad looking dude.

No, if anything, it's probably a picture of the real JPG.

> But bottom line I really don't care much about nym shifting.

It's not about nym shifting, it's about forgery, forging other
posters' credentials (name, e-mail address, etc.). So not innocent at
all. As I implied in my other response, I verified this case,

> Truth be
> known I've shifted a few times myself in the last few decades.

Yes, I know, but the case I've seen was completely innocent.

And there can be valid reasons for using other nyms. (Not nym shifting,
but some extra nym(s).)

> I also
> don't filter anyone. As previously said I look on it as interesting
> often helpful entertainment but take nothing seriously. But thanks
> anyway for the warning...

I think it's wrong to respond to a known forger, except of course to
call him on his abuse. I hope others (i.e. also you) think likewise.

On 09/05/2023 17:04, Ken Blake wrote:
> On Tue, 9 May 2023 03:06:20 +0100, "J. P. Gilliver (John)"
> <G6JPG@255soft.uk> wrote:
>
>> On Tue, 9 May 2023 at 00:12:49, Phil <philusenet1458@gmx.com> wrote: (my
>> responses usually follow points raised):
>>>> What did they think new would come out of asking the same question that has
>>>> been asked essentially once a month already by the same person asking it?
>>>
>>> Think you must have me confused with someone else. The first time I've
>>> been on this newsgroup is today.
>>
>> I wrote this earlier.
>>
>> "Every post from Phil, AJL, T, Layman, Theo, micky and others is a repeat
>> post already made hundreds of times already, that they copy & paste anew."
>>
>> You're all one and the same to me since you all repeat the same thing.
>> Even if you're new, this is the most often asked question on this group.
>>
>> You should have searched first instead of rehashing it over & over again.
>
>
> Although I agree with that last statement, let me point out that not
> everyone who comes to a newsgroup knows how to do a search on it or
> even that searching is possible. So I really never blame anyone for
> not first searching.
>
I fall into that category I'm afraid Ken. When I first subscribed to
this group I only downloaded 2,000 headers, so searching that might not
have turned much up. I'll educate myself and ask Google what the best
way to search Usenet is.

On 5/9/2023 1:23 PM, Frank Slootweg wrote:
> AJL <noemail@none.com> wrote:

>> I really don't care much about nym shifting.

> It's not about nym shifting, it's about forgery, forging other
> posters' credentials (name, e-mail address, etc.). So not innocent at
> all. As I implied in my other response, I verified this case,

Ah. I did misunderstand then.

> I think it's wrong to respond to a known forger,

Agreed.

> except of course to call him on his abuse.

If you KNOW he's a true forger why respond at all?

> I hope others (i.e. also you) think likewise.

I do. But for us less quick souls perhaps any future verified forgery
warnings could be a little less cryptic? I used to say call a spade a
spade but I guess that's not PC anymore...

AJL <noemail@none.com> wrote:
> On 5/9/2023 1:23 PM, Frank Slootweg wrote:
> > AJL <noemail@none.com> wrote:
>
> >> I really don't care much about nym shifting.
>
> > It's not about nym shifting, it's about forgery, forging other
> > posters' credentials (name, e-mail address, etc.). So not innocent at
> > all. As I implied in my other response, I verified this case,
>
> Ah. I did misunderstand then.
>
> > I think it's wrong to respond to a known forger,
>
> Agreed.
>
> > except of course to call him on his abuse.
>
> If you KNOW he's a true forger why respond at all?

I agree, but others seem to act (think?) differently.

> > I hope others (i.e. also you) think likewise.
>
> I do. But for us less quick souls perhaps any future verified forgery
> warnings could be a little less cryptic? I used to say call a spade a
> spade but I guess that's not PC anymore...

Being less cryptic might be risky for the one giving the warning. Not
too long ago a forger tried to destroy the victim and the group. It took
a long time for the dust to settle down and much harm was done to both
the victim and the group.

On 5/10/2023 8:29 AM, Frank Slootweg wrote:
> AJL <noemail@none.com> wrote:

>> for us less quick souls perhaps any future verified forgery
>> warnings could be a little less cryptic?

> Being less cryptic might be risky for the one giving the warning.

You don't think the forger quickly figured out that YOU were giving the
(cryptic) warnings seeing as how you obviously were referring to his
posts? Even dense me knew you were referring to him. But I thought you
meant AH had taken yet another new nym since I was not previously
familiar with the nym. And the forger even sounded like him... 8-O

> Not too long ago a forger tried to destroy the victim

From your short description I'm going to guess that the victim somehow
pissed off the forger who then wanted revenge. Typical Usenet carried a
little too far.

> and the group. It took a long time for the dust to settle down and
> much harm was done to both the victim and the group.

Too bad. Fortunately Usenet is just a pastime for me. If things get
unpleasant (beyond the normal) I just disappear or take a new nym as
I've done a few times before. Anonymity is both the curse and the
greatness of the place...

AJL <noemail@none.com> wrote:
> On 5/10/2023 8:29 AM, Frank Slootweg wrote:
> > AJL <noemail@none.com> wrote:
>
> >> for us less quick souls perhaps any future verified forgery
> >> warnings could be a little less cryptic?
>
> > Being less cryptic might be risky for the one giving the warning.
>
> You don't think the forger quickly figured out that YOU were giving the
> (cryptic) warnings seeing as how you obviously were referring to his
> posts? Even dense me knew you were referring to him.

Yes, but people react differently to different levels of 'talkback'.

> But I thought you
> meant AH had taken yet another new nym since I was not previously
> familiar with the nym. And the forger even sounded like him... 8-O

I don't think your thinking is incompatible with my thinking. I think
:-) we're thinking the same thing.

> > Not too long ago a forger tried to destroy the victim
>
> From your short description I'm going to guess that the victim somehow
> pissed off the forger who then wanted revenge. Typical Usenet carried a
> little too far.

Some people do not require anything substantial, to get/act pissed
off. Just any talking back at them is enough. AH?

> > and the group. It took a long time for the dust to settle down and
> > much harm was done to both the victim and the group.
>
> Too bad. Fortunately Usenet is just a pastime for me. If things get
> unpleasant (beyond the normal) I just disappear or take a new nym as
> I've done a few times before. Anonymity is both the curse and the
> greatness of the place...

I've always posted with my real name [1] and do not want to change/
lose that. Different strokes for different folks.

[1] Except for two nyms in (non-technical) groups where privacy is
important.

On 08/05/2023 13:28, Phil wrote:
>Hi all,
>
>Any recommendations for a Usenet app for Android. Only needed for text
>groups. Thanks.
Well after testing for a while I've upgraded to the paid version of PhoNews,
which allows posting. I'm using it now.

On 5/14/23 7:20 PM, Phil wrote:

> Well after testing for a while I've upgraded to the paid version of PhoNews,
> which allows posting. I'm using it now.

Congrats. I'll answer you using my PhoNews app. This one is installed on a
Chromebook. It just crashed but that may be (I hope) because I just turned
the Chromebook on after a few weeks and it was busy updating things. Seems
OK now though. Wonder what devices you're using PhoNews on. And I'd be
curious as to your opinion after using it for awhile...

On 15/05/2023 04:08, AJL wrote:
>On 5/14/23 7:20 PM, Phil wrote:
>
>> Well after testing for a while I've upgraded to the paid version of PhoNews,
>> which allows posting. I'm using it now.
>
>Congrats. I'll answer you using my PhoNews app. This one is installed on a
> Chromebook. It just crashed but that may be (I hope) because I just turned
> the Chromebook on after a few weeks and it was busy updating things. Seems
> OK now though. Wonder what devices you're using PhoNews on. And I'd be
> curious as to your opinion after using it for awhile...
>
>
Hi, I'm just using it on my Google Pixel 6a (Android 13) at the moment.
Seems to work pretty well. One thing I noticed that doesn't work is
changing the text size (through the settings).

It occasionally has a bit of a wobble where it won't load the messages in a
newsgroup, but closing and restarting the app usually fixes that. It's not
a regular thing, but is a slight annoyance.

I'll report back after using it a bit more.

On 15/05/2023 04:30, Phil wrote:
>On 15/05/2023 04:08, AJL wrote:
>>On 5/14/23 7:20 PM, Phil wrote:
>>
>>> Well after testing for a while I've upgraded to the paid version of PhoNews,
>>> which allows posting. I'm using it now.
>>
>>Congrats. I'll answer you using my PhoNews app. This one is installed on a
>> Chromebook. It just crashed but that may be (I hope) because I just turned
>> the Chromebook on after a few weeks and it was busy updating things. Seems
>> OK now though. Wonder what devices you're using PhoNews on. And I'd be
>> curious as to your opinion after using it for awhile...
>>
>>
>Hi, I'm just using it on my Google Pixel 6a (Android 13) at the moment.
> Seems to work pretty well. One thing I noticed that doesn't work is
> changing the text size (through the settings).
>
>It occasionally has a bit of a wobble where it won't load the messages in a
> newsgroup, but closing and restarting the app usually fixes that. It's not
> a regular thing, but is a slight annoyance.
>
>I'll report back after using it a bit more.
>
>
>
.....Bit of a strange one. When reading my last post from PhoNews on
Thunderbird, paragraph breaks don't seem to appear.

Strange!

On 5/14/23 8:30 PM, Phil wrote:
>On 15/05/2023 04:08, AJL wrote:

>> Wonder what devices you're using PhoNews on.

> I'm just using it on my Google Pixel 6a (Android 13) at the moment.
> Seems to work pretty well.

I have it on my phone too (Galaxy S10+, Android 12). It did that password
bug that I earlier posted about on my phone. I see from the headers that we
have the same version of PhoNews so at least I'm apparently up to date now.
Crossing fingers that the bug's gone after the last update.

< One thing I noticed that doesn't work is
> changing the text size (through the settings).

I just tried to change my text size and mine doesn't work either.

> It occasionally has a bit of a wobble where it won't load the messages in a
> newsgroup, but closing and restarting the app usually fixes that. It's not
> a regular thing, but is a slight annoyance.

I don't have that problem. Perhaps the device? Try it on any other Android
devices you have...

>I'll report back after using it a bit more.

Appreciate it.

On 5/14/2023 8:41 PM, Phil wrote:

> ....Bit of a strange one. When reading my last post from PhoNews on
> Thunderbird, paragraph breaks don't seem to appear. Strange!

Dunno. I switched to Thunderbird and you were missing a paragraph break
on your first PhoNews announcement post, but I do see breaks (between
our comments) on your last 2 posts, some more than one line wide...

On Sun, 14 May 2023 21:35:48 -0700, AJL <noemail@none.com> wrote:
> On 5/14/2023 8:41 PM, Phil wrote:

> > ....Bit of a strange one. When reading my last post from PhoNews
on
> > Thunderbird, paragraph breaks don't seem to appear. Strange!

> Dunno. I switched to Thunderbird and you were missing a paragraph
break
> on your first PhoNews announcement post,

I'm now using Groundhog on an Amazon tablet. On this newsreader
I see breaks on ALL your PhoNews posts. Apparently a newsreader
reading thing...

On 5/14/2023 10:41 PM, AJL wrote:
> On Sun, 14 May 2023 21:35:48 -0700, AJL <noemail@none.com> wrote:
>> On 5/14/2023 8:41 PM, Phil wrote:
>
>> > ....Bit of a strange one. When reading my last post from PhoNews
> on
>> > Thunderbird, paragraph breaks don't seem to appear. Strange!
>
>> Dunno. I switched to Thunderbird and you were missing a paragraph
> break
>> on your first PhoNews announcement post,
>
> I'm now using Groundhog on an Amazon tablet. On this newsreader
> I see breaks on ALL your PhoNews posts. Apparently a newsreader reading
> thing...

And I now see that my Groundhog app is screwing up the quotes. Back to
my original OPINION: There just doesn't appear to be any good Android
newsreader anymore...

On 15/05/2023 06:52, AJL wrote:
> On 5/14/2023 10:41 PM, AJL wrote:
>> On Sun, 14 May 2023 21:35:48 -0700, AJL <noemail@none.com> wrote:
>>> On 5/14/2023 8:41 PM, Phil wrote:
>>
>>> > ....Bit of a strange one. When reading my last post from PhoNews
>> on
>>> > Thunderbird, paragraph breaks don't seem to appear. Strange!
>>
>>> Dunno. I switched to Thunderbird and you were missing a paragraph
>> break
>>> on your first PhoNews announcement post,
>>
>> I'm now using Groundhog on an Amazon tablet. On this newsreader
>> I see breaks on ALL your PhoNews posts. Apparently a newsreader reading
>> thing...
>
> And I now see that my Groundhog app is screwing up the quotes. Back to
> my original OPINION: There just doesn't appear to be any good Android
> newsreader anymore...

Yes, seems nothing is anywhere near perfect. I suppose Usenet is niche,
so nobody puts much effort in to developing apps.

On 08/05/2023 20:17, Ralph Fox wrote:

> On Mon, 8 May 2023 13:28:49 +0100, Phil wrote:
>
>> Hi all,
>>
>> Any recommendations for a Usenet app for Android. Only needed for text
>> groups. Thanks.
>
> I am using NewsGroup Reader
> <https://play.google.com/store/apps/details?id=net.piaohong.newsgroup>

+1