Hello Maurice,

On Friday November 24 2023 00:17, you wrote to me:

What are we another step closer to?

6.6.6

Isn't it obvious?

What happens then? Does hellfire reign down on the Linux community? Or do they just start working on 6.6.7 shortly thereafter?

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20231112
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hey Nicholas!

What happens then? Does hellfire reign down on the Linux community?

Offhand I don't believe so. However I plan on subtitling 6.6.6 as the kv of the Beast. What that means remains to be seen as I don't have any inside information about or from the Beast.

Or do they just start working on 6.6.7 shortly thereafter?

Standard operating procedure.

You're no fun anymore. :-/

Life is good,
Maurice

-o o- o- o- -o o- o- o- o- -o -o o- o- o- -o -o
(\ /) /) /) (\ /) /) /) /) (\ (\ /) /) /) (\ (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - Sweet Sixteen Penguins of the Apocalypse.
--- GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Maurice,

On Friday November 24 2023 19:20, you wrote to me:

What happens then? Does hellfire reign down on the Linux
community?

Offhand I don't believe so. However I plan on subtitling 6.6.6 as the
kv of the Beast. What that means remains to be seen as I don't have
any inside information about or from the Beast.

Well, in that case I'm glad you get to do something different with this upcoming version. I still remember the 'build-up' and excitement prior to the 5.0 kernel. Then it came and went just like all the others.

Or do they just start working on 6.6.7 shortly thereafter?

Standard operating procedure.

You're no fun anymore. :-/

To be honest, I originally asked as if I didn't know about something that was in the works (as in a serious question), but at the same time realized where you were going with it. So I let it play out. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20231112
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hey Nicholas!

Then it came and went just like all the others.

True but in that case whatever the set goal happened to be at the time was usually met and then a new one gets set, such as getting stock kernels to work on risc processors, which I believe is the main goal of 6.6 kernels.

So I let it play out.

I reiterate, you're no fun anymore.

Life is good,
Maurice

-o o- o- -o -o o- -o -o o- -o o- -o o- o- -o -o
(\ /) /) (\ (\ /) (\ (\ /) (\ /) (\ /) /) (\ (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Maurice,

On Saturday November 25 2023 16:01, you wrote to me:

So I let it play out.

I reiterate, you're no fun anymore.

I've been done with all of the 'fun' stuff when it comes to Fidonet related technology for awhile now. I follow most development of any software that's still being worked on.

... Fidonet 4K - You load sixteen penguins and what do you get?

Has there been anything interesting in the 4K world when it comes to Fidonet?

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20231112
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hey Nicholas!

I follow most development of any software that's still being
worked on.

Understood. I believe once you fixed the word wrapping problem with a certain editor you went well beyond the call of duty. No committee to get in the way either. ;-)

Has there been anything interesting in the 4K world when it
comes to Fidonet?

Not since 1995 (September 30, 1995), and probably earlier than that. It should even work at higher resolutions just fine. Proper wordwrapping is all it took/takes.

As far as I am personally concerned, it isn't the lack of development that is the main problem. Fidonet needs a good purging of all the obsolete and buggy code rather than developing new obsolete and buggy code.

Life is good,
Maurice

-o -o o- o- o- o- -o -o o- -o o- o- o- -o o- -o
(\ (\ /) /) /) /) (\ (\ /) (\ /) /) /) (\ /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Maurice,

On Saturday November 25 2023 21:29, you wrote to me:

I follow most development of any software that's still being
worked on.

Understood. I believe once you fixed the word wrapping problem with a certain editor you went well beyond the call of duty. No committee to
get in the way either. ;-)

As I'm sure you knew, I meant FTN/BBS related softwares. But yes, getting nano fixed was quite a few years ago already. Time flies.

Has there been anything interesting in the 4K world when it
comes to Fidonet?

As far as I am personally concerned, it isn't the lack of development
that is the main problem. Fidonet needs a good purging of all the obsolete and buggy code rather than developing new obsolete and buggy code.

At this point, I'm just happy a handful or two are still programming for this technology, which is basically hanging on by a thread. ;(

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20231112
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hey Nicholas!

getting nano fixed was quite a few years ago already.

Those were the days. ;-) Anyhow I think you underestimate the potential of that fix. From fts-0001.016 I take the liberty of quoting;

fts-0001.016> Message text is unbounded and null terminated (note
fts-0001.016> exception below).

Being unbounded is what makes any resolution possible as per character display rows and lines are concerned. For me 4K Fidonet worked right out of the box and with some tweaking (the fun stuff) I am able to create some very unique MSGs while adhering to acceptable FTN standards. Not many can make that claim today.

Having said that I believe fidonet required a good enema more than 20 years ago.

Het leven is goed,
Maurice

o- o- o- -o
/) /) /) (\
^^ ^^ ^^ ^^
... On ælcere ea swa wyrse fordes, swa betere fisces.
In every river, the worse the ford the better the fish.
--- GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

Hello Maurice,

On Sunday November 26 2023 10:27, you wrote to me:

getting nano fixed was quite a few years ago already.

Those were the days. ;-) Anyhow I think you underestimate the
potential of that fix. From fts-0001.016 I take the liberty of
quoting;

I'm just glad it was something I could contribute, that ended up making it's way into the code permanently.

$ nano --version
GNU nano, version 7.2
(C) 2023 the Free Software Foundation and various contributors
Compiled options: --enable-utf8

I believe that feature was done sometime in the 5.x or 6.x versioning, and still going strong to this day. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20231112
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hey Nicholas!

Compiled options: --enable-utf8

That too makes it a excellent candidate for a BBS editor.

I believe that feature was done sometime in the 5.x or 6.x
versioning, and still going strong to this day. ;)

No surprises here. You took it over the top.

Life is good,
Maurice

o- o- o- o- o- -o -o o- o- o- o- o- -o o- -o -o /) /) /) /) /) (\ (\ /) /) /) /) /) (\ /) (\ (\ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... To nawihte ne hopað, se to hame ne higeð.
He hopes for nothing, who does not think about home.
--- GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)