Thanks B. [smiley]yahoo/rose.gif[/smiley]


It's still my birthday here!

Most-interesting observation. Thanks for bringing it around A.

Quote from: AMK on November 12, 2013, 02:39:03 AM
After millions of spin tests it has been shown that there will always be a minimum of 4 repeaters in a 37 spin cycle

You gotta love when observations are of the "holding" kind!

Hi guys.

Now we are hosted in Canadian soil with plenty of boon. We have high availability, a new backup schedule with snapshots every 3 hours, Solid State Drive cache, a 1Gbps (fast!) connection port. Hardware-wise a great treat for our community, so it's time to focus on the actual software for us to enjoy.

...Why the extended downtime?

The reason is simple. We enjoy a heavily modified codebase (compared to the raw/base forum install) with plenty of man-hours from yours truly spent on it already.

While scrapping all of the custom code and starting again from scratch would have worked to get us back faster, it would also mean having to re-do loads of work again, which means DAYS of work to get us on par to where we were, versus taking over from where we left in exchange of only one day downtime for getting our setup right.

It was the right choice, had to take the fair trade-off!

So: Now we're officially open again. On bigger premises, with the ability to deliver better services, we are here to provide a great taste on this year's end.


Enjoy your Bet Selection home again!
Vic

Quote from: Buffster on November 03, 2013, 11:18:46 PMWhat is the risk one should take to make a buck ?

Buff-mate, you are leaving the biggest one out: how many times you want to achieve the feat.


If you want to expose yourself the least to the house edge, looking for a one-hit-wonder on the even chances should do.


A la Ashley Revell:


Red or Black? - Betting your whole life on one roulette spin

Quote from: Turner on November 03, 2013, 11:33:36 PMWhere do you decide its not working playing 5 lines?  After 1 loss?

Yes T,


Betting and getting one straight loss on 5 lines sets you back for the whole of the current cycle.


Cheers!

Congrats! C# is (IMHO, syntax-wise) > Java 

Quote from: AlienZ on November 01, 2013, 03:43:13 PMThanks Vic, means a lot. Sure am looking forward to your BetSoftware Suite!

[smiley]cps/up.gif[/smiley]

Which programming language(s) do you use A-Z?

A-Z thanks for joining us.

[smiley]popo/r-matrix.png[/smiley]

Sharing coders always welcome!

Countermeasure: Detecting betting assistant programs for winning players.

As you know, any automated betting program which assists players to lose is more than welcome by the casino; they couldn't care less about them. But chances are the other way around isn't the same.

Solution: Virtual machines.

Assuming they target a list of .exe names or window titles for flagging programs, with a virtual machine used exclusively for gaming the API calls implemented by them return only what's inside the virtual machine, not what's executed on the main machine.

http://en.wikipedia.org/wiki/Virtual_machine

Some popular virtual machines:

http://www.virtualbox.org

http://www.vmware.com

Countermeasure: Analyzing bets placed by a punter at the online casino to detect his ordered betting system.

...This is the most obvious way for a casino to apply a countermeasure against a winning system.

They look at a punter's statistics looking for betting patterns which indicate he's using a certain system the casino may be wary of, resulting in expulsion.

Solution: Statistics fragmentation.

Casino's favorite type of bettor is the senseless bettor. Making random wagers for no rhyme or reason. Looking like a senseless bettor is a player's best bet to hold the casino account active without being flagged.

How?

If we have -say- three players in a team randomly picking who's turn to bet is it, statistics for a single player do not reflect the whole system at all, only unrelated fragments of the actual winning stream of bets.

When analyzing the betting statistics from any given player of the group, they aren't seen like a stream of ordered bets, but look like random bets made at random points.

The more players the merrier for this technique. i.e. A team with statistics fragmented in 10 players can run smoothly without risking having the statistical analysis for a single flagged player disclose anything about the whole team operation.

Thanks to video feed sharing and a sound understanding of "casino wallets", the team can hit different wallets/owners to lessen the odds of rising a flag.

Wallets repository: http://www.onlinecasinodollar.com/casino-owner.html

Thread dedicated to overcoming casino countermeasures with team play and technological means.

(P.S. including hypothetical ones, you never really know what's going on behind online casino's curtain! [smiley]aim/angel65.gif[/smiley])

Quote from: Pockets on October 22, 2013, 11:19:17 AM
So ladies(if there are any around here)

There are! 

---

...I love flat betting too; been developing and tweaking flat betting systems only for quite some time now.

Congrats for walking the hardest but most rewarding journey: beating the house edge with pure bet selection

 
Inter-session reinvestment = Nice 

Quote from: weddings on September 14, 2013, 01:58:01 AM
How do I set the number collector to auto click?

Hello, you can configure the placeholder bet where it says:

1@R_1@B

The nomenclature is simple:

<clicks>@<location>

Each separated by underscore.

2@R =  Two clicks on Red.

1@D1 = One click on Dozen 1.

Etc.

Exactly as they are seen in the generated definitions file.

My vote goes to both! 

Quote from: Turner on September 10, 2013, 10:36:43 PMwhat about windows 3.1....

16-bit is fully deprecated by most account (mine too). There are barely no 16-bit powered user computers active in 2013 

32-bit is still worth (I assume it'll be around for a long-enough time to make a smooth transition)

64-bit is kicking strong. Basically it's already a chunk of the present, and definitely the future.

---

Heck, some people is already deprecating WinXP since it's going to be dropped by Microsoft next year.

It doesn't make sense according to me, still there is a large XP user-base which deserves attention. Furthermore, while it's true you might have to skip the "new goodie" in town when targeting compatibility, developing practices aren't too extraneous for XP to avoid supporting them already.