Much lower take up than I thought might happen. No more takers with a website to their name?
Keep posting a reminder. Maybe folks step away from their systems
But I think this project might be best automated somehow. Let the
Then when you look at those one by one, you can practically grab the little screen shot as a logo.
Much lower take up than I thought might happen. No more takers with a website to their name?
To far beyond my limitations. Waaaaaaaaay beyond...
My thoughts went along the lines, if you don't apply for whatever
reason, then my workload is already that much lighter :) IF you do
apply, one or two at a time as so far, then the work load isn't so
large I can't manage it. And I can keep an eye on Avon's Systems
Retired messages to remove people.
Just going by the nodelist concerns me in so far as theres no
guarantee of any kind of particular data. Manually adding means I can
be certain the application fits the bill on all fronts, and talk to
whoever it is applying to fix anything that needs it.
Name Sure its in the nodelist.
URL Quite possibly different to the BBS address
Logo Can't find one of these in there.
Much lower take up than I thought might happen. No more takers with a website to their name?
Planning on it, just haven't had the time.
Just going by the nodelist concerns me in so far as theres no guarantee
of any kind of particular data. Manually adding means I can be certain
the application fits the bill on all fronts, and talk to whoever it is applying to fix anything that needs it.
Name Sure its in the nodelist.
URL Quite possibly different to the BBS address
Logo Can't find one of these in there.
But I think this project might be best automated somehow. Let the computer do the work for you. As you mentioned previously, maybe use
the nodelist to identify the system, and then "visit" the site automatically to collect the login/logo screen shot.
Also, Python script here, it's dirty and kludgy, WIP, but I'll clean it up tomorrow.
https://github.com/robbiew/nodelist-to-json
I'll then automate the update when new nodelists are published, so the API stays up to date.
Not sure if anyone else finds this useful, but there it is!
Much lower take up than I thought might happen. No more takers with a website to their name?
I have an idea... create some info about this, what to do etc. and
Quoting Spectre to Anybody <=-
Much lower take up than I thought might happen. No more takers with
a website to their name?
Also, Python script here, it's dirty and kludgy, WIP, but I'll clean tomorrow.
https://github.com/robbiew/nodelist-to-json
I'll then automate the update when new nodelists are published, so th stays up to date.
Not sure if anyone else finds this useful, but there it is!
Much lower take up than I thought might happen. No more
Fired off an email.
No worries! I actually think, after having done this, that using the nodelist by itself for this purpose isn't the best way to manage a BBS List--whether its used in a webring or in a BBS List script/MPL/Door. Structurally, the FTN spec just it doesn't contain/allow all the data you would need, unless there was a way to add (and keep separately, update, etc.) the data about a BBS's web url, telnet/ssh ports, etc, allow a sysop to update the info, etc.
I dont see why it cant.
I dont think we should be "stuck" with how it was designed in the 90's.
I do think we must make sure we dont break anything if we make changes - so consideration must be there.
I've talked about using the ITN flag to show the telnet port. I still think that that is possible. (So it with the INA field could represent
how a person connects to a BBS.) There are also other existing flags
that could hold other data "U" for example. Or we can create our own. "WEB:....", "EML: ...", "SSH:...", etc which I dont think will break existing system, but I'm willing to try if somebody else is.
The only limit that I'm aware of, is that a flag can only be 32 chars in length, so may be limiting for some web urls or email addresses...
I dont think we should be "stuck" with how it was designed in the 90's.
I do think we must make sure we dont break anything if we make changes - so consideration must be there.
I've talked about using the ITN flag to show the telnet port. I still think that that is possible. (So it with the INA field could represent
how a person connects to a BBS.) There are also other existing flags
that could hold other data "U" for example. Or we can create our own. "WEB:....", "EML: ...", "SSH:...", etc which I dont think will break existing system, but I'm willing to try if somebody else is.
I dont think we should be "stuck" with how it was designed in the 90' I do think we must make sure we dont break anything if we make change so consideration must be there.
I've talked about using the ITN flag to show the telnet port. I still think that that is possible. (So it with the INA field could represen how a person connects to a BBS.) There are also other existing flags that could hold other data "U" for example. Or we can create our own. "WEB:....", "EML: ...", "SSH:...", etc which I dont think will break existing system, but I'm willing to try if somebody else is.
I'd be happy to be a guini pig on this one, maybe with SportsNet? I'd love to get a nodelist working as a user interface however understand it was not designed to be so. I just think that a network with 100+ nodes might be a risky test to several BBS's, on a very active network. So maybe a test network .. I can back up my BBS prior to each test .. so no issues there. Just let me know and I'm in. I think the more ways to market, the better. And if can be translated on the webring or other
BBS's websites, even better. With my limited knowledge, I see this being
a lot of work for Avon with the number of BBS's FSX has ... unless there is a global setting that literally is adding a single flag once, and the server acquires the info on the next fidopoll. But ... again ... this
is beyond my scope of knowledge when we start talking the server side of things.
I'd be happy to be a guini pig on this one, maybe with SportsNet? I'd love to get a nodelist working as a user interface however understand it was not designed to be so. I just think that a network with 100+ nodes
So you could do that now, without an "official nodelist".
I have an idea... create some info about this, what to do etc. and
That could work. :)
I don't remember the details well... but do you know what I'm thinking
of? and if you do, did you shelve that or still working on it?
No worries! I actually think, after having done this, that using the nodelist by itself for this purpose isn't the best way to manage aBBS list
I dont see why it cant.
I'd be happy to be a guini pig on this one, maybe with SportsNet? I'd love to get a nodelist working as a user interface however understand
it was not designed to be so. I just think that a network with 100+
nodes might be a risky test to several BBS's, on a very active
network. So maybe a test network .. I can back up my BBS prior
better. With my limited knowledge, I see this being a lot of work
for Avon with the number of BBS's FSX has
... unless there is a global setting that literally
existing system, but I'm willing to try if somebody else is.
I'm happy to volunteer my assistance on the web side, for what it's worth. I'm certainly not against change, and if someone is willing to create a new (non-ftn) nodelist spec for the modern age network and test it
Maybe I'm looking for problems... :) But the additions if you wanted it to be complete would be...
BBS Name: Might be the same as the system name presently used could be different. Remembering this is a list name.
WWW Url Obvious
SSH/Telnet URL: Could be different if not on the same system.
Port: Problem here is that the port no longer defines the use for telnet/ssh
WWW Url Obvious
Actually I wouldnt have thought it was a requirement. Not all BBS'es
will have a website? But if webring was providing an ftelnet
interface to a BBS, then its definately not required?
Might this sucker work?
If you want a target to test against, you can test against me. Add an ITN:10023 to my node entry, and that should teleport you to 1995 and my Ezycom BBS :)
When you toss mail with FMAIL, apparently it renumbers the message
base every time it tosses. (complete tosser) Apparently this confuses clients, they think there are no new articles. Sooo, anyone one know
of something that won't renumber on toss?
If you're going to use it to drive the webring then yes you're going to need a webby URL. My initial thought was to use the fTelnet setup at the remote end. I'm looking into managing it from the webring end, but it requires getting the proxy sorted out. Apparently possible, but the intructions are a tad... thin...
Although non standard ports would be an issue...
I don't and never have run a news server <-> FTN gate so I really don't know but crashmail is a popular tosser to go along with jamnntpd, I think for this reason.
Thats off the top of my head. But the other thing is, not everyone in
the nodelist is going to want to be on the webring. At least thats a
guess, or have everything in place for it. I s'pose if you pre process
for DB insertion then you could drop or ignore the blanks. Not sure
how you'd remove systems either.
Actually I wouldnt have thought it was a requirement. Not all BBS'es will have a website? But if webring was providing an ftelnet interface to a BBS, then its definately not required?
If you're going to use it to drive the webring then yes you're going to need a webby URL. My initial thought was to use the fTelnet setup at
the remote end. I'm looking into managing it from the webring end, but
it requires getting the proxy sorted out. Apparently possible, but the intructions are a tad... thin...
What's the web url for? ftelnet?
(The onus would be on the sysop to get the port opened up - which
wouldnt be any different from getting to it from the telnetguide
right?)
Why not create a WEBRING entry in the nodelist, and describe a simple
set of rules/commands for processing?
Commands could be addressed to WEBLIST. SUBscribe, UNSUBscribe,
etc.
Maybe it could even faciliate a logo update if an attachment is
included.
This WEBLIST could be for the webring what ELIST is for echomail.
From a user's POV, it's like having an FSXnet 'zine. It's nice
to see the different www welcome pages providing an overview
of their systems, and good descriptions, and help on the different
ways to "connect".
I just set up a locally hosted fTelnet proxy & client embed, sort of reverse engineered it from Rick's myFtelnet set up so you can pass
the URL and Port (and other data) to the embed. LMK if I can help.
This WEBLIST could be for the webring what ELIST is for echomail.
Ahh you lost me there, whats elist? If you were making alterations via netmail then you could pre-authenticate an account to make the mods, and the passing of the netmail would be sufficient authentication in the first place. How many people run around spoofing netmail?
From a user's POV, it's like having an FSXnet 'zine. It's nice
to see the different www welcome pages providing an overview..
Not exactly what I had in mind going in, but a good result none the
less...
Much lower take up than I thought might happen. No more takers with a website to their name?
Pretty much, shrug, I don't like having to rely on third parties :)
I have it bookmarked, and have every intent of adding Storm BBS to it once I fix the webpage aspect of things. But I do occasionally
tend to be slow on such things.
Once that is done, it would work for both use cases. Unless of course
you host the ftelnet proxy, then you are in control of everything
(but all traffic goes through you...)
I just set up a locally hosted fTelnet proxy & client embed, sort of reverse engineered it from Rick's myFtelnet set up so you can pass the URL and Port (and other data) to the embed. LMK if I can help.
Now thats what I wuz looking for. Are you using the fTelnetProxy or something else? Either way a look at the setup would be spiffy.
To create the proxy site, I really just viewed the source from the myFtlenet site to grab the index + embed js & css files. I can zip
all the files up if you want them as reference.
Keep posting a reminder. Maybe folks step away from their systems
But I think this project might be best automated somehow. Let the
Then when you look at those one by one, you can practically grab the little screen shot as a logo.
I have an idea... create some info about this, what to do etc. and
Much lower take up than I thought might happen. No more
Fired off an email.
WWW Url Obvious
Actually I wouldnt have thought it was a requirement. Not all BBS'es
will have a website? But if webring was providing an ftelnet
interface to a BBS, then its definately not required?
Might this sucker work?
What's the web url for? ftelnet?
(The onus would be on the sysop to get the port opened up - which
wouldnt be any different from getting to it from the telnetguide
right?)
Why not create a WEBRING entry in the nodelist, and describe a simple
set of rules/commands for processing?
Commands could be addressed to WEBLIST. SUBscribe, UNSUBscribe,
etc.
Maybe it could even faciliate a logo update if an attachment is
included.
This WEBLIST could be for the webring what ELIST is for echomail.
From a user's POV, it's like having an FSXnet 'zine. It's nice
to see the different www welcome pages providing an overview
of their systems, and good descriptions, and help on the different
ways to "connect".
I just set up a locally hosted fTelnet proxy & client embed, sort of reverse engineered it from Rick's myFtelnet set up so you can pass
the URL and Port (and other data) to the embed. LMK if I can help.
Once that is done, it would work for both use cases. Unless of course
you host the ftelnet proxy, then you are in control of everything
(but all traffic goes through you...)
To create the proxy site, I really just viewed the source from the myFtlenet site to grab the index + embed js & css files. I can zip
all the files up if you want them as reference.
Sysop: | Shaun Ewing |
---|---|
Location: | Blue Mountains, Australia |
Users: | 193 |
Nodes: | 16 (0 / 16) |
Uptime: | 144:18:03 |
Calls: | 142 |
Files: | 187,815 |
Messages: | 324,061 |