First of all, I want to thank everyone who runs this forum for the fine job they've done. While I myself have not yet had any need for help, I have enjoyed and learned while helping others.
Due diligence disclaimer: I searched for a discussion on this issue, using "tynt" and "copy paste", but found none. Hopefully, I did not miss it. Also, I searched my control panel to see if there was already a remedy there, but I found none.
Okay, now down to business
When trying to help someone, I can't even paste their one-liner into a terminal window without it causing problems.
For example, a few minutes ago, while trying to assist over at SED help - cleaning up code, extra spaces won't go away, copying a modest one-line pipeline resulted in the following paste to my terminal:
VAR=`awk -F, '{print $2}' input.txt | sed 's/-i/\|/g;s/^.\{1\}//g;s/ //g'`
View Original: hxxp://www.unix.com/shell-programming-scripting/135131-sed-help-cleaning-up-code-extra-spaces-wont-go-away.html#ixzz0m26OTbwo
Having to delete that in a text editor when copy-pasting someone's sample data is just a mild annoyance, but to have that in the terminal is just terrible. It produces junk on the screen, junk in command history, and in a case-insensitive environment with vim installed (osx, for example), "View Original: ....." brings up vi in read-only mode.
For the love of all that you hold dear, is there any possibility that the tynt tracer script can be nuked from orbit? If not, can the char limit before it kicks in be bumped up a bit, so that it allows copying a few lines of code/data before it kicks in? If not, perhaps users who have enough bits or helpful posts could have access to a knob in their control panel to disable it? If not, perhaps it can only be included on pages for threads that have not had any activity in a day or two? (I'm just tossing out ideas in case any of them are palatable.)
If there is no chance of this going away, I would appreciate an explanation. Not because it is owed to me -- I do not feel any entitlement in that regard -- but because I am simply curious to know why something with such an obvious downside is embraced (does it help that much with traffic and/or attribution?).
Any consideration you give this post is greatly appreciated. Worst case, I'll just go back to using the javascript-less environment I was using. The downside of that is that notifications tend to go unnoticed for days. Not such a big deal, I suppose.
Again, despite my first thread being a whinge, I sincerely appreciate the work the staff has put into the site. It's a nice place. Keep it up.
Best wishes,
Alister