One particular problem, that does cover quite a few threads on their message board, is getting 'confirmation' when the posting server is changing or modifying the message-ID,
It's been just about forever since I actually last ran a usenet server (circa 1996), but lots of operators even back then (way before digital video started swamping things), that the ID message string was too small. Now were well beyond that point, where some operators have long ago modified their programs (the usenet operating rules having been changed) to handle many more (10^whatever) ID's.
Some didn't move fast enough, and are still trying to 'catch up'. Astraweb is probably the most major of those, and JBinUp ran right into problems with them.
But you're right, 'one would think' as old (and a bit creaky) as all this is.... but one does have to remember that it wasn't designed to do binary transfers in the first place; judicious use of pars and posting folks 'watching' their uploads (from downstream of where they're posting at) in simply good practice.
It's been just about forever since I actually last ran a usenet server (circa 1996), but lots of operators even back then (way before digital video started swamping things), that the ID message string was too small. Now were well beyond that point, where some operators have long ago modified their programs (the usenet operating rules having been changed) to handle many more (10^whatever) ID's.
Some didn't move fast enough, and are still trying to 'catch up'. Astraweb is probably the most major of those, and JBinUp ran right into problems with them.
But you're right, 'one would think' as old (and a bit creaky) as all this is.... but one does have to remember that it wasn't designed to do binary transfers in the first place; judicious use of pars and posting folks 'watching' their uploads (from downstream of where they're posting at) in simply good practice.