Hello Nelgin,
On Fri Oct 20 2017 10:19:18, Nelgin wrote to Accession:
So I gather with this mod the two are not (and/or don't need to be)
one in the same anymore as per Deuce's original plan?
That's correct - if it works. I've not fully tested it but it seems to
be ok from what I've seen so far.
The problem was with fsxnet where they sent echomail packets without a password but the tic files do have a password. The simple solution was
to have tickit.js look for a separate password in the sbbsecho.ini
file and use that instead.
I know exactly what the problem was. When Deuce was creating it and went that route, I was the first to complain. *MOST* networks (and I don't know why) do not use packet passwords, but do use TIC passwords. So since I have 100+ links here setup that way over the years, it was a pain in the butt dealing with the failed connections from tickit.js setup that way on other systems connecting here.
Of course, this may break existing implementations where both pakcet
and tic have the same password because now it'll be looking elsewhere
for a password. Just simply add the tic pw in echocfg.
It shouldn't break a thing. If both passwords are the same, it will see that both are the same. BUT now when they are actually different (or one being non-existant) it will work like every other software out there that already does this.
I tried arguing my point, but it was shot down a couple times by the original author. I just dealt with the problems when they arose from others connecting here and set them up with a packet password (I don't use tickit.js on my hub system, only my Synchronet leaf node these days).
Feedback appreciated as to whether it works for you or not.
A little late at this point. I probably won't use it. When I lost the argument,
I chose to use something else. :(
Regards,
Nick
... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
Synchronet thePharcyde_
telnet://bbs.pharcyde.org (Wisconsin)