An air strike was conducted against the pipeline that was the most significant contributor of the spill, however there were some other sources as well. It ended up being several times larger than the Valdez spill, a lot of it ended up on the beaches of Saudi Arabia, and it was never cleaned up, so it's still causing a lot of ecological damage.
I don't think I'd heard about this until now.
Also, it wasn't an air strike against the pipeline, it was the Iraqis dumping oil to prevent US marine landings (from what I heard, they were planning on setting it on fire if there were any ships there? Game-of-Thrones-style).
The air strike was to prevent further spillage:
> On January 26, three US F-117 fighter-bombers destroyed pipelines to prevent further spillage into the Persian Gulf.
Yeah, that's what I meant -- I just didn't word it right.
ca 1991, I hadn't gotten interested in world news yet. I would've been 12ish years old.
edit: I really don't get why people are downvoting this, the message appears to have at least 1298 characters.
Most clients that do attempt to split long texts into multiple messages get one of these wrong:
- They miscalculate the number of bytes available for payload, because they don't check with the server's idea of their hostmask (which can change during the session e.g. due to authentication) to calculate the length of the preamble as seen on the receiving end.
- They count characters and ignore the number of bytes they actually encode to (either in the message or the preamble, or both: there are some networks like the Korean Ozinger that allow Utf-8 nicknames).
KDE's Konversation does both correctly (it also has some other nice visualizations of server/protocol-imposed limits, e.g. when you try to change the channel topic it'll color text past the server limit in red, again taking into account character and formatting code encoding).
Most clients don't even try at all though.