I disagree with billytea. If I suck the threads, it's because I don't want to (or already have) read them through normal means.

Ooh! I get to be a *famous* Buffista!

t preen

And duh, Nilly is a verb. And noun. And so on. Isn't she already in the FAQ? (If not, I'm SHOCKED! Shocked, I tell you. Dismayed at our lack of thought.)

I disagree with billytea. If I suck the threads, it's because I don't want to (or already have) read them through normal means.

Is that the only way you can see the threadsuck being used?

Differing considerations are better spoken for by people who subscribe to them.

I can only cast a vote for my usage, just as you cast yours for yours.

it's because I don't want to (or already have) read them through normal means.

I get the "I don't want to" argument, but If you've already read them, then you shouldn't care one way or another.

Differing considerations are better spoken for by people who subscribe to them. I can only cast a vote for my usage, just as you cast yours for yours.

If we expected the membership to remain static I'd agree with you. But I feel we should put some thought into how others who may not yet be reading this thread will use the function.

For me, the decider is that of the people who would like to mark a thread as read, there exists another, relatively fast and simple mechanism by which they can do so; but for those who would like it to leave the current 'read' status unaffected, there isn't such a simple fix available - especially after the fact.

I get the "I don't want to" argument, but If you've already read them, then you shouldn't care one way or another.

When I've already read them, I don't care what the system sets. When I haven't, then I want them mark read. Ergo, if I were casting a vote (as I did) I'd vote for them to be marked read since there is no situation in which I want them left marked unread.

But I feel we should put some thought into how others who may not yet be reading this thread will use the function.

But if an existing majority uses it one way (which is why I'm speaking only for myself), then why make them do two steps x% of the time instead of one? And that's not counting increased bandwidth and server load. I'd rather tailor the usage to the current users, and change later, instead of choosing a side that makes things inefficient for the majority.

I think this boils down to the following considerations (in order): a) current usage b) bandwidth c) server load d) future considerations. Since there is no obvious overriding IA issue that I can determine.

But if an existing majority uses it one way (which is why I'm speaking only for myself), then why make them do two steps x% of the time instead of one?

Because there exists an alternative for them, but not for the minority.

Honestly, I'd rather write extra code for people who can't use the workarounds that one would use today (which is something else I do all the time). I don't know exactly how much money we have in the bank, but I'd rather the opportunity to lighten the load on the server and the bandwidth we're paying for, if a small enough percentage of people are the audience of which you speak.

Since I can't think of a reason to threadsuck that doesn't involve reading, I say that the sucked thread should be marked read.