This means that as the user goes thru different FTNs, the Network: line
is incorrect for 90% of the time - and I wonder... how did I f00k this up??? And how can I correct it???
However the NETWORK tag is anchored to the message network that the user is CURRENTLY IN. Meaning, as a user newscans messages on 2oFB across
many FTNs, whichever Conference the user was in when the newscan was started is displayed during the entire newscan...
it's very likely if you're not specifically inside the reader they aren't (temporarily) updated. so if you're doing some sort of looping, anything outside the reader would see those MCI codes reverted to what they were before you started. (for example a menu with a huge list of separate
scans of each base would show !MN as the user's current one between
every MN action, because only INSIDE the MN action would !MN be temporarily adjusted)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,052 |
Nodes: | 17 (0 / 17) |
Uptime: | 06:44:49 |
Calls: | 501,013 |
Files: | 109,383 |
D/L today: |
43 files (1,564K bytes) |
Messages: | 304,694 |