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...
Can we move this thread over to FSX_NET to discuss further and let's see if we can:
- confirm a list of things we're trying to address / enhance etc.
- develop some new standardised flags for the fsxNet nodelist
- test this all out
I have been trying to keep up with the threads here and in Mystic echo
but would welcome the chance to consolidate thinking and some next steps over in the Network Ops echo.
I just turned on FXS_NET so Im just waiting for a message to show up and ill be there.
Suggest you try for a rescan of the echo using a netmail to Areafix with your password in the subject line and in the body use
%RESCAN D=999
Tried that and got nothing but Ill try again
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 209:10:02 |
Calls: | 14,142 |
Files: | 295 |
Messages: | 551,093 |