Board: [WWIVnet] WWIV Networking Subject: Re: Talisman / WWIVnet From: apam (11:1/218)@8304.WWIVnet-FTN Date: Thu Apr 08, 2021 12:33 To.......... Rushfan #1@513.Wwivnet > That means the like was soft wrapped. WWIV will end with "\r\n" for > all lines, wrapped or not, then add a \x1 to those wrapped. I think that's different to what I'm talking about, the \x1 is a smiley face (and I'm seeing that too) but \x1A right at the end of the messages are a right arrow. > It's for looks at this point. #1 is user number and @100 is system. I > don't think modern wwiv will parse that out for figuring out who or > where to reply to when from{user,sys} exists and is populated. Ok, perhaps I should add it to be consistent? Actually, that was something else I was wondering about. Do all host->subcriber messages have the host as their fromsys, or does it retain the fromsys of the system that actually posted the message? Also, I was wondering about mark's networkb being incompatible with binkd. I know you said marks version was special, but was wondering once I've got this to a point we're happy with it, perhaps there could be a hub for talisman bbses that runs wwiv, kind of like what I'm doing with rushnet. Then Mark wouldn't need to worry about anything, as wwiv networkb would connect to him, and binkd would connect to the latest networkb which works.. (did I explain that properly lol) Oh, one other thing I'm unsure about. In the case of multiple WWIVnet setups, currently all of them use 20000:20000/? as the fake ftn node, which seems to mean if a system is part of multiple WWIVnet style networks they have to have different node numbers to differentiate? For example, if I was @101 on rushnet and @101 on wwivnet, binkd would receive s101.net to the incoming, and my software would somehow need to determine which network the packet is for - although I suppose it doesn't really matter, as subtypes would be different, and in WWIV email is one base, and on sending the user choses which network to go out on. I guess that will have to be a talisman limitation (email goes into seperate email areas in each net conference) Andrew -- Andrew Pamment (apam) HappyLand v2.0! --- Talisman v0.16-dev (Linux/x86_64) * Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (11:1/218) .