Hello All!

Over the next few weeks other echos that are not moderated will be added that form the basis of the BACKBONE.NA type lists.

As the new code is completed and tested these will disappear from the ELIST.* listings and transfer to the BACKBONE group.

I will have all echos within the one database but non moderated will be filtered away.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hi Vincent,

On 2022-01-31 21:31:00, you wrote to All:

Over the next few weeks other echos that are not moderated will be
added that form the basis of the BACKBONE.NA type lists.

As the new code is completed and tested these will disappear from the ELIST.* listings and transfer to the BACKBONE group.

I will have all echos within the one database but non moderated will be filtered away.

Well if you prevent any (auto) postings of them in this (and other) areas, nor listing them in the elist, nobody could get annoyed about it, or even has to know about it...

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Monday January 31 2022 22:52, you wrote to me:

Hi Vincent,

On 2022-01-31 21:31:00, you wrote to All:

Over the next few weeks other echos that are not moderated will
be added that form the basis of the BACKBONE.NA type lists.

As the new code is completed and tested these will disappear from
the ELIST.* listings and transfer to the BACKBONE group.

I will have all echos within the one database but non moderated
will be filtered away.

Well if you prevent any (auto) postings of them in this (and other)
areas, nor listing them in the elist, nobody could get annoyed about
it, or even has to know about it...

Correct once coding and testing is complete the ELIST reports etc, will only have moderated areas reported within but the entire content will be on the backbone (excluding some restricted areas).

This way the backbone will be more complete (at least better than it has been over the last 3+ years).

No flow though, is a another kettle of fish.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Vince,

I will have all echos within the one database but non moderated will be filtered away.

Good.

As DBRIDGE's moderator passed away, that echo is now unmoderated and not in need of one ...

Some folks may not even want their echo(es) on the outdated backbone, it's a concept from the 90-ies, not for 2021 ... I'm not alone to entertain that opinion ...

\%/@rd
--- DB4 - Jan 26 2022
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

On Feb 01, 2022 12:41am, Ward Dossche wrote to Vincent Coen:

Some folks may not even want their echo(es) on the outdated backbone,
it's a concept from the 90-ies, not for 2021 ... I'm not alone to entertain that opinion ...

It would be nice to have a list of active message areas whatever it is called doesn't really matter, why?, because with an updated list, it makes setting up a new system a piece of cake for new sysops.

Terry

... Platinum Xpress & Wildcat!..... Nice!!!!
--- Platinum Xpress/Win/WINServer v7.0
* Origin: The File Bank BBS! (3:640/1321)

Hi Vincent,

On 2022-01-31 22:49:55, you wrote to me:

Over the next few weeks other echos that are not moderated will
be added that form the basis of the BACKBONE.NA type lists.

As the new code is completed and tested these will disappear from
the ELIST.* listings and transfer to the BACKBONE group.

I will have all echos within the one database but non moderated
will be filtered away.

Well if you prevent any (auto) postings of them in this (and other)
areas, nor listing them in the elist, nobody could get annoyed about
it, or even has to know about it...

Correct once coding and testing is complete the ELIST reports etc, will only have moderated areas reported within but the entire content will be on
the backbone (excluding some restricted areas).

You should also make sure your tests don't go out in public!

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Tuesday February 01 2022 08:43, you wrote to me:

Hi Vincent,

On 2022-01-31 22:49:55, you wrote to me:

Over the next few weeks other echos that are not moderated will
be added that form the basis of the BACKBONE.NA type lists.

As the new code is completed and tested these will disappear
from the ELIST.* listings and transfer to the BACKBONE group.

I will have all echos within the one database but non moderated
will be filtered away.

Well if you prevent any (auto) postings of them in this (and
other) areas, nor listing them in the elist, nobody could get
annoyed about it, or even has to know about it...

Correct once coding and testing is complete the ELIST reports
etc, will only have moderated areas reported within but the
entire content will be on the backbone (excluding some restricted
areas).

You should also make sure your tests don't go out in public!

Now think about that !

If I test in another area then when complete change the posted msg area I have to test again to confirm the change is correct.

There again I did do it for a living for large companies so I do as I trained others :)


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hi Vincent,

On 2022-02-01 12:56:11, you wrote to me:

You should also make sure your tests don't go out in public!

Now think about that !

If I test in another area then when complete change the posted msg area I have to test again to confirm the change is correct.

There again I did do it for a living for large companies so I do as I trained others :)

Maybe things have changed in the last 30 years or so, but nowadays you don't develop/test in a production environment!

You could do a final test in the production environment, but then use a "bogus" area name, that doesn't exist, so you don't have to annoy anyone...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Tuesday February 01 2022 14:32, you wrote to me:

Hi Vincent,

On 2022-02-01 12:56:11, you wrote to me:

You should also make sure your tests don't go out in public!

Now think about that !

If I test in another area then when complete change the posted
msg area I have to test again to confirm the change is correct.

There again I did do it for a living for large companies so I do
as I trained others :)

Maybe things have changed in the last 30 years or so, but nowadays you
don't develop/test in a production environment!

You could do a final test in the production environment, but then use
a "bogus" area name, that doesn't exist, so you don't have to annoy anyone...

ADo you mean that the odd 100k+ I received last year for such was in error
and
the very large businesses were wrong in their practice for developing for their
mainframes and devolved systems ?

I think not.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hi Vincent,

On 2022-02-01 13:52:03, you wrote to me:

Maybe things have changed in the last 30 years or so, but nowadays you
don't develop/test in a production environment!

You could do a final test in the production environment, but then use
a "bogus" area name, that doesn't exist, so you don't have to annoy
anyone...

ADo you mean that the odd 100k+ I received last year for such was in error
and the very large businesses were wrong in their practice for developing for their mainframes and devolved systems ?

I think not.

Apparently you work in at totally different environment then most businesses. When we would be doing that on our clients computers we would be out of business real soon. (And the prices of your tomatos and other vegetables, in your supermarket would probably be somewhat higher)

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Tuesday February 01 2022 17:02, you wrote to me:

Hi Vincent,

On 2022-02-01 13:52:03, you wrote to me:

Maybe things have changed in the last 30 years or so, but nowadays
you don't develop/test in a production environment!

You could do a final test in the production environment, but then
use a "bogus" area name, that doesn't exist, so you don't have to
annoy anyone...

ADo you mean that the odd 100k+ I received last year for such
was in error
and the very large businesses were wrong in their practice for
developing for their mainframes and devolved systems ?

I think not.

Apparently you work in at totally different environment then most businesses. When we would be doing that on our clients computers we
would be out of business real soon. (And the prices of your tomatos
and other vegetables, in your supermarket would probably be somewhat
higher)

All clients are very large multi nationals running medium to large mainframes and that includes Banks.

In the UK and I assume the EU banks have a legal obligation that software have to go though various processes before formal usage and that includes testing that they comply with the specifications in full and satisfy the user needs.

There are a lot more legal requirements but for my using a Test hat that is the
only primary requirement , the rest sit behind.

I don't deal with small companies !

Nor one's that do not use mainframes or large server systems.

Sound like you work for one of the UK banks that have a habit of using s/w that
has not been fully tested then unleash to the general public who cannot access their accounts one way or another for days and weeks while they do better and more thorough testing !
Oh, I could also add in Airlines as well who tried to save money by releasing too early!

No customer that I worked on behalf of I am happy to report.


Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hi Vincent,

On 2022-02-01 16:14:34, you wrote to me:

Sound like you work for one of the UK banks...

Nope, nor any other bank in the world.

Btw: Where did the subject get so mangled?

Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello, Wilfred van Velzen.
On 1/2/22 18:00 you wrote:

Btw: Where did the subject get so mangled?

Apparently in your first reply to Vincent. But both your GoldEds had fun with it. :-)

Carlos
--- Hotdoged/2.13.5/Android
* Origin: Costa Blanca, Spain (2:341/234.12)

Hello Carlos!

Wednesday February 02 2022 17:02, you wrote to Wilfred van Velzen:

Hello, Wilfred van Velzen.
On 1/2/22 18:00 you wrote:

Btw: Where did the subject get so mangled?

Apparently in your first reply to Vincent. But both your GoldEds had
fun with it. :-)

:)

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hi Carlos,

On 2022-02-02 17:02:14, you wrote to me:

Btw: Where did the subject get so mangled?

Apparently in your first reply to Vincent. But both your GoldEds had fun with it. :-)

It was ok in my first reply when it left the door. Check out: "MSGID: 2:280/464 61f85aa7"
And all my subsequent replies just quoted the mess that came back from Vince!


Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

02 Feb 2022 18:27, you wrote to me:

Apparently in your first reply to Vincent. But both your GoldEds
had fun with it. :-)

It was ok in my first reply when it left the door. Check out: "MSGID: 2:280/464 61f85aa7" And all my subsequent replies just quoted the mess that came back from Vince!

True! I got confused. It was Vince's GoldEd only.

Carlos
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234)