2013 Bridge: Webmaster for District 25

Webmaster, database, email, comm comm, bulletin. Continue reading

Ausra Geaski.

2012 was long before “ACBL Live Results”1 made it easy for bridge players to find out within an hour or so the results of tournaments.Late in that year I saw a notice on the NEBridge.org2 home page that District 25 (i.e., New England) was seeking someone to post on the website the results from its tournaments as the tournaments were running. It asked interested players to contact the president of the New England Bridge Conference (NEBC), Ausra Geaski. I did, and after a short training session from Bob Bertoni, who owned and operated Megaherz Computer, the company that designed and implemented the website, I took over the responsibility.

On the evening of each day of the 2013 Knockout Regional in Cromwell I posted the results. The tournament director sent me a text file for each event. I amalgamated them into one large file text file using a program that had been provided to me. I made an HTML file that had an index at the top with one line linked to the anchor for each event that I had inserted at the top of the appropriate text. It was more basic HTML than rocket science.

Bob thought that I had done a good job in getting the results posted promptly. He told me that someone who was webmaster at one of the other units had tried to do it at a previous tournament and had made a big mess.

Bill Braucher.

I subsequently told Ausra, whom I occasionally saw at the Hartford Bridge Club3 (HBC). that I was willing and able to do more. Shortly thereafter another notice was posted on NEBridge.org. This one said that the district needed a webmaster. Bill Braucher was resigning from the post that he had held for seven years. I let Ausra know that I thought that I could do it. I also told her about my own website, Wavada.org (which was introduced here), but I don’t think that anyone ever checked it out.

One evening at a tournament Bob spent about an hour with me explaining how the district’s website was structured and how the built-in page editor worked. During this session he discovered that I already knew HTML, JavaScript, and CSS.4 He exclaimed, “Oh, you can code! You won’t have any trouble with this.”

A little later we realized that we had something else in common. Bob had attended Boston College on a debate scholarship.5 His coach was Tuna Snider, whom I knew fairly well. In the end Bob offered me the webmaster job at the same salary that Bill had earned.6 I countered with a demand for a 75% raise, and we settled on 50%.

The bridge world was very different then. The district’s website was its primary method of communicating with its members. It did not publish a newsletter, and it had no program for using email. For the most part postcards and flyers were snail-mailed to the clubs. The district relied on their owner/managers to pass the information on to the players. This method was somewhat costly and totally unreliable.

Allan Clamage.

Furthermore, the webmaster was not allowed to post any material unless the website editor, Allan Clamage7, had checked it for style and errors. Allan also taught me about standards that the district had established to govern the decisions. For example, the website never published an obituary or promoted any unit’s tournaments or other events.

Rich DeMartino

The Website Committee (Allan, Bob, District Director and NEBC Treasureer Rich DeMartino, and myself) had a strategy meeting during one of the lunch breaks at every tournament. I don’t remember much that transpired at these meeting, but the other members mostly endorsed my ideas for improving the website. After three or four meetings Rich declared that we seemed to know what we were doing and disbanded the committee. At about the same time Allan began to review what I posted only after the fact. I considered that show of trust as a great compliment. I only embarrassed him a few times, and he never got angry at me.

Harold Feldheim.

My primary goal was to attract more eyeballs to the site. Expert players Harold Feldheim and Jay Stiefel allowed me to post articles that they had written for The Kibitzer, the newsletter of the Connecticut Bridge Association (CBA). I also received material from Frank Hacker, Steve Rzewski, Bill Braucher, and a few others.

I began writing The View from B-Low under my nom de plume, Single Session Swiss8. After each tournament the webpage for The View whimsically recounted my own completely inexpert experiences. Most were true; a few were fish stories. Most of those articles still exist.9 The index to them is available here.


Database Manager: I remember that during one of my conversations with Allan, I exclaimed, “We don’t know who our players are!” He disagreed. He then showed me how he downloaded csv10 files of the entire ACBL roster every month. He then arranged for the ACBL to allow me to do the same. Allan used spreadsheets, but I undertook the major task of designing a MySQL database for use by the district and myself. At the time I wasn’t quite sure what I would do with the information, but I knew that we needed it.

I maintained two copies of the database, one on my local hard drive and one on the Wavada.org website that I had purchased from iPower so that I could share my travel journals with friends, family, and fellow travelers.

The database’s primary table had one record per player. Every table in any database should have a “key”—a field that uniquely identifies the record and cannot be changed. On the player table the key was the seven-digit ACBL number. Using it as the key would be a small problem if I wished to add records for non-ACBL members. Fortunately, if that ever happened, I could assign them a bogus number less than one million. The ACBL never used those numbers.

When a new roster was released I updated both the local and remote copies of the players table using scripts that I wrote in php. At first I did this only for currently active players in New England, but after a few months I decided to expand it to cover all of North America. The script11 that updated the players table also wrote records on a history table that contained each player’s point total at the time that the roster was posted.

One of my jobs as webmaster was to post a list every month of the New England players who had advanced in rank during the month. I decided to maintain a sub-table for these advancements using the file that was sent to me by the ACBL.

I soon realized that what I really wanted to know was who had been attending the tournaments in New England. I knew that the results posted on the district’s website as well as on the websites of the units listed all players in attendance. There were two major difficulties: 1) the ACBL numbers were not on the lists; 2) the formats were not consistent. It was an ugly project, but I eventually came up with scripts that could handle nearly all of the entries on all of the lists.It wasn’t close to perfect, but it was much better than nothing. I convinced myself that it was worth the effort.

I created two sub-tables for attendance: one for players whose ACBL numbers I was able to deduce from the name and town on the list and one for the others. The biggest problem was people with more than one address. The second-biggest problem was people who changed their names. I figured out ways to handle these problems, but they were labor-intensive and introduced the possibility of mistakes. Since I knew from the beginning that the table would not be perfectly accurate, I felt that I could live with this approach.

I also went through the same process for the three NABC tournaments that were run every year. Those files were much larger. It took me a day or more to process each one. I learned the importance of processing them promptly. If even a month elapsed, a lot of addresses changed.


Sending emails: Eventually, I wanted to use the database to send emails promoting the district’s tournaments. The first problem was that the email addresses on the ACBL’s database were incomplete. I reached out to my acquaintances throughout the district and found correct email addresses for at least half of the ones that were missing. I also went through the wooden box containing index cards with member data at the HBC and found a few there. To make sure that my good addresses were not overridden by the ACBL’s blank, confidential, or wrong addresses, I added a field to the player’s table for the source of the email and changed the php script so that it only used the email address on the roster if the previous source was “ACBL”.

<Mrk Aquino.

The second problem was that I had no authority and no budget for anything like this. At about the same time District 25’s president, Mark Aquino, had created a “B’s Needs Committee” to address the reasons that lower-level players (like myself) avoided attending the district’s events when their masterpoints exceeded the 750-point maximum for the “Gold Rush” games. Mark attended some of the meetings. I told the committee about the database that I had created, and I mentioned that I would like to send emails to promote the events sponsored by District 25. I was very pleased when Mark said, “Go for it!”

Ginny Farber.

The great thing about php was that it was—even in those days—thoroughly documented on the Internet. I discovered a way of sending emails through php. My first project was to promote the 2014 Senior Regional/Cape Cod Sectional in Hyannis, MA. The chairperson was one of my partners, Ginny Farber (then Ginny Iannini), who was introduced here.

I sent the emails to all members of District 25 and to anyone who, according to the attendance table on the database, had attended a recent tournament in New England or a national tournament. Realizing that I needed to be careful about being considered a spammer, I stated quite clearly in the email that anyone who wished to be removed from the list should reply to the email with that indication, and I would take care of it. I added an “OK to email?” field to the players table. I never mailed to anyone who had asked to be removed, and I was scrupulous about keeping this designation up to date..

Sarah Widhu.

The emails were very well received, and the attendance at the tournament exceeded expectations. The chairperson of the next event, the Summer Regional in Nashua, NH, was Sarah Widhu. She asked me to promote that event, and I did so. It was also well received, and the attendance was quite good. I was pretty sure that I had this whole process was worthwhile.


Email problems: The php script that I executed on my Wavada.org account was not completely fool-proof. Every so often it would send up to fifteen copies of the email to one person. This was, to put it mildly, quite annoying. I contacted iPower about it. Because I was unable to reproduce the problem for them, they could not solve it. However, it eventually went away. I never understood how this could have happened.

Unfortunately, this problem was completely dwarfed by another issue that raised its ugly head shortly thereafter. There were no errors, but none of the emails went out! Once again I contacted iPower. It took several weeks, and they never told me what they did, but the support team somehow fixed this.

However, after a few successful executions, the problem appeared again. After several weeks of interchanges with iPower support, I was finally informed that my account had been black-listed as a spammer by someone. Therefore, the iPower email server did not send out my emails.

Bob Bertoni.

I used the one phone call that I was allowed to tell Bob Bertoni that I was in email jail, and I asked if he could bail me out. He did some research and eventually negotiated a contract with MailChimp, a company that specialized in sending mass emails for businesses and non-profits, for the purchase of two million “credits” for emails for only $2500. The Executive Committee approved the appropriation. From that point on I never tried to send emails directly from iPower.


MailChimp: My credentials on the district’s MailChimp had a user ID of Guastafeste, which is the Italian term for party-pooper. I taught myself how to use the software to create the lists, which MailChimp called audiences, and the body of the emails, which MailChimp called campaigns. For the first few years the account was allowed to create as many lists and emails as we wanted. I created a new list for each email until MailChimp prohibited me from creating any additional lists.

I generally sent out the first set of emails five weeks before the event. A second set would be sent two weeks later. Each set would consist of a few slightly different emails to groups based on geography, masterpoints, and/or tournament attendance. The content sent to each group would differ, at least a little.

Because I was accustomed to composing my emails in HTML, I always used the “Code your own” template. I always wrote the code for the emails in UltraEdit on my PC and pasted the HTML code into the editing window on MailChimp. The editing program would immediately display the way that the email would look in the window on the left side of the screen. This method allowed me to position and size images exactly. It also allowed for the use of tables and almost anything else that could be done on a webpage. An unanticipated benefit was that if someone who needed to promote something had sent me an email that was already formatted, I could extract the HTML code, tweak it a little, and then paste it into the HTML editing window.

I reported one bug that I found in this process. If I tried to change the color (or anything else) for part of a word, MailChimp inserted a space between the two parts. The example was GOLDmother, which MailChimp changed to GOLD mother (with a space before the “n”). MailChimp refused to fix this obvious problem. By the way, it was not easy to get WordPress. which is the product used for these blogs, to produce this effect either.

The oldest HTML file that I found in the MailChimp folder on my PC was dated July of 2015. I suspect that the first tournament promoted on MailChimp was the Individual Regional in 2015. From that time through 2021 I composed, tested, and sent almost all of the emails promoting District 25’s events. They were amazingly successful, and I became known in New England bridge as “the email guy” rather than “the webmaster”. All told, I sent over one million emails.


Other projects: The database also allowed me to undertake posting on NEBridge.org photos12 of winners of events or strats at regionals (Winners Boards). The first tournament for which I implemented this feature was in the Knockout Regional in Cromwell in 2014. My plan was to ask winners to come to a spot where I could take their pictures with my point-and-shoot Canon. Only one or two complied.

There were several other problems. My friend Bob Derrah volunteered to help me chase winners down, but he had no camera of his own, and he could not figure out how to use mine. Eventually I discovered that the best time was either right after the round or the next day before the start of play. Still, I was lucky if I got photos of half of the winners.

I usually spent the better part of the week after every tournament assembling the five or six webpages of winners’ photos. I sent emails to every winner whose photo I lacked. A very high percentage of them responded, especially among the newer players. For the others I either pieced together substitutes from photos that I previously took or just put up an empty spot for them. The HTML code for the pages themselves was generated by a php script that ran off of a set of tables that was itself generated from a spreadsheet on my PC.

Was it worth the effort? I don’t know. I strongly believed that the regionals should be special, and the winners boards—and a lot of other things—contributed to making them feel that way to a lot of people. Most of those things disappeared during the pandemic. To me the post-pandemic regional tournaments seemed vacuous whereas before they always excited me.


The ACBL had two annual contests that rewarded the players in each of the fifteen ranks that had accumulated the most points. One exclusively counted points won at clubs. The other included all points. I decided in 2017 to create an award for each rank for points won in the events sponsored by District 25. That included the NAP and GNT qualifiers as well as the four regional tournaments and the two hybrid events—the Rainbow Weekend and the Senior Regional/Cape Cod Sectional.

My ability to do this without a great deal of effort was due to the access that I had to LZH files from the ACBL. An ACBL employee named Keith Wells provided me with these files that had all the information on the “masterpoint winners” lists that I had been using to populate the attendance tables, plus they had both the ACBL numbers and the total number of masterpoints that the players had at the time of the event. They also included players who had attended but earned no points. I was trained by Peter Marcus, the district’s chief director, in how to use the ACBLscore program to create csv files from the ones that I received from Keith.

It was pretty easy to keep the fifteen totals in the database. The only real difficulty I encountered was when a player who had participated in events in foreign countries was awarded masterpoints that the ACBL used solely for the purpose of eligibility. After each event I sent out emails to everyone in each of the fifteen masterpoint categories that listed the top fifteen players in that category. At the end of the year I created certificates honoring the winners.

I doubt that this effort by itself induced more than a few people to play, but, like the Winners’ Boards, they helped to contribute to the special atmosphere of regional events.


BridgeFinesse.com, a company in Florida established by Jay Whipple13, somehow got involved with sending emails to all players who had achieved a new rank in the previous month. The emails, which were signed by the appropriate district director encouraged the recipients to respond to the emails with their own ideas. Rich DeMartino was D25’s District Director (DD) when this process began. He asked me to post each comment that he received and to ask each player for whom I did not already have a suitable photo to send one. I did this for Rich and for his successor, Mark Aquino.

When Bob Bertoni became DD, he posted the comments he received on his own website. When he died in 2021, his temporary successor ignored the comments, but when the position was eliminated in favor of a Regional Director, the first one, Mark Aquino, asked me to post the new comments. I retrieved the ones from Bob’s website and posted them on NEBridge.org. I also posted the ones that Mark received.


The disaster: In October 2015 the system that hosted NEBridge.org suffered a catastrophic hardware failure. In the 30+ years that I had spent in the business I occasionally had to face some really bad situations, but I never had to deal with anything like Bob needed to address with this one. I told him that if I were he, I would be looking for a tall tree and a short rope.

NEBridge.org was the least of his problems. We were trying to get people to play our favorite card game at our events. His other customers’ depended on their websites for their very livelihoods.

Nevertheless, Bob got the district’s website back up and running pretty quickly, but most of what I had posted in the first few years was not recoverable, including all of the articles by Frank and Steve. I could have gone back to original sources and salvaged some of it, but all of the new projects that I had started left me no time to attempt more than I did.

Bob temporarily allowed me to use FTP to send files from my PC to the server. That saved me a lot of time. The new version of the website had a slightly different editing program for the pages. I liked it in some ways and hated it in others.


The Communications Committee: At the last meeting of the B’s Needs Committee Bob, who at that point was president of the NEBC, announced that he wanted to form a marketing committee. He then asked me to be its chairman. I wanted to be on the committee, but I had never been the chairman of a committee. I suggested Allan, but Bob was rather insistent. I eventually agreed, but I wanted it to be called the Communications Committee or, better yet, Comm Comm.

Beginning in 2016 a group of us met at tournaments for several years to talk about all aspects of communication—website, emails, tournament Bulletin, posting of results, guest lecturers at tournaments, signage, microphones, etc. I found the meetings useful, but a subsequent president, Jack Mahoney, decided that they were no longer necessary. I think that the biggest problem was that almost everyone on the committee was also on other committees. It also did not help that the only time available for the meetings was at 8:30 a.m. on Saturdays.


The front page of the last Bulletin.

Bulletins: In 2018 I was asked by Lois DeBlois, NEBC president, to begin editing the Bulletin for tournaments. Previously it had been published every day, but Lois wanted to reduce it to one publication that covered the entire tournament. The results that had been printed in the daily editions were by then available online. So, it was not necessary to provide a daily edition. I took on the responsibility of creating it in the new format as well as the setup for online bulletins that were provided by the same service that provided Live Results.

After the pandemic the Executive Committee considered the cost of both bulletins to be excessive. I wrote one last Bulletin for the Optical Regional in Southbridge, MA, in November of 2022.

In November of 2021 I informed the Executive Committee that I intended to resign as webmaster and all of the other positions that I held at the end of 2022. I feared that it would be difficult to find people who were willing and able to keep going many of the things that I started. The story of that process has been recorded here. I did not immediately resign from any of the committees.


1. ACBL stands for American Contract Bridge League, the governing body for competitive bridge in North America. The Live Results program was run by BridgeFinesse.com, a private company in Florida.

2. NEBridge.org is the website of the New England Bridge Conference, the governing body of competitive bridge for District 25 of the ACBL.

3. At the time I was still working at TSI and playing bridge only on Tuesday evenings and weekends. Ausra also played in some of those games, but my skill level was far beneath hers.

4. HTML (hypertext markup language) is the language of browsers. JavaScript is an object-oriented language used for screen design. CSS (cascading style sheets) allow for organization of styles.

5. Bob was eight years younger than I was. He probably graduated from BC in or around 1978. Therefore, he was probably at the party that Don Huprich, Stewart Mandel, and I attended at BC in 1977. That hair-raising adventure was described here. Bob died in 2021. His obituary can be read here.

6. I hate to explain the jokes, but it may not be obvious that neither Bill Braucher nor I was paid anything as webmaster. I did get $100 for each Bulletin. They were always around twenty pages.

7. I later learned that Allan was also a Wolverine, but he was nineteen years older than I was. He was shocked to learn that I had been a math major. He died in 2018. His obituary can be found here.

8. Every tournament that held knockouts also scheduled Single-Session Swiss events. They were team events held in the afternoon for players who had been eliminated in the morning session of the knockout. The event was commonly called “Loser Swiss”.

9. Unfortunately, as of 2024 this statement is not true. Someone deleted or moved almost everything that I posted during the ten years that I managed the website. He/she/they did not notify me of their intentions, and I cannot conceive of any reason to do this other than spite or obsessive concern about disk space. However, I also recalled that the first thing that I did in my first professional programming assignment was equally foolish. I removed all comments from a program created by my predecessor. The details can be read here.

10. A csv (comma-separated values) file was a text file in which each element of data in a record was separated from the others by commas or other delineators.

11. Web-based programs are for some reason called scripts. The ones that I wrote for the district were all in the php (personal home page) program language that could be downloaded at no charge.

12. The website committee was eventually cool to the idea of publishing photos. Some members were worried about showing favoritism towards some players. Rich insisted that the criteria for inclusion be very clear. When I explained that I wanted to include anyone who won any strat or flight in any event and that I would send emails to solicit photos from players whom I could not reach at the tournament, he agreed to the idea.

13. Jay eventually became president of the ACBL. He visited the district’s tournament in Nashua when Mark Aquino was district director.

2005-? Wavada.org

My very own website. Continue reading

In 2003 Sue and I took the “Best of Italy” tour sponsored by Rick Steves. I then wrote a journal compiled from the notes that I had recorded every day. After I was satisfied with the results I assembled them into a pdf file called “How I spent my Italian vacation” that I shared with other tour members and a few other people. That document is posted here.


The programming tools: During this same period IBM discontinued support for the Net.Data product that I had used to write the software for AxN (introduced here), TSI’s online clearinghouse for insertion orders from advertisers to newspapers. Instead, IBM had agreed to offer the php environment that had been developed by Zend1. I had previously learned about php from Ken Owen (Introduced here). He had told me that I could create and run php programs on my Windows computer for free by downloading WAMP, which stands for Windows (operating system) Apache (HTTP server) MySQL (database) php (scripting language). I downloaded it to my PC, set it up, and used it to write a little problem management system for TSI that was actually used for several years.

I had already learned that in order to do programming for the Internet that accessed a database you really need to know five languages: HTML, JavaScript, Cascading Style Sheets (CSS), SQL, and a scripting language to fit all the pieces together. I had books that documented the first three. I soon discovered that books on php and MySQL were not necessary. The syntax of each was thoroughly documented online, and answers to every question that I had were easily found using google. I never had to ask anyone for help.


The first project: Sue and I had planned for another trip to Italy in 2005. This time we invited our long-time friends Tom and Patti Corcoran to accompany us on another Rick Steves tour, “Village Italy”2. I intended to take notes and assemble them into another journal. This time, however, I wanted to do it a little more professionally. I purchased a Cascio point-and-shoot digital camera, mostly using points from one of my credit cards. Since I wanted to allow others in our tour group to be able to enjoy the journal, I needed to build a website. I knew how to do that on an AS/400, but I wanted projects like this to be independent of the business, and I was not about to buy an AS/400 and try to run it from my house. I wanted someone else to manage the site for me.

I did a little research on the Internet. A company named iPower seemed to offer everything that I needed at a fairly reasonable price. Its tools seemed to be well documented, and, especially for the first few years, the technical support was excellent. My first contract with them was signed in July of 2005. I might have had a free month or two before that.

I decided to name the website Wavada.org. Wavada.com was available, but I had no intention of using the website to make money. I wanted to a place to noodle around with Internet programming (my personal computer, which at the time was a laptop) and a separate place where I could show some of the things that I had developed to the world.

I needed some tools on my PC to let me edit the text and images. I had previously downloaded TextPad, a “shareware” (free but with requests for donations) product that was better at editing text than the program that came with Windows. I purchased a copy of UltraEdit, which could be tailored for use with the color-coded and spaced text of php scripts, and Paint Shop Pro, an inexpensive program for editing image files. My plan was to do all of the development on my PC and, once everything was working, upload everything to Wavada.org using either File Transfer Protocol (FTP) or the File Manager program that iPower provided.

The first journal: My first big project used php to create one web page for each day of the 2005 trip. I created a folder named Images and inside of that folder a folder the trip (VI). Inside the trip folders were folders for each day (VI01, VI02, etc.) and one each for the full-page version of the photos3 and the page (VI00) describing the preparations and the travel day. I later wrote a php script that was included at the top of the code for each trip that. This contained all the common scripts for handling layout and navigation as well as the unique elements such as character sets for foreign words.

A separate php script for each page contained the code necessary to display the page. Most of the necessary functions were stored in a file named JournalFunctions.php. A file named JournalSetup.php contained other settings. These were all “required” on every page. Styles were stored in JournalStyle.css and JournalMenuStyle.css.

For the most part the original design worked fairly well. One difficulty that I had no way to anticipate was that the Unix version on the iPower servers was more sensitive to capitalization than the Windows version. I had to be careful with the file names assigned to images.

Twenty years later I find it astounding to report that I completed all of this within a few months. To each member of the tour group I sent an email that invited them to view the finished product on Wavada.org. Quite a few of them looked at a good portion of the journal and responded that they really liked it.


Other projects: I needed to design a home page. I knew that I wanted to have a huge wave as the background so that people would know how to pronounce the name Wavada. I found a photo of with very high density that depicted a monstrous wave better than I could have even imagined. It was on the Internet, but I don’t remember the location.

iPower offered an incredible array of free features that were associated with the website. The two that I made the heaviest use of were email and WordPress. I only needed to create three or four email accounts, but I made good use of them. I made Mike@Wavada.org my primary email account. Much later I created another account called Yoga (the name of my laptop at the time). Email sent to the Mike account was automatically downloaded to Outlook on my desktop. The Yoga account was not. So, I could send or forward emails from Mike to Yoga for activities (such as ZOOM meetings) that required the laptop.

I also set up an account for Sue, but I don’t think that she ever used it.

The other free feature that I employed a lot was WordPress, the software that I used to make this and hundreds of other blog entries. The oldest object in the WordPress section of Wavada.org is from 2010. However, I don’t think that I made much use of the product until March of 2012. That is the date of the oldest images that I uploaded. I might have written a few earlier blog entries that contained no images. An incredible number of these images—and a few other files—were uploaded during the pandemic and the subsequent months.

At first the home page for Wavada.org simply contained links to the few items that I wanted to allow the public to see. I changed the format dramatically when I discovered a widget that was available in google’s jQuery library. This allowed me to present the table of contents in an attractive tabbed manner.

I wrote a large number of programs concerning the game of bridge (introduced here) for my own use. For a while I maintained a complicated set of programs that I wrote to keep a detailed record of the bidding agreements with my partners. Eventually I decided that this was too much work (as of 2023 I had played with 141 different partners). I also created online programs for displaying an article index for topics covered in the Bridge Bulletin (posted here) and for providing game plans for challenging declarer problems (posted here).

I figured out how to parse the pdf files for hand records from bridge games. I created a database of these hands so that I could establish probabilities to associate with certain bridge situations. For example, I determined that Losing Trick Count4 was more accurate at predicting the number of available tricks at game level or lower than point count that has been modified as suggested by Marty Bergen in his Slam Bidding Made Easier book. However, the opposite was true for higher contracts.

I started to attend Wednesday evening games at the Simsbury Bridge Club in 2004. At some point I created a webpage for the club. It was still in use in 2023. The link is here.

As an adjunct to my job as webmaster I created a database of bridge players throughout North America on Wavada.org for District 25 of the American Contract Bridge League (ACBL). That story has been chronicled here.

I adapted the code for the travel journals to create online pages for each chapter of the book that I wrote on papal history entitled Stupid Pope Tricks. The book is posted here. The story of the Papacy Project that led to its creation is chronicled here. I also posted in the same format Ben 9, my historical first-person novel about Pope Benedict IX, here.


1. In 2023 this product is still offered for the i5 operating system. Zend has been purchased by other companies a few times.

2. The journal for the 2005 tour is posted here.

3. I used the same file names that Cascio provided with the letter b at the end. For later journals I dispensed with the uploading of the smaller versions of the photos and instead uploaded a full-page version of each image and used HTML to specify the size displayed in the journal. I also changed the naming of the images in the daily folder to be meaningful.

4. Losing Trick Count is explained here and elsewhere on the Internet and in print.