The silliest exploit I never got around to attempting

[circuitshorter]

That's a much more technically precise answer than the previous one you gave me, which was "not sure."  Although better than the answer Castle once gave me to a different question which was "let me know when you find out."

Hah, what and when did you ask me about it?  My verbosity in responses tends to be inversely proportional to how much work I have to do, so it's possible I was just tunnel visioning something at work and couldn't put two and two together.

[Codewalker]

That's a much more technically precise answer than the previous one you gave me, which was "not sure."

Hawkwaaaaard.

Sorry, couldn't resist.

[circuitshorter]

Hawkwaaaaard.

Sorry, couldn't resist.

Not Sure can be code for "I'm not supposed to tell you that", fyi.

[Arcana]

Not Sure can be code for "I'm not supposed to tell you that", fyi.

Yeah, well sometimes "Synapse asked me to talk to you about this" was code for "Synapse wouldn't say, but I might be able to trick you into spilling."

Just kidding.  I never did that. 

To you.

[Arachnion]

[Codewalker]

Not Sure can be code for "I'm not supposed to tell you that", fyi.

I just wanted an excuse to drop the catch phrase.

That and an easy way to follow the thread in my 'new replies'.

[Mister Bison]

I just wanted an excuse to drop the catch phrase.

That and an easy way to follow the thread in my 'new replies'.

Already too many "Notify" threads ?

[Codewalker]

Already too many "Notify" threads ?

Notify sends an email every time somebody posts, which while I do occasionally want that, I don't for most threads that I want to follow.

[Mister Bison]

Notify sends an email every time somebody posts, which while I do occasionally want that, I don't for most threads that I want to follow.

Now does it only do this until you check out the thread ? Should do it once until you've read it (one for X posts, not one for every)