Ol> Like it's always the same. It's never Mystic's problem, the others are
Ol> doing it wrong. (Why should the guru read the fucking manual? Why should he
Ol> ask for advice? He always knows better ...)
As usual you immediately showcase your childish behavior and complete disregard
for being a decent human, for no reason at all.
It doesn't matter how large of an emotional meltdown you have, its not going to
change how software actually works. In Paul's case the failure was because of
the format of the escaped file name and that can be a problem with some mailers
when filenames are escaped the way BINKD does.
Yes, FTS did change it but they changed it *15 YEARS* after the other method
was already in the wild and implemented. That change doesn't magically make
legacy software work differently.
I don't know what "advice" you think I should ask for. The only way for Paul's
problem to be fixed would be if BINKD would escape as originally intended or
for those people to update to different software. Older software cannot be
updated. There is nothing *I* can do that would fix the problem he saw.
In Mystic's case it handles either format correctly and it escapes as
originally intended by the creators of BINKP. It does that because its the
only way that works with 100% of implementations we all tested against. You
can disagree if you want to, but that has nothing to do with what Paul posted
here.
I could care less if BINKD changes it and its easily arguable that they
shouldn't change it. But that doesn't change the way legacy software works no
matter how big of an emotional meltdown you have over it.
... Confucius say: "Its stuffy inside fortune cookie"
--- Mystic BBS v1.12 A48 2022/01/12 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
