Subj : Re: FidoNews submission
To   : Bj�rn Felten
From : Dan Clough
Date : Thu May 29 2025 08:49 am

-=> Bj�rn Felten wrote to Dan Clough <=-

BF>>    If IPv4 is busy, use IPv6. It's never busy. Welcome to the 21st
BF>> century.

DC> Busy?  It's a binkp connection attempt, not a phone call.  Duh.

BF>    LOL! Your expert opinion is duly noted.

It's not an opinion, it's simple fact.  Multiple binkp connections can
happen at the same time, unlike a modem/phone connection.  Your nodelist
entry specifies "CM", "IBN", and "INA".  Let me know if you need some
clarification on what those terms mean.

DC> I don't have IPv6, as my ISP doesn't offer it.

BF>    I've enjoyed IPv6 for almost two decades now, despite not having
BF> native IPv6 support. That's a really bad excuse. Try he.net like so
BF> many of us before we got native IPv6. It's even FREE of CHARGE!

It wasn't an "excuse", just a statement of fact.  I could not care less
about having/using IPv6.  Version 4 works just fine.

DC> Fix your shit.

BF>    Yes, Massa Gimme-Gimme. I will, of course, immediately see if I can
BF> give your Very Important Traffic on a depreciated network protocol,
BF> such as IPv4, higher priority.

It's not "deprecated" (the proper spelling of what you mean).  It's a
world-wide standard, in widespread use.  Also, I wasn't asking for
higher priority, just that your system match what it advertises as it's
capabilities.  CM/IBN/INA.  There aren't any "busy signals".

BF>    It might mean that my paying customers will have to accept reduced
BF> speed, but I'm sure they understand that a VIP, entitled non-paying
BF> client, must be given the highest priority.

Why would it affect them at all?  Are you using some kind of deprecated
hardware, or something?

I just tried replying to your netmail to me, and .... yep, can't get a
connection to 2:203/2.  It'll keep trying, and maybe eventually get
through.  Strange how your system(s) are so unreliable.



... All the easy problems have been solved.
=== MultiMail/Linux v0.52
--- SBBSecho 3.25-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)