Why access a Flash-based website at all? Either way use FlashBlock for Chrome.
Announcement
Collapse
No announcement yet.
BF Down - 3.28pm Sunday 20th Feb
Collapse
X
-
I lost 21 euro this time. Last two times betunfair crashed my back bets weren´t matched, so I can call myself lucky in a way.
But really, if you lost money or not shouldn´t determine the level of outrage. If these "maintenances" (or whatever they call them) continue, not a single trader will remain unaffected.
It´s like backing 0-0 and going in play. One day an early goal will bite you.
Comment
-
bf is looks like pretty big and serious bussines[lol], so they dont even listen to ''nigels complain'', to make some more serious impact, some bigger kickass needed here, like ''traders trade union'' and not to send them ''complaint'', at those they just have a good laugh and throw them to recycle bin, but make something like labor strike, couple days not trading or something, maybe then they will move theyr asses to do something about that....:Naughty
we need new Che Guevara :Thumbsсправка по The Geeks Toy на русском »» здеся ««
Comment
-
I know there are all manner of weasel clauses in betfairs terms and conditions which protect their back, particularly when they claim to be about 'betting' and people who use it like we do are unusual 'traders'.
It will be interesting to see what happens in light of Betfair 'publicising' trading etc.. through their new in-play interface, they can hardly claim to be ignorant of the trading that goes on.
Comment
-
Originally posted by skit View PostNot really. You just click on whatever flash elements you want to unblock.
Comment
-
You have to "clear" your browser from time to time.
After a period of time your browser hits 100% CPU
and everything lags.
(it can be seen in Task Manager).
I had three browsers for doing the job.
- Firefox for betfair main site and live feeds (Bet365 & bwin).
You can make it autoclean when close.
After a period of a 45 min I "cold" close it via Task Manager
and then reopen it the usual way.
- Lunascape for livescore.
When I notice that it hits 30%-40% CPU, "cold" close it via Task Manager.
I am using flashscores for the livescores and it doesn't remember my coupon.
So before closing it I copy (manually) my coupon to Opera.
Then, when it hits 30%-50% CPU the other and vice versa.
Recently, I started using another method, for livescores.
I have my coupon in the backup pc with TT running.
I just keep in the main pc a few livescores at each time that are in-play.
And little by little I add them, and lately I don't need to "cold" restart "livescores browser".
The big trouble for you is Saturday-Sunday I guess.
Today for example you will not notice much problem.
It depends on the amount of matches that you are monitoring.
Keep an eye in the Task Manager - CPU part and you will get my point.
Comment
Comment