I'm slowly migrating everything over from Windows to Linux. I have a
list of apps and functions that I use on Windows 11, checking each one
off when I have a Linux-based solution. When I have the list
completed, I'll cut over to Linux and not shed much of a tear....
One that I'm trying to check off is my newsreader. I've been using
Agent for years, but the developer has shelved further development of
the app and a few months ago stopped their newsgroup service as well.
Before that I used Gravity, which has been revived by Steve Gibson of
Gibson Research, but it isn't being produced for Linux, just Windows.
Question: What newsreader does the collective brain trust here
consider the best option, and why?
I'm using the latest version of Ubuntu Cinnamon, if that helps.
Thanks muchly!
I'm still using trn. I don't think it's been updated in decades, but it still >works.
ptomblin+netnews@xcski.com (Paul Tomblin) spake the secret code ><10mlkpq$k9g$1@linode.xcski.com> thusly:
I'm still using trn. I don't think it's been updated in decades, but it still >>works.
I'm working on a new version :)
<https://github.com/LegalizeAdulthood/trn>
Question: What newsreader does the collective brain trust here
consider the best option, and why?
According to Richard <>:
ptomblin+netnews@xcski.com (Paul Tomblin) spake the secret code >><10mlkpq$k9g$1@linode.xcski.com> thusly:
I'm still using trn. I don't think it's been updated in decades, but it still
works.
I'm working on a new version :)
<https://github.com/LegalizeAdulthood/trn>
I'm very interested. I'm using a copy on MacOS that I compiled in about 2017, >but I can't get it close to compiling with the current Mac programming >environment.
Tick, tick, tick, ...
[in reply to ReK2 Hispagatos <rek2@usenet_reborn.tui>]
[Added *the* newsreader group, news.software.readers, removed alt.free.nntp]
Steve Silverwood [KB6OJS] <steve.silverwood@gmail.com> wrote:
[...]
Question: What newsreader does the collective brain trust here
consider the best option, and why?
I'm very interested. I'm using a copy on MacOS that I compiled in about 2017,
but I can't get it close to compiling with the current Mac programming >>environment.
Tick, tick, tick, ...
I have the macOS CI builds on github currently disabled, but mostly
because the terminal handling in trn is funky and the macOS build
failed due to the order of includes and which termcap related headers
were included. It's probably not a big deal to figure that out, but I
don't have a mac on which I can manually edit/compile/test. I would
be very grateful for some collaboration there! My primary development >environment is Windows with WSL testing for linux.
. . .
Things are progressing nicely; the UTF-8 improvements contributed by
others have been integrated although they probably need some more
manual testing. Manual integration testing on all platforms and final
polish is where we're at for the 5.0 release.
legalize+jeeves@mail.xmission.com (Richard) wrote:
[fork of trn]
Things are progressing nicely; the UTF-8 improvements contributed by
others have been integrated although they probably need some more
manual testing. Manual integration testing on all platforms and final >>polish is where we're at for the 5.0 release.
trn expects the user to do things for himself in the composer.
Also, in followup, I parse for all that crap added to articles that make
them other than plain text, like nonbreaking spaces. When trn users who
care about this send an article, it is genuine plain text, devoid of all >nontext characters.
I hope this feature remains.
trn expects the user to do things for himself in the composer.
If there is a reason to declare a character set, I add MIME headers
manually. I don't expect trn to do it for me.
Also, in followup, I parse for all that crap added to articles that make
them other than plain text, like nonbreaking spaces.
When trn users who care about this send an article, it is genuine plain
text, devoid of all nontext characters.
Adam H. Kerman wrote:
trn expects the user to do things for himself in the composer.
If there is a reason to declare a character set, I add MIME headers >>manually. I don't expect trn to do it for me.
IBDT.
Also, in followup, I parse for all that crap added to articles that make >>them other than plain text, like nonbreaking spaces.
No(n)-break(ing) spaces *are* part of plain text, have been since ISO-8859-1 >and Windows-1252 (arguably the first 8-bit character encodings for PCs).
And they can be very useful.
When trn users who care about this send an article, it is genuine plain >>text, devoid of all nontext characters.
No(n)-break(ing) spaces are not "nontext characters" (which is an oxymoron).
Adam H. Kerman wrote:
Also, in followup, I parse for all that crap added to articles that make
them other than plain text, like nonbreaking spaces.
No(n)-break(ing) spaces *are* part of plain text, [...]
I think it's pretty obvious from the context that the OP is talking
about 7-bit US-ASCII when they say "plain text".
Thomas 'PointedEars' Lahn <usenet@PointedEars.de>:
Adam H. Kerman wrote:
Also, in followup, I parse for all that crap added to articles that make >>>them other than plain text, like nonbreaking spaces.
No(n)-break(ing) spaces *are* part of plain text, [...]
It helps to be specific and exact when talking about text encodings
and character sets.
I think it's pretty obvious from the context that the OP is talking
about 7-bit US-ASCII when they say "plain text". This is also the
historical usage of the term and this is the default character set
for MIME content-type text/plain.
Content using non-ASCII characters with content type text/plain has to >include a 'charset' parameter indicating ISO-8859-1 or whatever,--- Synchronet 3.21d-Linux NewsLink 1.2
otherwise the content beyond 7-bit ASCII is undefined. There are many >national character set extensions to 7-bit ASCII, of which ISO-8859-1
is just one. That is the purpose of the charset parameter in MIME.
In plain text Usenet and Mail, nonbreaking space should not be used even though it's in the character set.
Adam H. Kerman wrote:
In plain text Usenet and Mail, nonbreaking space should not be used even though it's in the character set.
It has a use in French, even in plain text.
Please give a real example, i.e. not just one where bad composition/ formatting leads to hard to read text.
Frank Slootweg wrote:
Please give a real example, i.e. not just one where bad composition/ >>formatting leads to hard to read text.
In French typography, question marks, exclamation points, semicolons,
and colons must be preceded by a space. The non-breaking space prevents
these punctuation marks from appearing alone at the beginning of a line.
Frank Slootweg wrote:
Please give a real example, i.e. not just one where bad composition/ formatting leads to hard to read text.
In French typography, question marks, exclamation points, semicolons,
and colons must be preceded by a space. The non-breaking space prevents
these punctuation marks from appearing alone at the beginning of a line.
Richard <legalize+jeeves@mail.xmission.com> wrote:
Thomas 'PointedEars' Lahn <usenet@PointedEars.de>:
Adam H. Kerman wrote:
Also, in followup, I parse for all that crap added to articles that make >>>> them other than plain text, like nonbreaking spaces.
No(n)-break(ing) spaces *are* part of plain text, [...]
It helps to be specific and exact when talking about text encodings
and character sets.
I think it's pretty obvious from the context that the OP is talking
about 7-bit US-ASCII when they say "plain text". This is also the
historical usage of the term and this is the default character set
for MIME content-type text/plain.
I'm not talking about ASCII only.
Combined characters with diacritical marks are certainly plain text.
He's simply wrong that a nonbreaking space is plain text;
I am aware of what the standard says,
For me it's tin, the CUI (Character/'Console' UI)
newsreader. Why? Because it's very versatile and CUI. Why hunt
around with a GUI and 'mouse' when you're using a pure plain
*text*medium? For example, I can read new articles (in all
subscribed groups) with one hand, resting on the keyboard.
I like tin, too, in spite of its ... peculiarities. I have even
started an introductory guide about it, which is temporarily
avaiable below:
<http://tilde.club/~ant/test/tin.html>
but hopefully soon to be published properly. Let me know what
you think is missing or wrong otherwise seends improvement.
ant <ant@tilde.club> wrote:
I like tin, too, in spite of its ... peculiarities. I have even
started an introductory guide about it, which is temporarily
avaiable below:
<http://tilde.club/~ant/test/tin.html>
but hopefully soon to be published properly. Let me know what
you think is missing or wrong otherwise seends improvement.
Nice guide!
If anything, I'd reverse things. Start by specifying how to
connect with SSL enabled, and only then describe plain-text
as the exception. Secure by default and all that!
<https://tilde.club/wiki/tin.html>
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 05:33:30 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
921 files (14,318M bytes) |
| Messages: | 264,603 |