*Informative* subj: Sendo sues MSFT for everything
I'm going to make the request, again, that people think about what\r\nthey're putting into both their subject lines and message bodies. I\r\njust read the Register article myself (really nice job, Andrew), and\r\nit's...staggering.
\r\n\r\n
However, reading Jay's subject line, I had no idea what his\r\npost was about.
\r\n\r\n
Again, people. Suggestive hints and "this is\r\ninteresting/unusual/enraging/etc" titles have their place... But it's\r\nnot here any more. I'm probably overly sensitive to this having a\r\nslow-ass machine, slow-ass connection, and suboptimal browsers at the\r\nmoment. But even if I didn't, the microcontent here is lacking. It's\r\ngetting to the point that the regulars can't figure out WTF is in a post\r\nuntil they've read the subject, read the post, and followed the links,\r\nI'd hate to think what the occasional, lurking, and drop-in readers\r\nthink.
\r\n\r\n
This is the same crap content and presentation we gave IWE hell for.\r\nWe should give ourselves the same hell.
\r\n\r\n
It's bad enough that subj. lines here are brief enough that even a\r\ndescriptive title is limited. Let's not handicap things further by not\r\neven trying.
\r\n