Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #156853 > unrolled thread
| Started by | MCSM <despammed@mcsm.anonaddy.me> |
|---|---|
| First post | 2026-11-06 13:04 +0100 |
| Last post | 2026-11-09 18:08 +0000 |
| Articles | 20 on this page of 22 — 7 participants |
Back to article view | Back to comp.mobile.android
[NeReO] - 1.6.1 is available MCSM <despammed@mcsm.anonaddy.me> - 2026-11-06 13:04 +0100
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-07 05:11 +0000
Re: [NeReO] - 1.6.1 is available MCSM <despammed@mcsm.anonaddy.me> - 2026-11-07 21:42 +0000
Re: [NeReO] - 1.6.1 is available Dave Royal <dave@dave123royal.com> - 2026-11-07 22:21 +0000
Re: [NeReO] - 1.6.1 is available MCSM <despammed@mcsm.anonaddy.me> - 2026-11-08 09:11 +0000
Re: [NeReO] - 1.6.1 is available Dave Royal <dave@dave123royal.com> - 2026-11-08 09:48 +0000
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-08 05:03 +0000
Re: [NeReO] - 1.6.1 is available "s|b" <me@privacy.invalid> - 2026-11-08 14:50 +0100
Re: [NeReO] - 1.6.1 is available "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-11-08 14:23 +0000
Re: [NeReO] - 1.6.1 is available snipeco.2@gmail.com (Sn!pe) - 2026-11-08 20:25 +0000
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-08 22:14 +0000
Re: [NeReO] - 1.6.1 is available "s|b" <me@privacy.invalid> - 2026-11-09 17:09 +0100
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-09 18:07 +0000
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-09 18:29 +0000
Re: [NeReO] - 1.6.1 is available [OT] "s|b" <me@privacy.invalid> - 2026-11-10 14:19 +0100
Re: [NeReO] - 1.6.1 is available snipeco.2@gmail.com (Sn!pe) - 2026-11-10 16:13 +0000
Re: [NeReO] - 1.6.1 is available Bill H <billh@domain.is.invalid> - 2026-11-10 08:17 -0800
Re: [NeReO] - 1.6.1 is available "s|b" <me@privacy.invalid> - 2026-11-12 17:28 +0100
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-08 22:12 +0000
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-08 22:11 +0000
Re: [NeReO] - 1.6.1 is available MCSM <despammed@mcsm.anonaddy.me> - 2026-11-09 09:01 +0100
Re: [NeReO] - 1.6.1 is available "BillH" <billh@domain.is.invalid> - 2026-11-09 18:08 +0000
Page 1 of 2 [1] 2 Next page →
| From | MCSM <despammed@mcsm.anonaddy.me> |
|---|---|
| Date | 2026-11-06 13:04 +0100 |
| Subject | [NeReO] - 1.6.1 is available |
| Message-ID | <mn.33107eab21959030.0@mcsm.org> |
NeReO 1.6.1 is out. NeReO is a text-only Usenet newsreader for Android
(8.0 or later), free and open source (GPL-3.0).
Download:
SourceForge: (direct DL)
https://sourceforge.net/projects/nereo/files/latest/download
GitHub:
https://github.com/mcsm64/NeReO/releases/tag/v1.6.1
Fixed:
- A long signature is no longer cut
- Reflow keeps columns, lone links and breaks after a full stop
- The next unread button stays in the thread
- A server that does not answer no longer stops the others
New:
- Bold, italics and underline as in MesNews
- A notice when a message was posted to another group
- Followed threads on top only while they have unread messages
Thanks to BIG Umberto for the reports and tests, to Dave Royal for
messages from another group, and to Cercaparole, Michele and Roxy for
the order of followed threads.
--
.:. MCSM .:.
-> posting from PC with MesNews <-
[toc] | [next] | [standalone]
| From | "BillH" <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-07 05:11 +0000 |
| Message-ID | <11cmbu9$35lk9$1@dont-email.me> |
| In reply to | #156853 |
On 11/6/2026 at 4:04:36 AM MCSM wrote: > NeReO 1.6.1 is out. NeReO is a text-only Usenet newsreader for Android > (8.0 or later), free and open source (GPL-3.0). > > Download: > SourceForge: (direct DL) > https://sourceforge.net/projects/nereo/files/latest/download > GitHub: > https://github.com/mcsm64/NeReO/releases/tag/v1.6.1 > > Fixed: > - A long signature is no longer cut > - Reflow keeps columns, lone links and breaks after a full stop > - The next unread button stays in the thread > - A server that does not answer no longer stops the others > > New: > - Bold, italics and underline as in MesNews > - A notice when a message was posted to another group > - Followed threads on top only while they have unread messages > > Thanks to BIG Umberto for the reports and tests, to Dave Royal for > messages from another group, and to Cercaparole, Michele and Roxy for > the order of followed threads. How about something that is not in this list. A new setting to allow changing the date format to MM/DD/YY for those of us in the United States.
[toc] | [prev] | [next] | [standalone]
| From | MCSM <despammed@mcsm.anonaddy.me> |
|---|---|
| Date | 2026-11-07 21:42 +0000 |
| Message-ID | <iXMHS.42735$sxp1.18921@usenetxs.com> |
| In reply to | #156865 |
"BillH" , torturando le sue meningi, ha scritto: > On 11/6/2026 at 4:04:36 AM MCSM wrote: > >> NeReO 1.6.1 is out. NeReO is a text-only Usenet newsreader for >> Android >> (8.0 or later), free and open source (GPL-3.0). >> >> Download: >> SourceForge: (direct DL) >> https://sourceforge.net/projects/nereo/files/latest/download >> GitHub: >> https://github.com/mcsm64/NeReO/releases/tag/v1.6.1 >> >> Fixed: >> - A long signature is no longer cut >> - Reflow keeps columns, lone links and breaks after a full stop >> - The next unread button stays in the thread >> - A server that does not answer no longer stops the others >> >> New: >> - Bold, italics and underline as in MesNews >> - A notice when a message was posted to another group >> - Followed threads on top only while they have unread messages >> >> Thanks to BIG Umberto for the reports and tests, to Dave Royal for >> messages from another group, and to Cercaparole, Michele and Roxy for >> the order of followed threads. > > How about something that is not in this list. A new setting to allow > changing > the date format to MM/DD/YY for those of us in the United States. Hi, good point, and it's not just cosmetic: today NeReO always shows day/month, so 07/11/26 reads as July 11 to an American, while it's November 7. I'll add a "Date format" setting with DD/MM/YY (the current default), MM/DD/YY and YYYY-MM-DD. It will also apply to the date in your quote introduction (%date%), so your replies use your format. One question: would you also like 12-hour time (3:45 PM) instead of 24-hour (15:45), or is the date enough? -- .:. MCSM .:. posting with NeReO 1.6.1
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal <dave@dave123royal.com> |
|---|---|
| Date | 2026-11-07 22:21 +0000 |
| Message-ID | <11co88h$3roe6$1@dont-email.me> |
| In reply to | #156873 |
MCSM wrote: > > I'll add a "Date format" setting with DD/MM/YY (the current default), > MM/DD/YY and YYYY-MM-DD. *It will also apply to the date in your quote > introduction (%date%), so your replies use your format.* A date in a quote attribution would preferably include the timezone, so that a reader of the reply can match it to a post in his own newsreader. -- Remove numerics from my email address.
[toc] | [prev] | [next] | [standalone]
| From | MCSM <despammed@mcsm.anonaddy.me> |
|---|---|
| Date | 2026-11-08 09:11 +0000 |
| Message-ID | <%0XHS.27450$DWye.5756@usenetxs.com> |
| In reply to | #156874 |
Dave Royal , torturando le sue meningi, ha scritto: > MCSM wrote: >> >> I'll add a "Date format" setting with DD/MM/YY (the current default), >> MM/DD/YY and YYYY-MM-DD. *It will also apply to the date in your >> quote >> introduction (%date%), so your replies use your format.* > > A date in a quote attribution would preferably include the timezone, > so > that a reader of the reply can match it to a post in his own > newsreader. > Good point: today the time in the attribution is in the replier's local zone, without saying so. I'll add two optional placeholders: one for the zone offset (+0100), and one that copies the original Date: line as it is, so readers can match the post in their own newsreader. I'll do It in next release (as and option) -- .:. MCSM .:. posting with NeReO 1.6.1
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal <dave@dave123royal.com> |
|---|---|
| Date | 2026-11-08 09:48 +0000 |
| Message-ID | <11cpghf$6t2l$1@dont-email.me> |
| In reply to | #156878 |
MCSM wrote: > Dave Royal , torturando le sue meningi, ha scritto: > > MCSM wrote: > >> > >> I'll add a "Date format" setting with DD/MM/YY (the current > >> default), > >> MM/DD/YY and YYYY-MM-DD. *It will also apply to the date in your > >> quote > >> introduction (%date%), so your replies use your format.* > > > > A date in a quote attribution would preferably include the timezone, > > so > > that a reader of the reply can match it to a post in his own > > newsreader. > > > > Good point: today the time in the attribution is in the replier's > local zone, without saying so. I'll add two optional placeholders: one > for the zone offset (+0100), and one that copies the original Date: > line as it is, so readers can match the post in their own newsreader. > I'll do It in next release (as and option) There's a Thunderbird addon that has 3 options for a date in a quote attribution IIRC: - the replier's local date - the quoted author's local date - international format It depends who you think the date is aimed at. -- Remove numerics from my email address.
[toc] | [prev] | [next] | [standalone]
| From | "BillH" <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-08 05:03 +0000 |
| Message-ID | <11covrm$15662$1@solani.org> |
| In reply to | #156873 |
Thanks for the reply, Yes, a 12 hour clock with AM and PM would be preferred. Not many folks in the US use the 24 hour clock. Mostly military and scientific folks (although there are others as well).
[toc] | [prev] | [next] | [standalone]
| From | "s|b" <me@privacy.invalid> |
|---|---|
| Date | 2026-11-08 14:50 +0100 |
| Message-ID | <nlbcusFh9a7U4@mid.individual.net> |
| In reply to | #156875 |
On Sun, 8 Nov 2026 05:03:50 -0000 (UTC), BillH wrote: > Thanks for the reply, > > Yes, a 12 hour clock with AM and PM would be preferred. Not many folks in the > US use the 24 hour clock. Mostly military and scientific folks (although there > are others as well). Not many people in the world use AM and PM. (-; -- Horum omnium fortissimi sunt Belgae. - Julius Caesar
[toc] | [prev] | [next] | [standalone]
| From | "Kerr-Mudd, John" <admin@127.0.0.1> |
|---|---|
| Date | 2026-11-08 14:23 +0000 |
| Message-ID | <20261108142324.4e64fab2414cf203b66980ba@127.0.0.1> |
| In reply to | #156882 |
On Sun, 08 Nov 2026 14:50:26 +0100 "s|b" <me@privacy.invalid> wrote: > On Sun, 8 Nov 2026 05:03:50 -0000 (UTC), BillH wrote: > > > Thanks for the reply, > > > > Yes, a 12 hour clock with AM and PM would be preferred. Not many folks in the > > US use the 24 hour clock. Mostly military and scientific folks (although there > > are others as well). > > Not many people in the world use AM and PM. (-; > Use ISO, don't both catering for these minority US folk with their non-compliant measurements. </troll> -- Bah, and indeed Humbug.
[toc] | [prev] | [next] | [standalone]
| From | snipeco.2@gmail.com (Sn!pe) |
|---|---|
| Date | 2026-11-08 20:25 +0000 |
| Message-ID | <1s49v8p.1t7u0x31n0uo1eN%snipeco.2@gmail.com> |
| In reply to | #156883 |
Kerr-Mudd, John <admin@127.0.0.1> wrote: > On Sun, 08 Nov 2026 14:50:26 +0100 > "s|b" <me@privacy.invalid> wrote: > > > On Sun, 8 Nov 2026 05:03:50 -0000 (UTC), BillH wrote: > > > > > Thanks for the reply, > > > > > > Yes, a 12 hour clock with AM and PM would be preferred. Not many > > > folks in the US use the 24 hour clock. Mostly military and scientific > > > folks (although there are others as well). > > > > Not many people in the world use AM and PM. (-; > > > > Use ISO, don't both catering for these minority US folk with their > non-compliant measurements. </troll> > 24 hour UTC for me, TYVM. -- Sn!pe, birdbrain. My pet rock Gordon just is.
[toc] | [prev] | [next] | [standalone]
| From | "BillH" <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-08 22:14 +0000 |
| Message-ID | <11cqs8n$oh5f$1@dont-email.me> |
| In reply to | #156888 |
On 11/8/2026 at 12:25:56 PM Sn!pe wrote: > Kerr-Mudd, John <admin@127.0.0.1> wrote: > > > On Sun, 08 Nov 2026 14:50:26 +0100 > > "s|b" <me@privacy.invalid> wrote: > > > > > On Sun, 8 Nov 2026 05:03:50 -0000 (UTC), BillH wrote: > > > > > > > Thanks for the reply, > > > > > > > > Yes, a 12 hour clock with AM and PM would be preferred. Not many > > > > folks in the US use the 24 hour clock. Mostly military and scientific > > > > folks (although there are others as well). > > > > > > Not many people in the world use AM and PM. (-; > > > > > > > Use ISO, don't both catering for these minority US folk with their > > non-compliant measurements. </troll> > > > > 24 hour UTC for me, TYVM. Why not support both unless you don't want the app used in the US. DD/MM/YY will confuse a lot of people in the US.
[toc] | [prev] | [next] | [standalone]
| From | "s|b" <me@privacy.invalid> |
|---|---|
| Date | 2026-11-09 17:09 +0100 |
| Message-ID | <nle9fmF2em2U3@mid.individual.net> |
| In reply to | #156892 |
On Sun, 8 Nov 2026 22:14:47 -0000 (UTC), BillH wrote: > Why not support both unless you don't want the app used in the US. DD/MM/YY > will confuse a lot of people in the US. Funny anecdote: today I was watching the (American) TV show 'See No Evil' about surveillance cameras used to solve murders. Every timestamp I saw was either 20/10/2008 or 2008-10-20 23:05:01 Surveillance cameras don't confuse people in the US? (-; -- Horum omnium fortissimi sunt Belgae. - Julius Caesar
[toc] | [prev] | [next] | [standalone]
| From | "BillH" <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-09 18:07 +0000 |
| Message-ID | <11ct25g$1fua0$1@dont-email.me> |
| In reply to | #156911 |
On 11/9/2026 at 8:09:33 AM s|b wrote: > On Sun, 8 Nov 2026 22:14:47 -0000 (UTC), BillH wrote: > > > Why not support both unless you don't want the app used in the US. DD/MM/YY > > will confuse a lot of people in the US. > > Funny anecdote: today I was watching the (American) TV show 'See No > Evil' about surveillance cameras used to solve murders. Every timestamp > I saw was either > > 20/10/2008 > > or > > 2008-10-20 23:05:01 > > Surveillance cameras don't confuse people in the US? (-; The could. Not so much with a date lieke 20/10/2008 which is oviously October 10th. Something like 07/01/2026 would be confusing. Is it Jule 1 or January 7?
[toc] | [prev] | [next] | [standalone]
| From | "BillH" <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-09 18:29 +0000 |
| Message-ID | <11ct3dt$19gq9$1@solani.org> |
| In reply to | #156914 |
On 11/9/2026 at 10:07:44 AM BillH wrote: > On 11/9/2026 at 8:09:33 AM s|b wrote: > > > On Sun, 8 Nov 2026 22:14:47 -0000 (UTC), BillH wrote: > > > > > Why not support both unless you don't want the app used in the US. > > > DD/MM/YY will confuse a lot of people in the US. > > > > Funny anecdote: today I was watching the (American) TV show 'See No > > Evil' about surveillance cameras used to solve murders. Every timestamp > > I saw was either > > > > 20/10/2008 > > > > or > > > > 2008-10-20 23:05:01 > > > > Surveillance cameras don't confuse people in the US? (-; > > The could. Not so much with a date lieke 20/10/2008 which is oviously October > 10th. Something like 07/01/2026 would be confusing. Is it Jule 1 or January > 7? Don't know what happened here with the spelling. I meant: They could. Not so much with a date like 20/10/2008 which is obvisously October 10th. Something like 07/01/2026 could be... Is it July 1 or January 7?
[toc] | [prev] | [next] | [standalone]
| From | "s|b" <me@privacy.invalid> |
|---|---|
| Date | 2026-11-10 14:19 +0100 |
| Subject | Re: [NeReO] - 1.6.1 is available [OT] |
| Message-ID | <nlgjthFdud1U3@mid.individual.net> |
| In reply to | #156914 |
On Mon, 9 Nov 2026 18:07:44 -0000 (UTC), BillH wrote: > On 11/9/2026 at 8:09:33 AM s|b wrote: > > > On Sun, 8 Nov 2026 22:14:47 -0000 (UTC), BillH wrote: > > > > > Why not support both unless you don't want the app used in the US. DD/MM/YY > > > will confuse a lot of people in the US. > > > > Funny anecdote: today I was watching the (American) TV show 'See No > > Evil' about surveillance cameras used to solve murders. Every timestamp > > I saw was either > > > > 20/10/2008 > > > > or > > > > 2008-10-20 23:05:01 > > > > Surveillance cameras don't confuse people in the US? (-; > The could. Not so much with a date lieke 20/10/2008 which is oviously October > 10th. Something like 07/01/2026 would be confusing. Is it Jule 1 or January 7? I just found it weird that those cameras were using that date format instead of the one that (most of) the US is used to. -- Horum omnium fortissimi sunt Belgae. - Julius Caesar
[toc] | [prev] | [next] | [standalone]
| From | snipeco.2@gmail.com (Sn!pe) |
|---|---|
| Date | 2026-11-10 16:13 +0000 |
| Message-ID | <1s4d7ys.js1xzll2ldutN%snipeco.2@gmail.com> |
| In reply to | #156914 |
BillH <billh@domain.is.invalid> wrote: > On 11/9/2026 at 8:09:33 AM s|b wrote: > > > On Sun, 8 Nov 2026 22:14:47 -0000 (UTC), BillH wrote: > > > > > Why not support both unless you don't want the app used in the US. > > > DD/MM/YY will confuse a lot of people in the US. > > > > Funny anecdote: today I was watching the (American) TV show 'See No > > Evil' about surveillance cameras used to solve murders. Every timestamp > > I saw was either > > > > 20/10/2008 > > > > or > > > > 2008-10-20 23:05:01 > > > > Surveillance cameras don't confuse people in the US? (-; > > The could. Not so much with a date lieke 20/10/2008 which is oviously > October 10th. Something like 07/01/2026 would be confusing. Is it Jule 1 > or January 7? > BillH says: "20/10/2008 which is oviously October 10th." ≈:o) If the MM/DD/YYY rule is followed it should be "Icosaber 10th." -- Sn!pe, birdbrain. My pet rock Gordon just is.
[toc] | [prev] | [next] | [standalone]
| From | Bill H <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-10 08:17 -0800 |
| Message-ID | <11cvg3j$29t22$1@dont-email.me> |
| In reply to | #156919 |
On 11/10/2026 8:13 AM, Sn!pe wrote: > BillH <billh@domain.is.invalid> wrote: > >> On 11/9/2026 at 8:09:33 AM s|b wrote: >> >> > On Sun, 8 Nov 2026 22:14:47 -0000 (UTC), BillH wrote: >> > >> > > Why not support both unless you don't want the app used in the US. >> > > DD/MM/YY will confuse a lot of people in the US. >> > >> > Funny anecdote: today I was watching the (American) TV show 'See No >> > Evil' about surveillance cameras used to solve murders. Every timestamp >> > I saw was either >> > >> > 20/10/2008 >> > >> > or >> > >> > 2008-10-20 23:05:01 >> > >> > Surveillance cameras don't confuse people in the US? (-; >> >> The could. Not so much with a date lieke 20/10/2008 which is oviously >> October 10th. Something like 07/01/2026 would be confusing. Is it Jule 1 >> or January 7? >> > > BillH says: "20/10/2008 which is oviously October 10th." ≈:o) > > If the MM/DD/YYY rule is followed it should be "Icosaber 10th." > I was obviously not checking what I typed. I meant October 20th. Oh well. :-(
[toc] | [prev] | [next] | [standalone]
| From | "s|b" <me@privacy.invalid> |
|---|---|
| Date | 2026-11-12 17:28 +0100 |
| Message-ID | <nlm7nkFakqfU5@mid.individual.net> |
| In reply to | #156920 |
On Tue, 10 Nov 2026 08:17:55 -0800, Bill H wrote: > I was obviously not checking what I typed. I meant October 20th. Oh > well. :-( We all knew that. (-; -- Horum omnium fortissimi sunt Belgae. - Julius Caesar
[toc] | [prev] | [next] | [standalone]
| From | "BillH" <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-08 22:12 +0000 |
| Message-ID | <11cqs4l$og0h$1@dont-email.me> |
| In reply to | #156883 |
On 11/8/2026 at 6:23:24 AM Kerr-Mudd, John wrote: > On Sun, 08 Nov 2026 14:50:26 +0100 > "s|b" <me@privacy.invalid> wrote: > > > On Sun, 8 Nov 2026 05:03:50 -0000 (UTC), BillH wrote: > > > > > Thanks for the reply, > > > > > > Yes, a 12 hour clock with AM and PM would be preferred. Not many folks > > > in the US use the 24 hour clock. Mostly military and scientific folks > > > (although there are others as well). > > > > Not many people in the world use AM and PM. (-; > > > > Use ISO, don't both catering for these minority US folk with their > non-compliant measurements. </troll> It is compliant here in the US. That is why I suggested it as an option, not as a change for everyone.
[toc] | [prev] | [next] | [standalone]
| From | "BillH" <billh@domain.is.invalid> |
|---|---|
| Date | 2026-11-08 22:11 +0000 |
| Message-ID | <11cqs2e$of9h$1@dont-email.me> |
| In reply to | #156882 |
On 11/8/2026 at 5:50:26 AM s|b wrote: > On Sun, 8 Nov 2026 05:03:50 -0000 (UTC), BillH wrote: > > > Thanks for the reply, > > > > Yes, a 12 hour clock with AM and PM would be preferred. Not many folks in > > the US use the 24 hour clock. Mostly military and scientific folks > > (although there are others as well). > > Not many people in the world use AM and PM. (-; I agree. That is why I suggested it as an option, not as a change for everyone.
[toc] | [prev] | [next] | [standalone]
Page 1 of 2 [1] 2 Next page →
Back to top | Article view | comp.mobile.android
csiph-web