Hello Nick!
Monday May 03 2021 11:44, you wrote to me:
On 03 May 21 15:08:00, Vincent Coen said the following to Wilfred Van Velzen:
Anyone with a view on this ?
I don't understand in 2021 why software authors are required to list
their own support echoes for their own products or face having them in "jeopardy".
Why can't a simple common-sense gentlemens agreement suffice?
You know D'Bridge is "mine", please just make it permanent. Thank you.
The process regarding the six month update policy which goes back to the original by Dana I am guessing is to ensure that a specific echo's moderator is
still around and in Fido.
I cannot preset a echo to be permanent as the s/w always forces a six month check followed by multiple warnings of expiry.
The above is without changing the way elist program works and also could
create echos staying in the ELIST system when the moderator has gone and possibly also the echo.
At the end of the day it only involves in setting up in your own system to resend the echname.ECO file to update it using such as crontab or what ever you
like for Windoz.
I did it for many years but once set up it does not require any addition effort
unless the ELIST Maintainer changes and even then up to last year the address was always 1:nn/21. (Sorry forgot the address).
As I was not allowed to use that address or 2:2/21 I've had to create one under
my control i.e., 2:25/21.
Vincent
--- Mageia Linux v7.1 X64/Mbse v1.0.7.21/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)