for NNTP?

Nicodemus <Ancient-of-Days@Heaven.Net>:
> for NNTP?

Why do you ask this in a Linux Mint newsgroup?

Yrrah

On 5/29/21 12:48 PM, Yrrah wrote:
> Nicodemus <Ancient-of-Days@Heaven.Net>:
>
>> for NNTP?
> Why do you ask this in a Linux Mint newsgroup?
>
> Yrrah
>
>
Because I use Linux Mint and have installed Knode but am having some
problems with it so, I toss it it out to the Mint community for help.

TheSidhe wrote:
> Because I use Linux Mint and have installed Knode but am having some
> problems with it so, I toss it it out to the Mint community for help.

Fundamentally (whatever that means in this context) the KDE desktop and
its 'extensions' are 'past history' in terms of Mint and its dev.

Also fundamentally, Knode, as an 'extension' of Kontact, which is an
extension of KDE is past history in terms of KDE and its dev.

For example, a 'natural' way to be using Mint and Knode would be to be
using Mint 18.3 KDE which was based on Ub 16.04 a LTS; and/but 18.3 was
'naturally' KDE 5.8.

I believe the highest Ubuntu/Kubuntu that Knode made it to was 16.10, so
it is conceivable that one could do backports for a Mint 18.3 (off Ub
16.04) whose support ended in Apr.

Not that there is anything earth-shattering about using an unsupported
Mint v. for accessing nntp, but if you used some other route for
acquiring a combination of Mint and Knode it might be interesting to
hear about it.

--
Mike Easter

On 5/29/21 1:27 PM, Mike Easter wrote:
> TheSidhe wrote:
>> Because I use Linux Mint and have installed Knode but am having some
>> problems with it so, I toss it it out to the Mint community for help.
>
> Fundamentally (whatever that means in this context) the KDE desktop
> and its 'extensions' are 'past history' in terms of Mint and its dev.
>
> Also fundamentally, Knode, as an 'extension' of Kontact, which is an
> extension of KDE is past history in terms of KDE and its dev.
>
> For example, a 'natural' way to be using Mint and Knode would be to be
> using Mint 18.3 KDE which was based on Ub 16.04 a LTS; and/but 18.3
> was 'naturally' KDE 5.8.
>
> I believe the highest Ubuntu/Kubuntu that Knode made it to was 16.10,
> so it is conceivable that one could do backports for a Mint 18.3 (off
> Ub 16.04) whose support ended in Apr.
>
> Not that there is anything earth-shattering about using an unsupported
> Mint v. for accessing nntp, but if you used some other route for
> acquiring a combination of Mint and Knode it might be interesting to
> hear about it.
>
I was reading an article and they mentioned KNode, so I checked my
software manager and it was there, from which I installed KNode and
launched it and tried to subscribe to AOIE but I get an error when I try
to fetch the list of groups. Was wondering if any one here at this forum
had any experience setting it up.

Mike Easter wrote:

> TheSidhe wrote:
>> Because I use Linux Mint and have installed Knode but am having
some
>> problems with it so, I toss it it out to the Mint community for
help.
>
> Fundamentally (whatever that means in this context) the KDE
desktop and
> its 'extensions' are 'past history' in terms of Mint and its dev.
>
> Also fundamentally, Knode, as an 'extension' of Kontact, which is
an
> extension of KDE is past history in terms of KDE and its dev.
>
> For example, a 'natural' way to be using Mint and Knode would be
to be
> using Mint 18.3 KDE which was based on Ub 16.04 a LTS; and/but
18.3 was
> 'naturally' KDE 5.8.
>
> I believe the highest Ubuntu/Kubuntu that Knode made it to was
16.10, so
> it is conceivable that one could do backports for a Mint 18.3 (off
Ub
> 16.04) whose support ended in Apr.
>
> Not that there is anything earth-shattering about using an
unsupported
> Mint v. for accessing nntp, but if you used some other route for
> acquiring a combination of Mint and Knode it might be interesting
to
> hear about it.
>
I think I have figured it out, had to install additional package
from the software manager called -Kde4pimlibs-kio-plugins, and it
seems to be wotking,

TheSidhe wrote:
> On 5/29/21 1:27 PM, Mike Easter wrote:
>> TheSidhe wrote:
>>> Because I use Linux Mint and have installed Knode but am having some
>>> problems with it so, I toss it it out to the Mint community for help.
>>
>> Fundamentally (whatever that means in this context) the KDE desktop
>> and its 'extensions' are 'past history' in terms of Mint and its dev.
>>
>> Also fundamentally, Knode, as an 'extension' of Kontact, which is an
>> extension of KDE is past history in terms of KDE and its dev.
>>
>> For example, a 'natural' way to be using Mint and Knode would be to be
>> using Mint 18.3 KDE which was based on Ub 16.04 a LTS; and/but 18.3
>> was 'naturally' KDE 5.8.
>>
>> I believe the highest Ubuntu/Kubuntu that Knode made it to was 16.10,
>> so it is conceivable that one could do backports for a Mint 18.3 (off
>> Ub 16.04) whose support ended in Apr.
>>
>> Not that there is anything earth-shattering about using an unsupported
>> Mint v. for accessing nntp, but if you used some other route for
>> acquiring a combination of Mint and Knode it might be interesting to
>> hear about it.
>>
> I was reading an article and they mentioned KNode, so I checked my
> software manager and it was there, from which I installed KNode and
> launched it and tried to subscribe to AOIE but I get an error when I try
> to fetch the list of groups. Was wondering if any one here at this forum
> had any experience setting it up.
>
Ubuntu – Package Search Results -- knode
https://packages.ubuntu.com/search?lang=en&suite=all&searchon=names&keywords=knode
Only Ubuntu 18.04 - Mint 19

Ubuntu – Details of package knode in bionic
https://packages.ubuntu.com/en/bionic/knode
depends
....
For the KDE desktop environment

KNode - KDE Applications
https://apps.kde.org/knode/
"This app is unmaintained and no longer released by the KDE community."

Nic wrote:
> I think I have figured it out, had to install additional package
> from the software manager called -Kde4pimlibs-kio-plugins, and it
> seems to be wotking,

Yes; I knew it was in the kde4pim, but I didn't understand how your Mint
would come to have the kde4pim package in its repo/s, since it didn't
start out w/ a kde4.

I'm currently working on seeing if I can get a currently supported
knode-trinity, which trinity DE is 'sorta' like a currently supported
kde 3.5 and currently supported 'qt3'.

--
Mike Easter

Mike Easter wrote:

> Nic wrote:
>> I think I have figured it out, had to install additional package
>> from the software manager called -Kde4pimlibs-kio-plugins, and it
>> seems to be wotking,
>
> Yes; I knew it was in the kde4pim, but I didn't understand how
your Mint
> would come to have the kde4pim package in its repo/s, since it
didn't
> start out w/ a kde4.
>
> I'm currently working on seeing if I can get a currently supported
> knode-trinity, which trinity DE is 'sorta' like a currently
supported
> kde 3.5 and currently supported 'qt3'.
>
For now I am happy that it works in its present incarnation, seems
to be a nice news reader and I like to have alternatives. I have
not tried it for email yet, will get around to it.

On 29.05.2021 at 16:27, Nicodemus scribbled:

> for NNTP?

Yes, I've used it as my newsreader for many, many years. Alas, it was
never even fully ported to qr4 — it still had qt3 bindings — and so
it's not available anymore in Plasma 5.

--
With respect,
= Aragorn

On 29.05.2021 at 14:32, Nic scribbled:

> Mike Easter wrote:
>
> > Nic wrote:
> >> I think I have figured it out, had to install additional package
> >> from the software manager called -Kde4pimlibs-kio-plugins, and it
> >> seems to be wotking,
> >
> > Yes; I knew it was in the kde4pim, but I didn't understand how
> > your Mint would come to have the kde4pim package in its repo/s, since it
> > didn't start out w/ a kde4.
> >
> > I'm currently working on seeing if I can get a currently supported
> > knode-trinity, which trinity DE is 'sorta' like a currently
> > supported kde 3.5 and currently supported 'qt3'.
>
> For now I am happy that it works in its present incarnation, seems
> to be a nice news reader and I like to have alternatives. I have
> not tried it for email yet, will get around to it.

It's not an email client. It supports replying via email, but insofar
as I remember — it has been a few years — it was not designed handle
_incoming_ email.

--
With respect,
= Aragorn

Mike Easter wrote:

> I'm currently working on seeing if I can get a currently supported
> knode-trinity, which trinity DE is 'sorta' like a currently supported
> kde 3.5 and currently supported 'qt3'.

I'm posting this from the current q4OS w/ TDE and Trinity-Knode 0.10.9 which
doesn't 'correspond' to the original Knode's version scheme which was at
4.something.

--
Mike Easter

Mike Easter wrote:
>
> I'm currently working on seeing if I can get a currently supported
> knode-trinity, which trinity DE is 'sorta' like a currently supported
> kde 3.5 and currently supported 'qt3'.

I installed the trinity-knode into the current q4OS release of the
Trinity DE which v. number does NOT correspond to the old conventional
knode v. scheme which was at 4.something. I subscribed to this group
and sent a msg, and it appeared in the knode sent dir, but it has not
appeared in this ng.

The app says that it can do mail, but I know Aragorn has had extensive
experience w/ knode.

--
Mike Easter

Mike Easter wrote:

> I installed the trinity-knode into the current q4OS release of the
> Trinity DE which v. number does NOT correspond to the old conventional
> knode v. scheme which was at 4.something.  I subscribed to this group
> and sent a msg, and it appeared in the knode sent dir, but it has not
> appeared in this ng.
>
Oh; I see. My clock was wrong. The msg did appear, I just didn't see it
because it was in the wrong order.

From q4OS TDE trinity-knode 0.10.9.

--
Mike Easter

Aragorn wrote:

> On 29.05.2021 at 14:32, Nic scribbled:
>
>> Mike Easter wrote:
>>
>> > Nic wrote:
>> >> I think I have figured it out, had to install additional
package
>> >> from the software manager called -Kde4pimlibs-kio-plugins, and
it
>> >> seems to be wotking,
>> >
>> > Yes; I knew it was in the kde4pim, but I didn't understand how
>> > your Mint would come to have the kde4pim package in its repo/s,
since
>> > it didn't start out w/ a kde4.
>> >
>> > I'm currently working on seeing if I can get a currently
supported
>> > knode-trinity, which trinity DE is 'sorta' like a currently
>> > supported kde 3.5 and currently supported 'qt3'.
>>
>> For now I am happy that it works in its present incarnation,
seems
>> to be a nice news reader and I like to have alternatives. I have
>> not tried it for email yet, will get around to it.
>
> It's not an email client. It supports replying via email, but
insofar
> as I remember — it has been a few years — it was not designed
handle
> _incoming_ email.
>
Thank you, saved me a lot of time,

Mike Easter wrote:

> Mike Easter wrote:
>
>> I installed the trinity-knode into the current q4OS release of
the
>> Trinity DE which v. number does NOT correspond to the old
conventional
>> knode v. scheme which was at 4.something. I subscribed to this
group
>> and sent a msg, and it appeared in the knode sent dir, but it has
not
>> appeared in this ng.
>>
> Oh; I see. My clock was wrong. The msg did appear, I just didn't
see it
> because it was in the wrong order.
>
> From q4OS TDE trinity-knode 0.10.9.
>
>
It appeared like you said wrong order, clock was off

TheSidhe wrote:
> I was reading an article and they mentioned KNode, so I checked my
> software manager and it was there, from which I installed KNode and
> launched it

Starting from a Mint 20.1 Cinn, no knode, no kde4pim. I installed the
KDE5 DE and Kontact from the repo/s which included the Kmail for that
Kontact, also no knode (which had been the route to get knode in earlier
KDE4).

I don't know what kind of combination of Mint plus KDE you have
installed unless it is a much older v. of Mint like 18.

--
Mike Easter

Mike Easter wrote:
> I don't know what kind of combination of Mint plus KDE you have
> installed unless it is a much older v. of Mint like 18.

What does

inxi -S

.... say about your system?

--
Mike Easter

On 5/29/21 3:27 PM, Mike Easter wrote:
> TheSidhe wrote:
>> I was reading an article and they mentioned KNode, so I checked my
>> software manager and it was there, from which I installed KNode and
>> launched it
>
> Starting from a Mint 20.1 Cinn, no knode, no kde4pim.  I installed the
> KDE5 DE and Kontact from the repo/s which included the Kmail for that
> Kontact, also no knode (which had been the route to get knode in
> earlier KDE4).
>
> I don't know what kind of combination of Mint plus KDE you have
> installed unless it is a much older v. of Mint like 18.
>
I also deleted Kmail because it was acting funky, looking for pgp
keyring..and also was wondering if it would negatively effect Knode, but
it not, thinking that Kmail was part of the pim package..

On 5/29/21 3:31 PM, Mike Easter wrote:
> Mike Easter wrote:
>> I don't know what kind of combination of Mint plus KDE you have
>> installed unless it is a much older v. of Mint like 18.
>
> What does
>
> inxi -S
>
> ... say about your system?
>
  Host: nic-System-Product-Name Kernel: 5.4.0-67-generic x86_64 bits: 64
  Desktop: Cinnamon 4.0.10 Distro: Linux Mint 19.1 Tessa

Hope this helps

Mike Easter wrote:
> I'm currently working on seeing if I can get a currently supported
> knode-trinity, which trinity DE is 'sorta' like a currently supported
> kde 3.5 and currently supported 'qt3'.

Another route to go to get knode and an interesting distro is a current
community PCLOS based on Trinity and its repo/s as well as pclos repo/s.
And, that pclos tde comes in both a 'big daddy' full of default app/s
as well as a 'mini-me' v. which is lighter w/ less default app/s but the
same repo/s.

Another 'lost' news agent is klibido which is designed for nntp
binaries. It is possible that klibido may also be in that same knode repo.

https://trinity.mypclinuxos.com/ This is a community respin of the
PCLinuxOS Distribution created by Texstar and relies heavily on the
PCLinuxOS repositories along with the repositories of the Trinity
Desktop Enviroment.

I think that if I were trying to 'Mint-ize' a KDE, I might start w/ Neon
and add Mint, rather than starting w/ Mint and adding KDE. But, that
wouldn't get Knode, but instead a Mint + its tools plus a current KDE
Plasma 5.

But, maybe Neon is 'too much like Ub' whereas default Mint is somewhat
less so, such as the flatpak vs snap issue.

--
Mike Easter

TheSidhe wrote:
> Desktop: Cinnamon 4.0.10 Distro: Linux Mint 19.1 Tessa

Ah, so. Ub 18.04 can access knode from its repo/s.

https://www.howtoinstall.me/ubuntu/18-04/knode/ How to Install knode in
Ubuntu 18.04

and...

Package knode
bionic (18.04LTS) (news): graphical news reader [universe]
4:4.14.10-7: amd64 arm64 armhf i386 ppc64el s390x

--
Mike Easter

Mike Easter wrote:

> TheSidhe wrote:
>> Desktop: Cinnamon 4.0.10 Distro: Linux Mint 19.1 Tessa
>
> Ah, so. Ub 18.04 can access knode from its repo/s.
>
> https://www.howtoinstall.me/ubuntu/18-04/knode/ How to Install
knode in
> Ubuntu 18.04
>
> and...
>
> Package knode
> bionic (18.04LTS) (news): graphical news reader [universe]
> 4:4.14.10-7: amd64 arm64 armhf i386 ppc64el s390x
>
>
Is that a good Ah so?

Nic wrote:
> Mike Easter wrote:
>> TheSidhe wrote:
>>> Desktop: Cinnamon 4.0.10 Distro: Linux Mint 19.1 Tessa
>>
>> Ah, so. Ub 18.04 can access knode from its repo/s.
>>
>> Package knode
>> bionic (18.04LTS) (news): graphical news reader [universe]
>> 4:4.14.10-7: amd64 arm64 armhf i386 ppc64el s390x
>>
> Is that a good Ah so?
>
It would mean "Oho. I get the picture now."

Previously I would have imagined that it wouldn't have made it to the
LTS 18.04 repo/s. I didn't have such a distro to boot up live.

But, AZ saw it in the 18.04 packages earlier.

--
Mike Easter

Mike Easter wrote:

> Nic wrote:
>> Mike Easter wrote:
>>> TheSidhe wrote:
>>>> Desktop: Cinnamon 4.0.10 Distro: Linux Mint 19.1 Tessa
>>>
>>> Ah, so. Ub 18.04 can access knode from its repo/s.
>>>
>>> Package knode
>>> bionic (18.04LTS) (news): graphical news reader [universe]
>>> 4:4.14.10-7: amd64 arm64 armhf i386 ppc64el s390x
>>>
>> Is that a good Ah so?
>>
> It would mean "Oho. I get the picture now."
>
> Previously I would have imagined that it wouldn't have made it to
the
> LTS 18.04 repo/s. I didn't have such a distro to boot up live.
>
> But, AZ saw it in the 18.04 packages earlier.
>
Thank you for all your help