By blocking *tynt*, I not only prevent the relevant scripts hosted on Tynt’s servers from loading, I prevent JavaScript objects that contains the word “tynt” anywhere in its text from loading. Since even local implementations of Tynt require calls to objects that contain the letters “tynt” in their names, my method has (so far for me, at least) blocked Tynt’s scripts everywhere I used to encounter them.

In re: being “faster,” AdBlock scrubs documents after the Mozilla engine has rendered them. I see no evidence that suggests blocking “.tynt.com” vs. “tynt” would be any more efficient in a practical, or significantly measurable, sense.

Note that my method will not work if someone were to rewrite the Tynt scripts to replace “tynt” as a sequence. So far, I have not encountered that.

It’ll be faster, too.