Page 1 of 1
Announce bids two at a time to avoid ascribing delays So you don't know if P or Opp delayed
#1
Posted 2024-October-16, 12:10
You can often get hints from delays by P or Opp.
If BBO showed bids two at time, you would not know who delayed.
Yes, TDs would get calls like "NE slow" vs "N slow", but should be able to see who is the problem
This would be fairer to all players.
If BBO showed bids two at time, you would not know who delayed.
Yes, TDs would get calls like "NE slow" vs "N slow", but should be able to see who is the problem
This would be fairer to all players.
#2
Posted 2024-October-16, 15:10
0 carbon, on 2024-October-16, 12:10, said:
You can often get hints from delays by P or Opp.
If BBO showed bids two at time, you would not know who delayed.
Yes, TDs would get calls like "NE slow" vs "N slow", but should be able to see who is the problem
This would be fairer to all players.
If BBO showed bids two at time, you would not know who delayed.
Yes, TDs would get calls like "NE slow" vs "N slow", but should be able to see who is the problem
This would be fairer to all players.
It's better than nothing (like f2f behind screens), but why stop there?
You can also show three calls at a time, and introduce delay when necessary too.
There is no technical problem in any of this, it's only a matter of willpower and regulations.
#3
Posted 2024-October-16, 16:11
This suggestion has been made from time to time for many years.
We just don't think this is enough of a problem to justify the change. There are so many non-bridge reasons for online delays, it's hard to take inferences from them.
We just don't think this is enough of a problem to justify the change. There are so many non-bridge reasons for online delays, it's hard to take inferences from them.
#4
Posted 2024-October-16, 16:25
barmar, on 2024-October-16, 16:11, said:
This suggestion has been made from time to time for many years.
We just don't think this is enough of a problem to justify the change. There are so many non-bridge reasons for online delays, it's hard to take inferences from them.
We just don't think this is enough of a problem to justify the change. There are so many non-bridge reasons for online delays, it's hard to take inferences from them.
I fully understand that as a commercial enterprise you do not feel obliged to boldly split infinitives where the WBF does not dare.
But to suggest that it is difficult to take inferences from the tempo of a trusted partner online is ingenuous, if not disingenuous.
Electronic play could easily limit this obvious opportunity of flaunting the Laws.
Kudos to the first online platform that actually does so.
#5
Posted Yesterday, 01:28
slow connection distracted not realizing its your bid you take interferace from slow play at your own risk
#6
Posted Yesterday, 02:28
If your user name would flash when it is your turn to bid or play it would help
#7
Posted Yesterday, 02:53
I think it might be ok to offer this option for serious competition like the ALT tourneys and national selection events, but for 99% of BBO play I think the cure is worse than the disease.
It is useful that everyone can know who it is that has a connection problem or may have gone for a dog walk:
- when my LHO is tanking, I know I can go make myself a drink because it will be a while before it is my turn
- when calling the TD because of a delay, it is good that I can indicate in the TD call who is tanking, to ease the work of the TD. And no, this is not trivial to automate, because sometimes a player is not tanking but waiting for a response to a query.
- when a person is tanking an opp can try to wake them up with a PM, or even get someone to give them a phone call
- when taking player notes, I can write if someone is fast or slow so I avoid inviting slow players to a speedball.
It is useful that everyone can know who it is that has a connection problem or may have gone for a dog walk:
- when my LHO is tanking, I know I can go make myself a drink because it will be a while before it is my turn
- when calling the TD because of a delay, it is good that I can indicate in the TD call who is tanking, to ease the work of the TD. And no, this is not trivial to automate, because sometimes a player is not tanking but waiting for a response to a query.
- when a person is tanking an opp can try to wake them up with a PM, or even get someone to give them a phone call
- when taking player notes, I can write if someone is fast or slow so I avoid inviting slow players to a speedball.
The world would be such a happy place, if only everyone played Acol :) --- TramTicket
#8
Posted Yesterday, 17:45
#9
Posted Today, 11:05
helene_t, on 2024-October-17, 02:53, said:
It is useful that everyone can know who it is that has a connection problem or may have gone for a dog walk:
- when my LHO is tanking, I know I can go make myself a drink because it will be a while before it is my turn
- when calling the TD because of a delay, it is good that I can indicate in the TD call who is tanking, to ease the work of the TD. And no, this is not trivial to automate, because sometimes a player is not tanking but waiting for a response to a query.
- when a person is tanking an opp can try to wake them up with a PM, or even get someone to give them a phone call
- when taking player notes, I can write if someone is fast or slow so I avoid inviting slow players to a speedball.
- when my LHO is tanking, I know I can go make myself a drink because it will be a while before it is my turn
- when calling the TD because of a delay, it is good that I can indicate in the TD call who is tanking, to ease the work of the TD. And no, this is not trivial to automate, because sometimes a player is not tanking but waiting for a response to a query.
- when a person is tanking an opp can try to wake them up with a PM, or even get someone to give them a phone call
- when taking player notes, I can write if someone is fast or slow so I avoid inviting slow players to a speedball.
I am not much persuaded by any of these points, IMO they could easily be handled with small improvements to the software:
- you want to make yourself a drink? Go right ahead, just press the "BRB" button first, your status will be apparent to TD (with a warning after 30s or whatever)
- there is a delay? The system knows and should flag it to TD, it should not be your job as opponent
- player X is having a connection problem? BBO already has a keep-alive mechanism (although it seems flawed at times) and the TD is advised by the system (there is also automatic robot substitution available)
- player Y was actually on the ball but waiting for a response to a query? The system advise the TD when no response is forthcoming (and do a much better job of handling follow-up queries)
- as TD you should have historical and current tempo statistics for each player and if organizing a speedball you should be able to set a filter for minimum speed.
Page 1 of 1