|NEW YORK YANKEES||TORONTO BLUE JAYS|
|Jacoby Ellsbury - CF||Ben Revere - LF|
|Brett Gardner - LF||Josh Donaldson - 3B|
|Alex Rodriguez - DH||Jose Bautista - RF|
|Brian McCann - C||Edwin Encarnacion - DH|
|Carlos Beltran - RF||Justin Smoak - 1B|
|Chase Headley - 3B||Russell Martin - C|
|Greg Bird - 1B||Ryan Goins - SS|
|Didi Gregorius - SS||Kevin Pillar - CF|
|Dustin Ackley - 2B||Colby Pennington - 2B|
|Adam Warren - RHP||David Price - LHP|
GO JAYS GO!
No bad language
Almost everyone abides by the letter of this, which is good, but people have been breaking the spirit of this rule far more often as GameThreads have got busier. So, to clarify: This rule isn’t only about not using f*** and s*** and so on, it’s also about not being a boring poo who responds to everyone and everything bad with "hell" and "ass" and stuff like that. This isn’t because we’re puritanical weenies, but rather because 1) it makes for really boring threads; 2) it lowers the general tone of discourse, leading to a(n albeit slow) death spiral in the quality of comments; and 3) see: 1, it makes for really boring threads. Like, really really. Variety is the spice of comments, so take a page from Gerse’s Expressing Displeasure Through Gibberish Dictionary (3rd Edition) and communicate your frustration using nonsense instead. Examples include: "Well that was a big ol pile of pants." "Florkbuckets." "What in the floop was he doing there?!". Each of those communicates "that sucked", "f***" and "what the hell?!" just as clearly as using the phrases themselves while also staving off a general decline in the tone of comments and keeping things fresh for your fellow commenters.
No GIFs/images during the game
No streaming links, unless legal
No attacks about players
DON’T TROLL OTHER SITES
Follow us on Twitter and Facebook.