@poker4adummy @thinkingpoker I have too. But lots of those hands rr pre, r flop, b turn, k river, or b/c river.
-
-
Replying to @NateMeyvis
@NateMeyvis@thinkingpoker true, although I don't know if he 3 bets that UTG+1. Just hard to say because people are so bad at plo81 reply 0 retweets 0 likes -
Replying to @RazzballViz
@poker4adummy
@thinkingpoker Sure; prob only if x=A (or K?). Point is we have to throw some out; meanwhile there are tons of bluffs.1 reply 0 retweets 0 likes -
Replying to @NateMeyvis
@NateMeyvis@thinkingpoker yeah you're probably right looking back. The bluffs have to outweighs the merges / value bets1 reply 0 retweets 0 likes -
Replying to @RazzballViz
@poker4adummy
@thinkingpoker Glad you think so. I'm not at all certain, but still convinced, that calling is better.1 reply 0 retweets 0 likes -
Replying to @NateMeyvis
@NateMeyvis@thinkingpoker yeah, the only reason it's a debate is the opponent's skill level, competent opponent it's a check call1 reply 0 retweets 0 likes -
Replying to @RazzballViz
@poker4adummy
@thinkingpoker Yeah; sounds right. (I guess occasionally you'll have enough bluffcatchers better than this to fold?)1 reply 0 retweets 0 likes -
Replying to @NateMeyvis
@NateMeyvis@thinkingpoker hmm, interesting question, I think so. Andrew's range has a ton of bluff catchers in it raising UTG1 reply 0 retweets 0 likes -
Replying to @RazzballViz
@poker4adummy
@thinkingpoker Yes, esp. conditional on the fact that he didn't bluff turn/riv.1 reply 0 retweets 0 likes -
Replying to @NateMeyvis
@NateMeyvis@thinkingpoker for sure. I'd be really interested to know Andrew's take on him later and if it effected his decision to c/r1 reply 0 retweets 0 likes
@poker4adummy @thinkingpoker Yep. Possible podcast hand!
-
-
Replying to @NateMeyvis
@NateMeyvis@thinkingpoker I hope so. Anything to get some quality plo8 discussion, I love it and its the only place I can get it0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.