1. Which FTSC projects/products interest you the most? (can be
several). Need not come with exact document name as some of them span several.
2. How familar are you with the issues that *C's face? No harm if
you are not or never have been one but include alternets as the experience can be the same.
3. If you have been a *C and experienced a site that needed
alternative to normal delivery, how did you deal with it? If you have not experienced that, what do you think you would do?
4. Since there is a call to conduct FTSC business mostly in the FTSC Public echo, how do you feel about that and why? What should remain
in the private echo and what transparent here?
5. How good do you think you are at working with others, especially
if their view is opposite to yours? How do you handle that?
1. Which FTSC projects/products interest you the most? (can be
several). Need not come with exact document name as some of them
span several.
2. How familar are you with the issues that *C's face? No harm if
you are not or never have been one but include alternets as the
experience can be the same.
3. If you have been a *C and experienced a site that needed
alternative to normal delivery, how did you deal with it?
If you have not experienced that, what do you think you would do?
4. Since there is a call to conduct FTSC business mostly in the FTSC Public echo, how do you feel about that and why? What should remain
in the private echo and what transparent here?
5. How good do you think you are at working with others, especially
if their view is opposite to yours? How do you handle that?
Good ${greeting_time}, Carol!
12 Nov 2017 11:51:32, you wrote to All Candidates:
1. Which FTSC projects/products interest you the most? (can be
several). Need not come with exact document name as some of them
span several.
All, at least because I run the ftsc.org site containing them.
I've managed a network segment for AmigaNet, for example. Besides thatI'm
coordinating the echo distribution in R24.
I'm fine with alternative delivery methods. Long time ago I've written a tool for combining FTS and UUCP into one transfer.
:) Transparency would help the community to get a better picture of each member/candidate and would also encourage members to be more productive. Maybe internal coordination and similar things should be kept private.But
this needs to be discussed with the other members.
It's not about someone being right or wrong, it's about producing good documentation. Different points of view actually help. The only disappointing thing is, when someone ignores common practices of other zones.
1. Which FTSC projects/products interest you the most? (can be
several). Need not come with exact document name as some of them
span several.
All, at least because I run the ftsc.org site containing them.
2. How familar are you with the issues that *C's face? No harm if
you are not or never have been one but include alternets as the
experience can be the same.
Being the hub in a quite large network (2:5020) I'm aware of some.
3. If you have been a *C and experienced a site that needed
alternative to normal delivery, how did you deal with it?
Does the "site" mean "node" here?
If you have not experienced that, what do you think you would do?
I have such experience, and (just a small) part of my knowledge is being (slowly) written as a FSP.
4. Since there is a call to conduct FTSC business mostly in the FTSC
Public echo, how do you feel about that and why? What should remain
in the private echo and what transparent here?
That was my idea, so I fully agree with it :-)
large5. How good do you think you are at working with others, especially
if their view is opposite to yours? How do you handle that?
That heavily depends of the opponents' experience and competence: I'd consider more seriously the person who writes FTN software or runs a
distribution node, than a chatterbox from a two-human "network" (or even "region").
Two numbers to compare:
gremlin@nb:~/dev/husky/hpt > git log | grep ^commit | wc -l
68
gremlin@fido:~ > grep ^link ~/fido/etc/links | wc -l
202
Two numbers to compare:
gremlin@nb:~/dev/husky/hpt > git log | grep ^commit | wc -l
68
gremlin@fido:~ > grep ^link ~/fido/etc/links | wc -l
202
Smile, you may have to explain that to the average person here
1. Which FTSC projects/products interest you the most? (can be
several). Need not come with exact document name as some of them
span several.
All, at least because I run the ftsc.org site containing them.grin, I like these questions because they arent the normal. They
seem to bring out more of 'who we are' than the standard ones.
Probably most here didnt kow you maintain the site.
3. If you have been a *C and experienced a site that needed
alternative to normal delivery, how did you deal with it?
Does the "site" mean "node" here?Yes. I'm not expecting something as wild as me at sea for months
Like possibly node/site has to be emailed instead of netmailed
due to frequent travel or something like that. Idea is 'out of
the normal pattern'.
If you have not experienced that, what do you think you would do?
I have such experience, and (just a small) part of my knowledge isWorks for me! BTW, I am in on some of that if I catch your meaning.
being (slowly) written as a FSP.
5. How good do you think you are at working with others, especially
if their view is opposite to yours? How do you handle that?
That heavily depends of the opponents' experience and competence:Fair enough that this is your call.
I'd consider more seriously the person who writes FTN software or
runs a large distribution node, than a chatterbox from a two-human
"network" (or even "region").
Two numbers to compare:Smile, you may have to explain that to the average person here trying
gremlin@nb:~/dev/husky/hpt > git log | grep ^commit | wc -l
68
gremlin@fido:~ > grep ^link ~/fido/etc/links | wc -l
202
to figure out who to vote for as the RC calls come out. Most are not
*nix admin or use husky.
gremlin@nb:~/dev/husky/hpt > git log | grep ^commit | wc -l
68
looks like "my li'l winkie is bigger than your's" stuff to me... supposedly he has 68 commits to the HPT repository
Alas, I don't maintain the site - I only run it. That means, I
maintain the server (actually, the container which may migrate among different servers), where the FTSC site resides.
As that was reminded by Fred, the position of site maintainer is vacant, and whether there would be any volunteers, they are welcome.
----- snip -----All, at least because I run the ftsc.org site containing them.
You *host* (provide the server hardware and software) the web site.
When I took over daily maintenance In April, 2014 there were MANY
missing documents. Those must have been the ones that you weren't "interested" in :)
Since then I have added the missing ones and automated the process so
new documents are added automatically within minutes of being hatched. Even now that I am no longer a FTSC member, I still provide that
service.
Even now that I am no longer a FTSC member, I STILL PROVIDE THAT
SERVICE.
togremlin@nb:~/dev/husky/hpt > git log | grep ^commit | wc -l
68
looks like "my li'l winkie is bigger than your's" stuff to me...
supposedly he has 68 commits to the HPT repository
I would say that this is a very important point that he contributed much
a FTN related software project.
Also I am wondering what you mean with "supposedly" ...
do you want to say that the number presented is wrong?
On what are you basing that assumption?
gremlin@fido:~ > grep ^link ~/fido/etc/links | wc -l
202
Smile, you may have to explain that to the average person here trying
to figure out who to vote for as the RC calls come out. Most are not *nix admin or use husky. I would hope all knw you are very technical
but suspect you zoomed over many heads there that are going to be
voting.
(For the rest, been a bit but he seems to be pulling up a list of
links? I am not a *nix person other than casually since about 2002 and
i never used HPT. I could be wrong but he looks tobe piping changes
to commit them to some HPT area then greping them back out. AV is
very technical and no one would disagree with that statement. He's probably the most technical on the FTSC).
People who want to get Fidonet links (primarily for echomail feeds)
have different types of Internet connections: most are behind dumb
NATs, some connections are additionally limited on which outer
services are allowed (especially in corporate networks) and some are
just enormously expensive (mobile connections being the most obvious example). So, to provide these downlinks with echomail, we have to
find methods of circumventing all the restrictions they have.
Sorry! I couldn't resist ;)
Actually, I don't care... We (in R50) have active development of the
FTN software, but nobody else want to participate in FTSC.
Guess, why.
Unfortunately his search pattern isn't specific enough to catch only the links, since there are several keyworks starting with "link". The next point is that the keywords might also be uppercase.
Sorry! I couldn't resist ;)
gremlin@fido:~ > grep ^link ~/fido/etc/links | wc -l
202
Smile, you may have to explain that to the average personUnfortunately his search pattern isn't specific enough to catch only
the links, since there are several keyworks starting with "link".
grep -ic "^link\s" ~/fido/etc/links
Sorry! I couldn't resist ;)
gremlin@nb:~/dev/husky/hpt > git log | grep ^commit | wc -l
68
I would say that this is a very important point that he68 commits is "much"??
contributed much to a FTN related software project.
anyone can do that in five minutes just updating spelling mistakes in comments...
one can also easily set up a bunch of link lines, grep them out and
post the number... logs can be faked as can most everything else...
Also I am wondering what you mean with "supposedly" ...exactly that... there's nothing in the statement that shows what those commits are/were...
On what are you basing that assumption?there is no assumption...
gremlin@nb:~/dev/husky/hpt > git log | grep ^commit | wc -l
68
I would say that this is a very important point that he
contributed much to a FTN related software project.
68 commits is "much"??It is more then 50.
anyone can do that in five minutes just updating spelling mistakesCorrect ... anyone COULD do it. Not many do.
in comments...
On what are you basing that assumption?
there is no assumption...He stated that he made 68 commits to Husky.
1. Which FTSC projects/products interest you the most? (can beWell, currently I don't know, how the workflow is organized. It, depends, whats
several). Need not come with exact document name as some of them span several.
2. How familar are you with the issues that *C's face? No harm ifI'm since 2005 NC and since 2012 RC24.
you are not or never have been one but include alternets as the
experience can be the same.
3. If you have been a *C and experienced a site that neededUsually I'm trying to connect however it is possible. Currently ftp/smtp is used, also normal binkd connects. I've got pots lines as well, but theese are not used anymore. This depends of the technical changing by our local telcos from isdn to voip.
alternative to normal delivery, how did you deal with it? If you have
not experienced that, what do you think you would do?
4. Since there is a call to conduct FTSC business mostly in the FTSC Public echo, how do you feel about that and why? What should remainI have no opinion about this at this time. I get the drafts and text-files from
in the private echo and what transparent here?
5. How good do you think you are at working with others, especiallyThe handling depends on the argument. Usually I try to let them calm down.
if their view is opposite to yours? How do you handle that?
The exhaustion of IPv4 address space forces many ISPs/telcos to
migrate customers to CGNAT or DSlite. I fully agree that we have to
look into finding solutions for nodes affected by those issues.
Another problem is legacy software only supporting IPv4.
The conclusion was that running a Fidonet node on a DS-Lite connection is doable.
On 15 Nov 17 10:53:57, Michiel Van Der Vlist said the following to
Markus Resch
The conclusion was that running a Fidonet node on a DS-Lite
connection is doable.
My entire Fido operation has ran on Ds-Lite for many years now.
And no ipv6..
Ds-lite??
Carol Shenkenberger wrote to All Candidates <=-
1. Which FTSC projects/products interest you the most? (can be
several). Need not come with exact document name as some of them span several.
2. How familar are you with the issues that *C's face? No harm if you are not
or never have been one but include alternets as the experience can be
the same.
3. If you have been a *C and experienced a site that needed
alternative to normal delivery, how did you deal with it? If you have
not experienced that, what do you think you would do?
4. Since there is a call to conduct FTSC business mostly in the FTSC Public echo, how do you feel about that and why? What should remain in the private echo and what transparent here?
5. How good do you think you are at working with others, especially if their view is opposite to yours? How do you handle that?
For candidates, there are no right or wrong answers here. While we may
see some
differences between zones, we may also see a lot of commonality that wasn't clear before. We succeed because we span a wide range of capabilities regardless of where we physically reside.
And no ipv6..
Ds-lite??
My misunderstanding. DS-Lite means something totally different in Canada.
Carol Shenkenberger wrote to All Candidates <=-
Hi Carol,
I'll be happy to answer your questions.
1. Which FTSC projects/products interest you the most? (can be
several). Need not come with exact document name as some of them
span several.
To be honest, I haven't kept up with a lot, though I know there is a debate about "mobile nodes" going on. I agree with Michiel that there probably isn't going to be a lot of expansion technology-wise with FTN but there is a dire need for documenting what already is available and working.
2. How familar are you with the issues that *C's face? No harm if
you are not
or never have been one but include alternets as the experience can
be the same.
Having been RC11 in the early 2000s, yes, I am. I have also been running The Micronet Information Network, a FTN-style network with QWK/NNTP gates, for 17 years now. I have been the zone coordinator the entire time. Lots of little headaches but they get fixed.
3. If you have been a *C and experienced a site that needed
alternative to normal delivery, how did you deal with it? If you
have not experienced that, what do you think you would do?
I have no problems with alternative delivery methods. I would say that BinkP is pretty standard in this age of the Internet though POTS is still a viable option also. My system can handle BinkP, FTP, ifcico, and mailer over telnet connections.
4. Since there is a call to conduct FTSC business mostly in the
FTSC Public echo, how do you feel about that and why? What should
remain in the private echo and what transparent here?
I don't have a problem with the FTSC conducting a majority of its business in the open. What should remain private are any interpersonal issues within the FTSC (though we all know what happens with that eventually) or discussions about ideas and subjects that should be discussed privately first and get the agreement of the majority of the group before discussing things publicly.
5. How good do you think you are at working with others, especially
if their view is opposite to yours? How do you handle that?
I don't have a problem with working with others. Outright castigation for suggesting something, well, not a good idea.
For candidates, there are no right or wrong answers here. While we
may see some
differences between zones, we may also see a lot of commonality that
wasn't clear before. We succeed because we span a wide range of
capabilities regardless of where we physically reside.
Fidonet has been and will be "controlled anarchy". We're all in this together whether we realize it or not. The network's survival and viability in today's age of instant gratification rests on our ability to modernize, extend, and make the network attractive to new sysops who would be interested in participating.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,036 |
Nodes: | 15 (1 / 14) |
Uptime: | 62:26:25 |
Calls: | 809 |
Calls today: | 15 |
Files: | 95,174 |
D/L today: |
2,115 files (209M bytes) |
Messages: | 297,896 |
Posted today: | 2 |