• Future Applications

    From Flavio Bessa@4:801/189.1 to All on Wednesday, November 22, 2017 14:57:12
    Hello everybody.

    I have been following the developments of the last FTSC election, and of course am interested to contribute and be a part of the elected team in the future.

    However, just not to barge in and cause more trouble than effectively contribute, is there anything that I can go through, read and prepare myself for the next term?

    Flavio

    ... "AI! Meu pinico n└o ┌ ouvido!" - CyberLeo
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Ward Dossche@2:292/854 to Flavio Bessa on Monday, December 11, 2017 01:36:35
    Flavio,

    However, just not to barge in and cause more trouble than
    effectively contribute, is there anything that I can go through, read and prepare myself for the next term?

    If I understand correctly ... you accepted a nomination for something you had no idea what it was about ?

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Andrew Leary@1:320/219 to Ward Dossche on Sunday, December 10, 2017 20:52:33
    Hello Ward!

    11 Dec 17 01:36, you wrote to Flavio Bessa:

    Flavio,

    However, just not to barge in and cause more trouble than
    effectively contribute, is there anything that I can go through,
    read and prepare myself for the next term?

    If I understand correctly ... you accepted a nomination for something
    you had no idea what it was about ?

    Flavio was not a candidate in the most recent election. I read his message as expressing interest in running in the future.

    Andrew

    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Ward Dossche@2:292/854 to Andrew Leary on Monday, December 11, 2017 03:32:30

    Andrew,

    Flavio was not a candidate in the most recent election.

    Isn't he? Because he is one whom I'd support.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Andrew Leary@1:320/219 to Ward Dossche on Monday, December 11, 2017 02:00:37
    Hello Ward!

    11 Dec 17 03:32, you wrote to me:

    Flavio was not a candidate in the most recent election.

    Isn't he? Because he is one whom I'd support.

    I probably would as well. I wish he had expressed interest prior to the election.

    Andrew

    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Alexey Vissarionov@2:5020/545 to Flavio Bessa on Monday, December 11, 2017 11:41:14
    Good ${greeting_time}, Flavio!

    22 Nov 2017 14:57:12, you wrote to All:

    I have been following the developments of the last FTSC election,
    and of course am interested to contribute and be a part of the
    elected team in the future.

    To contribute: that's simple - you may write a FSP or participate in public proof-reading of some documents once they will be posted here (yes, I see that English is not your native language, but my own experience shows that sometimes
    non-native spea^W writers find non-trivial issues which are not mentioned by natives).

    To participate: next FTSC election will be in the end of 2018, so once you'd show your involvement, any RC (including your R80C) may nominate you.

    However, just not to barge in and cause more trouble than effectively contribute, is there anything that I can go through, read and
    prepare myself for the next term?

    If you run large echomail distribution node, you most likely are ready. If you develop FTN software, you most likely are ready.

    Some idiots do neither, but are elected for each next term for many years.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

    ... :wq!
    --- /bin/vi
    * Origin: http://openwall.com/Owl (2:5020/545)
  • From Ward Dossche@2:292/854 to Alexey Vissarionov on Monday, December 11, 2017 10:31:53

    Alexey,

    To participate: next FTSC election will be in the end of 2018, so once you'd show your involvement, any RC (including your R80C) may nominate
    you.

    That RC has largely been MIA, so someone else will need to nominate Flavio. I don't even see why he couldn't be co-opted already.

    Some idiots do neither, but are elected for each next term for many
    years.

    Since 2 weeks more or less it has become more difficult as an idiot to get nominated.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Flavio Bessa@4:801/189.1 to Ward Dossche on Monday, December 11, 2017 07:43:34
    Hello Ward.

    11 Dec 17 01:36, you wrote to me:

    However, just not to barge in and cause more trouble than
    effectively contribute, is there anything that I can go through,
    read and prepare myself for the next term?

    If I understand correctly ... you accepted a nomination for something
    you had no idea what it was about ?

    I did not accept anything :)

    I just would like to be able to contribute in the future, and was asking for guidance on what to read, in order to understand the role and maybe be a candidate for future terms :)

    Flavio

    ... Gustavo Fuchs, o Boiola Mor da UnionNet!
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Flavio Bessa@4:801/189.1 to Andrew Leary on Monday, December 11, 2017 07:44:57
    Hello Andrew.

    10 Dec 17 20:52, you wrote to Ward Dossche:

    If I understand correctly ... you accepted a nomination for
    something you had no idea what it was about ?

    Flavio was not a candidate in the most recent election. I read his message as expressing interest in running in the future.

    That's right.

    Flavio

    ... "T═ faltando disquete!" - Perninha
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Flavio Bessa@4:801/189.1 to Ward Dossche on Monday, December 11, 2017 07:45:19
    Hello Ward.

    11 Dec 17 03:32, you wrote to Andrew Leary:

    Andrew,

    Flavio was not a candidate in the most recent election.

    Isn't he? Because he is one whom I'd support.

    Thank you for your confidence, but I wasn't a candidate for the current
    term. :)

    Flavio

    ... "Onde a Karyna mora?" "Ah, por a║!" - Dkg x Reptile, 1╖ E
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Flavio Bessa@4:801/189.1 to Andrew Leary on Monday, December 11, 2017 07:46:02
    Hello Andrew.

    11 Dec 17 02:00, you wrote to Ward Dossche:

    Isn't he? Because he is one whom I'd support.

    I probably would as well. I wish he had expressed interest prior to
    the election.

    Thank you as well. :)

    Flavio

    ... "Put@ que pariu, SEMPRE sobra pra mim..." - Dkg
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Michiel van der Vlist@2:280/5555 to Flavio Bessa on Monday, December 11, 2017 11:11:29
    Hello Flavio,

    On Monday December 11 2017 07:43, you wrote to Ward Dossche:

    I just would like to be able to contribute in the future, and
    was asking for guidance on what to read, in order to understand the
    role and maybe be a candidate for future terms :)

    A good start owuld be to read the FTSC documents.

    You can find them here: http://ftsc.org. Click on "Documents".


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Fred Riccio@1:132/174 to Flavio Bessa on Monday, December 11, 2017 07:38:15
    Hello Flavio!

    I just would like to be able to contribute in the future, and
    was asking for guidance on what to read, in order to understand the
    role and maybe be a candidate for future terms :)

    The documents that start with fta- will tell you about the role. They can be found at ftsc.org or grab yourself a copy of ftsc-all.zip the next time it comes around in the file echos. They are also available at the address in my origin line by WaZoo file request.


    The words below have been included in the "call for nominations" posting in this echo for at least the last two elections. They may be of some help to you.

    Note to candidates: The main task of the FTSC is to document current practise. Contrary to what the name suggests, the FTSC does not create standards out of the blue. Current Fidonet practise evolves and when
    it has stabilized, it may become a standard through FTSC documentation. Also, the FTSC is not an enforcement body. Those who wish to join the
    FTSC in order to "engineer Fidonet" may be in for a disappointment.
    Our main job is that of a clerk. We write the technical manual, we do
    not design the machine. To avoid disappointment, sysops interested in joining the FTSC are strongly advised to read the following documents:

    http://ftsc.org/docs/fta-1000.002
    http://ftsc.org/docs/fta-1001.007

    --- Msged/NT 6.0.1
    * Origin: Somewhere in New Hampshire's White Mountains (1:132/174)
  • From Ward Dossche@2:292/854 to Flavio Bessa on Monday, December 11, 2017 14:29:52

    I did not accept anything :)

    That was a goof of mine.

    I just would like to be able to contribute in the future, and was
    asking for guidance on what to read, in order to understand the role and maybe be a candidate for future terms :)

    I think you already qualify.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Dale Shipp@1:261/1466 to Alexey Vissarionov on Tuesday, December 12, 2017 00:52:00
    On 12-11-17 11:41, Alexey Vissarionov <=-
    spoke to Flavio Bessa about Future Applications <=-

    here (yes, I see that English is not your native language,
    but my own experience shows that sometimes non-native
    spea^W writers find non-trivial issues which are not
    mentioned by natives).

    True, but there are also some whose native language is not English that
    make wrong interpretations of what is written in English to suit their
    own agenda.

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)



    ... Shipwrecked on Hesperus in Columbia, Maryland. 00:54:15, 12 Dec 2017
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From Alexey Vissarionov@2:5020/545 to Dale Shipp on Tuesday, December 12, 2017 09:42:42
    Good ${greeting_time}, Dale!

    12 Dec 2017 00:52:00, you wrote to me:

    I see that English is not your native language, but my own
    experience shows that sometimes non-native spea^W writers
    find non-trivial issues which are not mentioned by natives
    True, but there are also some whose native language is not
    English that make wrong interpretations of what is written
    in English to suit their own agenda.

    For me that only means the documents _must_ _not_ (in the sense of FTA-1006) allow any and all misinterpretations. And proof-reading is definitely the best method to find the ambiguities before the documents are published.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

    ... that's why I really dislike fools.
    --- /bin/vi
    * Origin: http://openwall.com/Owl (2:5020/545)
  • From mark lewis@1:3634/12.73 to Dale Shipp on Tuesday, December 12, 2017 08:49:54

    On 2017 Dec 12 00:52:00, you wrote to Alexey Vissarionov:

    here (yes, I see that English is not your native language, but my own
    experience shows that sometimes non-native spea^W writers find
    non-trivial issues which are not mentioned by natives).

    True, but there are also some whose native language is not English
    that make wrong interpretations of what is written in English to suit their own agenda.

    definitely that... some is easily seen, too... for example...

    To participate: next FTSC election will be in the end of 2018, so
    once you'd show your involvement, any RC (including your R80C) may
    nominate you.

    "once you show your involvement" is not a requirement and never has been... one
    need technical skills and be able to read and understand the documentation... that's all...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Neoconservative angry gun-nuts in rehab with restraining orders.
    ---
    * Origin: (1:3634/12.73)
  • From Carol Shenkenberger@1:275/100 to Alexey Vissarionov on Friday, December 15, 2017 15:37:40
    Re: Future Applications
    By: Alexey Vissarionov to Flavio Bessa on Mon Dec 11 2017 11:41 am

    Good ${greeting_time}, Flavio!

    22 Nov 2017 14:57:12, you wrote to All:

    I have been following the developments of the last FTSC election,
    and of course am interested to contribute and be a part of the
    elected team in the future.

    To contribute: that's simple - you may write a FSP or participate in public proof-reading of some documents once they will be posted here (yes, I see that English is not your native language, but my own experience shows that sometimes non-native spea^W writers find non-trivial issues which are not mentioned by natives).

    Hi Flavio! To ths point Alexey is correct. There is more though. Input from Z4 on any issues that might affect them is a very needed thing.


    To participate: next FTSC election will be in the end of 2018, so once you'd show your involvement, any RC (including your R80C) may nominate you.


    He's right here too.

    However, just not to barge in and cause more trouble than
    effectively contribute, is there anything that I can go through,
    read and prepare myself for the next term?

    If you run large echomail distribution node, you most likely are ready. If you develop FTN software, you most likely are ready.

    Alexey feels you have to be a current mail distributor to some 50 nets or coding mailers/bbs software. Fact is there is a need for folks with a deep understanding of a zone or nodelist issues and other things. Also a need to make sure Z4 works with anything new.

    xxcarol
    --- SBBSecho 2.12-Win32
    * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)
  • From Nick Andre@1:229/426 to All on Friday, December 15, 2017 17:32:29
    On 15 Dec 17 15:37:40, Carol Shenkenberger said the following to Alexey Vissa

    If you run large echomail distribution node, you most likely are ready you develop FTN software, you most likely are ready.

    Alexey feels you have to be a current mail distributor to some 50 nets or coding mailers/bbs software. Fact is there is a need for folks with a deep understanding of a zone or nodelist issues and other things. Also a need t make sure Z4 works with anything new.

    Let me ask the non-technical people here. You know who you are. Tell me why we even need an FTSC anymore?

    It is not the job of the FTSC to make sure Z4 works with anything new, nor
    does the FTSC "hold hands" with people who cannot grasp how to properly run mailers or cannot understand how a nodelist works.

    The role of the FTSC is to document new stuff that becomes accepted as standard, and to clean up/help Michiel revise existing documents. Like him or not, at the very least he keeps the interest going for maintaining them.

    But it would be very logical going on 2018 now to "call it day" and dissolve the FTSC altogether; it is highly unlikely a new Fido technology is going to
    be adapted like BinkD was.

    The existing documents for the most common, popular transfer methods and storage of Fido mail is clear enough that a developer can write his own
    mailer, tosser, nodelist compiler, editor etc.

    What else is there now to do? Other than patchwork?

    Cue now to the noise...

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From mark lewis@1:3634/12.73 to Nick Andre on Friday, December 15, 2017 21:08:32

    On 2017 Dec 15 17:32:28, you wrote to All:

    Let me ask the non-technical people here. You know who you are. Tell
    me why we even need an FTSC anymore?

    interesting question...

    It is not the job of the FTSC to make sure Z4 works with anything new,

    true...

    nor does the FTSC "hold hands" with people who cannot grasp how to properly run mailers or cannot understand how a nodelist works.

    true... but it is the responsibility of all sysops to help others to understand
    technical aspects of FTN communications...

    The role of the FTSC is to document new stuff that becomes accepted as standard,

    mmmm... no... the role of the FTSC is to document how FTN works... period... some things are raised from proposals to standards when they become "widespread
    in use" but there's no definition of "widespread use"...

    and to clean up/help Michiel revise existing documents. Like him or
    not, at the very least he keeps the interest going for maintaining
    them.

    umm, wrong again... http://ftsc.org/docs/fta-1001.007

    3. Structure
    ------------

    3.1 FTSC Administrator
    ----------------------

    The FTSC administrator is appointed for a four year renewable term.

    To be eligible for appointment, an individual must be a Fidonet
    node, be actively involved in Fidonet, though not necessarily in a
    programming context, and should have proven organizational skills. A
    candidate need not be a member of the FTSC. It is recommended that a
    successful candidate not carry any *C or *EC responsibilities during
    the term of office.

    A candidate for FTSC Administrator may be nominated by any Standing
    Member.

    The FTSC Administrator is appointed on the basis of a vote by all
    Standing Members who are defined by the then-current edition of
    FTA-1003 (FTSC Membership List). A successful candidate must receive
    approval by at least a plurality of votes.

    Publication of the nominations and the voting procedure shall take
    place openly in the FTSC_PUBLIC echo, and voting shall close three
    weeks after publication of the vote. Votes shall be by netmail
    ballot to an independent enumerator.

    Responsibilities:

    1. Ensuring FTSC Mandate is adhered to.
    2. Facilitating communications links between members.
    3. Maintaining document distribution links.
    4. Coordinating all membership nominations and voting.
    5. Developing Working Groups as required.
    6. Ensuring that the FTSC seeks, accepts and responds to public
    input.
    7. Assigning FSP numbers to new Standards Proposals.


    nothing in there about revising any documents or driving that aspect of documenting FTN operations......

    But it would be very logical going on 2018 now to "call it day" and dissolve the FTSC altogether; it is highly unlikely a new Fido
    technology is going to be adapted like BinkD was.

    The existing documents for the most common, popular transfer methods
    and storage of Fido mail is clear enough that a developer can write
    his own mailer, tosser, nodelist compiler, editor etc.

    What else is there now to do? Other than patchwork?

    Cue now to the noise...

    meh...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... There's something about the Parisians- they're so very French.
    ---
    * Origin: (1:3634/12.73)
  • From Nick Andre@1:229/426 to Mark Lewis on Friday, December 15, 2017 22:36:28
    On 15 Dec 17 21:08:32, Mark Lewis said the following to Nick Andre:

    nor does the FTSC "hold hands" with people who cannot grasp how to properly run mailers or cannot understand how a nodelist works.

    true... but it is the responsibility of all sysops to help others to understand technical aspects of FTN communications...

    I'm doing my part...

    The role of the FTSC is to document new stuff that becomes accepted as standard,

    mmmm... no... the role of the FTSC is to document how FTN works... period..

    Accepted as standard amongst Sysops... you know, the people who actually take the time to download, install and use the software that a Fido developer writes. Features of that software find a good niche purpose or they don't.

    and to clean up/help Michiel revise existing documents. Like him or not, at the very least he keeps the interest going for maintaining them.

    umm, wrong again... http://ftsc.org/docs/fta-1001.007

    Good for you, you can copy and paste, completely oblivious to what I wrote.

    Reread about non-technical folk in the FTSC.., and study prior messages from Michiel carefully. Yes, notwithstanding some of the more banal and inane logic arguements, even I think some of that is a little cringe-worthy. But someone like him who is THAT logical and technical is example of what runs the FTSC.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Björn Felten@2:203/2 to Nick Andre on Saturday, December 16, 2017 06:31:54
    Let me ask the non-technical people here. You know who you are. Tell me why we even need an FTSC anymore?

    I don't regard myself as non-technical, but just the same I want to answer your question.

    With the present mandate, the FTSC is totally obsolete.

    The way to go is of course to give the FTSC the mandate to decide, not to just document. We could easily collect the hundreds of present documents and turn them all into one standard document.

    But our hands are obviously tied. Ergo, hobby programmers all around the world can happily invent all kinds of non-FTN stuff, and then send them in to the FTSC and get the shit documented, if only they have a few nodes (common practice) that are using their crappy software.



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se (2:203/2)
  • From Ward Dossche@2:292/854 to Mark Lewis on Saturday, December 16, 2017 06:38:30

    mark,

    The role of the FTSC is to document new stuff that becomes accepted ml>NA> as standard,

    mmmm... no... the role of the FTSC is to document how FTN works...

    I would call that 'semantics'. It's not a matter of being 'more right' than someone else who already is right.

    The FTSC administrator is appointed for a four year renewable term.
    """""""""
    Impossible. An appointment is done by another person, at best he is elected.

    To be eligible for appointment, an individual must be a Fidonet
    node, be actively involved in Fidonet, though not necessarily in a programming context, and should have proven organizational skills. A candidate need not be a member of the FTSC.

    In a way that is a violation of P4 3.5 although you will respond that the FTSC is not guided by P4 where-upon I will answer that FTSC is metioned 3 times in P4 with te P4 being the supreme document of Fidonet, hence the FTSC falls under
    specific stipulations. Where-upon you ... [I like things to move forward so I usurped your persona already a bit ... 8-) ]◄ ◄ ◄ ◄

    It is recommended that a
    successful candidate not carry any *C or *EC responsibilities during
    the term of office.

    Well, you know where that is going to take us. The current 'administrator' at times calls himself "coordinator", has bashed at least one RC that I know of in
    private netmail signing with "chairman" trying to force FTSC-things down his throat while 'enforcement' is not part of the FTSC-mandate ... and is an RC ...
    which he campaigned against ... until when he became an RC himself.

    As a reminder, I declined my nomination because I am a *C.

    An interesting matter which seems not to be covered by the document which you are quoting from is what happens when a standing 'administrator' who is up for re-election, runs and gets trashed ... in other words gets a vote of "no confidence" from the constituency ... When the voting RCs have no confidence, can such a person remain "coordinator" ?

    A successful candidate must receive
    approval by at least a plurality of votes.

    A clarification is required here. A plurality of all votes cast (including the abstentions) or a plurality of the 'Ayes' versus the 'Nays'.

    You guys got work to do on such shabby definitions.

    Take care,

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Nicholas Boel@1:154/10 to mark lewis on Saturday, December 16, 2017 22:19:14
    Hello mark,

    On Fri Dec 15 2017 21:08:32, mark lewis wrote to Nick Andre:

    Let me ask the non-technical people here. You know who you are.
    Tell me why we even need an FTSC anymore?

    interesting question...

    Very.

    nor does the FTSC "hold hands" with people who cannot grasp how
    to properly run mailers or cannot understand how a nodelist
    works.

    true... but it is the responsibility of all sysops to help others to understand technical aspects of FTN communications...

    If it's the responsibility of all sysops, then there's no job for the FTSC in that regard.

    The role of the FTSC is to document new stuff that becomes
    accepted as standard,

    mmmm... no... the role of the FTSC is to document how FTN works... period... some things are raised from proposals to standards when they become "widespread in use" but there's no definition of "widespread use"...

    Making it kinda redundant these days, eh? No definition of widespread use anymore..

    and to clean up/help Michiel revise existing documents. Like him
    or not, at the very least he keeps the interest going for
    maintaining them.

    umm, wrong again... http://ftsc.org/docs/fta-1001.007

    This will be good..

    3. Structure
    ------------

    3.1 FTSC Administrator
    ----------------------

    The FTSC administrator is appointed for a four year renewable term.

    To be eligible for appointment, an individual must be a Fidonet
    node, be actively involved in Fidonet, though not necessarily in a
    programming context, and should have proven organizational skills. A
    candidate need not be a member of the FTSC. It is recommended that a
    successful candidate not carry any *C or *EC responsibilities during
    the term of office.

    Oh wait, what? Definite proven organizational skills, but.. the recommendation after that has failed for a long time.

    1. Ensuring FTSC Mandate is adhered to.
    2. Facilitating communications links between members.
    3. Maintaining document distribution links.
    4. Coordinating all membership nominations and voting.
    5. Developing Working Groups as required.
    6. Ensuring that the FTSC seeks, accepts and responds to public
    input.
    7. Assigning FSP numbers to new Standards Proposals.

    Nobody can argue Michiel does not do any of the above, and actually.. is and would be the best at it in the future.

    nothing in there about revising any documents or driving that aspect
    of documenting FTN operations......

    Nope, that's the job of the members.. and should be.

    But it would be very logical going on 2018 now to "call it day"
    and dissolve the FTSC altogether; it is highly unlikely a new
    Fido technology is going to be adapted like BinkD was.

    The existing documents for the most common, popular transfer
    methods and storage of Fido mail is clear enough that a developer
    can write his own mailer, tosser, nodelist compiler, editor etc.

    What else is there now to do? Other than patchwork?

    Cue now to the noise...

    meh...

    By that reponse, you partially agree, but don't want to argue about it. Sure there's still new software being developed, but most go by the current standards. THEN as GAF sysops we have to intervene and try to show them the new
    stuff that apparantly never made it to standard, even though they should have been (we see people complain about it on a daily basis!) and some of these proposals get forced down the throats of new programmers by people in the FTSC.

    If it's not a standard, they usually don't initially implement it. When people bitch that it's not there, programmer says "well it's only a proposal!" and, there you have that circular dependency rearing it's head again. ;(

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Nick Andre on Saturday, December 16, 2017 22:31:14
    Hello Nick,

    On Fri Dec 15 2017 22:36:28, Nick Andre wrote to Mark Lewis:

    Reread about non-technical folk in the FTSC.., and study prior
    messages from Michiel carefully. Yes, notwithstanding some of the more banal and inane logic arguements, even I think some of that is a
    little cringe-worthy. But someone like him who is THAT logical and technical is example of what runs the FTSC.

    Well put, and coming from a non-FTSC member programmer of FTN software. You're not the first (well, maybe here in this echo) to say this.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Björn Felten on Saturday, December 16, 2017 22:33:48
    Hello Björn,

    On Sat Dec 16 2017 06:31:54, Björn Felten wrote to Nick Andre:

    Let me ask the non-technical people here. You know who you are.
    Tell me why we even need an FTSC anymore?

    I don't regard myself as non-technical, but just the same I want to answer your question.

    With the present mandate, the FTSC is totally obsolete.

    The way to go is of course to give the FTSC the mandate to decide,
    not to just document. We could easily collect the hundreds of present documents and turn them all into one standard document.

    Wait what? Give the FTSC more power? No. Sorry.

    But our hands are obviously tied. Ergo, hobby programmers all
    around the world can happily invent all kinds of non-FTN stuff, and
    then send them in to the FTSC and get the shit documented, if only
    they have a few nodes (common practice) that are using their crappy software.

    Most programmers of the hobby these days DON'T send their shit in to get documented. Nobody cares about the FTSC, especially in othernets. Hell, in the othernet I run as well as the official Mystic BBS software othernet, there are 3 or more *NEW* BBS softwares currently being developed! Do you ever wonder why
    their technology hasn't been brought here?

    Makes you wonder. People avoid Fidonet because of the enforcing of "rules" and "standards". Some people just want to do whatever the hell they want, and make it work. THEN, and only then, do they have to worry about backwards compatibility with the shit that's out there from the last few decades.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Ward Dossche on Saturday, December 16, 2017 22:40:52
    Hello Ward,

    On Sat Dec 16 2017 06:38:30, Ward Dossche wrote to Mark Lewis:

    In a way that is a violation of P4 3.5 although you will respond that
    the FTSC is not guided by P4 where-upon I will answer that FTSC is metioned 3 times in P4 with te P4 being the supreme document of
    Fidonet, hence the FTSC falls under specific stipulations. Where-upon
    you ... [I like things to move forward so I usurped your persona
    already a bit ... 8-) ]

    Ugh.. Fuck P4. Old and outdated, and nobody can agree to change it because half
    of the people involved are too stubborn or don't even know what's going on at the time.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Ward Dossche@2:292/854 to Nicholas Boel on Sunday, December 17, 2017 07:07:26

    Nick,

    Ugh.. Fuck P4. Old and outdated, and nobody can agree to change it
    because half of the people involved are too stubborn or don't even know what's going on at the time.

    Don't blame me for not having tried it.

    I love P4 ... you can prove and disprove anything with it.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Sean Dennis@1:18/200 to Nicholas Boel on Sunday, December 17, 2017 01:13:27
    Nicholas Boel wrote to Bj}{rn Felten <=-

    Nobody cares about the FTSC, especially in othernets.

    You must care because you're in here bloviating about it.

    --Sean


    ... Open mouth, insert foot, echo internationally.
    --- MultiMail/Linux
    * Origin: Outpost BBS * Limestone, TN, USA (1:18/200)
  • From Nicholas Boel@1:154/10 to Ward Dossche on Sunday, December 17, 2017 00:38:06
    Hello Ward,

    On Sun Dec 17 2017 07:07:26, Ward Dossche wrote to Nicholas Boel:

    Don't blame me for not having tried it.

    I don't.

    I love P4 ... you can prove and disprove anything with it.

    Keeps the arguments active for decades, too! ;(

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Sean Dennis on Sunday, December 17, 2017 00:38:56
    Hello Sean,

    On Sun Dec 17 2017 01:13:26, Sean Dennis wrote to Nicholas Boel:

    Nobody cares about the FTSC, especially in othernets.

    You must care because you're in here bloviating about it.

    And you as well.

    BTW, in case you just can't seem to catch up and need more clarification, the reference is not on myself, it's on the huge majority of Fidonet sysops, especially sysops who have steered clear of Fidonet for decades only to join up
    when and while everything else is drying up for just a tad more activity on their BBS to provide any users they/we may have.

    But thanks for jumping in to try to take a cheap shot. As a matter of fact, I do care.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Gerrit Kuehn@2:240/12 to Ward Dossche on Sunday, December 17, 2017 11:44:12
    Hello Ward!

    17 Dec 17 07:07, Ward Dossche wrote to Nicholas Boel:


    I love P4 ... you can prove and disprove anything with it.

    Yeah, great if you prefer arguing above actually getting something done.


    Regards,
    Gerrit

    ... 11:44AM up 343 days, 14:23, 3 users, load averages: 0.32, 0.23, 0.18

    --- Msged/BSD 6.1.2
    * Origin: We are the second generation (2:240/12)
  • From Markus Reschke@2:240/1661 to Nicholas Boel on Sunday, December 17, 2017 12:35:08
    Hello Nicholas!

    Dec 16 22:19 2017, Nicholas Boel wrote to mark lewis:

    it. Sure there's still new software being developed, but most go by
    the current standards. THEN as GAF sysops we have to intervene and
    try to show them the new stuff that apparantly never made it to
    standard, even though they should have been (we see people complain
    about it on a daily basis!) and some of these proposals get forced
    down the throats of new programmers by people in the FTSC.

    I agree that there are proposals which should have become a standard. But if the majority of the FTSC members vote against it, I have to accept that. For example, we had that with CDP, despite the fact that it is still supported by a
    few nodes (and by much more in the past). It was ignored for about 10 years and
    then voted down.

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Ward Dossche@2:292/854 to Markus Reschke on Monday, December 18, 2017 07:11:09
    Markus,

    I agree that there are proposals which should have become a standard. But if the majority of the FTSC members vote against it, I have to accept
    that. For example, we had that with CDP, despite the fact that it is
    still supported by a few nodes (and by much more in the past). It was ignored for about 10 years and then voted down.

    I would say a standard becomes a standard because a sufficient number of developers or users use it. That would shed a totally different role on the mandate of the FTSC.

    Take for example the case of IPv6 ... it's as good as nowhere in the nodelist, yet there is FTSC-documentation dealing with it.

    In the past, maybe more than 10 years ago, there was a sysop [who has departed the nodelist in the meantime] who wanted to push a particular issue past me and
    it didn't work, so he had himself elected in the FTSC and pushed it through that body although it wasn't used. Can't remember the name anymore nor what the
    issue was ... it wasn't accepted anyway and never made it to the nodelist.

    There will always be people with an agenda.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Markus Reschke@2:240/1661 to Ward Dossche on Monday, December 18, 2017 14:03:48
    Hi Ward!

    Dec 18 07:11 2017, Ward Dossche wrote to Markus Reschke:

    I would say a standard becomes a standard because a sufficient number
    of developers or users use it. That would shed a totally different
    role on the mandate of the FTSC.

    We don't have any clear definition of "sufficient number" or "widespread use". CDP is/was used primarily in/around R24. So it was invisible for most of the other regions, but in widespread use in R24.

    Take for example the case of IPv6 ... it's as good as nowhere in the nodelist, yet there is FTSC-documentation dealing with it.

    There are about 55 nodes supporting IPv6. Anyway, IPv6 is a special case since IPv4 address space is becoming a scarce commodity. That forces many ISPs/telcos
    to migrate customers to DS-lite and other solutions, resulting in the loss of IPv4 reachability in many cases. It's a good idea to be prepared for that.

    There will always be people with an agenda.

    Have I told you about my secret plan of world domination? :)

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Ward Dossche@2:292/854 to Markus Reschke on Monday, December 18, 2017 15:38:48

    Markus,

    Have I told you about my secret plan of world domination? :)

    Need help ? 8-)

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From mark lewis@1:3634/12.73 to Nick Andre on Monday, December 18, 2017 14:45:24

    On 2017 Dec 15 22:36:28, you wrote to me:

    The role of the FTSC is to document new stuff that becomes accepted
    as standard,

    mmmm... no... the role of the FTSC is to document how FTN works...
    period..

    Accepted as standard amongst Sysops... you know, the people who
    actually take the time to download, install and use the software that
    a Fido developer writes. Features of that software find a good niche purpose or they don't.

    FWIW: all i was targetting was your use of the phrase "document new stuff"...


    and to clean up/help Michiel revise existing documents. Like him or
    not, at the very least he keeps the interest going for maintaining
    them.

    umm, wrong again... http://ftsc.org/docs/fta-1001.007

    Good for you, you can copy and paste, completely oblivious to what I
    wrote.

    FWIW: i was only targetting your use of the phrase "help michiel"...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... I'm so lonesome in the saddle since my horse died.
    ---
    * Origin: (1:3634/12.73)
  • From Sean Dennis@1:18/200 to Nicholas Boel on Sunday, December 24, 2017 16:56:02
    Hello Nicholas,

    17 Dec 17 00:38 at you wrote to me:

    And you as well.

    I'm a member of the FTSC so I have a vested interest in it. You, on the other hand, don't.

    But thanks for jumping in to try to take a cheap shot. As a matter of fact, I do care.

    You have an odd way of showing it by insulting the very group you proclaim to care about.

    Later,
    Sean

    ... The light of a hundred stars does not equal the light of the moon.
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Outpost BBS * Limestone, TN, USA (1:18/200)
  • From Nicholas Boel@1:154/10 to Sean Dennis on Sunday, December 24, 2017 22:28:50
    Hello,

    On Sun Dec 24 2017 16:56:02 -0500, Sean Dennis -> Nicholas Boel wrote:

    But thanks for jumping in to try to take a cheap shot. As a matter of
    fact, I do care.

    You have an odd way of showing it by insulting the very group you proclaim to care about.

    First off, you may want to take a quick look at the FTSC memberlist.. I wouldn't be a part of it if I didn't give a shit.

    If you think "Nobody cares about the FTSC, especially in othernets" is insulting the FTSC, then you're a damaged individual. I take it you've gotten insulted a lot in life and are just naturally defensive now?

    If everyone cared about the FTSC these days, there would be a lot more members than there are now. Quite a few programmers (even ones that have been a part of
    the FTSC in the past) don't care about it any more, as much as I'd like to see
    that not be the case.

    I'm only speaking truth here, whether you like it or not.

    Regards,
    Nick

    --- Claws Mail 3.15.0 (GTK+ 2.24.31; x86_64-w64-mingw32)
    * Origin: thePharcyde_ distribution system (1:154/10)
  • From Richard Menedetter@2:310/31 to Dale Shipp on Thursday, December 28, 2017 12:49:30
    Hi Dale!

    12 Dec 2017 00:52, from Dale Shipp -> Alexey Vissarionov:

    there are also some whose native language is not English that make
    wrong interpretations of what is written in English to suit their own agenda.

    Have not really seen that.
    What I have seen plenty is texts that are absolutely badly written, and are ambiguous and allow multiple interpretations, because the text is NOT clear.

    And interpretations that do not match with your or the authors interpretation are not wrong.
    They are only wrong if the interpretation cannot be deduced from the text itself.
    Otherwise the author simply did a bad job, and phrased the text in a way that can be (validly!) interpreted in different ways.

    What do we learn from it??
    Simply ... texts should be written in a way that is unambiguous.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Why are there Interstate highways in Hawaii? (2:310/31)
  • From Ward Dossche@2:292/854 to Richard Menedetter on Thursday, December 28, 2017 13:32:46
    Richard,

    Simply ... texts should be written in a way that is unambiguous.

    Well said.

    I am tired about this nonsense that I'm not a native speaker so don't understand the language well enough.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Markus Reschke@2:240/1661 to Richard Menedetter on Thursday, December 28, 2017 13:56:58
    Hi Richard!

    Dec 28 12:49 2017, Richard Menedetter wrote to Dale Shipp:

    What do we learn from it??
    Simply ... texts should be written in a way that is unambiguous.

    Absolutely right! For example, there's a very annoying misinterpretation of the
    RFC for SIP. The RFC doesn't state anything on which codecs to use for both directions (caller/callee), i.e. same or different codecs. Some vendors simply assume both directions must use the same codec. Other vendors support different
    codecs for both directions. So you get one-way audio if you use the wrong combination of SIP phones/PBXs. It's so <facepalm> :(

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Dale Shipp@1:261/1466 to Ward Dossche on Friday, December 29, 2017 00:59:00
    On 12-28-17 13:32, Ward Dossche <=-
    spoke to Richard Menedetter about Re: Future Applications <=-

    Simply ... texts should be written in a way that is unambiguous.

    Well said.

    Of course.


    I am tired about this nonsense that I'm not a native
    speaker so don't understand the language well enough.

    What I was talking about was examples where it was quite clear that an
    item was optional, but someone insisted that people were not in
    compliance if they did not implement it. One example of several
    possible: the standards state what form a MSGID should take, but do not
    insist that one be present. Hence for someont to state that a system is
    not in compliance because they do not have a MSGID is not a matter of
    not being a native speaker, but simply one of attempting to impose their
    own bias.

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)


    ... Shipwrecked on Hesperus in Columbia, Maryland. 01:03:54, 29 Dec 2017
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From Ward Dossche@2:292/854 to Dale Shipp on Friday, December 29, 2017 09:40:38

    Dale,

    What I was talking about was examples where it was quite clear that an
    item was optional, but someone insisted that people were not in
    compliance if they did not implement it.

    I got the point. Thank you for the clarification.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Richard Menedetter@2:310/31 to Ward Dossche on Saturday, December 30, 2017 12:57:32
    Hi Ward!

    18 Dec 2017 07:11, from Ward Dossche -> Markus Reschke:

    For example, we had that with CDP, despite the fact that it is still
    supported by a few nodes (and by much more in the past).
    It was ignored for about 10 years and then voted down.
    I would say a standard becomes a standard because a sufficient number
    of developers or users use it.

    CDP was in widespread use in germany.

    Take for example the case of IPv6 ... it's as good as nowhere in the nodelist, yet there is FTSC-documentation dealing with it.

    That is a bit of a corner case.
    Many ISPs do not offer public IPv4 addresses any more.
    You get DS-Lite meaning public IPv6 and private IPv4.
    In that light it makes much sense to have a solution for it.

    Actually Belgium is at the top of the IPv6 usage, as a Belgian colleague of mine always reminds me ;)

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Why do people who know the least know it the loudest? (2:310/31)
  • From Robert Wolfe@1:116/17 to RICHARD MENEDETTER on Saturday, December 30, 2017 07:06:00
    Richard Menedetter wrote to Ward Dossche <=-

    Many ISPs do not offer public IPv4 addresses any more.
    You get DS-Lite meaning public IPv6 and private IPv4.
    In that light it makes much sense to have a solution for it.

    Yeah, fortunately, however, my ISP, Comcast, offers BOTH IPv4 and IPv6 addresses to those of us with Business Class service (which, for the past
    two or so years has been nothing but flawless for me). The only drawback
    is that you can have one or the other and not both IPv4 AND IPv6 in use
    at the same time.

    ... MultiMail, the new multi-platform, multi-format offline reader!
    --- MultiMail/OS/2 v0.50
    * Origin: Omicron Theta * Olive Branch MS * (662) 408-4283 (1:116/17)
  • From Markus Reschke@2:240/1661 to Robert Wolfe on Saturday, December 30, 2017 16:25:32
    Hi Robert!

    Dec 30 07:06 2017, Robert Wolfe wrote to RICHARD MENEDETTER:

    Yeah, fortunately, however, my ISP, Comcast, offers BOTH IPv4 and
    IPv6 addresses to those of us with Business Class service (which, for
    the past two or so years has been nothing but flawless for me). The
    only drawback is that you can have one or the other and not both IPv4
    AND IPv6 in use at the same time.

    Interesting. It would be great to get feedback from all regions about IPv4/6 deployment and things to watch out. We have to make sure that our network works
    fine with all the local peculiarities. BTW, we got a dedicated echo for IPv6: IPV6 ;)

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Ward Dossche@2:292/854 to Dale Shipp on Thursday, January 04, 2018 08:13:23


    Dale,

    What I was talking about was examples where it was quite clear that an
    item was optional, but someone insisted that people were not in
    compliance if they did not implement it.

    I got the point. Thank you for the clarification.

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Carol Shenkenberger@1:275/100 to Richard Menedetter on Saturday, January 06, 2018 11:22:50
    Re: Future Applications
    By: Richard Menedetter to Ward Dossche on Sat Dec 30 2017 12:57 pm

    For example, we had that with CDP, despite the fact that it is
    still supported by a few nodes (and by much more in the past).
    It was ignored for about 10 years and then voted down.
    I would say a standard becomes a standard because a sufficient
    number of developers or users use it.

    CDP was in widespread use in germany.

    I fought to keep CDP in but lost the battle along with Michiel. I believe it damaged Germany to remove it. Basically my stance is any one item in use and needed, should be retained if it harms no one else. I'd have to see if Michiel retained any records of that vote but it was turned down by those who didn't 'get it' on automated point setups that often later can turn full fledged nodes. It was actually pretty slick stuff!

    xxcarol
    --- SBBSecho 2.12-Win32
    * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)
  • From Carol Shenkenberger@1:275/100 to Markus Reschke on Saturday, January 06, 2018 11:34:09
    Re: Re: Future Applications
    By: Markus Reschke to Robert Wolfe on Sat Dec 30 2017 04:25 pm

    Interesting. It would be great to get feedback from all regions about IPv4/6 deployment and things to watch out. We have to make sure that our network works fine with all the local peculiarities. BTW, we got a dedicated echo for IPv6: IPV6 ;)

    I might remind one of my nodes of that. He's not getting a domain recognition (isn't CM listed either). Polls me with no issues at all.

    xxcarol
    --- SBBSecho 2.12-Win32
    * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)