posting from PC with MesNews <-
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.
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.
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.*
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.
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)
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).
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. (-;
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>
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. (-;
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>
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.
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.
posting from PC with MesNews <-
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.
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? (-;
On 08/11/2026 , BillH wrote:
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.
Please note:
This answer is in your last message, but is made for everyone!
Hi all,
thanks again, this has been a useful discussion. You're all right,
because you're asking for different things, and nothing stops NeReO from offering all of them as options.
The defaults will stay as they are today, so nobody sees anything change unless they choose to.
*Planned for the next release*
under Appearance -> Date and time:
- Date format: DD/MM/YY (default), MM/DD/YY, YYYY-MM-DD (ISO)
- Clock: 24-hour (default), 12-hour with AM/PM
- Time zone: phone's local time (default), UTC
So...
BillH gets 11/07/26 3:45 PM
Kerr-Mudd,John gets 2026-11-07
Sn!pe gets 24-hour UTC.
For the date in the quote attribution, following Dave's Thunderbird
example, you'll be able to choose whose time it shows:
- your own local time (default, as today)
- the quoted author's local time (as in their Date: line)
- international: ISO date and time in UTC
plus two optional placeholders: the zone offset (+0100) and the
original Date: line copied as it is.
Hope this will satisfy all of You ^^ ;)
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?
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 <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. :-(
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498678:20:20 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 912 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,867 |