> On Tue, 11 Mar 2003, Warlord wrote: > > @> > Based on my (admittedly limited) sample of messages on this list, the > @> > traffic can be broken down into the following categories: > @> > > @> > A) Discussions about non-Dragaera things. (spoiler space, > @> > politics, history) > @> > B) Discussions about general topics. (Morganti, the method > in which Paarfi > @> > is accustomed to expressing his thoughts, how to make Klava) > @> > C) Discussions of specific books. > @> > D) Bad jokes. > @> > @> Hey, I put at least 10 minutes effort into that poem. > @> I direct a haughty Warlord Sneer in your general direction. > > Yeah, I'm just jealous because I don't have the nerve to send the bad > jokes I write to the list. He who hesitates is lunch. Shyness on this list is *not* a survival trait. Go ahead and send them in. If they're worse than mine, I'll just have to try harder. :) > > @> > Only category C really needs to be marked, and that actually > appears to be > @> > the smallest category (as you'd expect it to be, unless a new > @> > book has just come out). > @> > @> The book title and "spoiler" in the subject line is sufficient. > @> If more is required, then so is discipline. > > Many people, such as, say, me, have mail clients that helpfully go to the > next unread message when you signal them that you're done with the one > you're on. This is why spoiler space was invented in the first place; it Progress is not what stands still. > gives people the opportunity to see a blank page when the new message > loads up, with a warning in it saying that they shouldn't scroll > down. This feature is a lot more important in text-based clients (such as > Pine, which I'm using), because these generally don't include multiple > panes that you can use to read subject lines at the same time as you're > reading an individual message, so actually reading the subject line to see > if the next message involved spoilers would involve lots of moving in and > out of various text menus. Directory list of inbox. Delete spoilers. Utilize "read next" function. > > The best way to handle this would actually be to have a spoiler mail > header that would be read by clients, which would present some kind of > warning when hitting a spoilery message (which would include the contents > of the header). The list itself is a discussion of the books. Being prepared is a part of disipline. If you see a discussion taking place (and this is a risk that you accept when you join the list) that is a spoiler for you, then delete it without reading further. Roll with the punches people. > Somebody should get in touch with the IETF about this. Are you kidding ? "The Last Contract" will be a collectors item by the time it reaches a board meeting. W Does 'anal retentive' have a hyphen? How about a colon?