![]() |
Feel free to pile on...
http://www.paulickreport.com/blog/fr...-post-betting/
I guess this is a much bigger problem than I realized. There really is no excuse for the software to crash like this. |
Quote:
|
Quote:
|
it was BIGS!!!
|
I can't even imagine why anyone would even think to attempt to bet on a race after it is over... unless that person has prior knowledge of it happening previously.
These bets should have been time-stamped, and it should have been clear that they were placed after the race had ended, and not been cashed. "Lucky, if somewhat dishonest"? Talk about an understatement. So I guess everytime we see a tote delay at a racetrack, we should all try to place bets on the race after it has ended? This happened June 28, and we are just reading about it now, and from the Paulick report, not the DRF. I think if Paulick hadn't gotten word of this, it would have never been made public. |
Quote:
|
Can I still bet that race ?
|
Quote:
You are correct on the reporting of the incident. Very disturbing that it came out in a blog over a week after it happened and not reported by one of the big three horseracing news outlets. It just fuels the paranoia that past posting happens more often than we all know. |
The whole thing is a disgrace. It is clear now this happens way more often than it is ever reported.
|
How many times does this happen versus a fixed race. I have no idea but would think that latter happens more.
Opinions? |
Quote:
|
Quote:
I guess it depends on your definition of a fixed race. My guess is you are completely wrong. |
Quote:
|
Quote:
|
Quote:
|
Quote:
http://www.desmoinesregister.com/app...RTS14/80527058 If the stewards don't believe him, isn't two weeks a bit light? |
Quote:
|
All times are GMT -5. The time now is 12:24 AM. |
Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.