🚀 go-pugleaf

In article <BzBuoy.6MB@ra.nrl.navy.mil> atkinson@itd.nrl.navy.mil (Randall Atkinson) writes:
>  In many cases the vendor doesn't exist and source code isn't
>available and so it _cannot_ be fixed.  Also recall that USENET is
>transported over weird links, not just UUCP and NNTP.

Not really much -- can you recall such a link NOW?
It's plain stupid to make serious decisions affecting millions
of machines and use the buggy software as a rationale!

The following universal remedy will help:

	main(ac, av)
		char **av;
	{
		register c;
		FILE *of;
		char buf[10240]

		sprintf(buf, "rmail.buggy %s", av[1]);
		of = popen(buf, "w");
		while( (c = getchar()) != EOF )
			putc(c & 0177);
		pclose(of);
	}

(translate to YFPL).

>>"Just send 8 bits" *is* backward compatible. Check your logic.
>
>Nope.  With email will crash other folks' machines, which is at least
>highly anti-social and possibly down right malicious.  With news that
>same thing might happen.

Wake up. There ALREADY are 8-bit newsgroups distrtibuted in US.
Subscribe to relcom.* and see (available at most major gateways).

Anybody heard about epidemic host crashing recently?

Didn't you realize that we're talking about changing the standard
POST FACTUM?

>Many of the hosts in question _haven't_ upgraded their software in
>years because they cannot upgrade their software -- which is why there
>is _still_ a hosts.txt at nic.ddn.mil.

And what? Should we all follow that line? Where's my handy card
puncher?! What kind of hosts you're talking about? I understand
why people are reluctant to touch machines which launch missiles;
but, excuse me, it is not the kind of the stuff we're talking about.


--vadim