We want to share an important update with our Betfair Community users.
Over the coming months, the Betfair Community platform will be winding down. The final active day for the platform will be December 21st. From December 22nd, users will no longer be able to access the platform.
Your discussions, insights, engagement, and, most importantly, feedback have helped shape the platform and guided innovation. Your feedback continues to be important to us, and we will continue to listen via our dedicated feedback channels, as well as through product testing and innovations.
To share your feedback and experience, visit: https://support.betfair.com/app/home
|
By:
Just more money being added to betfairs coffers with nothing coming back to customers. It wont affect me, directly at least, but i have to laugh at how betfair are closing down people who've found a niche and are going to milk it for all it's worth yet still advertise as a p2p exchange. I understand you don't tolerate certain customers activity Feck so why do you agree with the company continually skimming?
|
|
By:
The "skimming" is minimal, is more likely to affect those "certain customers" than myself and makes it more likely to get matched.
|
|
By:
My profits on over/unders have increased as a result of cross matching which has been in place for ages on football.
I wouldn't go quite so far as to say it is a 'good thing' though. It's an 'ok thing', but would be better if the customers were matched without skimming. |
|
By:
Cross-matching will be turned on for all pre-play win markets on British and Irish horseracing generally around 10-30 minutes before each race.
Fine for website users but how is API software supposed to know when it is actually switched on ? If API software guesses wrong then it will show incorrect prices to its user. |
|
By:
API software will only supply the actual prices - IIRC crossmatching is only available via website.
|
|
By:
When cross-matching is active the website displays virtual prices that cross-matching will facilitate. Bets are cross-matched when possible whether they originate from web or API.
Some API software calculates the virtual prices too so that it can display prices that are in line with the website prices. However, if the software were to calculate the virtual prices when cross-matching wasn't activated then it could display prices that wouldn't necessarily be matched if taken. Hence why some API software needs to definitively know whether cross-matching is active or not. I suppose smart API software could realise cross-matching wasn't active as soon as a users bet fails to match at a still available calculated virtual price, whereupon it could cancel that bet and proceed to attempt the cross-matching itself. But then again, in horse markets you wouldn't want to cross-match yourself due to the liability that can result from non-runners and so on. All round easier if a flag was added to GetMarketPricesCompressed etc to say whether cross-matching is active and thus whether virtual bets can be displayed. |
|
By:
why dont the just have it switched on al the time, seems arbitary way to go about things
|
|
By:
obviously, they are scared of possible scratches...
|
|
By:
They still haven't said how they deal with non-runners?
|
|
By:
Mr Magoo, I think I'm right in saying they sometimes change the RF's without ever advertising the change so I suppose if they got caught out they could manipulate it to cover themselves. The skimmer may even be coded to keep betfair's overall lays and backs in sync so that betfair would be minimally affected by RF's. I haven't tried to work out how so I may be havering but I'm thinking if a horse bolts and the bolter boys suddenly start laying all and sundry to take advantage of the impending R4 the skimmer might detect an imbalance and stop placing any backs on betfair's behalf.
|