2027 Laws - An Open Invitation

[sanst]

When BIGDEAL was announced I took the liberty to verify also this program.

 

All my tests were successful.

However I discovered some disturbing risk for a C+ library failure which (at least in theory) could compromize the program with internal addressing exception or even undetcted failure.

This risk was associated with the need to handle integer numbers within the full range [0 - 53644737765488792839237440000] (the number of possible different deals).

 

So I 'translated' BIGDEAL to Delphi where I have my own library routines able to handle integers of essentially unlimited size without any risk of overflow or other failure.

 

My tests confirmed that the outcome from both versions (started with identical parameters) were identical, but I was not able to eliminate the risk for malfunction in the C+ library.

Did you contact Hans van Staveren, who developed the program, over this? He can be reached at sater@xs4all.nl.

[pran]

Did you contact Hans van Stavere, who developed the program, over this? He can be reached at sater@xs4all.nl.

Frankly: I just do not remember.

[hrothgar]

I absolutely agree with you, Hrothgar; but what if they say "we don't see a reason to" anyway? What is the WBF going to do? What is the ACBL going to do? What is the WBF going to do to the ACBL if the ACBL continues to violate the Laws in their online games?

 

So, none of what I am going to describe here has anything to do with Laws, but it does involve the sorts of activities that the group responsible for writing the Laws should also be doing...

 

Neither the the ACBL, the WBF, or bridge players benefit from living in a world where individual platform providers are able to operate as monopolies / enjoy a dominant position in the field.

 

The single most important thing that the ACBL and the WBF can do to stop this from happening is to attempt to promote common standards for electronic playing environments. I know how / where I would go and slice things up.

 

1. Define a set of services that a bride platform must provide. These might include dealing / playing hands, scheduling tournaments, exchanging convention cards, E-commerce, displaying events, matching partners, ...

2. Define a standard API that clients (the applications that players use to play hands) use to communicate with the server

3. Definite a second set of API's for Vugraphs (both for streaming the content and subscribing to streams

4. Define a set of standards around storage (how are hands represented, how are access privileges controlled)

5. Last, define a set of standards around processing hand records (detecting cheating and the like)

 

The ACBL and the WBF have market power of their own.

 

Once you go and create a more competitive land scape, you can start to exercise this.

 

The ACBL can refuse to run events that sell master points that aren't using a standards based approach

The WBF can refuse to broadcast Vugraph using platforms that aren't using a standards based approach

 

Governments all over the world use these precise same set of methods to make purchasing decisions...

 

Its not rocket science

[mycroft]

That I definitely agree with. It's just that it's not in the Laws Commission's purview - although as you say, the people in there are the ones that can start movement on this. So, well, using the one hole in the wall of silence we are given to try to push them to do that is a glittering jewel. And it might even work! And if it does, great!

 

But my guess is that what I expect to have happen here is more likely than what you expect. And that's unfortunate.

 

Unfortunately, you and me being in the 5th age percentile of bridge players means that this is very hard to make clear to people. Even Boye Brogeland-level people. Even Brian Platnick-level people.

 

As far as "governments can", governments also have a lot more purchasing power (and lawsuit power) than the WBF or the ACBL. Witness what has happened when the championships have gone to China. Or to the US, with the fights with the CBP*.

 

I think this is necessary. I hope we can get some traction on some of this. I'd love to have some sort of IETF subcommittee/WBF submission of RFC for bridge APIs. I would love to see an online subcommittee of the BoD or of the WBF that will suggest, implement and make recommendations for the kinds of "follow instructions or else" things you are suggesting. I expect, given the way the 'net works, creation of those standards will have to be made by a committee at least half of whom are members of the industry, with all that entails. Frankly, otherwise we're going to get ObXKCD or the equivalent "this standard is unworkable in practise, so we'll make it work" (in 14 competing ways). The third game, the Microsoft 3E method, I don't expect because frankly there isn't a microsoft-sized player in the game (unless BillG gets himself on the standards committee of course).

 

I love what you're thinking. I don't think it belongs here. I am worried that trying to push a square peg through a round hole will actually discourage people from contemplating this. I hope I'm wrong. Sorry.

 

* Not that, frankly, the CBP is wrong. I'm almost certain that, given the casual method professional bridge ran under at the time (and probably still runs under), there were a huge number of people at the NABCs and the World Championships who were "working illegally in the US". Of course, the US's interesting definitions of "working" are likely to be misunderstood by, say, bridge24.pl 's contract people, and it is possible that it would be impossible to not be. Frankly, of the three times I have had any trouble whatever crossing the U.S. border, two of them were for bridge, because money (and I wasn't making any).